Photo editing

Food Photo File Format and Resolution Guide

By DishVivid · AI-assisted drafting · Published September 26, 2026 · Sources linked in the article

To ensure food photos display clearly across delivery apps, POS systems, and websites without rejection, independent restaurant operators should export a high-resolution JPEG master image and create destination-specific crops. A practical master image exported at 2400 to 3000 pixels on the long edge with an sRGB color profile and a file size between 2 MB and 5 MB balances visual clarity with manageable storage. From this single master, operators can produce tailored versions matching third-party technical caps, preventing blurry mobile cards and avoiding repeated reshoots when platform rules change.

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 the universal standard for online ordering and food photography. It uses lossy compression optimized for photographic gradients and textures. Exported at 80% to 90% quality, JPEG provides high visual fidelity while keeping file sizes small enough for fast ingestion.
  • PNG (.png): Best for Graphics, Poor for Food. PNG uses lossless compression, making it ideal for logos or transparent graphics. However, photographic food captures saved as PNG often exceed 10 MB without visible quality improvements on mobile displays, routinely exceeding upload limits.
  • 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.

Always export photographic files using the standard sRGB color space. Uploading images with Adobe RGB profiles can make dishes look dull or discolored in mobile browsers.

Master Resolution and Platform-Specific Rules

Rather than resizing an original capture for every ordering app, keep a clean master file. A master image measuring 2400 to 3000 pixels on the long edge preserves sufficient resolution for website banners, print materials, and digital menus.

From this master, adjust exports to match specific platform rules. For instance, the official Uber Eats Merchant Photo Guidelines distinguish between individual item photos and storefront cover images. Item photos must represent a single prepared menu item, keep the dish centered, avoid blur, borders, text, or promotional watermarks, and meet stated dimensions and file constraints. Because platform requirements and mandatory aspect ratios vary—such as 4:3 or 5:4 item ratios versus 16:9 storefront banners—operators should review current local platform rules before publishing.

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 Balanced JPEGs: Download the final file as a JPEG between 1 MB and 4 MB, well within standard merchant portal limits.

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: Dropping compression quality below 70% introduces harsh artifacts and pixelation across delicate sauces.
  • Adding Text Overlays or Logos: Placing prices, promotional badges, or borders on item photos violates delivery portal guidelines and causes rejections.
  • 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 Profile: Saved in sRGB to preserve natural tones?
  • Resolution: Master image measures at least 2400 pixels along the long edge?
  • File Size: Bounded between 1 MB and 5 MB to prevent upload errors?
  • 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