Cape Town Menu Photography: A Consistent Full-Menu Shoot

Plan the shot list before you plan the lighting

Build the list from the live menu, not from memory. Export every item from your POS or menu file into a spreadsheet with one row per dish and columns for section, price, allergens, current photo file name and status. Group rows by station: cold and raw, fried, grilled, curries and stews, starches and sides, desserts, drinks. A braai or grill plate, a line-fish dish and a Cape Malay curry each behave differently on camera, so grouping by kitchen station keeps the food at its best when it reaches the table.

Decide the count per dish. Most menus need one hero image per item, plus one wider shot for anything you want to feature on a QR landing page or a printed spread. That wider shot is where a seafood platter or a shared grill board earns its place; individual plates rarely need more than one angle.

Book the shoot around your service, not through it. Cape Town kitchens often run a quieter mid-afternoon window between lunch and dinner, which is when plating can be slowed down without tickets stacking up. Confirm with the chef which dishes can be plated off-menu for the camera and which must be pulled from a live order.

• One spreadsheet row per dish, with section, station and current file name
• One hero angle per item, one wider shot for feature dishes only
• Shoot between services, not during a rush
• Agree plating standards with the chef before the day

Use Cape Town's daylight deliberately

Cape Town's daylight swings hard between seasons, and that changes how you light a table by a window. Around the December solstice the city gets about 14 h 16 min of daylight and the noon sun sits about 80 degrees above the horizon. Around the June solstice that drops to about 9 h 44 min, with the noon sun only about 33 degrees high. A high summer sun throws short, hard shadows and floods a north-facing window with intensity; a low winter sun rakes across the room at a shallow angle and gives softer, longer, more directional light.

That gives you a workable seasonal schedule. In summer, shoot early morning or from mid-afternoon onward, when the sun is lower and the window light is less brutal; avoid the middle of the day near a window unless you diffuse it with a scrim or a white sheet. In winter, the low sun is your ally for most of the day, but the usable window is shorter, so batch the most difficult dishes first.

Position the table so the window sits to one side of the plate, roughly 45 degrees, rather than directly behind or in front of it. That gives shape to a bowl of curry and texture to a grilled crust. Keep the camera at about 45 degrees above the plate for most dishes and drop to a straight overhead 90 degrees for flat items like a pizza or a salad spread. Diffuse direct sun with a translucent panel; bounce a little light back into the shadow side with a white card or foam board.

Batch the shoot so the whole menu matches

Consistency comes from repetition, not from a single perfect frame. Set the camera on a tripod, lock the height and distance for each dish size, and keep the same background, the same surface and the same light for every item in a section. If you change the background halfway through the mains, the delivery grid will look like two different restaurants.

Work in station batches: shoot all cold dishes together, then all fried, then all grilled, then desserts. This reduces the number of times the kitchen has to reset and keeps similar textures lit the same way. Shoot each dish in a short burst, review on a laptop rather than the camera screen, and reshoot on the spot rather than discovering a soft focus problem after the food is gone.

Keep a simple shot log: date, dish, angle, file name, and whether it passed review. That log is what lets you add a new special next month without re-shooting the whole menu.

• Fixed tripod height and distance per dish size
• Same surface, same background, same light per section
• Shoot in station batches, review on a laptop
• Log every file with dish, angle and pass or fail

Name files so the menu and the photos stay in sync

Use a naming pattern that mirrors the menu structure, for example section-dishname-angle-date, in lowercase with hyphens and no spaces. A file called mains-linefish-grilled-hero-2025-11.jpg tells you what it is, where it belongs and when it was shot without opening it. Delivery dashboards and menu systems often sort alphabetically, so a consistent prefix keeps a section grouped together when you upload in bulk.

Keep a single master folder with subfolders per section, and a master spreadsheet that maps each menu item to its current file. When a dish changes, a price changes or an item is removed, update the spreadsheet the same day and move the old file into an archive folder rather than deleting it; you may bring the dish back seasonally.

Export at the sizes you actually need. Keep a high-resolution master, a version for print at 300 dpi at the printed size, and a square 1:1 crop for delivery tiles and social. Check the upload screen for each platform before you export: this site publishes a photo spec page for Uber Eats in South Africa, and where a platform does not publish pixel specs, check the upload screen itself rather than guessing.

Keep photos in sync as the menu changes

Menus move faster than photo shoots. Set a monthly review: pull the live menu, compare it to the master spreadsheet, and flag any item with a missing photo, an outdated photo or a photo of a dish that no longer exists. Seasonal specials, price changes and new dishes are the usual culprits.

When you shoot a new dish, match it to the existing set: same surface, same angle, same light direction. A single new photo that looks different from the rest will stand out in the grid for the wrong reason. If the kitchen has changed a dish substantially, such as a different plating or portion, reshoot rather than reuse.

For printed menus and QR menus, keep a print-ready folder and a web-ready folder side by side, both named from the same master list, so a reprint and a QR update pull from the same source. When you refresh the QR menu, check the mobile view in daylight, since a phone screen in bright Cape sun is less forgiving than a desktop monitor.

FoodPhoto takes a real photo of your own dish and improves light, background and crop for menus, delivery apps and social, keeping the food as it is, and every photo comes as a kit of sizes. For your own channels such as a website menu, Instagram, Google Business Profile, a QR menu or print, that kit saves exporting each size by hand. It cannot guarantee approval by any platform, so always check each platform's own requirements.

Platform and language details worth checking

In South Africa, the delivery apps listed here are Uber Eats and Mr D. Image requirements differ between them, and they can change, so confirm on the upload screen before a batch export. This site's published spec page covers Uber Eats for South Africa; for Mr D, check the merchant upload screen directly.

Menus in South Africa are commonly written in English, Afrikaans and Zulu. If you produce more than one language version, keep the same photo set across them so the dish looks identical whichever version a customer opens, and name the files with a language tag so the versions do not get mixed up.