Menu Photography in Jakarta: One Consistent Set for Print, QR and Delivery

Plan one shoot around your actual menu

Start by exporting your current item list from the POS or the delivery-app dashboard. Group dishes by how they are plated: rice plates such as nasi goreng, bowls of soto or bakso, skewered satay on a plate, and drinks. Shooting in these groups means the same lens height, background and garnish routine apply to every item in the group, so the finished set looks like one menu rather than a scrapbook.

Decide the master aspect ratio before you shoot. A 1:1 square master survives most delivery grids and prints cleanly on a QR menu; a 16:9 master suits a website header but wastes pixels in a square tile. For most Jakarta menus, shoot square and keep the dish centered with breathing room, then crop wider versions later if a printed layout needs them.

Book a half day for a menu of roughly 30 to 40 items if you are working alone. Fewer items or a helper will shorten that; a large menu with many garnishes will stretch it. Shoot the top-selling items first so that if the day runs short, the dishes that carry the most orders are already covered.

Use Jakarta's window light on a seasonal schedule

Jakarta sits close to the equator, so midday sun is high and harsh most of the year. Around the December solstice the city gets about 12 h 22 min of daylight and the noon sun reaches about 73 degrees above the horizon; around the June solstice it gets about 11 h 38 min and the noon sun reaches about 60 degrees. The lower June sun throws longer shadows, which matters if you shoot near a window.

For soft window light, shoot in the morning or late afternoon rather than at noon. Place the table beside a window that faces away from direct sun, so light comes in from the side. If the sun hits the table directly, hang a thin white curtain or tape a sheet of tracing paper to the glass. A white foam board opposite the window bounces light back into the shadow side of the plate.

Build a simple seasonal calendar. From roughly October to February, when the noon sun is highest, use the early morning window and keep the table pulled back from the glass. From roughly April to August, when the sun is lower, expect longer shadows and either shoot later in the afternoon or move the table further from the window. In the weeks around the equinoxes, light changes fastest, so shoot in a tighter block and check the first few frames before committing the whole menu.

Keep the camera at roughly 30 to 45 degrees above the plate for most dishes, and drop to table level for tall items like a bowl of bakso or a stacked rice dish. Lock white balance manually on a white card at the start of the session; mixed window light and kitchen fluorescents will otherwise make half the menu look blue and half yellow.

Batch shooting without losing consistency

Set up one station with a fixed background, a fixed camera height and a fixed light position, and do not move them between dishes. Use a tripod or a stack of books marked with tape so the camera returns to the same spot. Keep a small tray of garnish, a clean cloth and a brush at the station so plates leave the kitchen looking the same as the reference shot.

Shoot in small batches of five to eight dishes, review them on a laptop or tablet, then continue. Reviewing mid-session catches a drifting background or a greasy rim before it repeats across the whole menu. For each dish, take one straight-on frame, one at 45 degrees, and one close crop of the key texture, such as the char on satay or the surface of a soto. That gives you options for a square tile, a wide banner and a detail shot.

Keep a shot log as you go: item name, batch number, which frame is the keeper. A simple spreadsheet row per dish is enough. Without it, a 40-item shoot turns into an afternoon of guessing which file is which.

Name and store files so the menu stays in sync

Use a file name that carries the item and the version: for example nasi-goreng_2025-03_sq-01.jpg. Include the aspect ratio or crop in the name so the print designer and the person uploading to delivery apps pick the right file without opening it. Keep one folder per menu version and archive the previous one rather than overwriting it.

When a dish changes, reshoot it at the same station with the same background and settings, then replace only that file. Because the naming convention matches, the new photo drops into the printed layout, the QR menu and the delivery listing without a hunt. Review the whole set once a quarter and after any recipe or plating change.

Check each delivery app's upload screen for its current image requirements before you export. The apps operating in Indonesia that this site's spec pages would cover are GoFood, GrabFood and ShopeeFood, but no spec pages are published on this site for them, so confirm size limits and crop behavior on the upload screen itself rather than relying on an old screenshot.

Match the set to print, QR and delivery surfaces

A printed menu needs enough resolution for the final print size and a crop that leaves room for the price and description. A QR menu is viewed on a phone, so a square image at a modest file size loads faster than a full-resolution original. Delivery tiles are small and often cropped square, so the dish should fill most of the frame with the garnish visible at thumbnail size.

Export three versions from each master: a square for delivery and QR, a wider crop for print or web headers, and a tight detail crop for social posts. Keep the master file untouched and treat the exports as derivatives. This is where FoodPhoto fits for a restaurant's own channels such as the website menu, Instagram, Google Business Profile, QR menu and print: it takes a real photo of the restaurant's own dish and improves light, background and crop while keeping the food as it is, and every photo comes as a kit of sizes.

For delivery apps, upload your own real photographs shot at the station described above. No tool can guarantee that a platform will approve an image, so check each app's rules on the upload screen and keep the originals on file in case a listing is queried.