BMP to PNG conversion turns raw, uncompressed bitmap data into a compressed file that holds exactly the same pixels. Both formats are lossless, so no image information is discarded in either direction. What changes is only how the pixels are stored: BMP writes every row out raw, while PNG passes those rows through deflate compression first. In one internal test, a 1,440,674-byte BMP came out at 776,680 bytes as a PNG, a reduction of roughly 46 percent with every pixel value preserved. Smaller file, identical content, which is what makes this the safe conversion to run before editing, archiving, or uploading a bitmap anywhere.
What the DocPivot BMP to PNG Converter Does
The DocPivot converter reads a BMP file byte by byte, keeps every pixel intact, and writes a PNG that carries the same image data in a compressed container. There is no quality setting, no background color picker, and no flattening step, because none of those choices apply when both the input and the output are lossless. The tool reads the bitmap, preserves what is there, compresses it, and hands the file back.
It also reads 32-bit BMP files whose alpha channel is properly declared through a BITMAPV4 header with explicit channel masks. That matters more than it sounds, and the section on transparency below explains why some 32-bit bitmaps carry usable alpha and others do not. You can process up to 30 files in a single pass, which is the practical difference between converting a folder of screenshots and converting them one at a time.
If you need a different output format instead, the BMP to WebP converter produces smaller files at the cost of older-browser compatibility, and the BMP to AVIF converter goes smaller still.
How the DocPivot BMP to PNG Converter Works
DocPivot runs the conversion as a five-step pipeline inside your browser, with no upload at any stage.
- Read the bitmap. The file is decoded from its bytes, including 32-bit variants where the alpha channel is declared through a BITMAPV4 header with explicit red, green, blue, and alpha masks.
- Keep everything. No flattening, no background fill, no quality dial. Those controls are hidden rather than displayed in a disabled state, because PNG holds exactly what BMP holds and an inert slider only invites confusion.
- Optimize with oxipng. The PNG is compressed with oxipng compiled to WebAssembly, the same lossless optimizer used by Google Squoosh. The effort level is selected from the pixel count, so a large image finishes in seconds rather than stalling the tab for a marginal byte saving.
- Resize if requested. Options are original size, 2048 pixels, or 1200 pixels on the longest edge, and all of them shrink only. Asking for a size larger than the source changes nothing rather than upscaling and softening the image.
- Deliver the result. A single file keeps its original name with a new extension. Multiple files arrive as a ZIP archive, with dimensions and final size shown on each result card.
Because the entire pipeline runs on your own device, conversion speed depends on your processor and available memory rather than on server load or a queue position. A batch of small screenshots finishes almost immediately. A batch of large scanned bitmaps takes longer, and that is a property of your hardware, not a throttle.
What Happens to Each Part of Your File
Every component of a BMP has a defined outcome in the converted PNG, and none of them involves guesswork or a quality trade-off.
| Component | Result in the PNG |
|---|---|
| Pixels | Bit-for-bit identical to the source |
| Transparency | Preserved where the BMP declares alpha properly |
| Color depth | 24-bit sources produce PNG color type 2; alpha sources produce color type 6 |
| Compression | Raw rows become deflate streams, with filters selected by oxipng |
| EXIF and metadata | BMP carries none, so none is written |
| File size | Roughly halved on the test file described below |
The absence of metadata is worth stating plainly. BMP has no EXIF container, so there is no camera model, timestamp, or GPS coordinate to strip out. If your original photographs came from a phone and you need to check or remove that data before it reaches a bitmap workflow, the EXIF viewer shows what a JPEG or HEIC file is actually carrying.
File Size Results from the DocPivot BMP to PNG Converter
On the test file measured during development, a 1,440,674-byte BMP converted to a 776,680-byte PNG, a saving of about 46 percent. That figure comes from a single file and should be read as one data point rather than a guaranteed ratio, because PNG compression is content-dependent in a way that JPEG quality settings are not.
The variable is how much repetition the image contains. PNG compresses flat regions, solid fills, sharp edges, and repeated patterns extremely well. Screenshots, diagrams, logos, scanned line art, and interface mockups often compress far past 50 percent. A photographic bitmap with fine gradients and sensor noise compresses much less, because there is little for deflate to find. Two BMP files of identical dimensions can produce PNG files of very different sizes, and neither result indicates a problem.
If the goal is the smallest possible file rather than an exact copy, PNG is the wrong target format. The BMP to JPG converter will typically cut a photographic bitmap by 85 percent or more, at the cost of discarding data permanently. For an existing PNG that is already larger than you want, the image compressor handles the reduction step separately.
Transparency and 32-Bit BMP Files
A 32-bit BMP does not automatically carry a usable alpha channel, and this is the single most common surprise in BMP conversion. Whether transparency survives depends on which header the file was written with, not on the converter.
Under the classic 40-byte BITMAPINFOHEADER with BI_RGB compression, the specification defines the fourth byte of each pixel as unused padding, not as alpha. Browsers honor that definition correctly, so a 32-bit BMP written with the older header arrives fully opaque and there is genuinely no transparency to preserve. Under a BITMAPV4 header with BI_BITFIELDS, the file declares explicit channel masks including an alpha mask, and that alpha round-trips exactly into the PNG.
This is why a bitmap that looked transparent in one application opens opaque in another. The two programs made different assumptions about an undefined byte. DocPivot follows the declaration in the file rather than guessing, which means the result is predictable even when it is not the result you hoped for. If your source needs guaranteed transparency, keep it in a format that specifies alpha unambiguously; converting a working PNG through the PNG to WebP converter preserves alpha without the header ambiguity, and the WebP to PNG converter brings it back.
Who Uses the DocPivot BMP to PNG Converter
The tool serves people who receive BMP files rather than people who create them, since almost nothing produces BMP by choice anymore.
- Developers and QA testers handling screenshots from Windows utilities, automated test tooling, and older capture tools that still default to bitmap output.
- Archivists and records staff converting scanned bitmap collections into a compressed lossless format that halves storage without any preservation risk.
- Designers receiving legacy assets from clients, particularly logos and interface elements exported by discontinued software.
- Web and CMS teams who cannot upload BMP files because most platforms reject the format outright, and who need a web-compatible replacement.
- Engineers and technical staff working with instrument output, medical imaging exports, and industrial camera captures that still write uncompressed bitmaps.
What connects these cases is that the source file is not negotiable. Someone else produced it, the format is inconvenient, and the conversion has to be exact because the image may be evidence, a record, or a design asset that will be edited further.
When to Use the DocPivot BMP to PNG Converter
Convert BMP to PNG whenever you need the file to be smaller and web-usable without accepting any change to the image itself. That covers most situations where a bitmap has arrived in a modern workflow.
Use it before editing, because PNG is the format design applications, browsers, and content systems all accept without complaint. Use it before archiving, because halving a storage footprint with zero information loss is close to a free operation. Use it before uploading, because WordPress, Shopify, and most CMS platforms either reject BMP or handle it unpredictably. Use it when a file needs to be shared, since BMP attachments are large enough to hit email size limits that a PNG would clear comfortably.
Do not use it when file size matters more than exactness, when the image is a photograph destined for a web page, or when you already have a working PNG. For that last case, the PNG to JPG converter is the size-reduction path, and the image resizer handles dimension changes on their own.
Batch Conversion and Resizing in the DocPivot BMP to PNG Converter
DocPivot converts up to 30 BMP files in one pass, and the output arrives as a single ZIP archive when more than one file is processed. Each result card shows the output dimensions and the final byte size, so you can confirm the outcome before downloading rather than after.
The resize control offers three settings: original, 2048 pixels, and 1200 pixels on the longest edge. All three are shrink-only. Selecting 2048 pixels for an image that is already 1600 pixels wide leaves it at 1600 pixels, because upscaling adds interpolated pixels that were never captured and makes the image softer without adding detail. Resizing is the one operation on this page that is not lossless, and it is optional for exactly that reason.
For work that goes beyond a straight format change, the crop image tool handles composition and the general image converter covers format pairs that do not have their own dedicated page. If the converted PNG is destined for a browser tab icon, the favicon generator produces the full icon set from one square source.
How the DocPivot BMP to PNG Converter Compares to Server-Based Converters
The clearest difference between browser-based and server-based conversion is the daily limit, and the numbers here are lower than most people expect. Figures verified August 2026.
| Tool | Where it runs | Free daily limit | Batch size |
|---|---|---|---|
| DocPivot | Your browser | None | Up to 30 files |
| CloudConvert | Their servers | 10 conversions per day | Multiple, counted individually |
| Convertio | Their servers | 10 credits per 24 hours, 100 MB per file | Multiple, counted individually |
| FreeConvert | Their servers | 20 conversion minutes, capped at 10 operations | Multiple, counted individually |
| Squoosh | Your browser | None | One image at a time |
Browser-based processing on its own is not a distinguishing feature anymore, and it would be dishonest to present it as one. Google Squoosh runs locally, uses the same oxipng optimizer, and has no daily cap either. The practical gap is batch capacity: Squoosh is built for tuning one image with a comparison slider, not for pushing 30 bitmaps through in a single operation. Against the server-based converters, the gap is the cap itself, since a folder of 25 screenshots exhausts a free daily allowance on all three of them before you finish.
Limitations of the DocPivot BMP to PNG Converter
Several constraints are worth knowing before you start, and none of them have workarounds inside this tool.
Older 32-bit headers arrive opaque. A 32-bit BMP written with the 40-byte header declares its fourth byte as padding, so there is no alpha to carry across. This is a property of the source file rather than a fault in the conversion, and no converter can recover transparency that was never formally declared.
The saving is about half, not 88 percent. Lossless compression cannot match what JPEG achieves by discarding data. If a 46 percent reduction is not enough for your use case, the trade-off you actually want is a lossy format, not a different PNG encoder.
Photographic bitmaps compress poorly. PNG relies on flat regions and repeated patterns. Continuous-tone photography gives it very little to work with, and the resulting PNG may be only slightly smaller than the BMP.
Very large bitmaps consume memory. The image is decoded to a full-size canvas before encoding, so an extremely large BMP can strain a low-memory device or an older mobile browser. Converting such files in smaller batches is the reliable approach.
No metadata is written. Since BMP carries no EXIF or GPS data, none appears in the PNG. This is neither a privacy feature nor a loss, simply a fact about the source format. For genuine metadata removal on formats that do carry it, the remove metadata from photo tool is the correct page.
Frequently Asked Questions About the DocPivot BMP to PNG Converter
Yes. Both BMP and PNG store pixel values exactly, so the converted image contains the same pixels as the source. Only the storage method changes, from raw rows to deflate-compressed rows.
Roughly half, based on a test file that went from 1,440,674 bytes to 776,680 bytes. The actual ratio depends heavily on image content, with screenshots and diagrams compressing much better than photographs.
Yes, when the BMP declares its alpha channel through a BITMAPV4 header with explicit channel masks. Files using the older 40-byte header have no formally declared alpha and arrive opaque.
The file was almost certainly written with the 40-byte BITMAPINFOHEADER, which defines the fourth byte of each pixel as unused padding rather than alpha. Browsers follow that definition correctly, so there is no transparency in the file to preserve.
No. Every step runs inside your browser, so the files never leave your device. There is no upload, no server queue, and no stored copy.
Up to 30 files in a single pass. When you convert more than one file, the results are delivered as a ZIP archive.
No. Because processing happens on your own device rather than on a server, there is no per-day cap. The practical limit is your device memory when handling very large bitmaps.
Choose PNG when the image must remain identical, such as screenshots, logos, diagrams, and archival scans. Choose JPG when file size matters more than exactness, typically for photographs headed to a web page.
There is nothing to remove. BMP has no EXIF container, so a bitmap never carried camera, timestamp, or location metadata in the first place, and none is written into the PNG.
Because there is nothing to trade. Both formats are lossless, so a quality control would have no effect on the output, and a slider that does nothing is more misleading than no slider at all.
Yes. You can select 2048 pixels or 1200 pixels on the longest edge, and both options shrink only. Requesting a size larger than the original leaves the image unchanged rather than upscaling it.
There is no fixed limit, but the image is decoded to a full-size canvas before encoding, so available device memory sets the practical ceiling. Very large files convert more reliably in smaller batches.
Yes, on current mobile versions of Chrome, Safari, Firefox, and Edge. Large bitmaps are more likely to strain memory on a phone than on a desktop machine, so batch sizes should be smaller.
