Food Photos for Your Restaurant Website: Speed, Size, and Trust

Website food photos should match the display size, load fast on a phone, and show the dish the kitchen actually serves. Score your menu photo first, then compress it.

Your website is the only place your food photos play by your rules. No moderation queue, no forced crop, no single-item mandate. That freedom cuts both ways: nothing stops you from publishing a slow, dim, five-year-old gallery either. On your own site, the constraints that matter are speed, consistency, and honesty.

On this page
  1. What website photos do
  2. Sizing and performance
  3. Common mistakes
  4. Getting website-ready photos fast

What website photos have to do

A visitor on your site is one step from a reservation or an order. The photos have three jobs:

  • Prove the food is good. One strong, bright hero shot of a signature dish does more than a carousel of mediocre ones.
  • Load fast on a phone. Most restaurant traffic is mobile, often on a weak connection while deciding where to eat. Every half-second of image loading works against you.
  • Match reality. The website sets expectations that the plate then has to meet. Photos that oversell create the one-star review that mentions them.

Sizing and performance

There is no platform spec sheet here, so the guidance is practical rather than mandated:

Use Practical target
Full-width hero image Around 1600 to 2000 px wide
Menu grid or card images Around 600 to 800 px wide
Format Compressed JPG or WebP for photos
Weight A few hundred KB per image at most

Keep the camera originals at full resolution in your archive and export smaller copies for the web. The originals are what you will re-crop for food photos for Instagram, delivery platforms, and print later; the exports are what browsers should be given. Add descriptive alt text to each image while you are at it.

Common website food photo mistakes

  1. Uploading camera originals. A page of 8 MB photos can take many seconds to load on mobile data. This is the single most common self-inflicted wound on restaurant sites.
  2. Mixed-era galleries. Photos from three phones across five years, in three color temperatures. Batch-reshooting once beats patching forever.
  3. Stock food photos. Visitors recognize stock, and the gap between the stock pasta and your pasta erodes trust before anyone orders.
  4. Dark, warm interior shots as food backdrops. Ambient dining light photographs murky. Read how to fix dark food photos before you publish for shooting and correction.
  5. Soft focus at hero size. Blur that hides in a delivery thumbnail is obvious at full width. The guide on how to fix blurry menu photos at hero size explains which soft photos are rescuable and which need a reshoot.
Underexposed phone photo of a beef stir fry sitting in shadow under dim restaurant lighting
The same beef stir fry photo corrected to a bright, even exposure
BeforeAfter
A dim dining room shot of a beef stir fry, and the same photo after a MenuCapture exposure edit. At hero size on a website, the difference is obvious.

Getting website-ready photos fast

Shoot one consistent batch: your hero dishes plus anything the menu page will show, same window light, same angles, following our guide on how to take food photos with your phone in one batch. The restaurant photography planning guide covers the shot list so one session covers the site, delivery apps, and social at once, and menu photography basics collects the rest.

Editing is where consistency is won. MenuCapture edits each real photo from a text prompt, "bright neutral lighting, clean background, keep the dish as shot," so a batch shot across a whole afternoon still lands with one look. It costs $19 per month or $159 per year, with up to 300 edits a month, and because every output is an edit of your actual dish, the website keeps the promise the kitchen has to deliver on. Export compressed web copies, keep the originals, and put the reshoot on the calendar for the next menu change instead of the next five years.

Frequently asked questions

What size should food photos be on a restaurant website?

Match the display size, not the camera output. A full-width hero benefits from around 1600 to 2000 pixels wide; menu grid thumbnails need far less. The mistake to avoid is publishing 4000-pixel camera originals that a browser then shrinks.

Do food photos slow down a website?

Uncompressed ones do, and images are usually the heaviest thing on a restaurant page. Export web copies as compressed JPG or WebP and keep individual images to a few hundred kilobytes, and a photo-heavy menu page stays fast on a phone.

Should I put a photo next to every menu item on my site?

Only if the photos are consistently good. A menu where three dishes have great photos and the rest have none or worse photos draws attention to the gaps. Either photograph the full menu in one consistent batch or lead with a strong hero set.

Can I use my DoorDash photos on my own website?

If you shot them or own the rights, yes, and reusing one photo set everywhere keeps your brand consistent. Photos taken by a platform's photography program may carry usage terms, so check before reusing those.

Do website food photos need alt text?

Yes. Descriptive alt text like "margherita pizza with fresh basil" helps screen reader users and gives search engines context for image results, which is traffic delivery platforms never send you.

Turn your menu photos into orders

MenuCapture edits your real dish photos into clear, appetizing menu images that help you win more orders.

See MenuCapture plans