Which spec do you follow when a platform publishes two?
Follow the stricter figure. Grubhub publishes both 200 x 200 square PNG and 1600 x 1200 at 4:3 for the same menu item photo, on two of its own pages. DoorDash states 2 MB and 16 MB on one page. Toast recommends 750 x 450 and separately a 1000 pixel minimum. A file meeting the stricter number satisfies both readings.
Su Lee · Founder, MenuPhotoLab
Six years photographing Atlanta restaurants, and two running SocialLee, uploading their menus to DoorDash, Uber Eats and Grubhub.
Sources last read · 5 sources
Most photo advice assumes each platform publishes one number. Read the documentation closely and that turns out not to be true. Three of the five platforms I upload to publish figures that disagree with figures published by the same company, sometimes on the same page.
This matters for a practical reason rather than a pedantic one. If you follow the wrong half of a contradiction, your photo is rejected and the rejection notice quotes the other half back at you.
| Platform | Says one thing | And also says | Which to follow |
|---|---|---|---|
| Grubhub | 200 x 200 px, 1:1, PNG only | 1600 x 1200 px, 4:3, PNG or JPEG | 1600 x 1200 at 4:3 |
| DoorDash | Maximum 2 MB | Under 16 MB | Stay under 2 MB |
| Toast | Recommends 750 x 450 | Recommends a 1000 px minimum side | Export 1920 x 1080 |
Why does Grubhub publish two different photo sizes?
This is the largest contradiction in delivery photo documentation, and neither Grubhub page acknowledges the other exists. They are not two levels of detail on one rule. They disagree on every field.
| Grubhub help centre | Grubhub developer portal | |
|---|---|---|
| Minimum size | 200 x 200 px | At least 1600 x 1200 px |
| Aspect ratio | 1:1, square | 4:3 |
| File formats | .png only | .png, .jpeg or .jpg |
| Who it addresses | Restaurants uploading a menu themselves | POS and integration partners sending a menu feed |
An image that satisfies the help centre is 64 times smaller in area than the developer portal's minimum, and the wrong shape besides. Square is not 4:3.
Which one binds you appears to depend on how your menu reaches Grubhub, manual upload versus a partner feed. Grubhub does not say that anywhere, so treat it as my inference from who each page is written for, not as a rule you can hold them to.
What is DoorDash's actual file size limit, 2 MB or 16 MB?
Both, on one page, in two different sections. The part explaining why photos get rejected for size states a 2 MB maximum. The requirements run-down further down the same page lists item photos as under 16 MB.
A merchant reading top to bottom gets one answer. A merchant skipping to the spec table gets another, eight times larger.
There is no ambiguity about what to do, which makes this the easiest of the three: stay under 2 MB and you satisfy both readings at once. It matters mainly as a warning about the rest. If a platform can contradict itself inside one page, a number you read somewhere else six months ago deserves re-checking.
Does Toast's recommended image size fail Toast's own guidance?
Yes, on two counts. Here are both articles, in Toast's own words.
For menu item images, we recommend a rectangle 750 px by 450 px.
Toast Online Ordering Pro menu templates support 1:1 (square), 4:3 (rectangle), and 16:9 (rectangle) aspect ratios. We recommend a minimum height or width of 1000 pixels to ensure high image quality.
A restaurant that follows the first recommendation exactly produces a file that misses the second one twice.
Size. 750 px is its longest side, 250 px short of the 1000 px Toast asks for elsewhere.
Shape. 750 x 450 is 5:3, or 1.667. Toast lists three supported ratios and 5:3 is not one of them. It sits between 4:3 (1.333) and 16:9 (1.778).
Export 1920 x 1080 and both articles are satisfied with room to spare: it is 16:9, which Toast lists, and its shortest side is already above the 1000 px figure.
One honest note on wording, because it changes how hard this conflict bites. Both Toast figures are phrased as recommendations rather than requirements, so neither is a rule you can be rejected against in the way DoorDash's 16:9 is. The shape half is the firmer of the two, because "support" is the verb Toast uses for the three accepted ratios.
What this means if you sell on more than one platform
The usual advice is to export one file per platform. These contradictions mean that is not enough on its own, because for some platforms there is no single agreed target to export to.
What survives everything is framing the shot with room around the dish. Every conflict above is about size and shape, and both are decided when the photo is taken rather than when it is exported. A dish photographed tight to the edges cannot be recropped to 4:3 and 1:1 and 16:9 from the same original. A dish with margin can.
The practical rule I use on my own uploads: shoot wide, export to the strictest figure in each contradiction, and keep the original. Strictest means 1600 x 1200 for Grubhub, under 2 MB for DoorDash, and 1920 x 1080 for Toast. Every one of those also clears the looser figure it conflicts with.
Frequently asked questions
Which Grubhub photo size is correct, 200 x 200 or 1600 x 1200?
Both are published by Grubhub, on two different pages, and neither mentions the other. The help centre says at least 200 x 200 pixels, 1:1, PNG only. The developer portal says at least 1600 x 1200 pixels at 4:3 in PNG or JPEG. Upload 1600 x 1200 at 4:3: it clears the help centre's minimum many times over, and 200 x 200 would fail the developer portal on both size and shape.
Is DoorDash's photo file size limit 2 MB or 16 MB?
DoorDash publishes both figures on the same page, read 2026-09-22. The section on why photos are rejected states a 2 MB maximum; the requirements list further down states under 16 MB for item photos. Keep your file under 2 MB and you satisfy both, whichever one the review actually applies.
Why would a platform contradict its own documentation?
Usually because different pages are written for different audiences at different times and nobody reconciles them. Grubhub's two specs address restaurants and integration partners. Toast's two figures come from articles about different products. None of this requires bad faith, and it does not make either number less real to whoever reviews your photo.
Should I follow the stricter or the looser figure?
The stricter one, in every case here. A file that meets the tighter requirement also meets the looser one, so following the strict figure means you are covered whichever rule the platform's review applies. The reverse is not true: a 200 x 200 square PNG fails the Grubhub developer portal on size, shape and nothing else being wrong with it.
How current are these figures?
Every figure on this page was read off the platform's own page on 2026-09-22, and the sources are linked below with that date. Platform documentation changes without notice, so treat anything more than a quarter old as needing a re-check. The public record of when each figure was last read is kept at github.com/menuphotolab/delivery-app-photo-specs.
Not sure whether a photo you already have will pass?
Run it through the free Photo Rejection Checker. It tests the size, shape, format and file size of any photo against each platform's published specs, and lists the content rules alongside. No signup.
Check a photoKeep reading

Su Lee
Founder, MenuPhotoLab · Atlanta, Georgia
I have photographed Atlanta restaurants for six years as a food creator, and for the last two my sister and I have run SocialLee, shooting and uploading menus for independent restaurants around metro Atlanta. I wrote this page the way I wish the platforms had written theirs: every number read off their own documentation, with the date I read it, and where they contradict themselves I say so.
Sources
- Grubhub, Menu imagery specifications (developer portal: item 1600 x 1200 at 4:3, logo 200 x 200). This page is a JavaScript app and returns "Grubhub is loading..." to curl, so it has to be read in a rendered browser. A failed fetch here does not mean the page is gone., read
- Grubhub, Menu overview (help centre: 1:1 square, at least 200 x 200, .png only), read
- DoorDash, Common photo issues explained (both the 2 MB and the 16 MB figures), read
- Toast, Adding images to menu items ("we recommend a rectangle 750 px by 450 px", 5 MB, jpg or png), read
- Toast, Online Ordering Pro menu image requirements (1:1, 4:3 or 16:9, and a recommended 1000 px minimum side), read
Platform requirements change. This page carries the date each source was last checked.
Not affiliated with Grubhub, DoorDash, Toast, Uber Eats.
