---
title: "WEBP image format"
description: "Review WEBP image assets, customer-facing surfaces, and load-time implementation requirements for your selected Ordering.co setup."
canonical: https://www.ordering.co/features/webp-image-format/
---

Image format review

# Make every image format decision part of the experience.

Use a clear WEBP asset review to align the source files, visual treatment, and delivery surfaces your implementation needs.

[Talk to Ordering.co ](https://www.ordering.co/contact/)[Explore Ordering Web](https://www.ordering.co/platform/ordering-web/)

Format support, image processing, and channel availability depend on your website and app setup.

![Illustrative WEBP image-format concept](https://www.ordering.co/media/features/5dbf9c96ee9f8063ff8639cc241c14d20e20f28980979ac0bade5ecff623d7b3.png)

Illustrative example image-format visual.

Image delivery

## Every product photo reaches customers already optimized.

Ordering.co serves the product, category, and store images you upload in WebP, a compressed image format built for the web, without a separate export step on your side.

Where you use it: Storefronts and customer apps, fed by the images you upload in the Dashboard

### What WebP does for your images

- Served in WebP automatically

  Images you upload are served to customers in WebP, so there is no separate format or export step to manage.

- Smaller files, the same photo

  WebP compresses an image to a smaller file size than JPEG or PNG while keeping its visual quality, so pages with several product photos have less to load.

- Transparency where you need it

  WebP supports transparent backgrounds, the same as PNG, for images that call for it.

### Why it matters

- **A lighter menu to browse**Smaller image files mean a product gallery or category grid has less to load, which matters most on a slow connection.

Every image matters

## Use a repeatable review before images reach a customer-facing surface.

WEBP applies to imagery across your website and native apps. Run this review whenever you add or update image assets.

1. 01

   ### Asset format

   Identify the image formats and source assets your team intends to use.

2. 02

   ### Channel scope

   Confirm where image handling applies across the selected website and app experiences.

3. 03

   ### Visual review

   Test the final assets at their real display sizes before releasing a customer-facing change.

![Illustrative image format workflow](https://www.ordering.co/media/features/d2c3230763cdcaf17e8bf007caeb41d91348b3f55ef07bba25416b0a69fdf203.png)

Illustrative example image workflow.

Surface checklist

## Keep the format decision connected to the surface where it will appear.

- **Website imagery**Review responsive placement, cropping, and content hierarchy.
- **Native app imagery**Confirm the applicable app surface and device context.
- **Implementation handoff**Document assets, constraints, and the visual checks still required.

Next step

## Bring the source assets and required surfaces to the implementation review.

[Talk to Ordering.co](https://www.ordering.co/contact/)

## Plan image formats with the product surfaces they support.

Share the website and app experiences you need to evaluate with the implementation team.

[Talk to Ordering.co](https://www.ordering.co/contact/)[Explore features](https://www.ordering.co/features/all-features/)