Batch convert WebP to JPG

Last updated: August 29, 2026

Why is this whole folder suddenly WebP?

The images didn't change, the source did. WebP, developed by Google, is roughly 30% smaller than JPG at equal quality, and most large websites, Google Images, Reddit and Instagram among them, now serve it by default rather than as an option. Right-click, Save Image As, and the file that lands on disk is WebP because that's what the site sent your browser, not because anyone chose the format.

A whole folder ends up WebP for the same reason one image does, just repeated: a research session, a moodboard saved for reference, product photos pulled from a Reddit thread, all saved the same way from sites that all serve the same format. The folder is consistent because the source behavior was consistent, not because of anything unusual you did.

Browser extensions that bulk-download every image on a page compound this: they save exactly what the page served, so a single click can produce dozens of WebP files at once from a page that never offered a format choice in the first place. The resulting folder looks like a deliberate WebP collection; it's really just the byproduct of how modern image delivery works, repeated at scale instead of one file at a time.

Software that still won't open a WebP file

WebP support arrived late and unevenly across the software people actually use. Photoshop is the clearest example: Adobe's own documentation confirms native WebP support arrived in Photoshop 23.2, released in February 2022; anything older needs a separate plugin or rejects the file outright. Office fares similarly: Microsoft added WebP image support to Office well after WebP itself had been standard on the web for years, so older, unpatched installs of Word, Excel or PowerPoint can still refuse to insert a WebP image directly.

Upload forms are the least predictable of the three. Some accept WebP without issue, since it's now a standard web image type; many still don't, especially older government, insurance or job-portal forms built before WebP was common. There's no way to tell which without trying, which is exactly the moment this page becomes useful: convert once, and the format stops being a variable.

The safest default, if a batch is heading somewhere unknown, an email attachment, a form that hasn't been tested, a colleague's computer running unspecified software, is to convert to JPG before sending rather than find out afterward that it didn't open. Re-sending a folder because the first attempt failed costs more time than converting it upfront ever does.

Your OS can probably view it already, that's not the problem

It's worth separating two different problems, since they look identical from the file's icon. macOS has opened WebP natively in Preview and Quick Look since Monterey, and every current desktop browser displays WebP without any extra software. If a WebP file opens fine when you double-click it, viewing was never the issue: the specific program you're trying to use it in, Photoshop, Office, or an upload form, is.

That distinction matters because the fix is different depending on which problem you actually have. A file that won't preview at all needs a viewer or OS update; a file that previews fine but won't insert into a document or upload to a form needs converting, not viewing. This page is for the second problem.

It's worth checking before converting anything, too: try inserting the WebP file directly into the document or form first. If the current version of the software actually supports it, the extra conversion step is unnecessary, and it's worth knowing that for next time rather than converting out of habit. The problem is common enough to expect, not universal enough to assume.

Batch converting without this site

IrfanView and other general Windows image viewers that handle WebP can batch-convert a folder the same way they batch-convert anything else, once WebP support is installed; the batch dialog setup is the same one covered for batch HEIC conversion, since the mechanism doesn't care which format goes in. On a Mac, Preview opens WebP natively since Monterey and can export a multi-selected folder to JPEG the same way described there too; the steps aren't repeated here since they're identical once the file is open.

There's also a Mac-specific option that doesn't come up for HEIC: sips, the image-processing tool built into every Mac's Terminal since Mac OS X. A one-line loop through a folder, converting each WebP to JPG with sips, needs no app open at all and works identically whether the folder has three files or three hundred. It's not approachable if the Terminal is unfamiliar territory, but for anyone who already lives in it, it's faster than opening any app first.

None of these routes are wrong, they trade setup time for zero ongoing dependency on a website. The browser route trades that setup time away entirely, at the cost of needing an internet connection to load the page once, even though the conversion itself happens offline after that.

Converting the whole folder here

Drop the folder in, and every WebP file decodes using the browser's native WebP support, the same decoder that displayed the images on the original website, then re-encodes to JPG at your chosen quality. Nothing uploads, so a folder of 150 saved images processes the same way as a folder of 2, and there's no daily limit to run into partway through.

One thing this conversion can't do: preserve transparency. WebP supports an alpha channel the way PNG does; JPG doesn't support transparency at all, so any transparent WebP in the batch comes out with a solid background instead. Converting to PNG is the fix when that matters, at the cost of a larger file than JPG would produce.

Quality defaults to 90%, which for images already compressed once by a website's CDN is usually indistinguishable from the WebP original at normal viewing sizes. Photos of products, screenshots with photographic content, and general web imagery hold up well; flat graphics, logos and images with large areas of solid color compress more visibly and are worth a quick look at 95% quality or the PNG route instead if the batch is mostly that kind of image.

Nothing in this batch ever leaves your device: the same in-browser engine that handles a single WebP to JPG conversion runs the whole folder, file by file, without a network request for any of it. That's true whether the folder came from a research session or a bulk-download extension, and it's the same privacy guarantee this site makes for every conversion, not a special case for batches. For every other format this site converts to and from, not just WebP and JPG, the full image converter covers the rest.

Common questions