Menu Photography in Raleigh: Shooting a Whole Menu Consistently

Plan the shoot around Raleigh's daylight, not around your free afternoons

Raleigh's sun swings a long way across the year. Around the June solstice you get about 14 hours 26 minutes of daylight and the noon sun sits about 78 degrees above the horizon, which means hard, short shadows and bright light spilling deep into a dining room. Around the December solstice daylight drops to about 9 hours 34 minutes and the noon sun is only about 31 degrees high, so light comes in low and flat through windows and the useful window is short.

That difference should drive your shooting calendar. Treat window light as a tool with a season, not something you grab when the prep list is short.

A practical seasonal schedule:

For any shoot, put the dish about 1 meter from the window, at a 45 degree angle to the glass, and shoot from roughly 45 degrees above the plate for a natural diner's view. Turn off overhead lights and use a white foam board on the shadow side to bounce light back. Check the exposure on the brightest sauce or glaze so it does not clip.

• March to early April: shoot the spring menu in late morning, roughly 10 a.m. to noon, when the sun is climbing and light is soft but strong.
• Late April through August: shoot early, around 8 to 10 a.m., before the high summer sun throws harsh patches. North-facing windows stay usable longest.
• September and October: this is the easiest window of the year. Mid-morning light is soft and the sun angle is moderate, so book your biggest batch days here.
• November through February: shoot between about 10 a.m. and 1 p.m., close to the low winter sun, and expect to shoot near the glass. Plan fewer dishes per session because the good light lasts a shorter time.
• Any month: avoid the two hours around solar noon in summer, when the sun is near its highest and shadows are shortest and hardest.

Batch shooting: how to photograph 30 dishes without losing your mind

Batch by cooking method and plate color rather than by menu section. Shoot all the fried items together, then all the grilled items, then desserts. Each group needs a similar bounce and a similar camera height, so you stop readjusting the setup between plates. Grouping by plate color does the same for the background: white plates, dark plates and bowls each get their own block.

Work with the kitchen, not against it. Give the chef a list of eight to ten dishes per session and ask for them in the order you will shoot them. Have a runner bring one plate at a time and take it away as soon as the shot is done, so nobody crowds the table and nothing sits under a heat lamp.

Shoot three frames per dish and no more: one straight-on at plate level, one at 45 degrees, and one overhead at 90 degrees for anything in a bowl or with a scattered garnish. Name the files on the spot, before the next plate arrives.

Keep a written shot log with the dish name, the date, the camera height and which window you used. When a new item is added in February, the log tells you how to match it to the August set.

File naming and a folder structure that survives staff turnover

The photo that cannot be found is the photo that gets retaken. Agree on one naming pattern and write it on a card taped inside the office. A workable pattern is: menucode_dish-name_angle_date. For example, lunch_brisket-plate_45_2025-03. Use lowercase, hyphens instead of spaces, and no personal names, so the system outlives whoever shot it.

Keep one master folder and three subfolders: originals, print, and web. Originals are never edited. Print files are exported at 300 dpi at the physical size they will appear on the page. Web files are exported at the pixel size the destination needs.

For print, export at 300 dpi and keep the dish centered with generous margins so the designer can crop. For QR menus and online ordering pages, a landscape 16:9 crop works well in a scrolling list, while a square 1:1 crop is the safe shape for grid layouts on delivery apps and social. Export both from the same original so the dish never looks different between channels.

For the delivery apps, do not guess at pixel dimensions. This site has spec pages for Uber Eats, DoorDash, Grubhub and BentoBox covering the United States, and those are the place to check the current requirements before you export. Where a platform does not publish pixel specs, check the upload screen itself, since that is the version the app will actually accept.

Keep photos in sync with menu changes and 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 rule that matters for photography is simple: a photo must match the item the calories describe. If a sandwich loses its side or a bowl changes from rice to noodles, the old photo is now wrong, even if it is a better picture.

Build a monthly photo audit into the menu update routine. Walk the menu line by line and mark each item as current, changed, or retired. Changed items get reshot in the next batch. Retired items get their files moved to an archive folder rather than deleted, because seasonal dishes often return.

When a dish changes, update every place its photo appears in the same week: the printed menu, the QR menu, the website, the online ordering page and each delivery app listing. A photo that is current on the website and stale in an app is the most common inconsistency, and it is the one customers see at the moment they are deciding what to order.

Menus in the United States are commonly written in English and Spanish. If you produce a Spanish-language menu, shoot the same dishes once and reuse the images across both versions, so the two menus do not drift apart visually.

Where a consistent set of menu photos actually gets used

A printed menu rewards consistency more than any other channel. Ten dishes shot at different camera heights and color temperatures look like a collage. Ten dishes shot on the same window, at the same height, with the same bounce look like a restaurant that knows what it is doing.

A QR menu has the opposite problem: it is viewed on a phone, often at arm's length in a dim dining room. Favor tighter crops and brighter, cleaner plates, and test the page on an actual phone before you print the QR code.

Your own website menu, Instagram, Google Business Profile and any in-store screens all pull from the same master set. FoodPhoto takes a real photo of the restaurant's own dish and improves light, background and crop for menus, delivery apps and social while keeping the food as it is, and every photo comes back as a kit of sizes. That is useful for the restaurant's own channels; it does not replace shooting your own real photos for any platform that requires them.