Anaheim Menu Photography for Real Dishes
A full menu needs one consistent set of photos: same light, same angle, same crop, so a printed page, a QR menu and a delivery grid all look like they came from the same kitchen. In Anaheim that is mostly a scheduling problem, because the best light is window light and the window changes with the season. This page covers how to batch shoot, name and keep photos in sync with menu changes.
Shoot in batches, not one dish at a time
Set up once, then work through the menu in groups of similar plates. Group by vessel and color first: white plates together, dark bowls together, baskets and paper-lined trays together. Each group needs its own camera height and exposure, and switching groups mid-session is what makes a menu look stitched together.
A workable order for an Anaheim kitchen: cold small plates and salads, then tacos and handhelds, then seafood and grilled mains, then sides and rice, then desserts and drinks. Shoot the driest, least messy items before the wet ones so sauces and juices do not spread across the table. Budget a few minutes per dish for plating and reset, and keep a printed shot list on the counter with a checkbox per item.
- Same surface for every group: one board, one linen, one color
- Same camera height within a group, usually 45 degrees for plates and 90 degrees overhead for spreads
- Clean the rim and the surface between every dish
- Shoot the item as it is actually served, portion included
Use the Anaheim daylight calendar
Around the June solstice Anaheim gets about 14 h 15 min of daylight and the noon sun sits about 80 degrees above the horizon, so midday light comes almost straight down: harsh on a plate, and useless as soft window light. Around the December solstice there is about 9 h 45 min of daylight and the noon sun is only about 33 degrees up, so low winter sun rakes in through south and west windows for much of the day.
Practical schedule: in summer, shoot early morning or late afternoon and keep the window indirect, using a white wall or a sheer curtain as a diffuser; avoid the 11 a.m. to 3 p.m. window entirely. In winter, the low sun is your friend but it moves fast, so shoot in short blocks and rotate the table rather than moving the light. In spring and fall, the midday hours are workable if you flag the direct sun off the table with a card or a curtain.
- Summer: two blocks, roughly before 10 a.m. and after 4 p.m.
- Winter: one long block from mid-morning to early afternoon, rotating the table
- Any season: put the window to the side of the plate, not behind it
- Check the shadow under the plate; a hard edge means the light is too direct
Angles, crops and file sizes for three destinations
Shoot every dish in two framings: a square for delivery and QR grids, and a wider horizontal for printed menus and the website. A 45 degree angle flatters stacked food like burgers and tacos; a 90 degree overhead keeps a mezze spread or a seafood platter readable because each small plate stays separate. Get close enough that the food fills most of the frame, since thumbnails crop from the edges inward.
For platform pixel sizes, check this site's spec pages: they cover Uber Eats, DoorDash, Grubhub and BentoBox for the United States. Where a platform does not publish pixel specs, check the upload screen in the merchant dashboard, because that is the only place the current requirement is shown. Never upscale a small file to fill a large slot; reshoot or reframe instead.
Name files so the menu and the photos stay in sync
A photo set drifts out of date the moment a price or a portion changes, and the cause is almost always file names nobody can match to a menu line. Use a name built from the menu section, the item and a version: for example small-plates_guacamole_v2, tacos_al-pastor_v3, drinks_house-margarita_v1. Lowercase, hyphens instead of spaces, no dates buried in the middle.
Keep one master list, a spreadsheet with the menu line, the file name, the version and the date shot. When a dish changes, bump the version and reshoot only that item. When a dish is removed, mark the file retired rather than deleting it, so a seasonal item can come back without a new shoot.
- One folder per menu section, one master list for the whole menu
- Version numbers on every file, never 'final' or 'new'
- Retire removed dishes instead of deleting them
- Recheck the list whenever prices or portions change
Keep photos honest, especially where calories are shown
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. That rule applies to independents in practice too: if the photo shows a larger portion than the kitchen serves, or a garnish that is not included, the guest is being sold something the kitchen will not deliver.
Shoot the standard build, then shoot variations separately and label them. If a dish is available in two sizes, photograph both and name them by size. When the recipe changes, the old photo is now wrong, not just dated, and it should be replaced before the next menu print.
Print, QR and delivery from one shoot
One batch session should feed every surface. From each dish, export a square for delivery grids and QR menus, a horizontal for the printed menu and website, and a tight crop for social. Print needs the highest resolution and the least compression; delivery apps recompress heavily, so check the tile at thumbnail size on a phone before you upload.
If you shoot your own real photos and want the light, background and crop tidied for your website menu, Instagram, Google Business Profile, QR menu and print, FoodPhoto can do that while keeping the food as it is, and every photo comes as a kit of sizes. It cannot guarantee approval by any platform, and where a platform bans AI-generated images, shoot and upload your own real photo there.
Menu languages and layout
Anaheim menus commonly run in English and Spanish. If both languages appear on the same printed page, shoot horizontal images with the dish roughly centered so the photo can sit beside either text block without recropping. On a QR menu, keep the square tile and let the language switch happen in the text, not the image, so you do not need two photo sets.
Checklist before you publish
- Build a printed shot list grouped by plate color and vessel
- Pick two shooting blocks that match the current season's window light
- Shoot a square and a horizontal framing of every dish
- Name files by section, item and version before the session ends
- Log every file in one master list with the date shot
- Check each delivery tile at thumbnail size on a phone
- Reshoot any item whose portion or recipe changed
- Keep a Spanish-language layout test for printed pages
Questions
How many dishes can I photograph in one session?
Group similar plates and work in blocks of eight to twelve items, because setup and cleanup between dishes take longer than the shot itself. Cold items and desserts hold up best in a long session; anything fried or sauced should be shot last and plated fresh for each frame.
What time of day is best for window-light food photos in Anaheim?
In summer, shoot early morning or late afternoon because the midday sun is nearly overhead and too harsh. In winter, when the sun stays low, a long late-morning to early-afternoon block works well. Put the window to the side of the plate and diffuse direct sun with a sheer curtain.
Should menu photos be square or rectangular?
Shoot both. Delivery apps and QR menus use square or near-square tiles that survive thumbnail cropping, while printed menus and websites usually want a wider horizontal. Framing the dish slightly loose in the horizontal version lets you crop to square without losing the edges.
How do I keep photos updated when the menu changes?
Use versioned file names tied to menu sections and keep one master list of item, file name, version and date shot. When a dish changes, reshoot only that item and bump the version. Mark removed dishes as retired rather than deleting them.