Overview

The original documentation for this page is short and direct, so the HTML follows the same logic: explain why the WEBP format is recommended, point to safe conversion tools and leave a small operational flow for teams that handle images before publishing.

Better compression
Faster loading
Smaller files

1

Why use WEBP

Main benefits

More efficient compression

The WEBP format delivers lighter files while keeping visual quality similar to JPEG or PNG in many scenarios.

Better experience

Lighter images help the website load faster, which improves navigation and perceived quality.

SEO support

Pages with better technical performance also tend to benefit from signals that affect search optimization.

Simple workflow

No complex software is required to get started: fast online tools exist for day-to-day tasks.

2

Suggested tools

Online conversion

3

Recommended workflow

Before publishing

1. Start from the original

Always keep the original version of the image before converting so you do not lose room for future edits.

2. Convert to WEBP

Use one of the suggested tools to generate the optimized version of the asset.

3. Review quality

Confirm that the visual detail remains acceptable, especially in banners, product imagery or images containing text.

4. Replace it in Studio

Update the image used in the project and validate the behavior on desktop and mobile.

4

Quick checklist

Final validation

  • Confirm that the final file keeps the correct framing and crop.
  • Avoid over-compression on images with small text or critical detail.
  • Validate the impact on the frontend, especially in sliders, galleries and hero banners.
5

See also

Related pages