Cleveland Menu Photography for Real Dishes

Plan the shoot around Cleveland daylight

Cleveland's daylight swing is the single biggest variable in a window-light menu shoot. Around the June solstice you get about 15 hours of daylight and the noon sun reaches roughly 72 degrees above the horizon, so light comes down steeply and stays usable late into the evening. Around the December solstice you get about 9 hours and the noon sun sits at about 25 degrees, which throws low, long light straight into a window and leaves a short usable window in the middle of the day.

Build a shooting calendar from that rather than from your prep schedule. In summer, book menu shoots for mid-morning or late afternoon at a north-facing window, and use the long evening light for any exterior or dining-room shots. In winter, shoot between roughly 10 a.m. and 2 p.m. when the low sun is highest, and keep a diffuser on hand because a 25 degree sun rakes across the table. In spring and fall, expect fast-moving conditions and shoot fewer dishes per session so a cloud passing does not change the light halfway through a set.

• Summer: mid-morning and late afternoon sessions, north window, no direct sun on the plate
• Winter: 10 a.m. to 2 p.m. only, diffuser or sheer curtain on the window
• Shoulder seasons: smaller batches, reshoot any dish whose light shifted mid-set
• Keep one reference dish shot at the start of every session to compare color across days

Batch shooting a full menu consistently

Consistency comes from fixing everything except the food. Lock the camera height and angle first: a 45 degree angle works for most plates and bowls, and a straight-down 90 degree overhead works for flat items like pizza, pierogi on a platter or a composed salad. Pick one angle per menu category and keep it. If your sandwiches are shot at 45 degrees, shoot every sandwich at 45 degrees.

Set up one station with a fixed background, a fixed light position and a taped mark on the table where the plate goes. Then work in batches by category rather than by order of the menu: all appetizers, then all sandwiches, then all entrees, then desserts. Batching lets you keep the same garnish, the same plate and the same background in play, which is what makes the set look like one menu. Shoot each dish as a real plate you would serve, not a styled version, because the photo has to match what leaves the kitchen.

• Shoot 3 to 5 frames per dish: one hero angle, one tighter crop, one detail of texture
• Keep the plate mark and light position taped so every dish lands in the same spot
• Shoot a plain background (wood board, slate, linen) that suits both pierogi and a corned beef sandwich
• Note the dish name and menu section on a slate or in a shot log as you go

Name and file photos so they match the menu

A menu shoot produces hundreds of files, and the naming convention is what keeps them usable six months later. Name each file with the menu section, the item name and a version date, using lowercase and hyphens: apps-pierogi-2025-03.jpg. Avoid camera defaults like IMG_4471, which tell you nothing when you are rebuilding a QR menu at 11 p.m.

Keep one folder per menu section and a single master folder of approved finals. When you replace a dish photo, keep the old file rather than overwriting it, and add a version suffix. That way, if a printed menu is still in circulation with the previous photo, you can match what the guest sees to what the kitchen serves. Store the finals at the largest size you have and export smaller sizes from them for each destination.

Sizes for print, QR menus and delivery apps

One photo rarely fits every place it appears. A printed menu needs a high-resolution file at print size. A QR menu needs a fast-loading image that still reads on a phone. Delivery apps need a square-friendly tile that survives thumbnail compression, and social needs vertical and wide crops. Export from the master file rather than re-shooting.

For delivery app pixel and file requirements, check the upload screen itself, because platforms change specs without notice. This site keeps spec pages for Uber Eats, DoorDash, Grubhub and BentoBox in the United States, and those pages will tell you what the platform publishes and what it does not. Where a platform does not publish pixel specs, the upload screen is the authority.

• Print: export at the resolution your printer asks for, from the master file
• QR menu: keep files small enough to load quickly on a phone on cellular data
• Delivery apps: square-friendly crops, checked against the upload screen
• Social: vertical 4:5 and wide 16:9 crops from the same master

Keep photos in sync with menu changes

Menu photos go stale quietly. A dish changes portion, garnish or plate and the old photo stays on the QR menu for months. Build a simple sync habit: whenever a menu item changes, flag its photo the same day, and review the full photo set at each seasonal menu change. A spring menu in Cleveland is a natural checkpoint, and so is the switch from a summer patio menu back to an indoor one.

Calorie labeling adds a reason to keep photos accurate. 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, so a photo of the old version of a dish next to new calorie information is a real problem. Even independent restaurants that are not covered should treat photo and menu text as one unit.

If your menu runs in English and Spanish, as many Cleveland menus do, name and file photos by the item's stable internal name rather than by the printed label, so one photo serves both language versions.

Where FoodPhoto fits

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. Every photo comes back as a kit of sizes covering a hero image, delivery-app sizes, Instagram formats and Google Business Profile, which is useful when you are working through a long menu in batches. It cannot guarantee approval by any platform, so check each platform's upload screen for its current requirements.

A practical order of work

Start with the items that sell most and appear in the most places: the dish on the printed menu, the QR menu, the delivery app and the specials board. Get those to a consistent standard first, then work down the menu in category batches. Keep the master files, the naming convention and the seasonal review on a calendar, and the set will stay consistent as the menu changes.