MenuPhotoLab VS StackGo

MenuPhotoLab's answer

It never generates the food. The dish in the output is the dish the restaurant actually cooked, relit and reframed, because DoorDash, Uber Eats and Grubhub all require a menu photo to represent the item being sold. A generated dish is a compliance problem, not a shortcut.

The second thing is that it solves portability rather than beauty. DoorDash wants landscape 16:9 at a minimum of 1400 x 800 pixels, Uber Eats wants 5:4 to 6:4, and Grubhub wants 1:1. One exported file rarely satisfies every platform a restaurant sells on, so the same upload comes back sized correctly for each one.

MenuPhotoLab's answer

Two things. Most AI food tools can change what is on the plate. This one cannot, and that matters because a dish that was never cooked is a compliance problem on every major delivery platform rather than just a nicer picture.

The second is sourcing. Every platform specification published on the site is read off that platform's own merchant documentation and carries the date it was last verified, including the places where a platform contradicts itself. Grubhub publishes 4:3 in its developer documentation and 1:1 in its help centre, and the page says so rather than picking the convenient number.

MenuPhotoLab's answer

Independent restaurant owners and operators who sell on more than one delivery platform and shot their menu photos on a phone.

The typical case is not a restaurant with bad photos. It is a menu where a large share of the items have no photo at all, because a good dish photo is genuinely hard to get in a busy kitchen at 9pm between tickets. On one local menu I pulled recently, 29 of 59 items had no image. It also fits anyone who has had a photo rejected by a platform and cannot tell from the rejection notice what to change.

MenuPhotoLab's answer

I photograph restaurants in Atlanta, and for the last two years I have shot and uploaded independent restaurants' menus to DoorDash, Uber Eats and Grubhub myself.

The same two problems came up on every job. Half the menu had no usable photo, and the one file I exported never fit all three platforms, so I ended up re-cropping the same dish three times and still getting rejections I could not explain from the notice. MenuPhotoLab is the tool I wanted on those jobs. The rule that it never generates the dish comes from the same place: I was uploading to merchant portals under someone else's restaurant name, and an image that misrepresents the food is their problem, not mine.

MenuPhotoLab's answer

Next.js and TypeScript, deployed on Vercel. Postgres through Supabase for data and auth, S3 compatible object storage for the photos, and Stripe for billing.

Enhancement runs as a background job on Trigger.dev rather than in the request, because a single photo takes tens of seconds. The image work itself is done with hosted AI models, and every result is tied back in the database to the original upload, the job that produced it and the settings used, so any output can be traced to the customer photograph it came from.