Food Photo File Format and Resolution Guide

Keep the full-resolution source photograph, then make a separate JPEG and crop for the destination where it will appear. There is no universal pixel size or file-size range that guarantees acceptance across menus, delivery listings and websites. Inspect the actual exported file and merchant portal requirements before uploading.

Why File Format and Resolution Matter for Menu Displays

Digital menus require images that load quickly on mobile connections while maintaining crisp detail on high-density screens. When an image file is too small or heavily compressed, sauces lose texture, garnishes blur, and dishes look unappetizing. Conversely, oversized files cause upload timeouts in merchant portals or trigger aggressive re-compression that degrades quality.

Choosing the Right File Format: JPEG vs. PNG vs. WebP

Selecting the correct food photo file size and format begins with understanding how image formats handle photographic detail:

• JPEG (.jpg / .jpeg): The Practical Standard. JPEG is a widely supported choice for photographs; check the destination before uploading. It uses lossy compression optimized for photographic gradients and textures. In an editor with a quality setting, compare compression against the file limit and visible texture. DishVivid uses a fixed JPEG quality setting, not a user-selectable percentage.
• PNG (.png): Best for Graphics, Poor for Food. PNG uses lossless compression, making it ideal for logos or transparent graphics. Photographic PNGs can be larger than JPEGs. Size depends on the image; inspect the file instead of assuming it meets or exceeds a portal limit.
• WebP and HEIC: Modern Formats with Portal Friction. Smartphones often capture in HEIC, while websites serve WebP. Despite their efficiency, many merchant portals reject direct HEIC or WebP uploads. Convert mobile captures to standard JPEG files before uploading.

If your external editor offers color-profile conversion, use the profile requested by the destination and inspect the result. DishVivid has no manual color-profile selector or certification of color accuracy.

Master Resolution and Platform-Specific Rules

Rather than resizing an original capture for every ordering app, keep a clean master file. Preserve the original at its captured resolution rather than enlarging it to reach an arbitrary number. Print layouts and banners may need a different working file from an ordering thumbnail.

Consult the official Uber Eats merchant photo guidelines and our item-versus-cover preparation guide before selecting a crop. Those are different placements; a tool preset does not establish acceptance.

Step-by-Step Workflow: From Kitchen Capture to Export

A structured workflow keeps food photography consistent across channels:

1. Capture Native Resolution: Photograph dishes under balanced light using your camera or phone's native sensor resolution without digital zoom.
2. Set Framing and Margin: Center the plated item while leaving background margin so responsive crops do not clip the plate.
3. Refine Tone and Crop: Adjust exposure, contrast, and saturation to reflect the real dish. Browser-based tools like DishVivid Studio offer manual preview controls for brightness, contrast, saturation, and crop positioning, alongside channel presets and JPEG downloads. Note that the studio does not offer blur repair, automatic background removal, dedicated white-balance tools, or platform approval guarantees. If using optional AI candidate generation, operators must compare candidates with the physical dish to verify ingredients, portions, and presentation prior to export.
4. Export and Inspect: Complete the dish review and download a JPEG. DishVivid offers Original (source dimensions), Delivery wide (1600×900), Delivery classic (1500×1200), and Social square (1200×1200). It does not offer custom dimensions, a file-size target, PNG/WebP output or a compression slider. Check the downloaded file; use a separate resize/compression tool if needed.

Common Mistakes to Avoid

• Uploading Raw Smartphone HEIC Files: Failing to convert native smartphone captures causes upload errors in many merchant dashboards.
• Over-Compressing for File Size: Inspect the exported photo at its intended display size and at 100% for blockiness, ringing, and lost sauce texture. Use less compression if artifacts appear; no single quality percentage guarantees clean texture.
• Adding Promotional Overlays: Check the destination rules before adding prices, badges, borders or logos to an item image. Cover-image and packaging exceptions may differ.
• Cropping Too Tightly: Excessively close crops lose essential garnish and context when platforms apply responsive cropping masks.

Restaurant Operator Sizing and Format Checklist

• File Format: Exported as a standard JPEG (.jpg) file?
• Color: Downloaded file inspected; any required external profile conversion checked?
• Resolution: Source archived and downloaded dimensions suitable for the intended placement?
• File Size: Actual bytes checked against the destination limit?
• Framing: Plated dish centered with ample margin for dynamic crops?
• Compliance: Free of text overlays, logos, borders, and watermarks?
• Kitchen Accuracy: Final output visually confirmed against the real dish?

Sources and further reading

• Uber Eats Merchant Photo Guidelines: Official guidance regarding merchant-submitted menu photos, item centering, prohibited elements, and platform specifications.

Platform reference checked 10 October 2026. Archive and sizing steps are DishVivid suggestions; the destination sets its upload rules.