Menu Photo Workflow for Restaurants: 8 Steps

Most restaurants don't have a photo problem. They have a process problem.

The kitchen that always has current, on-brand images ready for every channel isn't the one with a better camera or a member of staff with "a good eye." It's the one that treats menu photography as a repeatable routine — the same few steps, in the same order, that anyone on the team can run.

This is that routine: eight steps from plating a dish to publishing the final image, who should own each part, the exact 2026 image specs for the main delivery apps, and the questions that come up the first time a restaurant puts it in place.

Why a system beats a good eye

When photography lives in one person's head, it breaks the week that person is on holiday. Three things go wrong without a defined routine:

• Nothing gets shot when the "photo person" is out. New dishes go live with no image, or a bad one.
• The set drifts. After a few weeks of different people shooting in different light, the menu stops looking like one restaurant.
• Files get lost. "That pasta photo" is somewhere in a WhatsApp thread, at the wrong resolution, with no version for the delivery app.

A workflow fixes all three by making each step small, ordered, and assignable. The goal isn't to make anyone a photographer — it's to make the photographer unnecessary.

Which channel needs which format (2026)

Before you shoot anything, know what you're shooting for. Every channel crops and compresses differently, and delivery apps reject images that don't fit. These are each platform's current published requirements for menu-item images:

The practical takeaway: shoot wide and high-resolution once, then crop down to each channel. You can crop a 3:2 landscape into a 1:1 square; you cannot do the reverse without losing the plate.

Step 1 — Plate the dish for the camera

No amount of editing rescues a poorly plated dish. Before the phone comes out:

• Wipe the rim. A smear of sauce or a drip on the edge ruins the frame.
• Place the garnish on purpose, not by reflex.
• Sauces should look glossy and fresh, not dried or dull.
• Cold dishes: no unwanted condensation. Hot dishes with elements that collapse — ice cream, foams, anything fried — get shot first and eaten second.
• Check the plate and the surface under it. A chip in the crockery pulls the eye as much as a plating mistake.

Step 2 — Set up the phone

• Main lens, 1x. Turn off digital zoom — it softens everything.
• HDR on when the light on the dish and the background differ.
• Highest resolution available. You will crop into this later.
• No flash. It flattens the food and throws hard reflections onto sauces and glassware.
• Grid on to keep the horizon level and compose on the thirds.

Step 3 — Angle and framing

Three angles cover almost every dish:

• Overhead (90°): salads, bowls, pizzas, paellas — anything where the ingredients read from the top.
• 45° (the table angle): the default. It looks the way food looks when you sit down to eat it.
• Side on (0°): burgers, sandwiches, layered desserts — anything with height and internal structure.

Leave breathing room around the plate. A delivery app will crop in; Instagram Stories will crop the opposite way. Tight framing removes your options.

Step 4 — Shoot a set, not a photo

• Take at least five frames of each dish from the chosen angle.
• Shift position slightly between frames — a little closer, a little back.
• Brace your elbow on the table or use a small tripod.
• Use the timer if no one is free to hold the phone.

Five frames is a cheap insurance policy. One blurry or badly-timed frame and you would otherwise re-plate the whole dish.

Step 5 — Transfer and name the files

This is the step teams skip, and the one that costs the most later. Decide a folder structure on day one and never save a processed photo over an original:

/FoodyFocus-Images/
  /Originals/
    /2026-09-04_Carbonara/
    /2026-09-04_House-salad/
  /Processed/
    /Instagram/
    /Delivery/
    /Web/
    /Print/

Name every folder with the date and the dish. Future-you, looking for one photo in a hurry, will be grateful.

Step 6 — Process to a house look

1. Upload the best original frame for each dish.
2. Apply your restaurant's brand profile — the same colour and light treatment every time. This is what keeps 40 photos looking like one menu.
3. Review the result. Adjust brightness and contrast only if the dish reads wrong.
4. Export the versions you need (Step 8).

Whether you edit by hand, with presets, or with an AI tool like FoodyFocus, the rule is the same: one consistent treatment, applied to every dish, so the set holds together.

Step 7 — Quality control

Check every image on a phone screen before it goes live — that is where customers will see it:

• Are the colours true to the real dish?
• Is anything important cut off at the frame edge?
• Is it sharp at full size?
• Does it sit next to your other menu photos without looking out of place?

Step 8 — Distribute by channel

With processed versions sorted into folders, publishing is a two-minute job:

• 1080 × 1080 → Instagram feed.
• 1080 × 1920 → Stories and Reels.
• The right crop per app (see the table above) → Uber Eats, Deliveroo, Just Eat, Glovo, DoorDash.
• 300 DPI → whoever lays out the printed menu.
• WebP → the website.

Who on the team owns what

In a small restaurant this usually lands on the owner or floor manager — which works until it doesn't. Split it instead:

• Capture: anyone on the kitchen or floor team who has had five minutes of instruction on angle and light. Steps 1–4.
• Processing and QC: one person, or one fixed process. This is what protects the house look. Steps 6–7.
• Distribution: partly automatable if your editing tool exports per-channel sizes directly. Step 8.
• Periodic review: once a month, someone checks that the published set still looks coherent — especially after several people have taken turns shooting.

Splitting it this way means a holiday, a busy shift or a staff change never stops the photos.

How long this actually takes

Once the routine is in place, a new dish takes roughly 10–15 minutes end to end — a few minutes to plate and shoot, a few to process, a couple to file and publish. A restaurant refreshing five dishes a week spends about an hour, absorbed into a normal shift rather than set aside as a project. A single professional shoot covering the same ground runs €300–€1,500.

Mistakes that drag it out

• Skipping Step 5. Saves two minutes now, costs twenty the next time someone hunts for a file.
• One frame per dish. If it's soft, you re-plate and re-shoot from scratch.
• Processing days later. You forget which file was which dish and which channel it was meant for.
• Deciding export sizes on the fly. Fix the list once (Step 8) and Step 8 stops being a decision.

Adapting it with no dining room or daylight

In a dark kitchen or a venue with no window light, all eight steps still hold — Steps 2 and 3 just change setting. Build one permanent capture spot in the kitchen: a reusable neutral background (a board, a white panel) and a work light always aimed the same way. Because it doesn't depend on the weather or the time of day, a fixed spot is more consistent than chasing daylight, and the colour correction in Step 6 evens out any difference between sessions.

Frequently asked questions

Do I really need five frames per dish?

It's not a rule, but variations of the same shot let you pick the best one without re-plating if the first frame doesn't work.

What if I don't have time for all eight steps on every dish?

The two that matter most are plating (Step 1) and the shoot (Step 4). Get those right and the rest is fast. Filing and distribution can be batched once at the end of the day for several dishes at a time.

Can one employee own the whole process?

They can, but it recreates the bottleneck. Spread the capture step across a few people and keep processing central — that's the resilient version.

Are AI-enhanced photos allowed on delivery apps?

Platform rules target images that misrepresent the dish — wrong portion, wrong item, text and borders added on top. Uber Eats' guidelines for customer-submitted photos reject AI-generated images; its merchant menu-photo guidelines don't mention AI at all. A photo that starts from your real dish and is only relit stays within the intent of every policy in the table above. Keep it honest to what reaches the table, and if you're unsure, a platform's merchant support can confirm.

How often should a dish's photo be updated?

When the plating changes, the crockery changes, or one photo is visibly weaker than the rest of the menu. Prioritise your highest-selling dishes rather than redoing everything at once.

Does this change for a restaurant group with several locations?

The eight steps are the same. Assign one capture contact per location, but centralise processing and the brand profile at group level so every location's photos still look like the same restaurant.

The bottom line

Menu photography for restaurants no longer needs a studio or a photographer. It needs a routine that survives shift changes.