Menu Photography in Boston: Shooting a Full Menu Consistently

Plan the shoot around Boston's daylight, not around a single day

Boston's window light changes dramatically across the year, so the same table by the same window will not give you the same photo in June and December. Around the June solstice there are about 15 h 06 min of daylight and the noon sun sits about 71 degrees above the horizon, which means steep, hard light through south-facing windows and long usable mornings and evenings. Around the December solstice there are about 8 h 54 min of daylight with the noon sun only about 24 degrees up, so light comes in low and flat and you have a short working window.

For a full-menu batch shoot, pick your season deliberately. Late spring and early fall give the most forgiving mid-morning light. In deep summer, shoot early morning before the sun climbs or late afternoon when it drops, and diffuse the window with a sheer curtain or a sheet of diffusion material. In winter, the low sun means you can shoot through more of the day, but keep the table close to the window and turn off overhead lighting that will mix color temperatures.

Build a simple seasonal calendar: a summer block for lighter dishes and cold items, a winter block for chowder, braises and baked dishes, and a short reshoot window each quarter for seasonal specials. Book the shoot on a cloudless or evenly overcast day and note the time of day you used, so a replacement photo of one dish later matches the rest of the set.

• June: shoot 8 to 10 a.m. or after 5 p.m. to avoid the steep midday sun
• December: shoot mid-morning to early afternoon; the sun stays low
• Keep a fixed camera position and window table for every batch so reshoots match
• Use a sheer curtain as diffusion rather than direct sun on glossy sauces

Batch shooting a full menu: order of work

A full menu is a production line, not a series of portraits. Group dishes by how they are made and how they look: cold items and salads first, then fried and grilled items, then sauced and braised dishes, then desserts. This reduces trips to the kitchen, keeps hot food from sitting under lights, and means similar dishes are shot under identical conditions, which is what makes the delivery grid look intentional.

Set up one fixed position: a table near the window, a camera on a tripod or a stable stack, and a consistent background. Shoot each dish from a 45-degree angle for most plates and a straight overhead 90-degree shot for bowls, pizzas and flat items. Use a 1:1 crop in mind for delivery tiles and a 16:9 or wider frame for website banners. For each dish, capture one clean hero frame, one tighter crop for the app tile, and one detail shot if the dish has a distinctive texture.

Work in short blocks of 8 to 12 dishes with a break to reset the table. Keep a written shot list with the menu's exact item names beside each frame number, and shoot the item as it is actually served, including the garnish and portion, so the photo matches what the guest receives.

Naming files so a full menu stays findable

A menu shoot produces dozens or hundreds of files, and unnamed camera files are useless within a week. Adopt a naming convention before the shoot and use it in camera or at import. A practical pattern is menu-section, item-name, angle, and version, separated by hyphens: starters-clam-chowder-45-v1.jpg. Keep the item name spelled exactly as it appears on the menu so the file can be matched to the menu listing.

Store the original full-resolution frame separately from the cropped exports, and keep a simple spreadsheet or shared document that maps item name to file name, shoot date and which channels it has been published to. When a dish changes, update the version number rather than overwriting the old file, so you can roll back if the new photo does not work on a particular platform.

If the menu is published in both English and Spanish, add a language or menu-code field to the file name or the tracking sheet, so the right photo is attached to the right listing.

Matching photos to the menu, calories and platform rules

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. If you swap a dish's ingredients, change the portion, or replace a photo with one of a different build, check that the calorie figure and the image still describe the same plate.

For delivery apps, check the current upload screen rather than relying on remembered numbers. This site has spec pages for Uber Eats, DoorDash, Grubhub and BentoBox for the United States at /delivery-photo-specs/uber-eats/united-states/, /delivery-photo-specs/doordash/united-states/, /delivery-photo-specs/grubhub/united-states/ and /delivery-photo-specs/bentobox/united-states/, with matching /usa/ pages. Where a platform does not publish pixel specs, the page says so; in that case follow whatever the upload screen shows and test one item before uploading the whole menu.

Keep one master image per dish at full resolution and export per channel: a square tile for delivery grids, a wider crop for your own website, and print-resolution files for the printed menu. Never upscale a small delivery export for print.

Keeping photos in sync with menu changes

Menus change more often than most restaurants plan for: a fish of the day, a seasonal switch, a price change or a sold-out item. Decide which changes require a new photo. A price change does not, but a new garnish, a different plate, a changed portion or a substitution does, and so does any change that affects the calorie figure.

Put a short review on the calendar, ideally weekly during seasonal transitions and monthly otherwise. Walk the live menu against the tracking sheet, flag items with no photo or an outdated one, and shoot replacements in the next batch so they match the existing set's light and angle. When an item is removed, take the photo down from the website and QR menu rather than leaving an orphaned image, and update the delivery app listing.

• Weekly in spring and fall, monthly otherwise
• Flag any dish whose plate, portion or garnish changed
• Remove photos of discontinued items from every channel
• Reshoot seasonal specials at the start of each season, not mid-service

Boston-specific practicalities

Boston's food identity is well known for seafood, chowder, lobster rolls, baked beans and a strong Italian-American tradition, and those dishes bring specific photography problems. Chowder and bisque go flat and dull quickly, so shoot them within a minute of plating and use a small white card to bounce window light into the surface. Lobster rolls and fried seafood lose their texture fast, so keep them last in each block and shoot immediately. Glossy sauces and oyster shells pick up hard reflections, which is another reason to diffuse the window.

For a restaurant's own channels, a real photo of the restaurant's own dish can be improved for light, background and crop while keeping the food as it is. FoodPhoto works on the merchant's own photo and returns a kit of sizes for the website menu, Instagram, Google Business Profile and QR menu; it does not generate a different dish and cannot guarantee approval by any platform. Where a platform bans AI-generated images, shoot and upload your own real photo there and use edited versions only on your own channels.