Web Design13 October 2026 · 5 min read

Menu photography that sells without killing the page

A phone held over a table in a restaurant at service time

Food photographs sell food. They also, done the way most sites do them, add four megabytes to a page and cost you the customer before the picture has finished loading. Both of those things are true at once, and the job is getting the first without the second.

Why menu photographs are worth the trouble

People order what they can see. On a menu with pictures on some items and not others, the pictured items sell disproportionately, which is a lever worth having on the dishes with the best margin.

They also reduce the thing that costs you most on a first order: hesitation. A customer who does not know what a dish looks like either asks, which ties up the phone, or orders the thing they already know.

What a usable photograph is

One dish, close, from above or just off it. A tray of six dishes photographs badly and crops worse.
Daylight, near a window, no flash. A phone in daylight beats a camera under fluorescent tubes. The reason restaurant photographs look yellow is the kitchen lighting, and no filter fixes it properly.
The real portion, in your real packaging. A photograph that flatters the dish beyond what arrives is a complaint you have scheduled for later.
Shot square. Every system will crop it; square survives every crop.

The part that kills the page

A modern phone takes a photograph of about four megabytes. Twenty of those on one menu page is eighty megabytes, and on a phone on a bus that page does not load at all. The customer does not report a slow site, they go to the app instead.

What fixes it is unglamorous and should be the system’s job, not yours: convert to a modern format, resize to the sizes actually displayed, serve the right size for the screen, give every image fixed dimensions so the page does not jump while it loads, and load the ones below the fold only when they are needed. Done properly the whole menu weighs less than one untouched photograph. We cover the mechanics in why your website is slow.

Not every item needs one

Photograph the dishes that sell, the ones you want to sell, and anything a customer cannot picture from its name. Chips do not need a photograph. A house special with a name nobody outside the shop understands absolutely does.

Half a menu photographed well beats a whole menu photographed badly, because inconsistent photography reads as a cheap site and a cheap site reads as a cheap kitchen.

Getting the images right is part of the build on web design, and how they are served inside an ordering menu is part of ordering platforms.

Questions

Before you ask.

Do menu photographs increase orders?

Yes, and unevenly: on a menu where some items have pictures and some do not, the pictured items sell disproportionately. That makes photography a lever worth pointing at the dishes with the best margin.

How should I photograph food for a menu?

One dish at a time, close, in daylight near a window with no flash, shot square so every crop works, showing the real portion in your real packaging. Kitchen lighting is what makes most restaurant photographs look yellow.

Why do food photographs make a website slow?

A phone photograph is around four megabytes. Twenty of them on a menu page is eighty megabytes, which on a phone on a bus does not load at all. The customer does not report a slow site, they open an app instead.

How do you stop photographs slowing a menu down?

Convert to a modern format, resize to the sizes actually shown, serve the right size for the screen, give every image fixed dimensions so the layout does not jump, and load below-the-fold images only when needed.

Does every menu item need a photograph?

No. Photograph what sells, what you want to sell, and anything a customer cannot picture from its name. Half a menu photographed well beats a whole menu photographed badly, because inconsistent images read as a cheap site.