Skip to content

Menu Photography in Nashville: One Consistent Set for Print, QR and Delivery Apps

A Nashville menu lives in several places at once: a printed sheet, a QR code on the table, delivery app tiles, and your own ordering page. When each of those shows a different-looking photo of the same dish, the menu reads as unfinished. The fix is a repeatable shoot you can run in one afternoon and repeat every time the menu changes.

Plan the shoot around Nashville daylight

Nashville's window light changes far more than most kitchens expect across the year. Around the June solstice the city gets about 14 h 28 min of daylight and the noon sun sits about 77 degrees above the horizon, so a south-facing window throws a short, steep, hard pool of light close to the glass. Around the December solstice you get about 9 h 32 min and the noon sun is only about 30 degrees up, which sends light deep into the room at a low, raking angle.

Use that to build a seasonal schedule. In late spring and summer, shoot between 9 and 11 a.m. or after 3 p.m., when the sun is lower and the light is softer, and keep tables at least 1 m back from the glass so the shadow edge is not razor sharp. In late fall and winter, midday is your best window: the low sun reaches further inside, so you can place the table 2 to 3 m from the window and get an even wash. Whatever the season, tape a marker on the floor for the table position and note the time you shot, so next month's new item matches the rest of the set.

Bring a white foam board for the shadow side and a black card to flag stray reflections off glossy sauces. Turn off overhead fluorescents and any colored accent lighting, because mixed color temperature is the hardest thing to fix later.

  • June: shoot 9-11 a.m. or after 3 p.m., table 1-2 m from the window
  • December: shoot around midday, table 2-3 m from the window
  • Same table position, same time of day, every batch

Batch shooting a full menu without a studio

Shoot every dish the same way so the grid looks like one set. Lock the camera height and the distance to the plate: a 45 degree angle works for most plates because it shows both the surface and the height of the food, while a straight overhead shot at 90 degrees suits bowls, pizza and shared platters. Pick one and keep it.

Work in batches by category rather than by dish: all fried items, then all plates, then all sides, then drinks. Fried food in Nashville kitchens, hot chicken included, loses its shine within minutes, so shoot it last in each batch and plate one portion at a time. Keep a wet towel and a pair of tweezers on the table to wipe plate rims and move stray crumbs.

Use a phone on a tripod with the grid turned on, tap to focus on the front edge of the food, and lock exposure so a bright white plate does not darken the dish. Shoot one frame full-frame and one slightly wider, so you have room to crop to 1:1 for app tiles and 16:9 for a website banner without losing the edge of the plate.

  • One angle for the whole menu, chosen by dish type
  • Plate one portion at a time, shoot it within two minutes
  • Capture a tight frame and a wider frame of every dish

Name and store files so the menu stays in sync

File names are what keep a large menu manageable. Use a fixed pattern: category, item name, version date, and angle. Something like sides-mac-and-cheese-2025-03-45deg.jpg tells you what it is, when it was shot, and how, without opening it. Never leave files called IMG_4471.

Keep one master folder per menu version and a spreadsheet that lists each item, its file name, its price, and the date the photo was taken. When a dish changes, for example a new bun, a different side, or a price change that alters the portion, add a new file with a new date rather than overwriting the old one. That way you can always tell which photo matches the current menu.

If your menu is written in English and Spanish, which is common on US menus, name the files in a way that works for both, and keep a short note in the spreadsheet for the translated item name so the photo is attached to the right line on each version.

Match photos to the menu, including calorie labeling

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 rule for photography is simple: the photo must show the item the calories describe. If the calorie figure was calculated for a sandwich with a standard side, do not use a photo of the same sandwich with a different side or an extra portion.

For independent Nashville restaurants the rule may not apply, but the habit is still worth keeping. Photograph the standard build of each item, note the portion size and any included side in your spreadsheet, and update the photo whenever the recipe or portion changes. If you add a seasonal special, shoot it before it goes on the menu, not after.

Delivery app specs, print and QR menus

Sizing is where a consistent set usually falls apart. This site publishes spec pages for Uber Eats, DoorDash, Grubhub and BentoBox, each for the United States, so check those pages for the current upload guidance before you export. Where a platform does not publish pixel specs, check the upload screen in your merchant dashboard, because that is the version your images will actually be measured against.

Delivery apps crop and compress images differently, so a photo that looks good full size can lose the rim of the plate in a small square tile. Export a 1:1 crop with the food centered and at least 10 percent empty space around the plate, and keep the dish filling roughly 70 to 80 percent of the frame. For print, export at 300 dpi at the size the item will actually appear, which for a typical menu column is often no more than 4 cm wide. For a QR menu, keep files small enough to load quickly on a phone on cellular data.

FoodPhoto takes a real photo of the restaurant's own dish and improves the 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.

When a dish changes, update it everywhere at once: the printed sheet, the QR menu, your website, and each delivery app. A photo that is right on the app but stale on the printed menu is the most common mismatch diners notice.

  • Check this site's spec pages for Uber Eats, DoorDash, Grubhub and BentoBox (US)
  • If specs are not published, read the upload screen in the merchant dashboard
  • Export 1:1 with 10 percent breathing room, 16:9 for web banners, 300 dpi for print
  • Update print, QR, website and apps in the same pass

Checklist before you publish

  1. Pick one camera angle per dish type and mark the table position on the floor
  2. Note the time of day you shot and repeat it for every new batch
  3. Shoot fried items last and within two minutes of plating
  4. Name every file with category, item, date and angle
  5. Keep a spreadsheet linking item, file name, price and calorie figure
  6. Export a 1:1 tile and a wider crop from every master shot
  7. Check the current upload guidance for each app before exporting
  8. Refresh print, QR, website and app photos together when a dish changes

Questions

How do I photograph a whole menu in one day?

Work in categories, not dish by dish. Set one camera position, one light setup and one angle per dish type, then shoot all fried items together, all plates together, and so on. Plate one portion at a time, shoot within a couple of minutes, and keep a spreadsheet open so you can log each file as you go. A tight shot list and a fixed table position matter more than extra equipment.

What should I name menu photo files?

Use a fixed pattern that includes the category, the item name, the date and the angle, for example mains-shrimp-and-grits-2025-04-45deg.jpg. Avoid camera default names. Add the same file name to your menu spreadsheet next to the price and any calorie figure, so you can see at a glance which photo matches the current version of the item.

Do delivery apps have the same image size requirements?

No. Each platform crops and compresses differently, and requirements change. This site publishes spec pages for Uber Eats, DoorDash, Grubhub and BentoBox for the United States. Where a platform does not publish pixel specs, check the upload screen in your merchant dashboard, since that is what your file will be measured against.

How often should menu photos be updated?

Whenever the item changes in a way a diner would see: a new portion size, a different side, a changed garnish, a new plate, or a price change that reflects a different build. Otherwise, refresh the whole set once a season so the lighting and styling stay consistent across the menu. Update the printed menu, QR menu, website and delivery apps in the same pass.

Start with a dish