Why will my software not open a .webp file?

WebP was designed for browsers, and desktop software was slow to follow. Photoshop only added support in 23.2, Office in 2021, and Outlook still will not render one inline. Converting to BMP sidesteps the problem entirely.

More about converting WebP to BMP

Convert WebP to BMP when the destination is a machine rather than a person — legacy Windows software, industrial control panels, lab instruments and embedded systems that accept uncompressed bitmaps and nothing else. None of them have any idea what a WebP is. WebP is a delivery format, not a working format. Browsers render it everywhere, but the moment a .webp leaves the browser it hits software that never caught up — Photoshop only added WebP support in version 23.2, Office before 2021 will not place one, Outlook will not render one inline, and a long tail of upload forms validate against a hard-coded list that has never heard of it.

BMP — Windows Bitmap — is none — three uncompressed bytes per pixel with technically in 32-bit mode; most software ignores it and support described as: universal, but rarely the preferred format anywhere. Where WebP is optimised for the last hop to a browser, BMP is what the software on the other side of that hop is expecting. Converting is a one-step fix for the "this file type is not supported" wall.

Size is the trade-off worth knowing about: BMP files are 15-40x larger than WebP — a 2 MB WebP becomes a 35 MB BMP. Plan for the size: BMP output is roughly width x height x 3 bytes regardless of what the picture contains. Resize before converting if the destination caps file size.

When you'd use this

Reasons to convert WebP to BMP usually come down to compatibility, file-size, or specific feature requirements. Common situations:

  • An app or platform only accepts BMP uploads.
  • You need a feature unique to BMP (e.g. transparency, vector scaling, animation, multi-page pages, etc.) that WebP doesn't provide.
  • You're optimising file size — modern formats often produce smaller files than the older format you started with.
  • You need a single archival format across a project so files behave consistently in the same viewer.

How to do it in webp.now

  1. Open the WebP → BMP tool on webp.now.
  2. Drag your WebP file onto the drop zone, or click Select files. You can drop a whole folder of files at once.
  3. The output is fixed to BMP. If the format supports extra options (page size, transparency background, quality, EXIF stripping), tweak them in the right-hand panel.
  4. Click Convert. The job runs on our server and finishes in a few seconds for typical photos.
  5. Download the result. Files stay in storage for 24 hours and are then permanently deleted.

The entire flow is free for the first 10 jobs per day with no signup required. A free account doubles that quota; a premium plan removes the limit entirely.

Tips and common pitfalls

  • If the goal is simply "make this open in my software", BMP is usually the right call — but check whether the destination accepts PNG or JPG first, since those are accepted even more widely.
  • Convert from the highest-quality WebP you have. Each lossy re-encode costs a little detail, and starting from an already-compressed copy compounds it.
  • Strip metadata before sharing. Images saved from the web can carry the original photographer's EXIF, including camera serial and, occasionally, GPS coordinates.
  • Batch the job rather than converting one at a time — the queue runs conversions in parallel and returns a single zip.
  • Keep the .webp original if the image is also going back onto a web page. Serving the BMP version instead will cost you page weight.
Try the WebP → BMP tool
Free, no signup required. Files deleted in 24 h.
Open WebP → BMP
Back to all FAQ