PDFJadoo › Blog › BMP to WebP: Legacy Image on the Web

BMP to WebP: from raw pixels to page weight, edges respected

The direct answer: drop the BMP, pick the quality — High (92%), Balanced or Smaller — and the legacy image comes back as a WebP a small fraction of its raw size, with any transparency kept, ready to live on a web page. BMP to WebP is a combination article and says so: the BMP source story (uncompressed raw pixels, ~3 bytes each, the legacy folder's weight) meets the WebP destination story (predictive compression, alpha support, browser-native) — and the meeting is genuinely useful for one cargo in particular: screenshots and graphics whose sharp edges JPG's block compression would haze. WebP's lossy mode still compresses, so the edge rule from the sibling articles applies with a setting attached: edge-critical graphics belong at High; photographic bitmaps take Balanced happily; and where every pixel must stay exact for documentation, the PNG sibling remains the lossless answer. The boundary is the family's familiar one: WebP is for browsers — the archive keeps its BMP or PNG master, because forms, documents and print still live in the older formats.

Free, in your browserFiles never uploadedHigh 92% · alpha kept · browsers only
PDFJadoo logoBy the PDFJadoo Team4 min read
Diagram: a heavy legacy BMP screenshot becoming a light WebP on a web page
The screenshot was made before web pages mattered. Now it has to load on one.

Why WebP suits the legacy screenshot

The direct answer: a screenshot's flat regions and repeated patterns are prediction-friendly — WebP guesses each block from its neighbours and stores small corrections — so the file collapses far below the BMP's raw rent while keeping edges crisper than JPG's independent blocks manage at the same weight. Equipment screens, archived diagrams and old software captures are exactly this content. One quotable division of labour completes the family: PNG when the pixels must be provably exact (documentation, OCR), WebP when they must be light and legible (publication), JPG when the destination is the paperwork world. Same bitmap, three honest exits, chosen by where the image will live.

Transparency rides along: a capture with see-through regions keeps them in WebP, so a legacy graphic can float over a modern page's background — a small anachronism the format handles gracefully.

The republication workflow

The direct answer: archives and documentation libraries republishing old captures should convert from the BMP (or PNG) master per page, at High, and keep the masters untouched — web copies are regenerable; masters are not. A page rebuilt from masters can be re-converted when formats shift again, as they will.

Convert a BMP to WebP, step by step

The direct answer: drop the BMP — or a batch of legacy captures — pick High for edge content, convert, and download singly or as a ZIP.

Step 1 — classify the capture. Edge-critical (text, diagrams) → High, or PNG if exactness is provable-or-nothing. Photographic → Balanced serves.

Step 2 — drop your BMP onto BMP to WebP. Conversion runs on your device — no raw giants upload anywhere.

Step 3 — pick the quality. High (92%), Balanced or Smaller, by the image's job on the page.

Step 4 — press Convert to WebP and inspect an edge. The sharpest text or line at display size is the verdict.

Step 5 — download each file or the batch ZIP. Publish the WebP; the master stays in the archive.

When the page is not the destination

The direct answer: email, forms, office documents and print reject WebP as firmly as they reject BMP's weight — for those doors the legacy image exits as JPG (photos) or PNG (edges), and this converter stays a web-only tool. Destination first, format second, always.

The archive's screenshots, finally loadable on a web page.

High for edges, Balanced for photos, alpha kept — batches as ZIP, masters untouched.

Open BMP to WebP

Sources

A worked example: the equipment wiki

The direct answer: a maintenance wiki's forty legacy BMP screenshots — 230 MB of raw captures embedded in its old documentation — convert at High to WebPs totalling under 9 MB, and the wiki's pages go from timing out to loading instantly, with every equipment screen still legible at full size. The walkthrough's one exception proves the rule: two captures of dense diagnostic text were kept as PNG instead, because their readers zoom to 200% and exactness was the requirement. The other thirty-eight never missed the pixels they shed. Right exit per image, not per folder.

Edge cases

Photographic bitmaps for the web. Balanced WebP serves them as happily as JPG would, lighter; the JPG sibling matters only when the destination leaves the browser.

Colour-critical captures. Where a capture's exact colours are evidence (calibration screens, test output), publish the PNG and pay its weight — evidence outranks economy.

Before you finish: the 60-second check

Fair questions

Will BMP to WebP lose quality?

WebP is lossy at these settings, but at High (92%) images look identical to the eye at display size. For documentation where every pixel must be provably exact, use BMP to PNG instead — the lossless sibling.

Why not just use JPG for the web?

You can — but WebP is typically lighter at the same visual quality and keeps transparency, and it treats a screenshot's sharp edges more kindly than JPG's block compression. JPG's home is the paperwork world, not the page.

Does transparency survive?

Yes — transparent areas of your BMP stay transparent in the WebP, so a legacy graphic can float over a modern page's background.

Can I convert a whole batch?

Yes — drop as many BMP files as you like. Each converts with the same settings; download them one by one or all together as a ZIP.

How much smaller will it be?

Dramatically — raw BMP stores about 3 bytes per pixel with no compression, and WebP's predictive coding collapses flat, repetitive screenshot content especially well. Expect a small fraction of the bitmap's size.

Is my image uploaded?

No — the picture is decoded and re-encoded entirely on your device; your files never leave it.

Tool behaviour — the High (92%) / Balanced / Smaller quality settings, transparency kept, batch conversion with ZIP download — is from PDFJadoo's own BMP to WebP page. Checked 18 November 2026.

Keep reading