Platforms6 min read·Updated

Contentful Images: Convert to WebP Before the Images API

Contentful can add `fm=webp` to image URLs. That is a good last mile. It is a bad only mile when editors upload 8 MB PNGs. Store a 1600–2000 px WebP and every `w=` variant is faster to generate and lighter to cache.

Transforms are not a substitute for a good master

The Images API resizes and reformats on demand. First-hit latency and cache keys still start from the uploaded asset. A sane WebP master reduces payload even when a developer forgets fm=webp on one template.

Why it matters

  • Preview environments hit uncached transforms constantly.
  • Multiple frontends (web, app) share the same asset.
  • Brand PNGs do not belong in production at 4000 px.

How to do it

  1. Download the asset or use the source from the DAM.
  2. Convert to WebP at your largest w= parameter.
  3. Replace the asset in Contentful so published entries keep the same ID when possible.

Settings that work

Match the max width your next/image or <img> requests (often 1920). Quality 80.

Convert a batch in your browser. Nothing is uploaded.
Open the converter

Put it into practice

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

Open the converter

Frequently asked questions

Yes if some assets remain JPEG. If everything is already WebP, `fm=webp` is optional.

Yes. Upload through the web app or CMA.

Keep reading

Platforms6 min read

WebP for Strapi

Strapi can upload WebP and generate responsive formats. Convert media to WebP locally so upload plugins stay simple.

Read more
Platforms6 min read

WebP for Sanity

Sanity's CDN can auto-format, but oversized originals still slow Studio and first paints. Convert assets to WebP before they enter the dataset.

Read more
Tutorial6 min read

WebP in Next.js

next/image can serve WebP, but huge files in /public still hurt. How to pre-convert static assets and CMS images for Next.js App Router.

Read more