drag & drop, click, or paste from clipboard
Drop to add
drag & drop, click, or paste from clipboard
PNG is a better format than BMP by almost every measure — smaller files, lossless compression, full alpha transparency support. The only reason to convert from PNG to BMP is because a specific downstream application demands BMP and will not accept PNG. That situation is more common than you might expect: older industrial machines, certain embedded system flash tools, legacy Windows applications built before PNG support was ubiquitous, and some hardware testing toolchains all fall into this category.
Two facts to prepare for before running this conversion: first, the output files will be substantially larger than the source PNGs — an uncompressed 24-bit BMP stores every pixel as three raw bytes with no compression, so a 1 MB PNG may become a 10–20 MB BMP. Second, transparency does not survive the conversion. Standard BMP has no alpha channel; any transparent or semi-transparent areas in your PNG will be filled with a solid color — white by default, or black if you configure the tool that way.
PNG transparency works at per-pixel level — each pixel carries an opacity value from 0 (fully transparent) to 255 (fully opaque). BMP carries none of that; the format simply does not have an alpha channel in its standard 24-bit form.
When Enhydra RPO converts a PNG with transparency to BMP, it composites the PNG onto a solid background before encoding:
Soft edges (anti-aliased logo outlines with partial transparency) become hard edges against whichever background you select. This is an unavoidable consequence of the format limitation.
The size increase from PNG to BMP is the other unavoidable reality of this conversion. PNG uses lossless compression that is highly effective for images with large uniform areas and sharp edges — typical for logos, UI graphics, and illustrations. BMP stores raw pixels with no compression at all.
A rough guide: a PNG file at 2000×2000 px is typically 200 KB to 2 MB depending on content. The same image as BMP is exactly 2000 × 2000 × 3 bytes = 12 MB, every time, regardless of content. For batches of large images, output ZIP sizes can be large — verify you have adequate disk space before running a batch of high-resolution PNGs.
This size difference is why BMP is not used for general-purpose image storage. It is format-compliance output for software that demands it, not a quality or workflow improvement over PNG.
Yes. The tool offers a background color option — white or black — for transparency flattening. Select the one that matches what your downstream software expects before running the batch.
No quality is lost in terms of visible pixel values for opaque areas. BMP is uncompressed and lossless. The only change to the image is that transparent areas are replaced with a solid color.
PNG uses lossless compression, sometimes reducing file size by 70–90% compared to raw pixel data. BMP stores raw, uncompressed pixels. The BMP size reflects the true uncompressed footprint of the image data.
Enhydra RPO outputs standard 24-bit BMP. If your target software specifically requires 8-bit (256-color indexed) BMP, the output may not be accepted. Check your software documentation for the exact BMP variant it supports.
Not directly — BMP cannot carry transparency. The transparent areas will always be filled with a solid color. If your software can work with an alternative format that supports alpha (like 32-bit BMP or TIFF with alpha), that may be a better path.