Menu Photography in Milwaukee: Batch Shooting a Full Menu

Plan the shoot around Milwaukee's daylight

Milwaukee's light changes a lot between solstices. Around June the city gets about 15 hours 11 minutes of daylight and the noon sun sits about 70 degrees above the horizon, so window light is strong and high for much of the working day. Around December you get about 8 hours 49 minutes and the noon sun is only about 24 degrees up, which means low, raking light through windows and a much shorter usable window.

That argues for scheduling the full-menu shoot in late spring or early summer, when the daylight block is long enough to cover 30 to 60 dishes in one or two days. If a menu change lands in winter, shoot the new items in a tighter midday block and match the look to the summer set by diffusing the window with a scrim and filling from the same side as the original shoot.

Keep a written note of the light setup for each shoot: window used, time of day, diffusion and fill position. When you add a dish in February, you can reproduce the July look instead of guessing.

• Summer: book the shoot between mid-morning and mid-afternoon, when the high noon sun gives you the longest consistent block
• Winter: keep the shoot inside a two to three hour midday window and expect low-angle light that needs diffusion
• Record the time, window and diffusion used for each batch so later additions match

Build a repeatable shooting station

Consistency comes from a fixed station, not from a good photographer. Pick one table near a window, tape its position on the floor, and mark where the tripod legs go. Use the same surface, the same two or three backgrounds and the same plateware across the menu so the delivery grid reads as one set.

Shoot every dish from the same camera height, roughly 45 degrees for plates and straight down for bowls and pizzas, and keep the same distance so each tile has a similar crop. Lock white balance manually instead of leaving it on auto, because auto white balance will drift as clouds move and make half the menu look warm and half look cool.

Aim for a handful of frames per dish (somewhere around ten is a workable starting point, though it depends on how many garnishes and angles you want), then pick one keeper immediately rather than sorting hundreds of files later.

• Tape the table and tripod positions so every session starts from the same spot
• Fix camera height and distance per dish type: 45 degrees for plates, overhead for bowls and pizza
• Set white balance manually and leave it locked for the whole batch
• Shoot a plate of cheese curds or a butter burger first as a test frame before committing the day

Match photos to calorie and menu 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. The practical rule for photography is simple: a photo must match the item the calories describe.

That means a photo of the dish as it is actually served, with the standard portion and the standard sides. If your photo shows extra fries, a larger pour or a garnish the kitchen does not always include, the picture and the calorie figure stop describing the same plate. Shoot the standard build, and photograph variations as separate items only if they carry their own calorie figure.

Menu languages are a separate decision. Milwaukee restaurants list English and Spanish in their materials where it suits their customers, but the photo does not change with the language. One image set serves both, as long as the dish pictured is the dish named.

Name files so the menu and photos stay in sync

The most common menu-photo failure is not bad lighting, it is a photo of last season's dish sitting next to this season's description. A naming convention prevents most of it. Use a short code for the item, the version date and the size, for example fish-fry-2025-06-hero or fish-fry-2025-06-square.

Keep one master list, a spreadsheet is enough, with columns for item code, menu section, price band (not the price itself), photo file, shoot date and status. When a dish changes, mark the row and reshoot only that item. When a dish is removed, archive its files rather than deleting them, so a returning special can be found again.

Delivery apps and QR menu builders often let you upload a photo per item. If the app does not publish pixel specs, check the upload screen itself for its stated requirements rather than relying on a blog post. This site keeps spec pages for Uber Eats, DoorDash, Grubhub and BentoBox in the United States, and those pages are the place to start before a batch upload.

Refresh the set when the menu changes

Treat the menu photo set as a living document with a review date, not a one-time project. A simple rhythm works: a full reshoot when the menu is substantially redesigned, and item-level reshoots whenever a dish, portion or plating changes. Seasonal specials get their own short shoot and their own file prefix.

Printed menus and QR menus go stale at different speeds. Print runs lock a photo set for months, while a QR page can be updated the same day. Keep the print set and the digital set named with the same item codes so you can update one without hunting through folders.

When you shoot, capture one extra frame of each dish on a plain background. It costs seconds on the day and gives you a clean image for social posts, Google Business Profile and press requests later.

• Set a review date for the full photo set and put it in the same calendar as menu revisions
• Reshoot an item when its portion, plating or name changes
• Keep print and digital files under the same item codes
• Archive removed dishes instead of deleting them

Where FoodPhoto fits

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 back as a kit of sizes, which helps when the same fish fry has to appear on a printed menu, a QR page and a delivery tile. It cannot guarantee approval by any platform, so always check each app's own upload requirements.