
The short version: you can absolutely use AI food photography for restaurants to turn a rushed phone snapshot into a clean, appetizing menu photo — fixing the light, swapping a cluttered background, straightening the crop to fit a delivery app. What you should not do is generate a dish that doesn't exist, add toppings you don't serve, or plate a portion the kitchen never sends out. The first is better photography. The second is false advertising, and on a delivery platform it comes back to you as refund disputes, rejected listings, and one-star reviews.
This guide is about getting menu photos without a photographer the honest way. We'll draw a clear line between editing and fabricating, walk through what the major delivery platforms generally expect, and give you a step-by-step workflow for turning a real photo of your real food into something that's ready to upload — without crossing into pictures that get you in trouble.
There are two very different things hiding under the phrase "AI food photography," and confusing them is where most of the trouble starts.
The first is enhancement: you cook the dish, you photograph it, and AI helps you clean up the image. It corrects color that came out yellow under kitchen lights, replaces a messy stainless-steel counter with a calm background, evens out harsh shadows, and crops the frame to the aspect ratio a platform wants. Nothing about the food itself changes — you're doing what a food stylist and a retoucher would do, just faster and without a studio.
The second is fabrication: you type "a gourmet double cheeseburger with melting cheddar and crisp lettuce" into a text-to-image tool and it invents a burger from scratch. It looks incredible. It is also not your burger, not your bun, not your portion, and possibly not even a real food item at all.
This guide is entirely about the first kind. Oxava is built as an editor, not a fabricator — you upload a photo of the food you actually serve, and it brings the lighting, background, and framing up to platform standard. That distinction isn't just ethics for its own sake. It's what keeps your listings live, your refund rate low, and your reviews honest.
On a delivery app, the photo is the storefront. Nobody smells the kitchen or sees the steam. A customer scrolling Uber Eats or Yemeksepeti at 8 p.m. decides in a second or two, and that decision is driven almost entirely by the thumbnail. A dish photographed under flat fluorescent light on a wet counter reads as "skip." The same dish, lit well and framed cleanly, reads as "order."
That's the upside — and it's real. Better photos genuinely lift orders, which is why platforms push restaurants to add images to every item.
But delivery adds a second pressure that dine-in never had: the customer opens the box later, alone, and compares it directly to the picture that sold it. In a restaurant, the plating in the photo is aspirational and everyone knows it. In a delivery bag, the photo becomes a promise. If the gap is too wide, you don't just get a disappointed diner — you get a refund request, a chargeback, and a public review that mentions "nothing like the picture." That single dynamic is why the honesty line below matters more for delivery than for almost any other kind of product photography.
This is the spine of the whole topic, so it's worth being precise. Here's a simple test that settles almost every case:
If the customer opened the box, would they recognize this as the same dish?
If yes, you're enhancing. If no, you've crossed into fabrication. Let's make it concrete.
These edits change the image, not the food. They're the everyday work of food photography and they're completely legitimate:
These change what the customer believes they're buying:
It isn't a hypothetical risk. Delivery customers document mismatches obsessively — side-by-side "expectation vs. reality" photos are a genre of their own on social media, and a restaurant that trends for the wrong reason rarely recovers the listing's rating. Beyond the reviews, an inflated photo is a direct engine for refund disputes: the customer paid for the picture, got something smaller, and the platform sides with them. And in markets like the US, dressing up food you don't serve runs straight into truth-in-advertising rules — the FTC treats a materially misleading product image as deceptive advertising, and "it's just marketing" is not a defense that holds up.
Enhancement carries none of that risk, because the thing in the bag still matches the thing in the photo. That's the whole game.
Every platform has its own image guidelines, and — importantly — they change often and differ by country. Treat everything below as general orientation, not a spec sheet. Always confirm the current numbers in the platform's own partner or merchant dashboard before you shoot, because that's the only source that won't go stale.
| Platform | What they typically ask for | The underlying principle |
|---|---|---|
| Uber Eats | High-resolution image, commonly a squarish/landscape crop, one dish per photo, no text or logos baked in | Show the real item clearly, filling the frame |
| DoorDash | Sharp, well-lit photo, typically one item centered, minimum resolution enforced on upload | The dish is the subject; no collages or promos |
| Yemeksepeti / Getir | One product per image, real portion, clean and legible framing | The photo represents the actual serving |
Notice that the rules differ but the principles are identical everywhere:
If you build to those three principles, you'll pass almost any platform's review regardless of the exact pixel dimensions — and the AI enhancement steps below are all aimed at meeting them.
Here's the whole workflow, from the kitchen to the upload button.
AI enhancement makes a good photo great; it can't invent detail that was never captured. Give it something honest to work with:
Upload that photo to an editor and bring it up to standard. In Oxava you'd:
Throughout, the food itself stays exactly as photographed. You're adjusting the picture, not the plate.
Before anything goes live, run every image past these five questions:
If all five pass, upload it. If any fail, fix the food or reshoot — don't fix it in the edit.
A few patterns show up again and again:
If you're a home baker, a one-person cloud kitchen, or selling on Instagram and WhatsApp, you feel the photographer gap most sharply — there's no marketing budget and no studio, but the photo still decides the sale.
The good news is the workflow scales all the way down. One honest daylight photo of your actual cake, taken on a phone by a window, is enough raw material. AI enhancement handles the rest: a clean background instead of your kitchen, corrected lighting, and a crop that fits wherever you're posting. You get menu photos without a photographer and without a studio.
The honesty line matters even more at this scale, because your customers are often neighbors and repeat buyers who'll notice instantly if the box doesn't match the post. Photograph the real thing, enhance the image, and let the accuracy build the trust that turns first orders into regulars. If you also sell physical goods alongside food — jars, mixes, packaged treats — the same principles carry over to a proper storefront, which our Shopify product photography workflow walks through end to end.
Practically and legally, yes — it has to be recognizably the same dish. Menu photos have always been somewhat aspirational (better lighting, tidier plating), and that's fine. What's not fine is a photo showing ingredients or a portion the customer won't receive. On delivery apps especially, a large gap drives refund disputes and, in some markets, counts as deceptive advertising.
Editing a real photo of your real dish — lighting, background, crop — is standard practice and perfectly legal. What crosses the line is using AI to fabricate food you don't serve or to misrepresent what's in the box. Follow the truth-in-advertising principle (the image must not materially mislead) and you're on safe ground.
It can, technically — but you shouldn't for an actual menu. A dish generated from a text prompt isn't your food, your portion, or your recipe, so it misleads customers and invites disputes. Always start from a real photo of the actual dish and use AI to enhance it, not invent it.
Use natural daylight near a window, plate the dish exactly as you serve it, shoot straight-on or at a 45-degree angle close enough to fill the frame, and keep it sharp and in focus. A clear, honest photo gives the editor good raw material; enhancement improves the picture but can't recover detail that wasn't captured.
It varies by platform and country and changes over time, so the honest answer is: check the current spec in your platform's partner or merchant dashboard before you shoot. As a rule of thumb, provide a high-resolution image with one dish filling the frame, no text or logos, in the aspect ratio the platform requests — that satisfies most guidelines even as the exact numbers shift.
If you've been putting off menu photos because you don't have a photographer, this is the workflow: photograph your real dish once, in daylight, and let Oxava handle the lighting, background, and framing that make it platform-ready. It's an editor, not a fabricator — you upload the food you actually serve, and it brings the image up to standard without ever changing what's on the plate.
Start with one dish. Snap an honest photo, open it in the Oxava studio, clean up the light and background, reframe it to your delivery app's ratio, and run it past the five-question honesty check before you upload. Once you've done one, the rest of your menu follows the same loop — and every photo you publish is one your customers will still recognize when they open the box.
Be the first to hear about new techniques, model updates and ideas on AI generation.