Delivery Photo Spec Checker — Free, No Signup

Why a spec checker matters for restaurant menus

Every delivery marketplace enforces photo requirements on upload. The penalty for missing them is not a polite warning — it's a hard rejection that pushes your menu item into a no-photo placeholder, where conversion drops by as much as 30–44% depending on the platform. DoorDash's own research on 15,000 merchants found items with photos sell up to 44% more than items without, and Deliveroo reports that restaurants with photography boost overall orders by 20–30%.

The catch is that every platform wants something slightly different. Uber Eats requires a 5:4 to 6:4 landscape aspect ratio at minimum 1,200 × 800 pixels. DoorDash wants 16:9 landscape at minimum 1,400 × 800. Grubhub wants 4:3 at 1,024 × 768 minimum. Rappi, iFood and Glovo want square (1:1) images, each with a different minimum and file-size cap. A restaurant that maintains the same catalog on three or four platforms effectively has to export the same dish four different ways, or accept that some platforms will reject the single export they use everywhere else.

What causes a rejection

From looking at thousands of menu-photo rejections the common patterns are straightforward: photos below the minimum resolution, photos in the wrong aspect ratio (most commonly, a DoorDash 16:9 export uploaded to a square-only platform like Rappi or Glovo), files above the platform's max size cap, and formats the platform does not accept (HEIC and TIFF are widely unsupported). Less frequently, photos get flagged for text overlays, watermarks, collages, or visible faces — but those are content rules, not technical specs, and this tool does not check for them.

How this tool works

The checker is entirely client-side. When you select a photo or paste a URL, the browser decodes the image with the native Image element and reads width, height and file size directly — no upload, no server round-trip, no analytics on your image. The four checks it runs on every platform are: (1) minimum pixel dimensions, (2) aspect ratio within the platform's accepted tolerance, (3) file size under the platform cap, and (4) file format in the platform's accepted list.

When you upload a URL, we still decode dimensions in the browser but cannot always read the file size because of cross-origin browser restrictions. In that case, file-size becomes a non-blocking warning instead of a hard fail. For the most reliable result, download the image and drag it into the uploader.

Fixing a failing photo

Most failures fall into one of two camps. (1) Aspect and resolution: if the photo was shot in a dramatically different aspect than the platform requires, resizing alone will crop meaningful content. Either reshoot with more breathing room around the dish, or use an AI tool that can extend the frame (outpainting) before exporting per-platform. (2) File size: this is almost always a compression issue — a photo shot on an iPhone in HEIC can be 3–8 MB, over the Glovo limit. Re-exporting as a JPEG at 85% quality at the platform's recommended dimensions drops the file size into the low hundreds of KB without a visible quality hit.

For restaurants with 30+ dishes across three or more platforms, the economics of maintaining platform-compliant photos manually break down quickly. The menu photo cost calculator shows the tradeoffs between photographer, freelance, and AI-generated approaches.

Keep the checker up to date

Delivery platforms publish their guidelines but revise them periodically. We re-verify each platform's specs every quarter against the merchant-center documentation and partner help pages linked in the table above. If you spot a discrepancy, contact us and we'll cross-check.