Skip to content

Tokyo Menu Photography: One Shoot, Every Menu

A Tokyo menu rarely lives in one place. The same gyoza appears on a printed lunch menu, a QR page, a delivery listing and a Google Business Profile, and each version needs a clean, consistent photo. This guide covers how to shoot the whole menu in batches, use Tokyo's window light across the year, and keep image files matched to menu changes.

Plan the shoot around Tokyo's daylight

Tokyo's light changes dramatically between solstices, and that decides when you can shoot by a window without flash. Around the June solstice the city gets about 14 h 25 min of daylight and the noon sun sits about 78 degrees above the horizon, so direct sun falls steeply and briefly. Around the December solstice you get about 9 h 35 min and the noon sun is only about 31 degrees high, so low sun reaches deep into a room and stays there for hours.

  • December to February: low sun at about 31 degrees at noon pushes far into the dining room. Shoot between 10:00 and 14:00 with a sheer curtain or a white shoji screen as a diffuser, and watch for hard stripes across the table.
  • March and October: mid-height sun gives soft, workable light most of the day. Use these months for large batch days when you need many dishes done quickly.
  • June to August: the sun is about 78 degrees at noon, so window light is steep and short. Shoot earlier or later in the day, or move the table half a meter back from the glass to avoid a hot band of light on the plate.
  • Year-round: book two sessions per shooting day, one in late morning and one in early afternoon, and keep the same table position so shadows and background stay consistent across the menu.

Batch shooting a full menu

Group dishes by how they are made and plated, not by where they sit on the menu. Ramen, udon and soba bowls can be shot back to back while the broth station is hot; sushi and sashimi together while the counter is cold and clean; fried items like tempura and tonkatsu in one run so oil temperature and batter color stay uniform. This keeps the kitchen calm and makes the photos look like one menu rather than a collection of separate shoots.

Set the camera at a consistent height and distance for each group. A 45-degree angle suits bowls and plates with height, a straight overhead shot at 90 degrees works for flat presentations and set trays, and a low 15 to 20 degree angle flatters stacked or tall items. Lock the white balance manually instead of leaving it on auto, because a bowl of ramen and a plate of sashimi will otherwise render with different color temperatures. Keep one small reference card in the first frame of each batch to confirm focus and exposure before you continue.

Shoot for print, QR and delivery in one pass

Shoot wider than any single use needs. A frame with a little empty space around the plate can be cropped to 1:1 for delivery tiles, 16:9 for a website banner and a taller ratio for a printed menu column. If you crop tight in camera, you lose the ability to reformat later. Leave the rim of the plate visible in the master file so the dish reads clearly at thumbnail size.

For delivery listings, check the current requirements on the platform's own upload screen. This site has spec pages for Uber Eats Japan, Square Online Japan and Yelp Japan, and those pages cover what each platform asks for. Demae-can also operates in Japan; check its merchant materials directly for its image rules. Japanese is the language menus are commonly written in nationally, so keep dish names in Japanese in the master file and add a second language only if your own customers need it.

Name and store files so the menu stays in sync

A photo library falls apart when file names are generic. Use a fixed pattern: menu category, Japanese dish name, a two-digit sequence, and the date of the shoot. For example, a ramen dish shot in October 2025 becomes ramen-shoyu-01-2025-10. Sort files by category in folders that match your menu sections, and keep the master files separate from the cropped exports you upload.

When a dish changes, reshoot only that item and give it a new date in the file name. Keep the old file but move it to an archive folder so nobody uploads last season's photo by mistake. Maintain a simple list with one row per menu item: file name, date shot, and where it is published. Update the row whenever a price, portion or garnish changes, because a photo of a bowl with a missing topping is worse than no photo.

Keeping photos current as the menu changes

Seasonal menus in Tokyo move quickly, and printed menus, QR pages and delivery listings rarely update on the same day. Decide which channel is the source of truth and refresh the others from it. If the printed menu is reprinted quarterly, treat that as the moment to review every photo, retire images of discontinued items and reshoot anything whose plating has drifted.

QR menus are the easiest to keep current, so use them to test new dishes before committing to print. When you change a photo on a delivery listing, check how it looks in the small tile on a phone, not on a desktop monitor. A dish that reads well at full size can turn into an unreadable brown shape at thumbnail scale.

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, and every photo comes as a kit of sizes. For your own channels such as the website menu, Instagram, a QR menu or print, that kit saves reformatting the same dish several times.

Practical checks before you upload

Before publishing a batch, review the images together on one screen at the size customers will see them. Look for color drift between dishes, plates that are cut off at the edge, and backgrounds that changed between batches because the table moved. Fix these in the master files rather than patching individual exports.

Finally, confirm that the photo matches what the kitchen sends out today. Delivery customers compare the image with the container they open, and printed menus are checked against the plate on the table. A modest, accurate photo builds more trust than a styled one that no longer resembles the dish.

Checklist before you publish

  1. Measure your window light at noon in June and December before booking shoot days.
  2. Group dishes by preparation station and shoot each group in one continuous run.
  3. Lock white balance and camera height for each group of dishes.
  4. Frame with spare space around the plate so you can crop to 1:1 and 16:9 later.
  5. Name every master file with category, dish name, sequence and shoot date.
  6. Keep a one-row-per-dish list of file names, shoot dates and where each is published.
  7. Review new photos at phone thumbnail size before uploading to any delivery listing.
  8. Reshoot any dish whose portion, garnish or container has changed.

Questions

What time of day is best for photographing food by a window in Tokyo?

It depends on the season. In December the noon sun is only about 31 degrees high, so low light reaches far into the room and late morning to early afternoon works well with a diffuser. In June the noon sun is about 78 degrees, so light is steep and short; shoot earlier or later, or move the table back from the glass.

How many photos do I need per dish for print, QR and delivery?

Shoot one wide master per dish and crop from it. You need a square version for delivery tiles, a wide 16:9 version for website banners, and a taller crop for printed menu columns. Keeping the master uncropped means you can make all three without reshooting.

How do I keep menu photos updated when dishes change?

Use a dated file name for every master, archive old files instead of deleting them, and keep a list with one row per dish showing the file name, shoot date and where it is published. Reshoot only the changed dish and update the row.

Where can I find image size requirements for delivery apps in Japan?

Check the platform's own upload screen, since requirements can change. This site has spec pages for Uber Eats Japan, Square Online Japan and Yelp Japan. For other apps operating in Japan, including Demae-can, use the platform's merchant documentation.

Start with a dish