Windows bitmap badge
- Input
- An 80×50 24-bit BMP with a blue rectangle, pale background, and white BMP text, 12,054 bytes.
- Output
- A 501 byte RGB PNG at the same dimensions. The center sampled near the same blue as the input.
BMP → PNG compressed our 80×50 Windows BMP from 12,054 bytes to a 501 byte PNG without changing dimensions.
From real runs
| Element | Result | What happens |
|---|---|---|
| Pixel dimensions | Kept | The 80×50 BMP opened as an 80×50 PNG after conversion. |
| RGB colors | Kept | The blue center region and pale corner colors sampled as the expected RGB values in the PNG. |
| Compression | Changed | The uncompressed 12,054 byte BMP shrank to 501 bytes through PNG compression. |
| Alpha channel | Lost | The tested BMP was 24-bit RGB, so the output PNG was RGB and did not invent transparency. |
| Resolution metadata | Changed | BMP pixel-per-meter metadata was not exposed as a matching PNG metadata field in our inspection. |
| Editability | Kept | The PNG is still a raster image, suitable for pixel editing but not vector or layer editing. |
The 80×50 BMP opened as an 80×50 PNG after conversion.
The blue center region and pale corner colors sampled as the expected RGB values in the PNG.
The uncompressed 12,054 byte BMP shrank to 501 bytes through PNG compression.
The tested BMP was 24-bit RGB, so the output PNG was RGB and did not invent transparency.
BMP pixel-per-meter metadata was not exposed as a matching PNG metadata field in our inspection.
The PNG is still a raster image, suitable for pixel editing but not vector or layer editing.
We converted our BMP sample (703 KB) with Image engine on 2026-10-20. It took 62 ms and produced a 19 KB PNG file, 97% smaller than the input. The engine raised 1 warning, listed below.
Input · sample.bmp · 703 KB
600 × 400 px, 24-bit
Output · sample.png · 19 KB
600 × 400 px, 8-bit, colour type 2
A BMP scan converted to PNG is still a raster page. Use OCR-oriented workflows if the important output is text, fields, or table values.
ImageMagick 7
magick in.bmp out.pngPNG compression keeps raster pixels losslessly, but it does not recover layers or text from a screenshot.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=bmp&to=png.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.bmp" -F "from=bmp" -F "to=png" \
-F 'options={"dpi":96}' \
--output output.png| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading BMP | number | 96 |
| width | Writing PNG | number | 0 |
| height | Writing PNG | number | 0 |
| fit | Writing PNG | contain · cover · fill | contain |
| quality | Writing PNG | number | 90 |
| background | Writing PNG | string | #ffffff |
| stripMetadata | Writing PNG | boolean | true |
For the tested 24-bit BMP, PNG preserved the raster content without a lossy compression step. Metadata and application-specific BMP details are a separate issue.
BMP is often uncompressed. Our simple 12,054 byte bitmap became a 501 byte PNG because flat regions compress well.
No. The RGB BMP produced an RGB PNG. Transparency only exists if it is present and supported in the source data path.