FoodPhoto.ai guide
Delivery app photo requirements for restaurants
Official-source delivery app photo requirements for restaurants: DoorDash, Uber Eats, Google Business Profile, crop rules, file sizes, rejection fixes, and checker tools.
Start with the highest-risk requirements
DoorDash, Uber Eats, Google Business Profile, and regional marketplaces do not use one universal menu-photo crop. Use this hub to check the current size, ratio, file, format, and rejection rules before publishing, so a listing photo is not rejected or auto-cropped into something unappetizing.
FoodPhoto.ai improves lighting, background, crop, and export size without changing ingredients, portion, or plating. FoodPhoto begins with two previews on your own dish, with a verified account and no card. Free previews are significantly slower than paid plans and are prepared in a separate queue: about 30–35 seconds in normal conditions, and longer when the service is busy or the edit is complex. Keep the chat open and do not repeat the request while it processes. See the current plans and usage estimates for photos, menus and campaigns.
Platform photo specs at a glance
There is no single universal crop. The table below summarizes the main delivery and listing platforms. Specs change, so always confirm against each platform’s own current merchant or Help Center documentation before a large upload.
| Platform | Recommended ratio | Typical size | Notes |
|---|---|---|---|
| DoorDash | 16:9 landscape | At least 1400 × 800 px | Official item-photo guidance; confirm the account field. |
| Uber Eats | 5:4 to 6:4 recommended | Width ≥550 px; height ≥440 px | Merchant guidance; file cap 10 MB, preview the actual crop. |
| Google Business Profile | Square (1:1) | 720 × 720 px or larger | JPG or PNG; accurate, recent photos of real dishes |
| Grubhub | 1:1 square for merchant menu uploads | At least 200 × 200 px; 1600 × 1600 px is a FoodPhoto working recommendation | Merchant menu guidance: PNG. Check POS/integration feeds and the current account separately; no universal approval or file cap asserted. |
What gets a delivery photo rejected
The most common rejection and auto-crop triggers are: the wrong aspect ratio for the platform, resolution below the minimum, oversized files, added text or watermarks or borders, busy backgrounds that turn to mush at thumbnail size, and images that do not honestly match the dish that arrives. Fix these before upload rather than after a rejection.
A one-minute pre-publish checklist
Before you upload, check the aspect ratio, pixel dimensions, file size, and format for the target platform; confirm the lighting and background are clean; remove any overlays, watermarks, or borders; and verify the image accurately represents the actual dish, portion, and ingredients.
How restaurants use this workflow
- Photograph the real dish with a phone, using window light when available.
- Use FoodPhoto.ai to fix lighting and sharpness, strip text and watermarks, and export the correct per-app crop so photos clear delivery platform review.
- Export the image for menus, delivery apps, Google Business Profile, social ads, and seasonal landing pages.
Related FoodPhoto.ai guides
FAQ
Do my photos meet DoorDash, Uber Eats, and Grubhub upload rules?
An export does not prove platform acceptance. Start with your own photograph of the real dish, compare ingredients, portion and packaging after editing, and confirm the current market, account and upload field. Each platform may review or reject submissions; editing or generated imagery is not automatically permitted.
What crop and resolution do the delivery apps actually want?
DoorDash item guidance lists at least 1400 × 800 px and 16:9 landscape as separate constraints; a 1440 × 810 px canvas is a FoodPhoto working choice. Grubhub merchant-menu guidance lists square 1:1 PNG at least 200 × 200 px; a sharper 1600 × 1600 master is a recommendation, not its minimum. Uber Eats item guidance recommends 5:4 to 6:4, with width at least 550 px and height at least 440 px. Cover and integration fields differ; confirm the destination account rather than treating one crop as universal.
Why do delivery apps reject or auto-replace menu photos?
Wrong dimensions, aspect ratio or file format, blur, overlays, inaccurate portions and missing image rights can cause review problems. Compare the result with the served dish and read the current destination policy. A clean export, crop check or FoodPhoto edit does not guarantee approval.
Start with the real dish photo
FoodPhoto.ai is built for truthful enhancement: review every output against the real dish to preserve its portion size, ingredients and menu promise, and check the platform’s current official merchant documentation before uploading a clean, sharp, overlay-free image in the required aspect ratio.
Open the studio to process a real image, or create an account.