{"id":12304,"date":"2026-11-03T11:48:00","date_gmt":"2026-11-03T17:48:00","guid":{"rendered":"https:\/\/infiniteuploads.com\/?p=12304"},"modified":"2026-11-03T11:48:33","modified_gmt":"2026-11-03T17:48:33","slug":"convert-images-to-webp-wordpress","status":"publish","type":"post","link":"https:\/\/infiniteuploads.com\/blog\/convert-images-to-webp-wordpress\/","title":{"rendered":"How to Convert Images to WebP in WordPress (4 Ways)"},"content":{"rendered":"\n

You can convert an image to WebP in WordPress four ways. Export it as WebP before you upload. Add one small filter so WordPress makes WebP versions itself. Install a free plugin. Or let your CDN convert and serve WebP automatically, with your originals left alone.<\/p>\n\n\n\n

I'll walk through each one with real steps, then show you how to check it actually worked. Most guides skip that part, and it's where most sites quietly fail.<\/p>\n\n\n\n

The quick answer<\/h2>\n\n\n\n
\n
A handful of images:<\/strong> convert them on your computer first, then upload the .webp files. WordPress has accepted WebP uploads since 5.8.<\/li>\n\n
Every new upload, no plugin:<\/strong> use the core `image_editor_output_format<\/code> filter so WordPress saves JPEG and PNG sizes as WebP.<\/li>\n\n`
`Every new upload, with settings:<\/strong> the free Modern Image Formats plugin from the WordPress Performance Team.<\/li>\n\n`
Old and new images, no regenerating, AVIF too:<\/strong> convert on delivery. It's the simplest and quickest option, it puts no strain on your server, and it's what Infinite Uploads Image Optimization does on the Business plan.<\/li>\n<\/ul>\n\n\n\nBefore you start: check your server can make WebP<\/h2>\n\n\n\nWordPress doesn't encode images itself. It hands the job to your server's image library, Imagick or GD, and WebP only works if that library supports it. The WordPress 5.8 WebP announcement<\/a> says exactly that. Checking takes 30 seconds.<\/p>\n\n\n\n \nIn your dashboard, go to Tools > Site Health<\/strong>.<\/li>\n\n Click the Info<\/strong> tab.<\/li>\n\n Open the Media Handling<\/strong> section.<\/li>\n\nLook at Active editor<\/strong>, then find WEBP in the supported formats list for that editor (ImageMagick or GD).<\/li>\n<\/ol>\n\n\n\nSite Health on a test WordPress 7.1.4 site. Imagick is the active editor, and both ImageMagick and GD list WebP and AVIF.<\/figcaption><\/figure>\n\n\n\nIf WebP isn't listed, methods 2 and 3 won't work on your host until they add it. Methods 1 and 4 don't depend on your server, so they still do.<\/p>\n\n\n\nMethod 1: Convert images to WebP before you upload<\/h2>\n\n\n\nNo plugin, no code, and it's fine for a few images. You convert the file on your computer, then upload the .webp like any other image. WordPress makes its thumbnails and other sizes in the same format as the file you upload, so a WebP upload gets WebP sizes.<\/p>\n\n\n\n\nOpen the image in Squoosh<\/a>, Google Chrome Labs' free tool that compresses images right in your browser.<\/li>\n\n Pick WebP<\/strong> as the output format on the right.<\/li>\n\n Drag the quality slider down until you see a difference, then nudge it back up a little.<\/li>\n\n Download the file and upload it to Media > Add New Media File<\/strong>.<\/li>\n<\/ol>\n\n\n\nComfortable in a terminal? Google's cwebp<\/a> tool does the same thing in one line. Quality runs from 0 to 100 and defaults to 75.<\/p>\n\n\n\n cwebp -q 80 photo.jpg -o photo.webp<\/code><\/pre>\n\n\n\nThe catch is obvious. It's manual, it does nothing for the images already in your library, and every browser gets the WebP, with no JPEG fallback.<\/p>\n\n\n\nMethod 2: Make WordPress create WebP with a filter<\/h2>\n\n\n\nWordPress 5.8 added a filter called image_editor_output_format<\/a>. It tells WordPress which format to save generated image sizes in. Map JPEG and PNG to WebP and every new upload gets WebP sizes. Add this to a code snippets plugin or your child theme's functions.php:<\/p>\n\n\n\n add_filter( 'image_editor_output_format', function( $formats ) {\n\t$formats['image\/jpeg'] = 'image\/webp';\n\t$formats['image\/png'] = 'image\/webp';\n\treturn $formats;\n} );<\/code><\/pre>\n\n\n\n\nConfirm WebP shows up in Site Health (see above).<\/li>\n\n Add the snippet and save.<\/li>\n\n Upload a new JPEG.<\/li>\n\nOpen it in Media > Library<\/strong> and check the file URLs for the generated sizes end in .webp.<\/li>\n<\/ol>\n\n\n\nThree things to know. It only touches new uploads, so existing images need regenerating with a tool like wp media regenerate<\/code>. There's no fallback, so every visitor gets WebP. And in WordPress 7.1, sites on Chrome or Edge 137 and newer process images in the browser instead of on the server, but the 7.1 client-side media processing post<\/a> says that path honors this same filter. So the snippet still works. We dug into what else 7.1 changed in does WordPress 7.1 optimize your images?<\/a>.<\/p>\n\n\n\n Method 3: Convert to WebP with a plugin<\/h2>\n\n\n\nIf you'd rather click than code, Modern Image Formats<\/a> is the free plugin from the WordPress Performance Team. It has 100,000+ active installs and is tested up to WordPress 7.1.4.<\/p>\n\n\n\n \nGo to Plugins > Add New Plugin<\/strong>, search for Modern Image Formats<\/strong>, then install and activate it.<\/li>\n\n Go to Settings > Media<\/strong> and scroll to the Modern Image Formats section.<\/li>\n\n Set Image output format<\/strong> to WebP<\/strong>. It picks AVIF by default when your server supports it.<\/li>\n\n Decide on Output fallback images<\/strong>. Left unchecked, WordPress only makes the WebP sizes and keeps your original upload as is. Check it if you also want JPEG or PNG copies of every size.<\/li>\n\nClick Save Changes<\/strong>, then upload a test image.<\/li>\n<\/ol>\n\n\n\nModern Image Formats 2.7.1 under Settings > Media, with the output format set to WebP.<\/figcaption><\/figure>\n\n\n\nLike the filter, it only converts new uploads. Its plugin page<\/a> says to regenerate existing images with Regenerate Thumbnails or wp media regenerate<\/code>. One nice touch: it skips the WebP version when it would be bigger than the original.<\/p>\n\n\n\n The big optimization plugins convert too. Per their own plugin pages:<\/p>\n\n\n\n \nEWWW Image Optimizer<\/a> includes WebP conversion in the free version. One-click WebP and AVIF conversion and delivery is a premium feature.<\/li>\n\n Imagify<\/a> includes WebP conversion on its free plan, which covers 20 MB of images a month (about 200 images).<\/li>\n\n Smush<\/a> lists serving WebP and AVIF automatically as a Pro feature.<\/li>\n<\/ul>\n\n\n\nWe compared these in more depth in the best WordPress image optimization plugins<\/a>.<\/p>\n\n\n\n Method 4: Convert to WebP automatically with Infinite Uploads<\/h2>\n\n\n\nEvery method so far converts files on your server and stores extra copies. Infinite Uploads works the other way, and honestly, it's the simplest and quickest of the four. Your media lives in the cloud and goes out through our CDN's 119+ edge locations. With Image Optimization<\/a> turned on, each JPEG or PNG is converted when a visitor asks for it, then cached at the edge. Your server does none of that work.<\/p>\n\n\n\n Each browser gets the best format it supports: AVIF first, then WebP, then your original as the fallback. Images are right sized and compressed on the way out. And your original files are never changed<\/a>, so there's nothing to regenerate and nothing to undo.<\/p>\n\n\n\n The Infinite Uploads plugin screen on a test site. Image optimization is listed as a Business plan feature.<\/figcaption><\/figure>\n\n\n\nOne honest note before the steps. Image Optimization is a Business plan feature. The Free plan gives you 10 GB of cloud storage and 20 GB of CDN bandwidth a month, but it doesn't include image optimization<\/a>. Once you're on Business, it takes a minute (full steps in the docs<\/a>):<\/p>\n\n\n\n \nInstall Infinite Uploads, connect your account and move your media to the cloud.<\/li>\n\n Open the Infinite Uploads<\/strong> menu in your dashboard and find the Image Optimization<\/strong> section.<\/li>\n\n Set Enable Image Optimization<\/strong> to Yes<\/strong>.<\/li>\n\n Leave the optimization level on Balanced<\/strong> and keep AVIF and WebP both checked. That's the default.<\/li>\n\nClick Save Settings<\/strong>.<\/li>\n<\/ol>\n\n\n\nNew settings apply the next time each image is requested. Want them live right now? Purge the CDN cache<\/a>. You can also set a maximum image width<\/a> and exclude images<\/a> you don't want touched. If you already run another plugin's WebP conversion, turn that part off<\/a> so the two don't double up. Lazy loading can stay.<\/p>\n\n\n\n Business starts at $29 a month billed monthly, or $24 a month billed yearly. See every plan on the pricing page<\/a>. If you're weighing up delivery-time tools, here's how Infinite Uploads compares with Optimole<\/a>, which also converts to WebP and AVIF in the cloud.<\/p>\n\n\n\n Want to see it on your own images? Try any plan free for 7 days<\/a>.<\/strong> Your trial includes the features of the plan you pick, so choose Business to test Image Optimization.<\/p>\n\n\n\n How to check your images are really WebP<\/h2>\n\n\n\nA .jpg in the URL doesn't mean a JPEG reached the browser, and a plugin saying \"converted\" doesn't mean it's being served. Check what actually arrives:<\/p>\n\n\n\n\nOpen a page on your site in Chrome and press F12 to open DevTools.<\/li>\n\n Click the Network<\/strong> tab, filter by Img<\/strong> and reload the page.<\/li>\n\n Click an image and look at the Content-Type<\/strong> response header.<\/li>\n\nimage\/webp<\/code> or image\/avif<\/code> means it worked. image\/jpeg<\/code> or image\/png<\/code> means it didn't.<\/li>\n<\/ol>\n\n\n\nWith Infinite Uploads, also check that the image URL is on your infiniteuploads.cloud CDN domain. If it isn't, the image is still coming from your server. My images aren't being optimized<\/a> covers the usual causes.<\/p>\n\n\n\n Which method should you pick?<\/h2>\n\n\n\n\nA few images, no extra tools: method 1<\/strong>.<\/li>\n\n Developer, new uploads only, fine without a fallback: method 2<\/strong>.<\/li>\n\n Click-to-configure, new uploads only, free: method 3<\/strong>.<\/li>\n\nThe simplest, quickest and best way overall: method 4<\/strong>. It covers your whole library, AVIF too, puts no strain on your server, leaves originals untouched and has nothing to regenerate.<\/li>\n<\/ul>\n\n\n\nWebP has wide support. Can I use<\/a> puts it at about 97% of browsers in use. AVIF is usually smaller still. If you're wondering whether to go further, read AVIF vs WebP for WordPress<\/a>. And if you want the backstory on our setup, here's when Infinite Uploads started serving AVIF and WebP<\/a>.<\/p>\n\n\n\n Convert once, check the Content-Type, and stop shipping JPEGs nobody asked for.<\/p>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":" Four ways to convert images to WebP in WordPress: before you upload, with a core filter, with a free plugin, or automatically on delivery. Plus how to check it worked.<\/p>\n","protected":false},"author":3787,"featured_media":14929,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"wds_primary_category":14,"footnotes":""},"categories":[26,14],"tags":[174,119,28,23,173],"class_list":["post-12304","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-performance","category-tutorials","tag-avif","tag-images","tag-optimization","tag-performance","tag-webp"],"acf":[],"_links":{"self":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/12304","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/users\/3787"}],"replies":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/comments?post=12304"}],"version-history":[{"count":6,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/12304\/revisions"}],"predecessor-version":[{"id":14927,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/12304\/revisions\/14927"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/media\/14929"}],"wp:attachment":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/media?parent=12304"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/categories?post=12304"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/tags?post=12304"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Which method should you pick?<\/h2>\n\n\n\n\nA few images, no extra tools: method 1<\/strong>.<\/li>\n\nDeveloper, new uploads only, fine without a fallback: method 2<\/strong>.<\/li>\n\nClick-to-configure, new uploads only, free: method 3<\/strong>.<\/li>\n\n