How to Do Client Photo Delivery for Food Photographers: A Step-by-Step Guide

Client photo delivery for food photographers comes down to a repeatable system: shoot to a spec, cull the keepers, batch edit for a consistent look, export to the exact sizes each delivery platform requires, and hand off files through a link the client can actually use. When you are shooting menus for restaurants and food-delivery apps, the delivery step is where most of your turnaround time hides, so tightening it is the fastest way to get paid sooner and keep clients coming back.

This guide walks through the full workflow, from the moment the shoot ends to the moment the client approves. The short version: standardize your naming and folder structure, edit the whole shoot as a batch so every dish looks like it belongs to the same menu, meet the platform’s crop and file-size rules before you export, and send a clean, well-labeled gallery. Do those five things and a delivery that used to eat a full day shrinks to an afternoon.

Why delivery is the real bottleneck in food photography

A single restaurant shoot can produce a few hundred frames across a dozen or more dishes. The photography is the fun part. The grind is everything after: sorting the frames, matching color and tone across every plate, cropping each shot to the sizes a delivery app expects, and packaging it all so the client is not left guessing which file goes where. Food-delivery clients tend to move fast. They want menu photos live in the app this week, not next month, and they often need the same dish in several aspect ratios for the hero card, the list thumbnail, and the promo banner.

That pressure is why a loose, improvised delivery process quietly costs you. Every hour spent hand-matching exposure between the first plate and the twentieth, or re-exporting because the thumbnails came back too soft, is an hour you are not shooting or billing. Building a delivery pipeline you can run the same way every time is what lets you take on more menu work without drowning in post.

Step 1: Agree on the delivery spec before you shoot

The cleanest deliveries are decided at the contract stage, not at the end. Before the shoot, confirm with the client exactly what they need for their platform. For food-delivery apps that usually means a specific pixel dimension and aspect ratio per placement, a maximum file size, a color space (sRGB for anything going on the web or in an app), and a file format, almost always JPEG for final menu assets.

Ask these questions up front:

• Which platforms will the photos appear on, and what are each one’s image specs?
• What aspect ratios do they need per dish? Many apps use a square or 4:3 hero and a smaller list thumbnail.
• Is there a maximum file size the app enforces on upload?
• Do they need a plain, neutral background for consistency across the menu, or styled lifestyle shots?
• How many final selects per dish, and who chooses, you or them?

Write the answers into a one-page spec sheet and keep it in the project folder. When you know the target dimensions and the look before you press the shutter, you frame with room to crop and you never re-shoot because a plate was cut off in the required square.

Step 2: Build a naming and folder system you reuse every time

A consistent file structure is the unglamorous backbone of fast delivery. Decide on one convention and apply it to every job. A reliable pattern is client_date_dish_sequence, for example bistro_0620_carbonara_01. Dish names in the filename mean the client can find the shot they want without opening a single image, and it makes building their menu straightforward on their end.

Set up a standard folder tree for each project: one folder for RAW captures, one for selects, one for final exports, and inside exports a subfolder per platform or per aspect ratio. Because the structure is identical on every job, you stop thinking about it, and anyone helping you can drop into the project and know where everything lives. This is also what makes batch operations safe later, since your editing tool is pointed at predictable folders.

Step 3: Cull ruthlessly to your best selects

Culling is choosing the keepers and cutting everything else, and doing it decisively is one of the biggest time savers in the whole pipeline. For menu work the goal is usually one hero frame per dish plus a backup, not fifteen near-identical plates. Go through the shoot and reject the obvious misses first: soft focus, a stray thumb in frame, a garnish that slid, a reflection you did not want. Then compare the survivors dish by dish and pick the single strongest angle.

Be honest and quick. The longer you deliberate on two nearly identical frames, the more time you lose across a hundred dishes. If your editing tool offers AI culling that flags duplicates, closed eyes on people, or out-of-focus frames, lean on it to do the first sort so you only make the final artistic call. Fewer, better selects also make the client’s job easier, since they are not wading through choices to build their menu.

Step 4: Batch edit for one consistent look across the menu

This is the step that separates a professional menu from a random pile of food photos. On a delivery app, a customer scrolls a grid of dishes from the same restaurant. If one plate is warm and bright, the next is cool and dim, and a third has a green cast, the whole menu looks amateur and untrustworthy. Consistency of color, exposure, and tone across every dish is the deliverable, not just sharp individual shots.

Editing each frame by hand to match the others is slow and drifts over a long shoot. The reliable approach is to define your look once and apply it across the entire batch, then fine-tune outliers. This is exactly where AI batch editing earns its place: it can learn your editing style from your past work and apply consistent color and tone to a full shoot in one pass, so plate number one and plate number fifty match without you nudging sliders on each.

Imagen’s AI photo editing for food delivery apps is built around this exact need. It learns your personal editing style through an AI profile, then applies a uniform grade across an entire menu shoot, delivers even color and tone from the first dish to the last, and handles culling too. It is a desktop app with cloud processing that works on your RAW files, and with pay-as-you-go pricing, where you pay for what you export and exploring the tools is free, the batch step that used to take hours becomes the part of your day you barely think about. Fast, consistent editing is precisely what makes fast delivery possible.

A few things to note about scope. Batch editing gives you a consistent grade, exposure balance, white-balance correction, and culling. Jobs like removing a distracting object from behind a plate, blending several exposures into a true HDR composite, or fixing lens geometry are a separate step handled by a dedicated tool, not part of a style-driven batch grade. Keep those specialty tasks out of the batch pass so the batch stays fast and predictable.

Step 5: Crop and export to each platform’s exact specs

With the whole menu graded, now you produce the actual delivery files. Work from the spec sheet you built in step one. For each dish, crop to the required aspect ratios, remembering that the composition you framed with room to spare now pays off. Export each ratio into its own folder so nothing gets mixed up.

Match the platform’s technical rules precisely. Convert to sRGB so colors look the same in the app as they did on your monitor. Export as JPEG at a quality level that stays under the app’s maximum file size while keeping the food looking crisp, since an overcompressed thumbnail with visible artifacts undercuts the whole point. If the app enforces a hard dimension, hit it exactly rather than sending oversized files the platform will re-compress on its own terms. Doing the resizing yourself keeps you in control of how the final photo looks.

Step 6: Package and send a gallery the client can actually use

How you hand off matters as much as the files themselves. Sending a pile of loose attachments over email is where confusion starts. Instead, deliver through an online gallery or a shared cloud folder with a clear structure, ideally mirroring your platform subfolders so the client sees exactly which image is the hero, which is the thumbnail, and which is the banner for each dish.

Include a short read-me or a caption note that states the naming convention and which folder maps to which placement. Add a line about usage rights and, if relevant, how to request a revision. A clean, labeled delivery signals professionalism and cuts down on the back-and-forth that eats your evenings. For recurring restaurant clients, keep the gallery link structure identical every time so they learn where to look once and never ask again.

Step 7: Handle revisions and lock the final approval

Build one revision round into your process so it does not catch you off guard. When the client comes back, collect all their notes in one message rather than fixing things piecemeal. Because your edits were driven by a consistent style profile, a global tweak, say the client wants the whole menu slightly warmer, can be re-applied across the batch rather than redone plate by plate.

Once the client signs off, mark the project approved, archive the final export folder with the RAW files, and log the delivery. Keeping the finished, graded set alongside the style you used means the next shoot for that same restaurant starts from a known look, and their menu stays visually consistent across seasons and new dishes.

Common client delivery mistakes to avoid

A few recurring errors sink otherwise good food shoots. Inconsistent color across the menu is the biggest, and it comes from editing frame by frame instead of batching to one look. Delivering the wrong dimensions is the second, usually because the spec was never confirmed before the shoot. Oversized files that the app crushes into mush, ambiguous filenames the client cannot map to dishes, and a delivery method that scatters files across email threads all create friction that reads as unprofessional.

The fix for nearly all of them is the same: decide the spec first, edit as a batch for consistency, export to precise sizes, and hand off through a structured gallery. When the system is the same on every job, the mistakes stop being possible. For more on speeding up the post side, see how a repeatable pipeline turns a full-day edit into an afternoon, and how style profiles keep a brand’s look steady across every shoot. You can also start a batch on your own catalog at Imagen’s photo editing platform to see how the grade holds across a whole menu, and to try the new Studio, where you cull, edit and export in one project.

What’s new in Imagen: Handing work to a client is the last step of the shoot, and Imagen is now an intelligent, agentic Studio for professional photographers, one project where you cull, edit, review and export in any order. You can export finished JPG, TIFF or PNG files straight from Imagen, or send the AI edits back to Lightroom Classic as XMP. The Studio is rolling out gradually as a beta.

Frequently asked questions

How fast should I deliver food photos to a client?

For menu and delivery-app work, aim for a turnaround of a few business days, and confirm the deadline in your contract. Delivery apps often want photos live quickly, so the faster your culling, batch editing, and export pipeline runs, the more comfortably you can meet a tight timeline without cutting corners on quality.

What file format and size do food-delivery apps need?

Almost always JPEG in the sRGB color space, sized to the platform’s required dimensions and kept under its maximum upload file size. Confirm the exact specs with the client before the shoot, since aspect ratios and size caps vary between apps and between placements like the hero card and the list thumbnail.

How do I keep every dish on a menu looking consistent?

Edit the whole shoot as a batch to one defined look rather than adjusting each photo independently. Applying a single, learned editing style across all dishes keeps color, exposure, and tone even from the first plate to the last, which is what makes a menu grid look like one cohesive set instead of a mix of separate photos.

Should I let the client choose the final photos or do I cull first?

Cull first, then present a tight set of strong selects, usually one hero per dish plus a backup. Handing a client hundreds of near-identical frames slows them down and pushes the sorting work onto them. A curated gallery makes their menu build faster and makes you look more decisive and professional.