A photo is evidence, not a recipe
You photographed a dish at a restaurant, or someone sent you a picture of what their grandmother made, and now you want to cook it. This is one of the genuinely useful things image models do — and one of the easiest to get wrong, because a confident-sounding ingredient list can hide how much the photo could not show.
It helps to be precise about what is actually visible in a picture of finished food.
A photo can usually show: the general category of dish, the visible components and roughly how they are cut, the cooking method suggested by colour and surface, the approximate proportions on the plate, garnishes, and how it was served.
A photo cannot show: anything dissolved or absorbed, the seasoning, the fat used, marinating or resting time, the cooking temperature, the order of operations, allergens, or any of the quantities. Salt is invisible. So is the stock, the acid, the sugar, and every technique that happened before the plate.
That gap is where the actual cooking lives. A tool that reads the photo can give you a strong starting draft; you supply the rest.
Take a photo that is worth reading
If you know you want to cook the dish later, thirty seconds of care at the table doubles what any tool — or any experienced cook — can get from the image.
- Shoot in the best light available, and avoid the phone's flash. Colour is one of the main signals for cooking method, and flash destroys it.
- Get one angle from directly above for the composition and proportions, and one from about 30 degrees so height, sauce thickness, and layers are visible.
- Photograph a cut or spooned portion, not just the intact plate. What is inside is far more informative than what is on top.
- Include something for scale — a fork, a spoon, the rim of the plate. Portion size is one of the hardest things to infer.
- Photograph the menu description or any label if there is one. A single line of text will resolve more ambiguity than five more photos.
If the dish arrives and you take one dim photo from the side, you will get a plausible-looking recipe for a dish that is not quite the one you ate.
Read the draft critically, in a fixed order
When you have a generated recipe — from CookFeed's photo-to-recipe feature or any other tool — resist the urge to start cooking. Go through it in this order, because errors early in the list invalidate everything after them.
- Is the dish identification plausible? If the tool named a specific regional dish, does the rest of the recipe match that dish's actual method, or has it produced a generic version wearing the name? This is the most common failure and the easiest to spot.
- Are the quantities internally consistent? Check the ratios you know: liquid to grain, fat to flour, acid to oil in a dressing. These are the numbers most often wrong, because they were never visible.
- Does the method produce the texture in the photo? A sauce that clings was probably reduced or thickened. A crust means dry heat, high heat, or both. If the instructions do not explain the visible result, a step is missing.
- Are the cooking times and temperatures sensible for your equipment? Times assume a pan, an oven, and a heat level the tool cannot see.
- What is missing entirely? Salt levels, resting time, and the seasoning adjustments at the end are frequently thin or absent, and they are usually the difference between fine and good.
The things you must never take on trust
Some categories are not a matter of the recipe being a bit off. Check these against a reliable source every time, regardless of how confident the output looks.
- Allergens. A photo cannot reveal nuts in a sauce, dairy in a stock, gluten in a thickener, or cross-contamination in a kitchen. If anyone eating has an allergy, the photo is not evidence of anything.
- Cooking temperatures for meat, poultry, fish, and eggs. Use your local food-safety guidance and a thermometer, not a generated number.
- Preserving, canning, curing, and fermenting. These depend on acidity, salt concentration, and time in ways that are not negotiable. Do not adapt a preservation recipe from a photograph.
- Storage and reheating claims. Follow local guidance rather than a generated estimate.
- Anything for someone with a medical dietary requirement. Verify against product labels and qualified advice.
This is not a caveat about one product. It is what "generated from an image" structurally means, and how CookFeed uses AI sets out the same limits for every AI feature in the app.
Cook it once as written, then fix it
Make the draft roughly as given the first time, but taste at every stage and keep a pen nearby. Note what was under-seasoned, what cooked faster than stated, and what you would change.
The second version is the real recipe. Almost nobody gets a photograph-derived dish right on the first attempt, and that is not a failure of the tool — it is how cooking from any unfamiliar source works. The advantage of starting from a draft is that you are editing something instead of staring at a blank page.
Save the corrected version, not the original. A recipe you have cooked, adjusted, and annotated is worth keeping; a generated draft you never made is clutter. Our guide on organising your recipes so you actually cook them covers what to keep and what to throw away.
When a photo is the wrong starting point
Two situations where you should skip this approach entirely.
If the dish is well known and well documented, look it up instead. A photo-derived draft of a classic dish will usually be worse than a good written recipe for it, because the written version encodes the technique the photo cannot show.
If what you actually want is dinner tonight from the food in your kitchen, the photo is a detour. Start from the ingredients instead — that is a different and usually faster route, covered in cooking with what you already have.
Photo-to-recipe is at its best in the specific case it was built for: a dish you experienced, cannot look up, and want a credible starting point for. Used that way, and reviewed properly, it turns a picture on your phone into something you can put on a table.