Platforms6 min read·Updated September 5, 2026

Strapi Media Library: Ship WebP Without a Provider Plugin

Strapi's upload plugin can create breakpoints. Those breakpoints inherit a bad original. Convert blog and product media to WebP at 1600 px in the browser, then upload once. You avoid sharp/libvips failures on small PaaS plans.

Responsive formats still need a good source

If you enable responsiveDimensions, Strapi writes several files per upload. Starting from WebP keeps that folder small and makes S3/Cloudinary bills predictable.

Why it matters

PaaS memory limits crash image processing on 20 MB PNGs.
Multiple frontends consume the same /uploads URLs.
Editors can use a private converter instead of a CLI.

How to do it

Convert the content batch locally.
Upload WebP via admin or the upload API.
Keep quality in Strapi moderate if you still generate extra formats.

Settings that work

1600 px / 80% for articles. 2000 px / 80% for full-bleed.

Put it into practice

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

Open the converter

Frequently asked questions

With the right upload plugin settings or a provider, yes. Pre-converting is more reliable on small hosts.

Cloudinary is fine at scale. For a brochure site, local WebP uploads are enough and cheaper.

Keep reading

Platforms6 min read

WebP for Contentful

Contentful's Images API can format=webp, but huge masters still cost transform time and origin weight. Pre-convert assets to WebP.

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.