Minneapolis Menu Photography for Print, QR Menus and Delivery Apps
A Minneapolis menu has to work in three places at once: a printed page, a QR menu on a phone screen, and a grid of delivery-app tiles. This guide covers how to shoot a full menu consistently, when to use window light in a city that swings from about 15 h 25 min of daylight in June to about 8 h 35 min in December, and how to keep photos in sync when dishes and prices change.
Plan the shoot around Minneapolis daylight
Minneapolis sits at about 44.98 degrees north, which means window light changes dramatically across the year. Around the June solstice the noon sun is roughly 68 degrees above the horizon and the day runs about 15 h 25 min. Around the December solstice the noon sun is only about 22 degrees high and daylight drops to about 8 h 35 min. A north-facing window gives the most even light year-round; a south window floods in summer and barely reaches the room in winter.
Build a seasonal shooting schedule instead of guessing on the day. In late spring and summer, shoot between 9 and 11 a.m. or after 4 p.m. to avoid the steep noon sun that throws hard shadows across plates. In winter, the low sun comes straight into south windows, so shoot midday near the window or move to a north window entirely. Book large batch shoots in the shoulder months (March, April, September, October) when the sun is moderate and the light is easiest to repeat from one session to the next.
- June: shoot before 11 a.m. or after 4 p.m.; diffuse direct sun with a sheer curtain.
- December: shoot between 11 a.m. and 2 p.m. at a south or west window; expect short working hours.
- Year-round: a north-facing window and a white foam board as a bounce card keep light consistent.
- Overcast days in any season give soft, repeatable light for a full menu in one session.
Batch shooting a full menu in one or two sessions
Shooting one plate at a time over weeks produces a menu that looks like it came from different restaurants. Instead, group dishes by how they photograph: bowls and salads, handhelds, plates with sauces, desserts and drinks. Set up one station, keep the camera in the same position and shoot each group back to back. A 45-degree angle works for most plated dishes; a straight overhead (90 degrees) works for bowls, pizzas and flat lays; a low 20 to 30 degree angle suits burgers and stacked sandwiches.
Work from a written shot list built from your current menu, not from what the kitchen feels like sending out. Ask the kitchen to plate every item to the same standard the customer receives, and shoot the dish within two minutes of plating so sauces do not set and garnishes do not wilt. Keep a notebook or spreadsheet with the dish name, menu section, price and the file name as you go. That log is what makes the next step, naming and syncing, possible.
- Shoot 8 to 12 dishes per session to keep plating quality up.
- Use one background (a slate tile, a wood board or a plain linen) for the whole menu.
- Shoot a square 1:1 frame for delivery tiles and a wider 16:9 frame for banners and your website hero.
- Capture a clean plate shot and, where useful, one in-context shot with a hand or utensil for social.
File naming and keeping photos in sync with menu changes
Delivery apps and QR menus change more often than printed menus. Name every file with the dish, the menu section and a date, for example `burger-classic-2025-03.jpg`, so anyone on staff can find the right image when a price or description changes. Keep a master folder and a published folder; only images in the published folder go to the apps and the website. When a dish is removed or replaced, archive its photo in the same move so it does not reappear on a tile by accident.
Printed menus and QR menus need a version check before every reprint or QR update. Walk the menu line by line against the photo log: does every item have a current photo, does the photo match what the kitchen sends out, and is the price current? If a portion size or garnish changed, reshoot rather than reuse. For QR menus, a dated PDF or web page tied to the same log keeps the photo and the description aligned.
- Use a consistent pattern: `section-dish-YYYY-MM.jpg`.
- Keep one master folder and one published folder; never upload from a phone camera roll.
- Log every dish name, section and shoot date in a shared spreadsheet.
- Recheck the log before each print run and each QR menu update.
Matching photos to calorie and menu-label 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 your calorie listing is for a standard build, the photo should show that standard build, not an upgraded version with extra cheese or a side that is not included. Independent Minneapolis restaurants are not covered by the chain rule, but if you publish calorie or nutrition information voluntarily, the same principle applies: the photo and the numbers should describe the same plate.
For multilingual menus, Minneapolis menus commonly appear in English and Spanish. Keep the photo tied to the dish, not the language, so one image serves both versions of the menu. If a dish name differs between the English and Spanish menu, note both names in the file log so staff can find the right photo quickly.
Platform specs and where to check them
Delivery platforms change their image requirements without much notice, and not every platform publishes pixel specs publicly. This site keeps 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 the merchant dashboard, which shows the current crop and size before you save.
If a platform bans AI-generated images, shoot and upload your own real photo of the dish to that platform. Do not label any image as ready for a specific platform; approval is always the platform's decision. For your own channels, such as your website menu, Instagram, Google Business Profile, a QR menu or printed material, you control the crop and format, which makes it easier to keep one master image and export the sizes you need.
- Uber Eats: see /delivery-photo-specs/uber-eats/united-states/
- DoorDash: see /delivery-photo-specs/doordash/united-states/
- Grubhub: see /delivery-photo-specs/grubhub/united-states/
- BentoBox: see /delivery-photo-specs/bentobox/united-states/
A practical workflow for Minneapolis menus
Start with the menu itself: list every item, note which need photos and which are already covered, and group them for batch shooting. Shoot in one or two sessions using the seasonal light guidance above, name files as you go, and update the log the same day. Then export the sizes you need: a square tile for delivery apps, a wider image for the website and a print-ready file for the printed menu. Recheck the log before each print run and each QR menu update.
FoodPhoto takes a real photo of the restaurant's own dish and improves light, background and crop for menus, delivery apps and social, keeping the food as it is. Every photo comes as a kit of sizes, including a hero image, delivery-app sizes, Instagram formats and Google Business Profile, so one shoot can feed every surface your menu appears on.
Checklist before you publish
- Write a shot list from the current menu and group dishes by type before the session.
- Pick a window and time of day based on the season and the sun angle.
- Set one camera angle per dish type and keep the background consistent.
- Shoot within two minutes of plating so sauces and garnishes hold.
- Name every file with section, dish and date as you shoot.
- Keep master and published folders separate and upload only from published.
- Recheck the photo log against the menu before each print run and QR update.
- Confirm current image specs in each platform's upload screen before publishing.
Questions
How do I photograph a whole menu without hiring a photographer?
Shoot in batches by dish type at one window with consistent light and background, use a written shot list from your current menu, and shoot each plate within two minutes of plating. A phone on a small tripod at a fixed angle is enough if the light is soft and the background does not change between dishes.
When is the best time of year to shoot menu photos in Minneapolis?
The shoulder months, roughly March, April, September and October, give moderate sun that is easy to repeat between sessions. In June the noon sun is about 68 degrees high and daylight runs about 15 h 25 min, so shoot early or late. In December the sun is only about 22 degrees high with about 8 h 35 min of daylight, so shoot around midday at a south or west window.
Do delivery apps require photos for every menu item?
Requirements vary by platform and change over time, and some platforms do not publish detailed pixel specs publicly. Check the upload screen in each merchant dashboard, which shows the current crop and size, and confirm the platform's current photo policy before relying on any image.
How do I keep menu photos current when dishes or prices change?
Name files with section, dish and date, keep a shared log of every dish and its photo, and recheck the log before each print run and QR menu update. Reshoot when a portion or garnish changes rather than reusing an older image, and archive photos of removed dishes so they do not reappear on a tile.