Platforms6 min read·Updated

Drupal WebP: Convert Images Without a Fragile Module Stack

Drupal 10+ can create WebP image style derivatives. That does not fix a 12 MB TIFF in the media library. Convert sources to WebP first so every style (thumbnail, large, wide) is cheap to generate and cheap to cache.

Image styles vs source files

Image styles transform a source. If the source is a 5000 px PNG, the first request after a cache clear burns CPU. A 2000 px WebP source makes styles fast and the page light even when a style is missing.

Why it matters

  • Anonymous page caches still store HTML that points at image derivatives.
  • Media Library bloat slows backups and stage syncs.
  • Some modules generate WebP on demand and fail on shared hosts.

How to do it

  1. Audit public:// for oversized originals.
  2. Bulk convert replacements at the largest style width you actually use.
  3. Replace media entities or re-upload. Flush image style cache once.

Settings that work

Match large or wide style width (often 1440–1920 px). Quality 80.

Convert a batch in your browser. Nothing is uploaded.

Put it into practice

Convert your images to WebP right now, free and privately in your browser.

Open the converter

Frequently asked questions

Yes. Core can generate WebP derivatives when GD/ImageMagick supports it. Uploading WebP sources is still valid.

Only if editors will keep uploading JPEG/PNG. If your pipeline outputs WebP, you can skip extra modules.

Keep reading

Tutorial8 min read

WebP for WordPress

Step-by-step guide to converting and uploading WebP images to WordPress, fixing upload errors, handling fallbacks and speeding up your site without extra plugins.

Read more
SEO6 min read

Migrate a site to WebP

A practical migration: convert in batches, update HTML, redirect old .jpg URLs, keep OG JPEGs.

Read more
Tutorial6 min read

WebP in Laravel

Convert marketing assets to WebP locally, and convert user uploads with Intervention or the Fast WebP API.

Read more