Skip to content

Detroit Menu Photography for Print, QR and Delivery

A full menu shot in one session only works if the setup, the light and the file names are decided before the first plate is plated. Detroit's seasonal light swings hard, from a high June sun to a low December one, so the shooting schedule has to change with the calendar. This guide covers batch shooting, naming, keeping photos in sync with menu edits, and the calorie-label rule that ties a photo to a specific item.

Plan the shot list around the menu, not the dishes

Start from the point-of-sale export, not from what looks good on the pass. Sort items by menu section, then flag which ones need a photo for the printed menu, the QR menu, the delivery apps, or all three. A dish that appears only in print can be shot once and reused; a dish that appears on DoorDash, Uber Eats and Grubhub needs a square crop and enough headroom that an automatic crop will not cut the rim of the plate.

Group by how the dish is built, not by cuisine. Burgers, sandwiches and Coney dogs share a low three-quarter angle; bowls, shawarma plates and soups share a 45 to 60 degree angle from above so the layers read; pizzas and flatbreads want a straight overhead 90 degree shot so the square cuts and toppings are legible. Shooting one group back to back means you set the camera height once and change only the plate.

  • Shoot every item that appears on any menu surface, even if you only need it for print
  • Mark dishes with variable builds (mixed grills, combo plates) and decide the reference build before the shoot
  • Shoot the standard portion, not a generous one, so the photo matches what the kitchen sends

Batch shooting that keeps a full menu consistent

Set a fixed camera position and leave it. A tripod or a phone clamped to a shelf at the same height and distance for every dish is the single biggest factor in whether the finished menu looks like one set. Keep the same background for the whole session: a matte surface in a color that contrasts with the plate, so a white bowl on a white table does not disappear.

Work in batches of eight to twelve items, with the kitchen plating two ahead of the camera so nothing sits under the light and dries out. Shoot three frames per dish: the main angle, one closer crop, and one wider frame with space around the plate for the delivery tile. Wipe the rim and check for drips before each frame; at menu-tile size a smear on the plate edge is the most visible defect.

  • Lock exposure and white balance manually so auto settings do not shift between plates
  • Shoot a plain reference frame at the start of each batch to check color later
  • Keep garnishes identical across the session: same herb, same sauce dot, same side

A Detroit daylight schedule by season

Detroit's window light is a seasonal tool, and the numbers decide the schedule. Around the June solstice the city gets about 15 h 06 min of daylight and the noon sun reaches about 71 degrees above the horizon. That high sun means direct window light is steep and short-lived; shoot between roughly 10 a.m. and 2 p.m. with a diffuser in the window, or shift to a north-facing window for softer, steadier light. Around the December solstice there is about 8 h 54 min of daylight and the noon sun sits at only about 24 degrees, so low sun comes deep into a south-facing room. That is useful for warm side light on plated food, but the usable window is short: plan the session to start mid-morning and finish before the light drops.

In practice: schedule long full-menu shoots in late spring and early fall, when the sun is mid-height and the working window is comfortable. In deep winter, book the shoot for the middle of the day and keep a backup continuous light, because a cloudy December afternoon gives you almost nothing. In high summer, avoid late afternoon entirely; the low, hard light through a west window creates blown highlights on glossy sauces.

  • June: shoot 10 a.m. to 2 p.m. behind a diffuser, or use a north window
  • December: shoot 10 a.m. to 1 p.m. and have a fill light ready
  • Overcast days: best for even light, worst for exposure consistency, so meter every dish

Name files so the menu stays in sync

The photo library is where menu photography usually falls apart. Six months after the shoot, nobody remembers which of forty images is the current version of the same sandwich. Use a name that carries the item, the version and the surface: item-code_date_size. For example, a chicken shawarma plate shot in March for delivery might be shawarma-plate_v2_2025-03_sq. Keep the point-of-sale item code in the name so a menu change can be traced to a photo without opening the file.

When a dish changes, retire the old images rather than overwriting them. Move superseded files into an archive folder, keep the current set in one folder per menu surface, and update the QR menu and the delivery app listings from that single folder. If a price or portion changes but the plate looks the same, the photo can stay; if the build changes, reshoot.

  • One folder per surface: print, QR menu, delivery, social
  • Never edit a file name after upload without updating the menu link
  • Log the shoot date inside the file name, not only in metadata

Calorie labels and the photo that has to match

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. The practical consequence for photography is that a photo must match the item the calories describe. If the photo shows a plate with a side that is not part of the declared item, the image and the calorie figure stop agreeing.

Before the shoot, get the declared build for every item that carries a calorie figure and plate exactly that. For independent Detroit restaurants that are not covered by the rule, the same discipline still helps: a photo that matches the build protects you if the menu later adds calorie information, and it keeps delivery orders from generating complaints about missing components.

Sizing for print, QR menus and delivery apps

Print and QR menus need a large, sharp file that holds up at the printed size and at arm's length on a phone. Delivery apps crop to their own tiles. This site publishes spec pages for Uber Eats, DoorDash, Grubhub and BentoBox, each in a United States and a USA version. Where a platform does not publish pixel specs, check the upload screen in the merchant dashboard, because the accepted crop and minimum size are shown there.

For the restaurant's own channels, 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. It cannot guarantee approval by any platform, so always confirm the current requirement on the platform's own upload screen before a full menu goes live.

Checklist before you publish

  1. Export the full item list from the point-of-sale system and mark which surfaces each item appears on
  2. Group dishes by plate angle and shoot each group back to back
  3. Lock camera height, exposure and white balance before the first plate
  4. Shoot three frames per dish: main, close crop, wide frame for delivery tiles
  5. Name every file with item code, version, shoot date and size
  6. Confirm the declared build for any item with a calorie figure and plate exactly that
  7. Check each platform's upload screen for the current crop and minimum size
  8. Archive superseded photos instead of overwriting them

Questions

How long does it take to photograph a whole restaurant menu?

It depends on item count and plating speed, not on camera settings. Once the camera position and light are fixed, the bottleneck is the kitchen: with two plates ready ahead of the camera, you can move steadily through a section at a time. Split a large menu across two sessions by section rather than rushing one long day, and keep the same camera height and background in both sessions.

What angle should I use for menu photos?

Use a low three-quarter angle for burgers, sandwiches and hot dogs so the layers show; a 45 to 60 degree angle from above for bowls, plates and soups so the components read; and a straight 90 degree overhead shot for pizza and flatbreads so the cuts and toppings are clear. Keeping one angle per dish type makes the menu grid look deliberate.

Do menu photos need to match calorie information?

Yes, where calorie labeling applies. In the United States, 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 must match the item the calories describe, so plate exactly the declared build, including sides, before you shoot.

How do I keep menu photos current when dishes change?

Tie every photo to the point-of-sale item code and add a version and shoot date to the file name. Keep one current folder per surface (print, QR menu, delivery, social) and move replaced images to an archive. Reshoot when the build or portion changes; keep the photo when only the price changes.

Start with a dish