To batch convert WebP files: drag the whole folder into our WebP to JPG converter and download the results as one ZIP — everything runs locally in your browser, nothing uploaded. If you live in a terminal, magick mogrify -format jpg *.webp does the same job in one line. Both take minutes; converting files one at a time takes an afternoon. Here is when to pick which, and what to watch for.
Where a pile of WebP files comes from
Bulk WebP shows up in three predictable ways. Chrome saved a research session's worth of images as .webp because that is what the sites served. A website redesign handed you an asset dump — the previous developer exported everything as WebP and the new CMS wants JPG. Or a supplier sent a product catalog in the format their system happens to produce. Different sources, same problem: dozens or hundreds of files in a format that needs to become something else. There is a fourth, quieter source too: anyone archiving or mirroring a website pulls down whatever it served, which in 2026 is mostly WebP.
Option 1: the browser, whole folder at once
The browser converters are built for exactly this scale:
- Open the converter for your target format — WebP to JPG for photos and maximum compatibility, WebP to PNG for anything with transparency or sharp text.
- Drag the folder in. The page reads every file in it and queues the batch automatically.
- Download as one ZIP. Original filenames are preserved with only the extension swapped, so
IMG_4021.webpcomes back asIMG_4021.jpgin the same pile.
Two properties matter at batch scale. Everything happens on your machine — no upload queue, no server, so a hundred files move as fast as your CPU rather than as fast as your upload bandwidth. And your images never leave the device, which is the point when the folder is client work or product photos that are not public yet. If either target needs a refresher, the single-file guides cover the details: how to convert WebP to JPG and how to convert WebP to PNG.
Two practical notes. Browser tabs have memory limits: a few hundred typical web images per batch is comfortable, a thousand 20-megapixel files is not — split those into chunks and run them sequentially. And take the ZIP option for large batches: browsers throttle simultaneous individual downloads, Safari most strictly of all, and one archive sidesteps the whole question.
Option 2: ImageMagick, one line
If the terminal is already open, ImageMagick's mogrify converts an entire directory in place:
magick mogrify -format jpg -quality 90 *.webp
On Windows, the PowerShell equivalent:
Get-ChildItem *.webp | ForEach-Object { magick $_.FullName ($_.BaseName + ".jpg") }
For PNG output, swap the format and drop the quality flag, which PNG ignores. This is the right answer when conversion belongs in a script — a build pipeline, a nightly job, a folder you process every week. For a one-off pile of files, it is faster to open a browser tab than to install ImageMagick.
Option 3: one-by-one online converters, and why they fail
The classic online converter flow — upload, wait, convert, download, repeat — was tolerable for one file and collapses at twenty. Each file makes a round trip to someone's server, queues behind other people's conversions, and hands your images to a third party in the process. Free tiers add daily caps right when you need volume. It is the wrong tool for batch work, full stop; if privacy or speed matters even slightly, options 1 and 2 are the whole list.
JPG or PNG for the batch
One rule covers most folders: photos go to JPG, graphics with transparency or text go to PNG. Mixed folder? Split by content, run two batches. When in doubt with photos, JPG is the smaller and more universal choice. If the WebP files arrived via Chrome's save-as habit, how to stop Chrome saving WebP explains why the pile formed — though converting them after the fact is usually less effort than fighting the browser.
Naming and structure notes
The converter keeps filenames and changes only the extension, so scripts and spreadsheets that reference the files mostly survive the swap — grep your references for .webp afterward to catch the stragglers. Watch for one edge case: a folder containing both logo.webp and logo.png converts to two files named logo.png. Rename one before converting, or the collision resolves however your ZIP extractor feels like handling it.
For the under-the-hood view of what batch conversion does to each file — validation, decode, encode — the batch conversion tutorial walks the pipeline.
The folder that started all this is still sitting on your disk. Drag it into the converter, download the ZIP, and the pile becomes a non-issue before your coffee cools.