The RecipeFix browser extension puts one button on recipe pages. Click it and the recipe comes across to RecipeFix, where you choose the diet and the serving count and get the whole thing rewritten · ingredients and cooking steps both.
When you paste a link, our server has to fetch that page itself, and plenty of recipe sites decline automated requests, sit behind anti-bot protection, or build the recipe with JavaScript a plain fetch never runs. The extension runs in YOUR browser, on the page as you already see it · reading what is on your screen, using access you already have, and only when you click. Nothing is bypassed and nothing is broken into.
Open a recipe anywhere. Click “Adapt with RecipeFix”. Choose your diet and serving count · nothing is pre-selected for you. Cook it, with rewritten steps and corrected measurements.
Nothing leaves your browser until you click. It sends the recipe · title, ingredients, instructions, servings, times · not the page: navigation, comments, reviews, adverts and related posts are excluded. It makes no network requests of its own, keeps no storage, uses no cookies, and asks for one permission that applies only to the tab you clicked on. Recipe text is never recorded in analytics.
No. RecipeFix works entirely on the website: paste a recipe link, or the recipe text, and it adapts the same way. The extension saves you a copy-and-paste, and it rescues the minority of recipes our server cannot fetch. It is a convenience and a fallback, not a requirement.
When you paste a link, our server has to fetch that page itself, and some sites decline automated requests, sit behind anti-bot protection, or build the recipe with JavaScript a plain fetch never runs. The extension runs inside your own browser on the page as you already see it, so it reads what is on your screen using access you already have. Nothing is bypassed or broken into.
No. Until you click the button, it has only checked whether the page publishes recipe structured data, in order to decide whether to show the button at all. The recipe is read only when you click, and nothing is read on pages you never click on. There is no background scanning and no crawling.
No. It sends the recipe: title, ingredients, instructions, servings and times. Navigation, comments, reviews, related posts, adverts, sidebars and footers are explicitly excluded. If it cannot read the recipe confidently it sends only the page's address and RecipeFix fetches it the ordinary way.
It travels to RecipeFix in the part of the web address browsers never transmit to a server, so it stays in your browser until you press adapt yourself — the same moment as if you had pasted it in by hand. Recipe text is never recorded in analytics; we measure which site it came from and which reading method worked, never the recipe itself.
Chrome and Edge first, then Firefox. Any Chromium browser — Brave, Opera, Arc, Vivaldi — installs the Chrome version. Browser extensions are a desktop feature, so on a phone use recipefix.app directly; it does the same job.
No. The extension is free and works with the free RecipeFix plan, which includes five recipe adaptations a month with no account needed. It does not change what your plan includes.
RecipeFix works without it · paste a recipe link →
Related: Gluten-Free Recipe Converter · Is This Recipe Gluten Free? · Recipe Multiplier & Divider