Cincinnati Menu Photography for Print, QR Codes and Delivery Apps

Plan the shoot around Cincinnati daylight, not the calendar alone

At the June solstice, Cincinnati gets about 14 h 45 min of daylight and the noon sun sits roughly 74 degrees above the horizon. High summer sun means a south-facing window throws a short, steep patch of light: usable for a narrow window of the morning, then gone. Near the December solstice, daylight drops to about 9 h 15 min and the noon sun is only about 27 degrees up, so low winter light rakes deep into the room and stays usable for most of the working day.

That difference should drive your shooting schedule. In summer, book window tables early and plan the rest of the menu for a controlled setup; in winter, you can shoot far more of the menu with natural light alone. Check the sun's path through your own windows once, note the hours the light is even, and reuse that note every shoot.

• June solstice: roughly 14 h 45 min of daylight, noon sun about 74 degrees up. Shoot window dishes in the morning before the light steepens.
• December solstice: roughly 9 h 15 min of daylight, noon sun about 27 degrees up. Window light stays low and usable for most of the day.
• Between the two, recheck the window patch each month; it shifts faster near the equinoxes than near the solstices.
• Keep a bounce card or white foam board to lift shadows on the side away from the window.

Batch the menu by how dishes are plated and served

Shoot in batches grouped by plating style rather than by menu order. Cold plates, hot plates, bowls, sandwiches and drinks each need a different setup and a different amount of time before the food changes on camera. A bowl of soup or a plate of pasta looks right for a couple of minutes; a sandwich or a salad holds longer.

Build a shot list from your actual menu, not from what looks good on a mood board. Include the items that carry the menu: the dishes customers order most, the higher-margin sides and drinks, and any item that already has a calorie count attached under FDA menu labeling. For a Cincinnati kitchen, that might mean a batch of chili-topped dishes, a batch of breakfast plates, and a batch of sandwiches, each shot back to back so the setup stays the same.

• Group by plating: bowls and pasta first, then sandwiches and plates, then drinks and desserts.
• Shoot the most-ordered items while food is freshest; add sides and drinks afterward.
• Use one camera height per group (a low 30 to 45 degree angle for plated entrées, straight overhead for bowls and pizzas) so the menu reads as one set.
• Keep a damp cloth and spare plates on set; a fingerprint on the rim shows at thumbnail size.

Shoot once for print, QR and app tiles

A printed menu needs a crop that fits its layout, a QR menu is viewed on a phone held at arm's length, and a delivery app tile is smaller still. Shoot each dish slightly wider than you think you need, then crop. A 1:1 square crop works for app tiles and social; a 16:9 or 3:2 landscape crop suits printed menu panels and website headers.

Keep the food centered and leave breathing room at the edges so the same file can be cropped three ways without cutting into the plate. Before you upload to any delivery platform, check that platform's current upload screen: this site publishes spec pages for Uber Eats, DoorDash, Grubhub and BentoBox, and those pages are the place to confirm the sizes and rules each platform applies in the United States.

Name and store files so a menu change takes minutes

A menu changes more often than a photo shoot happens. Name every file with the dish name, the menu section and a version date, for example chili-spaghetti-entrees-2025-03. Keep one master file per dish at full resolution and export the crops from it, so a price change or a new side never sends you back to the kitchen.

Store masters in a shared folder the person who updates the menu can reach, and keep a simple list mapping each dish to its file. When an item leaves the menu, retire the file rather than deleting it; seasonal dishes often come back.

• Format: dish-section-YYYY-MM, no spaces.
• One master per dish, crops exported from it.
• A shared index sheet listing dish, file name and last update date.
• Retire, don't delete, photos of seasonal items.

Keep photos in sync with calorie counts and menu edits

In the United States, restaurant chains with 20 or more locations must show calorie counts for standard menu items, and FDA guidance covers online menus as well as menu boards. A photo has to match the item the calories describe. If a photo shows a larger portion, extra side or different garnish than the calorie listing, the image and the number disagree, and that is a labeling problem, not just a design one.

Build the sync into your workflow: when a portion, recipe or garnish changes, reshoot the photo the same week the calorie count is updated. For independent Cincinnati restaurants outside the chain rule, matching photo to portion is still the practical standard, because a delivery customer who receives a smaller plate than the photo shows will notice.

Where each photo goes

Use one set of dish photos across your own channels: the printed menu, the QR menu, the website menu, Instagram, Google Business Profile and any print signage. On delivery platforms, upload your own real photos of your own dishes and follow each platform's current upload screen for size and content rules.

FoodPhoto takes a real photo of the restaurant's own dish and improves light, background and crop for menus, delivery apps and social, keeping the food as it is, and every photo comes as a kit of sizes for those channels. It cannot guarantee approval by any platform, so treat platform uploads as your own step, checked against each platform's rules.