Questions people actually ask.

Because the source did not say. If a video says “a little oil”, the honest answer is “a little oil” — turning that into 15 ml would be RecipeMirror inventing a fact and putting it in the cook’s hands as though the person in the video had said it. Every other recipe app fills that gap. Not filling it is the product.

You are never blocked by it. Cook straight away and judge it at the pan, which is what you would do anyway — and what you used is remembered for next time.

Because a long video usually shows more and says less. A short recipe video states quantities because it has to; an hour of somebody cooking in their own kitchen is full of “this much” and a hand gesture. RecipeMirror reports what was said, so a longer video can genuinely contain fewer stated amounts.

Shorter, more explicit videos give stronger guides. That is a real limitation and not a bug we are hiding.

Correct it. Your correction is kept as yours, sits above the reading, and is never overwritten by a later pass. If RecipeMirror reads the source again and disagrees with you, it shows you the difference and asks — it does not quietly replace what you established.

Only your account. It is not public, not searchable, and not shown to other cooks. Guides built from a private family recording have no share button — that consent was for your household only, not for sending the guide on.

Before the microphone opens you confirm that everyone being recorded is happy for RecipeMirror to capture the recipe. That confirmation is kept with the recording for our records; having permission stays your responsibility.

To read it, RecipeMirror sends it to Google’s Gemini. That is a real transfer to a third party and we name it rather than calling it “processing”. Everyone we send data to is listed on what we keep.

Only if you want us to. When you bring one in you choose: keep it so the guide can be re-read later, or delete our copy as soon as the reading is done. If you chose delete, the file goes and the screen tells you it has gone.

A photograph of a recipe page is never stored at all — it is read inside the request and dropped.

Kitchen Profile, or email privacy@recipemirror.com. Full detail on delete your data, including the one thing that survives and why.

Preparing is RecipeMirror watching or reading a source and building a guide from it. That is the part that costs real money — a model call against a video — so it is metered: 15 preparations a month, and the count resets each calendar month rather than being a lifetime allowance.

Saving a link costs nothing. Cooking costs nothing. Only the reading is counted.

Yes. Cook it as many times as you like. A guide, once built, is yours — reopening it, scaling it, shopping for it and cooking it all cost nothing.

No. A photo RecipeMirror cannot read releases the preparation. “Try again in better light” and “that cost you one of your recipes” should never appear on the same screen.

Nothing today. Paid plans for people who prepare lots of dishes are coming, and they will be announced before anyone is charged. Cooking a dish you already have, your own recipes and family recordings stay free. See pricing.

RecipeMirror cannot read those videos from a URL — the platforms do not make the video available to read, and downloading it would mean re-hosting somebody’s work, which we do not do. The link is saved so you do not lose it. If you have the clip or a voice note on your phone, use Upload video/audio, or add the recipe details yourself.

RecipeMirror reads the structured recipe data most cooking sites publish for search engines. A page can look like a recipe to a person and carry none of it. Two different messages exist on purpose: “we opened the page and found no recipe data” and “we could not open the page”. If you see the first on a site you know publishes recipes, tell us — that is a bug worth hearing about.

Yes. Photograph a cookbook page or recipe card, choose a PDF (up to 8 MB, every page is read), or type or paste the recipe. Headings like “Step 1” are tidied away, and the result is the same step-by-step guide as a video.

Yes. Turn on hands-free in cook mode and say “next”, “back”, “go to step 10”, “what was the previous step?”, “how much salt?” or “start a timer for 5 minutes”. Your browser needs microphone permission. Each step can also be read aloud.

Yes. On your shopping list, send a link. Whoever opens it can tick items without an account, and their ticks appear on your list within a few seconds. You can turn the link off at any time.

It reads the pack’s figures from Open Food Facts and applies the UK traffic-light rules for fat, saturates, sugars and salt — the same answer every time, with the reasons and what a better pick looks like. Being ultra-processed or having additives is shown for context but does not decide the verdict. Always check the pack if anyone has an allergy.

Not without knowing the density, and it will not guess. A cup of flour and a cup of honey are not the same weight, and a conversion that ignores that is a wrong number wearing a right one’s clothes. Conversions within a dimension — grams to kilograms, millilitres to litres — work.

Not in the app stores yet. The web app works on any phone today — in your browser, tap Add to Home screen to use it like an app. An Android app is in testing and iPhone follows; join the list on the home page for one email when they launch.

No, and it says so on the page. It describes what the system actually does, written by the people who built it. That is not the same as legal review and we will not imply it is.

Email hello@recipemirror.com, or use the contact form. A person reads it. We do not publish a response-time commitment because we will not state one we cannot keep.