Menu Photography in Denver: Shooting a Full Menu Consistently

Why a full menu needs one system, not one great shot

Delivery feeds, QR menus and printed cards all crop hard. A dish that looks generous in a wide shot can read as an empty plate at thumbnail size, so decide early what each photo must survive: a square tile, a tall phone screen, a printed half-page.

Consistency is what makes a menu look professional. Same camera height, same distance, same background and same light direction across every item means a diner scanning the grid reads food, not differences in photography. Shoot one dish as a test, review it on a phone at thumbnail size, then lock the setup before the next forty plates.

• Fix camera height and distance for every dish in a category
• Use one background and one surface for the whole shoot
• Review the test dish on a phone before continuing
• Shoot a square frame first, then a wider frame for print

A seasonal window-light schedule for Denver

Denver's daylight swings hard between solstices. Around June the city gets roughly 14 h 49 min of daylight and the noon sun sits about 74 degrees above the horizon, which means harsh overhead light and long, bright evenings. Around December it gets about 9 h 11 min and the noon sun is only about 27 degrees, so light comes in low and rakes across the room.

Use that to plan shoots rather than fight it. In summer, shoot near a north-facing window in mid-morning or late afternoon and avoid the 11 a.m. to 2 p.m. window, when the sun is nearly overhead and shadows fall straight down into plates. In winter, the low sun reaches deep into the room, so a south or west window works well in late morning, but move tables back from the glass or the light will be too directional and blow out glossy sauces.

Book batch days around this: two or three long sessions in shoulder seasons (spring and fall), when the noon sun sits between those extremes, give you softer, more even light for the widest range of dishes. Keep a white foam board or a sheet of parchment opposite the window to bounce light back into shadowed sides of the plate.

• June: north window, mid-morning or after 3 p.m., never midday
• December: south or west window, late morning, pull tables back from the glass
• Spring and fall: best window for long batch days
• Bounce card opposite the window to soften the shadow side

Batch shooting a whole menu in one or two days

Batch shooting works when the kitchen and the camera follow the same order. Group dishes by how they are plated, not by menu section: all bowls, all handhelds, all desserts. That way the styling setup changes a few times rather than forty.

Prep in waves of five to eight plates so food is photographed hot and fresh. Keep a shot list printed with item names and note which dishes need a garnish or side that must appear in the photo. For chains covered by US calorie labeling rules, the photo must match the item the calories describe, so photograph the exact portion and build the menu lists, not a stylized version.

• Sort the shot list by plating style, not menu order
• Prep five to eight dishes per wave
• Photograph the exact build and portion the calorie count describes
• Shoot the full dish, then a tighter crop for delivery tiles

Naming files so photos stay findable

A menu photo is only useful if you can find it six months later when the dish changes. Use a naming pattern that includes the menu section, the item name and the date: for example, starters_green-chile-burrito_2026-03. Avoid spaces and accented characters in file names, since some upload tools and CMS platforms handle them badly.

Keep one master folder per menu revision and a subfolder of exported sizes. When a dish is retired, move its files to an archive folder rather than deleting them, so you can prove what was photographed and when if a calorie listing or delivery listing is questioned.

• Pattern: section_item-name_YYYY-MM
• No spaces or accented characters
• One master folder per menu revision
• Archive retired dishes instead of deleting

Keeping photos in sync with menu changes

Menus change seasonally, and delivery listings drift out of date faster than printed cards. Set a monthly check: open each delivery listing beside the current menu and confirm the photo, the description and the calorie figure all describe the same plate. When a recipe changes, reshoot rather than reuse, because a photo of the old build next to new calorie numbers is a mismatch.

For printed and QR menus, keep the photo library versioned so a reprint only requires swapping the changed items. If your menu is published in English and Spanish, name and file both language versions together so neither falls behind.

Platform image requirements change and not every app publishes exact pixel specs. Check the upload screen for the current requirements before exporting, or use the spec pages on this site, which cover Uber Eats, DoorDash, Grubhub and BentoBox for the United States.

• Monthly: compare each delivery listing to the live menu
• Reshoot any dish whose recipe or portion changed
• File English and Spanish menu versions together
• Check the upload screen or the spec pages before exporting

Where the finished photos go

Shoot once, export many. A square crop suits delivery tiles and social grids, a 16:9 frame suits website banners and menu boards, and a tall 4:5 crop suits phone-first ordering pages. Keep the originals so you can re-export when a platform changes its requirements.

For the restaurant's own channels, a tool like FoodPhoto can help: it 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. It cannot guarantee approval by any platform, so always check each app's current requirements yourself.

Denver menu photography checklist