Skip to content

Uber Eats Photo Size in Poland: Image, Menu and Upload Specs

Uber Eats publishes only part of its image requirements, and the numbers restaurants repeat online often do not match what the upload screen enforces. This page separates what Uber documents for menu integrations from what is only a photo tip, then gives a master-file workflow that survives any crop and a Poland-specific preparation plan for Menu Maker.

What Uber Eats actually publishes about menu photos

Uber's developer documentation for menu integrations lists the technical limits: file size under 25 MB, format JPG, WEBP or PNG, and width and height each between 320 px and 6000 px. That is the whole published envelope. Uber Eats does not publish a required aspect ratio or a recommended pixel size for menu item photos, so treat any figure quoted as official with caution and check the upload screen inside Uber Eats Manager for the current field.

Separately, Uber Eats publishes photo guidance that is about content, not pixels. Shoot in indirect natural window light rather than harsh direct sun or fluorescent light. Use a top-down angle for plates and bowls, and about 45 degrees for burgers, sandwiches and other tall items. Cut and stack burgers, wraps and burritos so the filling shows, garnish for color but keep the photo a true representation, and avoid extreme close-ups that hide ingredients and portion size.

Upload happens per item in Menu Maker inside Uber Eats Manager, and each photo shows an in-review or rejected status in the Items tab. Build your files to sit comfortably inside the published envelope: a JPEG under 25 MB with both sides between 320 px and 6000 px will not fail on a technical limit, and a large file gives you room to re-crop later without reshooting.

  • Format: JPG, WEBP or PNG
  • File size: under 25 MB
  • Width and height: each between 320 px and 6000 px
  • Aspect ratio: not published by Uber Eats, confirm on the upload screen
  • Upload path: Menu Maker in Uber Eats Manager, status visible in the Items tab

A safe master file that survives any crop

Because no official ratio is published, the safest master is a landscape frame with the whole dish inside a centered square. If the app crops to square, to 4:3 or to a wide banner, the food stays in frame. Shoot on a tripod at chest height for top-down plates and slightly above eye level for burgers, then step back so there is empty table around the plate. That margin is your crop buffer.

Export the master as a large JPEG, roughly 3000 px on the long edge, which is well inside the 6000 px ceiling and far above the 320 px floor. Keep the original camera file untouched and export a working copy for editing. When you need a tighter version for a thumbnail, crop from the master rather than reshooting, so the lighting and garnish stay identical across the menu.

Check the crop before upload by viewing the image at thumbnail size on a phone. If the garnish disappears or the portion looks small, the crop is too tight. Uber's own guidance against extreme close-ups is the reason: the guest is judging quantity as much as appearance.

  • Shoot landscape, keep the dish inside a centered square
  • Leave a margin of empty table on all four sides
  • Export about 3000 px on the long edge, under 25 MB
  • Keep the untouched original, edit a copy
  • Test every crop at phone thumbnail size

Naming dishes for a Polish menu and keeping photo and text consistent

Menus in Poland are commonly written in Polish, so the item name on Uber Eats will usually be Polish and the photo has to match that name literally. If the listing says "kotlet schabowy z ziemniakami i mizerią," the photo must show the breaded cutlet, the potatoes and the cucumber salad, not a cutlet with fries. A mismatch is the fastest route to a rejected photo or a refund request.

Write the item name first, then shoot to it. List the visible components in the name itself, because the guest reads the name and the thumbnail together. For dishes with a sauce on the side, show the sauce in the frame or state it in the description. Where the Polish name is unfamiliar to some guests, add a short English or descriptive line in the item description rather than in the photo, since text baked into images is not a reliable way to communicate.

Keep one visual convention across the menu: same surface, same light direction, same angle per dish type. A menu where pierogi are shot top-down and the schnitzel is shot at 45 degrees looks deliberate; a menu where every photo has a different background looks assembled from stock.

Polish dishes that are hard to photograph, and how to handle them

Pierogi are pale, low-contrast and often glossy with butter. Shoot them top-down on a dark matte plate, add a scatter of fried onion or chives for color, and use a small amount of side light from a window to create texture on the dough. Avoid stacking them into a mound that reads as one beige shape at thumbnail size.

Żurek and other soups are opaque and monochrome. Use a bowl with a visible rim, place the sausage and egg half so they break the surface, and shoot slightly above 45 degrees rather than straight down, so the depth of the bowl reads. Bigos has the same problem in reverse: it is a brown mass, so include a slice of bread or a spoon of sour cream for contrast and keep the portion edge visible.

Kotlet schabowy and placki ziemniaczane are wide and flat, which suits a top-down shot with the side salad placed beside rather than on top. Herring in oil or cream reflects light badly; shoot it at an angle with a polarizing filter or move the light source to the side to kill the hotspot. Sernik and makowiec are pale and crumbly, so cut a clean slice, show the cross-section, and use a colored plate to separate the cake from a white table.

  • Pierogi: dark matte plate, top-down, garnish for color
  • Żurek: 45 degrees, sausage and egg breaking the surface
  • Bigos: add bread or sour cream for contrast
  • Kotlet schabowy: top-down, sides beside not on top
  • Herring: side light to control reflections
  • Sernik and makowiec: show the cut cross-section

The allergen rule that affects how you photograph

Under EU Regulation 1169/2011, allergen information for the 14 regulated allergens must be available for food sold without packaging, and for distance selling including delivery apps the mandatory information must be available before the purchase is concluded. In practice, that means the allergen details live in the item description or a linked allergen list inside the app, not in the photo.

Photos never replace that information, and a photo should not suggest ingredients the dish does not contain. If the kitchen can swap the sauce or remove the cheese, do not photograph the version with the extra ingredient unless the listing describes it. Keep the photographed build identical to the recipe the kitchen sends out, and update the photo when the recipe changes. This protects you on both the allergen side and the accuracy side of Uber Eats review.

Pre-upload checklist for Menu Maker

Run this before you touch the Items tab. It catches the technical failures and the content failures in one pass, and it keeps the menu consistent as you add items over time.

For the restaurant's own channels, such as the website menu, Instagram, a QR menu and print, FoodPhoto takes a real photo of the restaurant's own dish and improves light, background and crop, keeping the food as it is, and delivers every photo as a kit of sizes. Those files are for your own channels; the Uber Eats listing still needs your own real photo uploaded through Menu Maker.

Checklist before you publish

  1. Confirm the current format, size and ratio on the Menu Maker upload screen before exporting
  2. Export a JPEG under 25 MB with both sides between 320 px and 6000 px
  3. Keep the whole dish inside a centered square with table margin on all sides
  4. Match the photographed components to the exact Polish item name
  5. Shoot plates and bowls top-down, burgers and tall items at about 45 degrees
  6. Use indirect window light, not direct sun or fluorescent tubes
  7. Check the allergen and ingredient description matches what is on the plate
  8. Review the photo at phone thumbnail size before submitting

Questions

What is the required image size for Uber Eats menu photos in Poland?

Uber's developer documentation for menu integrations lists a file under 25 MB in JPG, WEBP or PNG, with width and height each between 320 px and 6000 px. Uber Eats does not publish a required aspect ratio or a recommended pixel size for item photos, so check the upload screen in Menu Maker for the current field. A large JPEG inside those limits is the safe choice.

Why was my Uber Eats menu photo rejected?

The status shows in the Items tab in Uber Eats Manager. Common causes are a photo that does not match the item name, an extreme close-up that hides portion size, text or logos baked into the image, poor lighting, or a file outside the published limits. Fix the mismatch between the description and the plate first, then re-upload.

Should I shoot menu photos top-down or at an angle?

Uber Eats' own guidance is top-down for plates and bowls, and about 45 degrees for burgers, sandwiches and other tall items. For Polish dishes, pierogi and placki ziemniaczane work top-down, while żurek and other soups read better slightly above 45 degrees so the depth of the bowl shows.

Do I need a separate photo size for each delivery app?

Yes, in practice. Uber Eats publishes only the wide envelope described above, and other apps publish their own requirements, so keep one large landscape master with the dish centered in a square and export per app from that master. Never reshoot for each platform; re-crop from the master so lighting and garnish stay consistent.

Start with a dish