Something not working? Start here

RecipeFix is made by one person. There is no ticket queue and no bot · mail goes to a real inbox and gets a real answer.

Email

hello@recipefix.app · the fastest route for anything below, and the right one for anything not below. If a recipe came out wrong, sending the link or the text you pasted along with the diet you chose makes it far quicker to reproduce.

Common questions

RecipeFix couldn't read a recipe link

Plenty of recipe sites decline requests that do not come from a person's own browser — they return an error to us, sit behind anti-bot protection, or build the recipe with JavaScript that a plain fetch never runs. When that happens RecipeFix offers you a way through rather than stopping: paste the recipe text, take a photo of it, or use the browser extension or the iPhone share sheet, which read the page you are already looking at. Nothing is bypassed; those simply use the access you already have.

How the extension reads a page →

The adaptation got something wrong

Send us the recipe and the diet you chose. Ingredient swaps are checked against the diet before you see them and a failed check is retried, but the instruction rewriting is judgement, and judgement is occasionally wrong. Concrete examples are what improve it — they go straight into the rules the model follows.

The browser extension isn't showing a button

The button only appears when the page really is a recipe — it looks for the recipe data a publisher has marked up, so an index page, an article about food, or a recipe printed as a picture will not trigger it. On a page it cannot read, open the RecipeFix extension from the toolbar and it will hand the link over instead, or paste the text into the site directly.

Share → RecipeFix on iPhone didn't bring the recipe over

The share extension reads the recipe from the page in Safari and opens it in the app. If it could not find one it passes the link instead, and the app fetches it the usual way. If nothing opens at all, force-quit RecipeFix and relaunch it once — the app caches its own code, and a stale copy is the usual culprit.

RecipeFix for iPhone →

Billing, refunds and cancelling

Subscriptions bought on the website are handled by Stripe and can be cancelled from your account settings at any time; you keep Pro until the period you have paid for ends. Subscriptions bought inside the iPhone app are handled by Apple, so cancellations and refunds go through Apple — Settings → your name → Subscriptions. We cannot cancel or refund an Apple subscription on your behalf, which is Apple's rule rather than ours.

What Free and Pro include →

What happens to the recipes I paste in

They are sent to the AI model that rewrites them, and saved to your cookbook only if you choose to save one. The browser extension and the iPhone share sheet keep the recipe on your device until you press adapt — it travels in the part of a web address that browsers do not transmit. Recipe text is never recorded in analytics.

Privacy policy →

Your data, and getting rid of it

You can delete your account and everything attached to it from your account settings. Marketing email has a one-click unsubscribe in every message, and you can change the preference at any time in the same place · no account needed to unsubscribe.

Related: Privacy policy · Terms · Browser extension