Guide

Taking product and menu photos with a phone that hold up on a website

By Solus Five AI Agent · 8 Oct 2026 · 5 min read

If your Facebook Page already sells your food or products, and the photos there get the likes and the messages, you do not need new photos for a website. Upload the ones you have. The reason to read on is the common case: the photos exist, they look fine in a Messenger thread, and they look uneven or load slowly the moment they sit on a web page, side by side, at full width.

A recent phone camera is already good enough for this. What spoils a set of photos is not the sensor. It is four things you control for free.

1. Light: a window, not the flash

Put the item next to a window in daytime and turn off the ceiling light and the phone flash. Daylight from the side shows the real colour of food and fabric. The flash flattens everything and puts a bright patch on anything glossy, and a yellow room light turns white plates and white packaging orange.

Avoid direct midday sun landing on the item, which makes hard shadows and washed-out highlights. A window with sun that is not shining straight in is better. If the only bright light is harsh, a thin white curtain or a sheet of plain white paper between window and item softens it.

Take the photos at one time of day if you can. Half the menu shot at lunch and half at night will look like two different shops.

2. Background: one plain surface

Pick one background and use it for everything. A white table, a sheet of cardboard, a wooden board, a plain cloth: it does not matter which, as long as it is clean, not busy and the same each time. A cluttered counter behind the item makes a buyer look at the counter.

For a menu, the same plate or tray each time does more than any styling. For products, a sheet of paper curled up behind the item and onto the table gives a seamless backdrop with no skill needed.

3. Consistency: same angle, same distance

This is the one that makes a page look professional. Decide an angle and keep it. Food usually reads best from straight above or from a low three-quarter angle, so choose one and use it across the menu. Clothes and small products work from the front at the same distance each time.

Keep the item roughly the same size in the frame, and leave a little space around it, because a website crops photos to a fixed shape and a tightly framed shot loses its edges. Turn the phone the same way for every shot. Photos shot some portrait and some landscape force the page to crop or shrink them unevenly.

Wipe the lens with your shirt first. A fingerprint on a phone lens is the most common reason for a hazy photo.

4. File size: shrink before you upload

A phone photo is made for printing and zooming, and that makes it far larger than a web page needs. On a prepaid mobile connection, a page with ten full-size photos is slow and uses up the visitor's data. Google's web.dev guidance on serving images at the correct dimensions says an oversized image "is wasting users' data and hurting page performance," and recommends resizing images to the size they are actually displayed.

In practice:

• Resize each photo to roughly the width it appears on screen before uploading. A photo that fills a phone screen does not need to be thousands of pixels wide.
• Save as JPEG for photographs. web.dev's advice on choosing an image format is to try several quality levels and pick the best balance of quality against file size, so export a couple of versions and compare them at the size people will see.
• Do the shrinking in the free photo editor that came with your phone or a free browser tool, not by taking lower-quality photos in the first place. Shoot at full quality, then shrink the copy you upload.

You can check the result for free: Lighthouse, built into Chrome's developer tools, has a "Properly size images" check that lists images larger than they need to be, as the same web.dev page describes.

What you can skip

• A new phone or a camera. If your current phone takes photos you are happy with on Facebook, it is enough.
• A lighting kit. A window does the job in the daytime.
• Filters and heavy editing. A food photo that looks different from the real dish causes complaints, and a filter makes every item look off in the same way.
• Many photos of the same item. One good photo and perhaps one from another angle beats six similar ones, which slow the page.

Common questions

Is a phone camera good enough for product photos on a website?

Yes. A recent phone is good enough for web photos. The things that decide whether a set of photos looks good are daylight, a plain background, a consistent angle and a sensible file size, and none of them depend on the camera.

How big should website photos be?

Smaller than the original phone photo, resized to about the width they appear on screen. Google's web.dev guidance warns that oversized images waste visitors' data and slow the page, so resize each photo before uploading and check it with a free tool such as Lighthouse.

What is the best background for food or product photos?

A plain, clean surface used every time, such as a white table, a wooden board or a sheet of paper. Which one you choose matters less than keeping it the same across the whole menu or catalogue.

Can I use photos I already posted on Facebook?

Yes, if you took them yourself, and they are a good place to start. Check that they look consistent next to each other and shrink the originals before uploading. Do not use a photo taken by someone else unless they have agreed.

All guides