Skip to content

Menu Photography in Chicago: Consistency Across Print, QR Menus and Delivery Apps

A Chicago menu rarely lives in one place. The same dish has to look right on a printed board, a QR menu, a DoorDash tile and an Instagram post, and it has to keep looking right after you change a price or swap a special. This guide covers how to batch shoot a full menu, name and store the files so nothing gets lost, and time your shoots around Chicago's very different summer and winter light.

Plan the shoot around your actual menu

Before you touch a camera, export a current item list from your point-of-sale or menu system and sort it by category: starters, mains, sides, desserts, drinks. Shoot in that order so the styling setup changes as little as possible between frames. Grouping by category also means garnishes, plates and backgrounds stay consistent, which is what makes a menu look like one menu rather than a folder of unrelated photos.

Decide which items get a photo. Delivery apps reward images on every item, but printed menus often only carry a handful. Mark each item as must-shoot, optional or skip, and note whether it needs an alternate version for a QR menu where the photo appears larger than on a delivery tile.

  • Shoot every dish at one consistent 45-degree angle for the master image, then add a straight-on 90-degree shot only for tall items like burgers or layered desserts
  • Keep the same plate family and background per category so the grid reads as a set
  • Photograph drinks and sides too; they are the items most often missing a photo on delivery menus
  • Note items that are seasonal or rotate weekly and flag them for reshoots

Batch shooting: one setup, many dishes

Batch shooting means you build the light and background once and move dishes through it. Set a table near a window, put your backdrop behind the plate, and mark the plate position with tape on the table so every dish lands in the same spot. Then work through your list in order, shooting three to five frames per item and checking focus on the phone or camera screen before the dish leaves the table.

Shoot tethered or with a phone on a tripod so the camera position never moves. If you change the height or distance, everything shot after that point will not match what came before. Keep a written log as you go: item name, frame numbers, any notes about a garnish that ran out. That log is what makes file naming possible afterward.

For a full menu, plan on a longer session than you expect. Cold dishes lose their edge under lights, so shoot salads and cold plates first, then hot items, and have the kitchen send one dish at a time rather than a tray.

A seasonal window-light schedule for Chicago

Chicago's daylight swings hard between solstices, and that changes what window light you can actually use. Around the June solstice the city gets about 15 hours 3 minutes of daylight and the noon sun sits about 72 degrees above the horizon, so direct sun is steep and harsh and window light stays usable late into the evening. Around the December solstice there is about 8 hours 57 minutes of daylight and the noon sun is only about 25 degrees above the horizon, so low sun rakes deep into the room and the usable window is short.

Build the calendar around that. In summer, shoot in the morning or late afternoon when the sun is off the window, or use a sheer curtain to diffuse it, and you can schedule sessions into the early evening. In winter, aim for the middle of the day, keep the window clear of low sun by shooting from the side the sun is not hitting, and expect to finish before mid-afternoon. In both seasons, a white foam board opposite the window bounces light back into the shadow side of the plate.

  • Summer: book shoots between mid-morning and early afternoon, or after the sun has moved off the window; daylight lasts long enough for evening sessions
  • Winter: book a tight midday window, check the forecast for sun angle, and have a backup date because overcast weeks are common
  • Spring and fall: light changes week to week, so test the window a day before a large batch shoot
  • Turn off overhead lights that mix color temperature with daylight; a single light source is easier to correct later

Naming, storing and syncing files with menu changes

Name every file with the item name and a version, for example italian-beef-v2.jpg, not IMG_4471.jpg. Use lowercase, hyphens instead of spaces, and no accented characters, so the same file uploads cleanly to a website, a QR menu builder and a delivery portal. Keep one master folder with full-resolution originals and export smaller versions per channel rather than re-cropping from a compressed copy.

The harder problem is staying in sync. When a dish changes, a price changes, or an item is removed, the photo has to follow. Keep a simple tracking sheet listing each item, its current photo file, the date it was shot, and which channels it appears on. When you update a menu, work from that sheet and mark which photos need a reshoot.

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 must match the item the calories describe, so if a portion or recipe changes, reshoot rather than reuse the old image.

Sizing photos for printed menus, QR menus and delivery apps

One master image per dish, cropped per channel, is the only workable system. Printed menus usually need a landscape or square crop at print resolution. QR menus are read on a phone held at arm's length, so a square or 4:5 crop with the dish filling most of the frame works better than a wide shot. Delivery tiles are small squares, so shoot with the food centered and leave margin around the plate that you can crop away.

Delivery platforms do not all publish pixel specs, and the ones that do change them. Our spec pages on this site cover Uber Eats, DoorDash, Grubhub and BentoBox for the United States; where a platform does not publish exact pixel dimensions, check the upload screen in your merchant portal, which shows the current requirement and crop tool.

If a platform bans AI-generated images, shoot and upload your own real photo of the dish to that platform and do not use generated or altered food imagery there. For your own channels, a real photo of your own dish can be improved for light, background and crop while keeping the food exactly as served.

Chicago-specific shooting notes

Chicago's best-known dishes photograph in ways that shape your setup. Deep-dish pizza needs a high angle to show the layers and a side shot to show the height, and it slumps quickly, so shoot it within a minute of cutting. Tavern-style pizza is thin and wide, so a straight overhead frame on a dark surface keeps the edges from disappearing. Italian beef is wet and messy by design, so shoot it on a board with the jus in a separate cup and wipe the rim before every frame.

Local food culture here also means Polish and Eastern European plates, Mexican dishes, and a serious fine-dining scene, each with its own plating logic. If your menu runs in English and Spanish, keep photo filenames and captions in both languages so the QR menu and website versions stay matched. Avoid styling a dish differently from how it leaves the kitchen: a delivery customer compares the photo to the container that arrives.

Checklist before you publish

  1. Export your current item list and mark each dish must-shoot, optional or skip
  2. Tape the plate position on the table and keep the camera on a tripod for the whole batch
  3. Shoot cold dishes first, then hot items, one dish at a time from the kitchen
  4. Book summer sessions for morning or early evening and winter sessions for a tight midday window
  5. Name files by item and version in lowercase with hyphens, and keep full-resolution masters separate
  6. Track each item's photo, shoot date and channels in one sheet and update it with every menu change
  7. Check the upload screen in each delivery portal for the current crop and size before exporting
  8. Reshoot any item whose portion, recipe or calorie count has changed

Questions

How many photos should a restaurant have for its menu?

At minimum, one photo per item you sell on delivery apps, because a missing image makes an item easy to scroll past. For printed menus, a handful of hero dishes is usually enough. Photograph everything once in a batch and you can decide later which channels use which images.

What is the best time of day to shoot menu photos using window light?

It depends on the season and which way your window faces. In Chicago, summer daylight runs about 15 hours and the noon sun is high, so morning or late afternoon light is easier to control. In winter, with about 9 hours of daylight and a low sun, aim for midday and keep direct sun off the plate.

Do menu photos need to match calorie counts on delivery apps?

Yes. 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. The photo must match the item the calories describe, so reshoot if the portion or recipe changes.

How do I keep menu photos updated when prices or dishes change?

Keep a tracking sheet listing each item, its photo file, the date it was shot and where it appears. When you edit the menu, update the sheet at the same time and flag any item whose photo no longer matches what the kitchen serves.

Start with a dish