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.
Format support, image processing, and channel availability depend on your website and app setup.

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 browseSmaller 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.
- 01
Asset format
Identify the image formats and source assets your team intends to use.
- 02
Channel scope
Confirm where image handling applies across the selected website and app experiences.
- 03
Visual review
Test the final assets at their real display sizes before releasing a customer-facing change.

Surface checklist
Keep the format decision connected to the surface where it will appear.
- Website imageryReview responsive placement, cropping, and content hierarchy.
- Native app imageryConfirm the applicable app surface and device context.
- Implementation handoffDocument assets, constraints, and the visual checks still required.
Next step
Bring the source assets and required surfaces to the implementation review.
Plan image formats with the product surfaces they support.
Share the website and app experiences you need to evaluate with the implementation team.