Convert WebP to JPG on Windows

A project folder lands with WebP exports from the web team. Your colleague opens them in Outlook or PowerPoint and gets blank placeholders. Many CRM uploads, print vendors, and older Windows apps still expect JPEG. The mismatch is common when production ships modern formats but sales, support, and vendors live in email and slide decks. Converting locally avoids asking everyone to install codecs and keeps staging assets off third-party upload tools.

WebP vs JPEG

WebP saves bytes on the web. JPEG still wins for compatibility in email, slides, and legacy systems.

	WebP	JPEG
Modern browsers	Native	Native
Email attachments	Often fails	Opens everywhere
PowerPoint / Word	Hit or miss	Reliable
Transparency	Yes	No (flatten first)
Typical file size	Smaller at same visual quality	Larger but universal

Workflow	Recommendation
Production website	Keep WebP with JPEG fallback in HTML
Client email bundle	Convert to JPEG
Design review in slides	JPEG or PNG depending on transparency

Flatten transparency on a solid background before JPEG export if the asset had alpha. For broader image compression, see how to compress images on Windows . For exporting WebP from PNG, see PNG to WebP on Windows .

Handoff type	JPEG quality hint
Email bundle	q80 to q85, max 1920 px wide
Print vendor	q90+, ask for color profile
CRM thumbnail	q75, cap width per portal spec

Convert one file in Paint

On Windows 11, Paint opens many WebP files.

1. Open the file in Paint.
2. File → Save as → JPEG picture.

Fine for five files. Tedious for fifty sprint assets.

If Paint shows a blank canvas, the WebP may use features Paint does not render; use dwebp or GetCompress instead. Spot-check one conversion before batching an entire design drop.

Convert many files in PowerShell

Open Command Prompt or PowerShell. Install webp tools with winget:

winget install webp

Install FFmpeg if you use the second method:

winget install --id Gyan.FFmpeg -e

dwebp plus FFmpeg:

mkdir jpeg-out
Get-ChildItem *.webp | ForEach-Object {
  dwebp $_.Name -o "$env:TEMP\t.png"
  ffmpeg -y -i "$env:TEMP\t.png" -q:v 3 "jpeg-out\$($_.BaseName).jpg"
}

FFmpeg only (when decode works directly):

mkdir jpeg-out
Get-ChildItem *.webp | ForEach-Object {
  ffmpeg -i $_.Name -q:v 3 "jpeg-out\$($_.BaseName).jpg"
}

Method	Best for
dwebp + FFmpeg	Tricky WebP with alpha
FFmpeg only	Simple raster WebP batches

Save to a new folder. Adjust -q:v 3 for quality vs size.

Method	When to use
dwebp + FFmpeg	Alpha or odd WebP variants
FFmpeg only	Simple photo WebP at scale
GetCompress	GUI batch with width and quality presets

Animated WebP needs a still frame export first; this guide covers static WebP only. For motion assets, export MP4 or GIF through your video workflow instead of flattening animation into one JPEG.

Using GetCompress

GetCompress fits convert WebP to JPG on Windows when Paint one-by-one is too slow or you need consistent max width across a folder.

Drag WebP files or a project folder into the app. Choose JPEG output, set max width and quality, then export.

Workflow features that help:

• Batch queue: convert a full asset drop without PowerShell scripts.
• Presets: save “client JPEG 85%” for repeat handoffs.
• Resize plus convert: cap width for email in one step.
• Local processing: keep staging UI and unreleased marketing off online converters.
• Folder monitoring: auto-convert new WebP drops when your pipeline saves to a watched folder.
• Quality presets: when Outlook or a CRM rejects oversized attachments.

After conversion, compress further in the same app if JPEG files still exceed upload limits. Reuse the same preset each sprint so web and sales teams get predictable file sizes without another PowerShell script.

Windows marketing ops can watch a shared assets\incoming\ folder for WebP drops from CI, auto-convert to JPEG for sales enablement, and leave production WebP untouched on the CDN. Folder monitoring in GetCompress fits that handoff without scheduled Task Scheduler scripts.

When Paint opens WebP but colors look washed out, trust dwebp or GetCompress instead of saving from Paint for brand-critical assets. Spot-check hex values against the Figma spec on one file before batching the folder.

PowerShell loops fail silently when dwebp is not on PATH after winget install. Open a new terminal after install, run dwebp -version once, then batch. GetCompress avoids that PATH friction for teams who batch WebP every sprint without maintaining scripts.

Outlook inline images still prefer JPEG on many corporate tenants. Convert WebP sprint assets before dropping them into HTML mail templates; otherwise recipients see broken image placeholders even when the same WebP loads fine in Chrome.

Design ops can pair GetCompress folder monitoring with a staging-to-jpeg\ output folder so sales always picks up JPEG bundles while engineering keeps WebP in the repo for production. Same source drop, two local output presets, no upload converters.