Skip to content

Convert WebP to JPG on Windows: 3 Methods

Convert WebP to JPG on Windows with GetCompress, Paint, or PowerShell. Flatten transparency first for email, slides, and apps that only accept JPEG.

By Petr Samokhin

A project folder lands with WebP exports from the web team. A colleague opens them in Outlook or PowerPoint and gets blank placeholders. Many CRM uploads, print vendors, and older Windows apps still expect JPEG.

Convert locally, keep the WebP masters for production, and flatten transparency before JPEG export when the asset had an alpha channel.

WebP vs JPEG

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

WebPJPEG
Modern browsersNativeNative
Email attachmentsOften failsOpens widely
PowerPoint / WordHit or missReliable
TransparencyYesNo (flatten first)
Typical file sizeSmaller at similar lookLarger but universal
WorkflowRecommendation
Production websiteKeep WebP, add JPEG fallback if needed
Client email bundleConvert to JPEG
Design review in slidesJPEG, or PNG if you need transparency
File useJPEG quality hint in GetCompress
Email bundleHigh or Medium, max 1920 px wide
Print vendorHigh or Original; ask for color profile needs
CRM thumbnailMedium or Low; cap width per portal rules

For broader image compression, see how to compress images on Windows . For exporting WebP from PNG, see PNG to WebP on Windows .

Animated WebP is out of scope here. Use a video or GIF workflow for motion assets.

Method 1: GetCompress

Best for: Asset drops, consistent max width, and reusable sales JPEG presets.

GetCompress main window with image settings open, including quality, resolution, and format options
  1. Open GetCompress and drop WebP files or a folder into the queue.
  2. Choose JPEG output. Set quality and an optional max width.
  3. Export to a new folder. Keep the WebP originals.

Processing stays on your PC. Save a preset such as “client JPEG 85%” so you can reuse it next time. Folder monitoring can watch an incoming folder when web CI drops WebP assets for sales enablement. Exact target file size is a video workflow only; for images, use quality and dimensions.

Method 2: Convert one file in Paint

Best for: A handful of files on Windows 11.

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

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

Limitation: Tedious for dozens of files. Colors can look off on brand-critical assets; verify against the design source.

Method 3: Convert many files in PowerShell

Best for: Scripted folders when you already use winget tools.

winget install webp
winget install --id Gyan.FFmpeg -e

Open a new terminal after install, then confirm dwebp -version once.

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"
}
MethodBest for
dwebp + FFmpegTricky WebP, including alpha
FFmpeg onlySimple photo WebP batches

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

Limitation: PATH and install friction. Silent loop failures are common if dwebp is missing after winget install.

Which method should you use

SituationStart here
Files you send often, width + quality presetsGetCompress
Under about 10 filesPaint
Scripted foldersPowerShell

Outlook inline images still prefer JPEG on many corporate tenants. Convert before dropping assets into HTML mail templates.

When Paint is enough

Paint is enough for a few JPEG attachments when the preview looks correct.

GetCompress also helps when you often get a folder of WebP assets for sales or support: one preset, local processing, optional resize, and optional folder monitoring. Keep production WebP on the CDN. Convert delivery copies only.