Oakland Menu Photography for Real Dishes
A full menu photographed in one consistent batch looks like a restaurant that has its act together, and it makes printed menus, QR menus and delivery listings easier to keep current. Oakland's daylight swings from about 14 h 37 min at the June solstice to about 9 h 23 min in December, so the window you shoot beside changes with the season. This guide covers batch shooting, naming files, and keeping photos matched to the menu as dishes change.
Plan the batch before you cook anything
A menu shoot fails when it is treated as a series of one-off photos. Decide the full shot list first: every orderable item, plus the modifiers that change what arrives on the plate, such as a protein swap or a side that is pictured separately. Group dishes by how they are plated and by how long they hold up under lights, so cold items and hot items are not sitting out together.
Work in blocks of six to ten items. Cook a block, shoot it, reset the table, and move on. This keeps food at its best and keeps your surface, background and camera position identical from tile to tile, which is what makes a varied menu look like one set.
- Write the shot list straight from the POS so nothing orderable is missed
- Shoot best sellers and high-margin items first in case the day runs short
- Keep one table as the permanent set: same surface, same background, same camera height
- Photograph combo plates and family meals as they are actually served
A seasonal window-light schedule for Oakland
Oakland's noon sun sits about 76 degrees above the horizon around the June solstice and about 29 degrees around December, which changes how light comes through a window and how long your shooting window lasts. In summer the sun is high and hard, so direct window light is short-lived and contrasty. In winter the sun is low, light rakes deeper into the room, and the usable window is longer.
Use this as a starting schedule and adjust to which direction your windows face. North-facing windows give the most even light year-round and are the safest choice for a permanent set.
- Late spring and summer (May to August): shoot mid-morning or mid-afternoon, when high sun is not blasting straight in; avoid the hours around noon unless the window is shaded
- Autumn and winter (November to February): low sun reaches further into the room, so expect a longer usable window and watch for warm color cast in late afternoon
- Around the equinoxes (March, September): light is closest to neutral and the window is moderate; good months for a full-menu reshoot
- North-facing window: usable most of the day, every season
- East-facing: morning only; west-facing: afternoon only; south-facing: shade it and shoot off the diffused edge
- Diffuse direct sun with a white curtain or a sheet of diffusion material, and bounce light back with a white foam board opposite the window
Camera position, crops and exposure for every dish
Pick two angles and stick to them for the whole menu. A 45-degree angle shows height and layers, which suits stacked plates, sandwiches and bowls. A straight overhead shot at 90 degrees suits plates where the arrangement matters, such as composed plates, pizzas and shared platters. Get the camera at the same height and distance for every dish in a category so the tiles line up in a grid.
Shoot each dish in at least two aspect ratios: a square 1:1 for delivery tiles and QR menus, and a 16:9 or 3:2 landscape for website headers and printed menu bands. Leave breathing room around the plate so a crop does not clip the rim. Lock exposure and white balance manually after the first frame of a block so every tile in that block matches; if you shoot on a phone, tap and hold to lock, then adjust the exposure slider once rather than per shot.
Keep sauces glossy but not wet with pooled oil, wipe plate rims, and remove stray crumbs. Those small habits matter more on a menu of many dishes than any single hero shot.
- 45 degrees for height, 90 degrees for arrangement; no other angles mid-menu
- Square 1:1 master plus a 16:9 or 3:2 landscape version of every dish
- Shoot a plain card at the start of each block to check white balance later
- Fill the frame to roughly 80 percent with food, keeping the full rim visible
Name files so photos and menu stay in sync
The most common menu-photo problem is not lighting; it is a photo of the old version of a dish sitting next to a new description. Build a naming convention that ties each file to its menu entry, and use it without exception. A workable pattern is category, item, version and ratio, for example: tacos_birria_v3_1x1.jpg and tacos_birria_v3_16x9.jpg.
Keep one master folder and one spreadsheet or document listing each menu item, its photo file name, the date shot, and the date it was last checked against the menu. When a recipe, portion or plating changes, bump the version number and reshoot only that item on the same set. Because the set is fixed, a single reshoot still matches the rest of the menu.
Review the whole list whenever the menu changes seasonally or when prices or descriptions are edited. Anything with a new garnish, a different side or a changed portion needs a new photo.
- Use lowercase, hyphens or underscores, and no spaces in file names
- Include a version number and the aspect ratio in every file name
- Keep a photo log with item name, file name, date shot and date checked
- Reshoot the item, not the menu, when one dish changes
One set of photos, several destinations
Printed menus, QR menus, your website and delivery listings all pull from the same batch, but they crop differently. A square tile for a delivery listing may be shown small, so check each photo at thumbnail size on a phone before you upload. QR menus are read on a phone at arm's length, so the same thumbnail test applies.
For delivery platforms, check the current upload screen rather than relying on a remembered pixel size. This site publishes spec pages for Uber Eats, DoorDash, Grubhub and BentoBox covering the United States, and those pages are the place to start; where a platform does not publish pixel specs, the upload screen in your merchant dashboard is the authority.
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, which is another reason to reshoot whenever a portion or recipe changes.
- Test every tile at phone thumbnail size before uploading
- Export a square, a landscape and a vertical version of each dish
- Recheck calorie-labeled items against their photos after any recipe change
- Keep the master files; platforms change their display crops over time
Keeping the set current through the year
Set a rhythm: a full reshoot when the menu changes substantially, and single-item reshoots as specials rotate. Seasonal menus in Oakland often shift with what is available locally, so plan the big shoot for a quieter weekday morning when the kitchen can plate without rushing service.
If some items were shot on a phone in poor light, FoodPhoto can improve light, background and crop on a real photo of your own dish for your website menu, QR menu, Instagram, Google Business Profile and print, keeping the food as it is, and each photo comes as a kit of sizes. It cannot guarantee approval by any platform, so always check each platform's own upload requirements.
Checklist before you publish
- Build the shot list from the POS and mark best sellers to shoot first
- Set one permanent table with a fixed surface, background and camera height
- Choose a shooting window based on the season and which way your windows face
- Lock exposure and white balance at the start of each block of dishes
- Shoot every dish at 45 degrees and overhead, in 1:1 and 16:9
- Name files with category, item, version and ratio, and log them in a spreadsheet
- Test each finished photo at phone thumbnail size before uploading anywhere
- Reshoot single items whenever a recipe, portion or plating changes
Questions
How many dishes can I photograph in one day?
It depends on your kitchen and how fast plates can be produced, but most full-menu shoots work in blocks of six to ten items with a short reset between blocks. Group items that are plated similarly and shoot cold items last so they do not sit out. Build in time for a second pass on any dish that does not read clearly at thumbnail size.
What size should menu photos be for delivery apps and QR menus?
Shoot square 1:1 masters for delivery tiles and QR menus, plus a 16:9 or 3:2 landscape version for website headers and printed menu bands. For exact pixel requirements, check the upload screen in each platform's merchant dashboard; where a platform does not publish pixel specs, that screen is the authority. This site's spec pages cover Uber Eats, DoorDash, Grubhub and BentoBox for the United States.
Do calorie-labeled menu items need a matching photo?
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 if a portion, recipe or side changes, reshoot the item and update the listing together.
How do I keep menu photos from going out of date?
Use a naming convention that includes a version number, keep a photo log with the date each item was shot and last checked, and review the list whenever the menu changes. Reshoot only the changed item on the same fixed set so it still matches the rest of the menu. A seasonal full reshoot catches drift across the whole list.