filetity

BMP -> WEBP · Local tool

BMP to WebP

Turn uncompressed BMP files into WebP, sized for a web page.

Last updated

  1. 01 / Your device

    the file stays here

  2. 02 / Browser memory

    the work runs locally

  3. 03 / Back to you

    saved on this device

When you would use this

Situations, not settings.

A bitmap headed for a web page
Two problems at once: nothing serves BMP, and the file is far too heavy. One pass fixes both.
Screen captures going into documentation
A docs site full of raw bitmaps loads slowly. The same screenshots as WebP are a fraction of the weight.
A build pipeline that expects modern formats
Asset tooling often refuses BMP outright rather than converting it. Handing it WebP skips the argument.

How it works / no cloud

A conversion engine, not an upload form.

Your browser decodes BMP and encodes WebP, so filetity reads the bitmap, redraws it and writes WebP at the quality you choose. Nothing is uploaded and no extra engine is downloaded, because both codecs are already in the browser.

  • Offline ready
  • Installable app
  • No file limit queue

Straight answers

No accordion. Nothing hidden.

Is it free?
Yes, with no watermark and no page limit.
Does it need an account?
No. There is no account system.
Is my file processed on my device?
Yes. The file is read by your browser and never uploaded. There is no server to send it to.
What formats are supported?
BMP in. WebP out, one file per image, or a ZIP when you convert several.
What are the limits?
No image count limit. WebP is lossy at the default quality, so this is the picture's first lossy pass. Older desktop software and print counters still refuse WebP, so check where the file is going.
Does it work on mobile?
Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
Does it work offline?
Yes, after you have used it once. Your browser keeps what the tool needs, so it then works with no network connection.
Why go to WebP rather than JPG?
Because WebP holds transparency and packs the same picture tighter at a matching quality. If the file is going on a web page, WebP is the better target. If it is going to a print counter or an old program, JPG is the safer one.
Is this reversible?
No. WebP is lossy at the default quality, so detail the BMP stored exactly is thrown away to get the size down. Keep the BMP if you might need to edit the picture again later.
What size difference should I expect?
A large one. A BMP is not compressed at all, and WebP is among the better compressors available inside a browser, so the two are not close. The measured figure is shown before you download.
Can I go straight from a screenshot to WebP?
Yes. Windows screen capture and older scanner software still write BMP, and one pass turns that straight into something a page can serve.
Why does it say an image could not be read?
Almost always a damaged file or an unusual colour profile, which the browser's decoder rejects. Open the BMP in any image viewer and save it again, then retry. When several were dropped, nothing is written until every one decodes, so one bad file holds up the batch.

Keep working locally

7 available · more coming