Turn uncompressed bitmaps into smaller, web-friendly PNGs in your browser—up to 20 files, 100.00 MB each. Explore more utilities on Free tools, tighten bytes with the PNG Compressor, or resize with the Image Resizer.
PNG options
For 32-bit BMP with transparency. Off composites onto white before export.
zlib 1–9
Higher levels spend more CPU searching DEFLATE redundancy—often best for screenshots and flat UI. Default 6 balances speed and size.
Decoding uses the Canvas API via createImageBitmap in your browser. PNG encoding uses local zlib (pako) with your chosen level. Files are not uploaded to SynthQuery for conversion.
BMP files
Drop BMP here or click to browse
Up to 20 files · max 100.00 MB each · client-side only
About this tool
The Windows Bitmap (BMP) family stores pixels in a straightforward, largely uncompressed layout that engineers and legacy systems have relied on for decades—yet that honesty on disk translates into bulky files, slow email attachments, and formats modern browsers and CDNs handle reluctantly compared with Portable Network Graphics. SynthQuery’s free BMP to PNG Converter closes that gap without sending your images through a mystery upload queue. You drag in up to twenty .bmp files, each as large as one hundred megabytes, pick a PNG zlib compression level from one through nine with six as the balanced default, and decide whether thirty-two-bit bitmaps should keep real alpha or flatten onto white for tools that still fear transparency. Your browser decodes BMP natively through the same Canvas imaging stack it uses for JPEG and WebP, then SynthQuery rebuilds lossless PNG scanlines locally with configurable DEFLATE effort so flat screenshots and UI captures often shrink dramatically versus raw BMP row storage. A monospace-friendly byte readout beside every row shows honest before-and-after sizes—PNG is not magically smaller in every edge case, but uncompressed twenty-four-bit BMPs with repetitive colors routinely collapse once filtering and zlib get involved. Download individual PNGs, trigger staggered multi-file saves, or pack everything into a ZIP built with JSZip, all while your pixels stay on-device. That privacy posture matches our WebP Converter, PNG Compressor, and Image Resizer: you load the app shell like any website, yet conversion is client-side. Whether you are modernizing an archive of Paint exports, trimming Windows screenshot weight before Slack, or handing assets to a web team that expects .png slugs, this page is the fast, explainable bridge. Scroll to About & FAQ for format theory, desktop comparisons, and compression guidance, or jump to the Free tools hub when you want the full utilities grid beside AI writing and compliance tools.
What this tool does
SynthQuery focuses on predictable, inspectable conversion rather than black-box “optimize” buttons. BMP inputs decode through createImageBitmap and a two-dimensional canvas context with alpha enabled so thirty-two-bit sources retain separate transparency when you leave the preserve toggle on; turning it off premultiplies translucent edges against white and emits an RGB PNG, mirroring workflows where slide decks or older CMS fields flatten everything. PNG output is true lossless for the RGB or RGBA samples you encode: zlib level adjusts encoder effort, not pixel values, so you can re-run at nine for archival ZIPs and at three for quick drafts without worrying about generational blur. Batch processing reuses the same compression and alpha policy across every queued file, which keeps brand and documentation teams consistent when they harmonize dozens of bitmaps captured from the same tool. The comparison column translates raw bytes into human units and a signed percentage delta so stakeholders see whether storage savings justify the format shift without opening a spreadsheet. ZIP export uses JSZip in the browser, which means archives never touch SynthQuery disks either—only your CPU and memory participate. Accessibility is handled through labeled switches, slider association, keyboard-activatable drop zones, and decorative preview thumbnails with empty alt text because filenames already convey identity in the adjacent text. Limits mirror practical “desktop folder cleanup” scenarios: twenty files and one hundred megabytes each cover large screenshots and scanned pages while nudging users toward desktop Chrome or Edge when a phone feels sluggish. Unsupported exotic BMP variants—certain OS/2 headers, deeply embedded color profiles without decoder support, or truncated files—surface as row-level errors you can retry after repairing the source in a desktop editor. EXIF and other rich metadata blocks common in camera RAW pipelines are not part of classic BMP; do not expect automatic metadata transplant into PNG ancillary chunks beyond what the canvas exposes as pixels.
Technical details
BMP files typically store rows bottom-to-top or top-to-top depending on the height sign in the BITMAPINFOHEADER, with optional bit masks for sixteen- and thirty-two-bit modes; browsers abstract those details when they decode to bitmaps for Canvas. PNG, standardized as ISO/IEC 15948, describes IHDR dimensions, bit depth, color type, compression method zero (DEFLATE), filter method zero, and interlace method—SynthQuery writes non-interlaced truecolor RGB or RGBA streams with filter type zero per scanline prepended for simplicity and broad compatibility. Both formats are lossless at the sample level you encode: BMP’s “uncompressed” twenty-four- and thirty-two-bit modes store bytes literally (plus padding to four-byte row boundaries), while PNG wraps filtered rows in zlib streams, so repetitive colors—common in screenshots—compress well even though no frequency-domain lossy step occurs. Transparency differs: thirty-two-bit BMP often uses an explicit alpha channel in the pixel layout; PNG expresses alpha as a separate byte per pixel in color type six or via tRNS with palettes in other modes this tool does not target. Metadata expectations diverge: BMP seldom carries EXIF the way JPEG or HEIC does; PNG can host ancillary chunks such as tEXt, zTXt, or eXIf, but this converter does not synthesize those from BMP headers—what you see is what the canvas reads. Web platforms overwhelmingly prefer PNG or modern derivatives (WebP, AVIF) for crisp edges; BMP remains valid in img tags but triggers larger downloads and fewer optimization presets on CDNs. File size comparisons on this page measure container bytes only; perceptual quality is identical aside from alpha handling when you disable preservation. For regulated workflows, log whether flattening occurred and whether originals remain archived immutably.
Use cases
IT departments migrating thousands of legacy Help screenshots from BMP to PNG can queue manageable batches, choose a high zlib level for redundant UI chrome, and attach ZIP outputs to knowledge-base tickets without installing IrfanView on every laptop. Graphic designers receiving brand assets from vendors who still export Windows bitmaps drop them here before Figma or Affinity import, preserving alpha when logos include soft edges. Game modders converting texture dumps from older engines keep thirty-two-bit alpha for overlays while shrinking mod download sizes compared with raw DIB stores. Photographers scanning reflective prints sometimes receive BMP intermediates from scanner software; PNG gives them a lossless web-friendly handoff before optional JPEG or WebP for delivery. Marketing teams cleaning Windows Print Screen folders before email campaigns avoid ten-megabyte inline images by re-encoding to PNG and then running the PNG Compressor for palette quantization when appropriate. Archivists building public-domain image sets normalize on PNG for consistent HTTP caching headers and predictable color types while documenting encoder settings in README files. Developers embedding icons in Electron or Tauri apps replace BMP resources with PNG to simplify retina scaling and reduce installer weight. Educators publishing lab manuals with diagrams originally saved from classic Paint teach students why compression levels matter by toggling zlib and reading byte deltas live. Agencies juggling mixed Windows and macOS studios use the browser tool as a neutral meeting-ground format step before creative suites ingest files. Whenever AI-generated or AI-edited imagery sits next to these conversions, pair SynthQuery’s AI Content Detector and Humanizer on surrounding copy so compliance matches visual polish.
How SynthQuery compares
Microsoft Paint, IrfanView, GIMP, and Affinity Photo can all save PNG from BMP when installed, updated, and permitted by IT policy. SynthQuery targets the moment you already have files in Downloads, need consistent zlib control, and do not want to launch a full editor or upload confidential pixels to a hosted converter. The table below summarizes common trade-offs—pick based on whether you need RAW development, batch scripting, or a zero-install browser workflow.
Aspect
SynthQuery
Typical alternatives
Install footprint
Runs in a modern browser tab; no MSI, App Store, or plugin hunt before converting.
Paint and GIMP require local installs; IrfanView is Windows-first with its own update cadence.
Batch + ZIP
Queue up to twenty BMPs, compare sizes, download individually or as a JSZip archive.
Desktop tools support batch when you learn their automation or shell integrations.
Compression control
Explicit zlib level 1–9 with a labeled slider and documented defaults.
Some exporters hide PNG effort behind generic quality or export presets.
Privacy posture
Decode and encode locally; BMP bytes are not sent to SynthQuery for conversion.
Hosted converters may upload to shared infrastructure—read terms for confidential art.
Alpha handling
Toggle preserve alpha for 32-bit BMP or flatten to white for RGB PNG output.
Editors offer similar choices but buried in export dialogs.
How to use this tool effectively
Start with the BMP masters you actually intend to ship—renamed exports from design tools, Print Screen captures, or legacy scanners. If a file is not truly a bitmap, the queue will surface a decode error instead of silently corrupting pixels, so keep vendor-specific DIB variants backed up until you verify the browser read them correctly. Open the left column and set PNG zlib level: values near one finish quickly and suit rapid iteration on large batches; values near nine spend more CPU searching redundancy in filtered scanlines, which often pays off on screenshots with big solid regions. Toggle Preserve alpha channel when your source is thirty-two-bit BMP with meaningful transparency for icons, overlays, or game sprites; disable it when you know the destination will composite on white anyway and you prefer a smaller RGB PNG without an alpha plane. Click Add BMP or drag files onto the dashed hero card—the tool accepts the image/bmp MIME type and common .bmp extensions, enforces the hundred-megabyte ceiling per file, and caps the queue at twenty entries to protect mobile RAM. Each row shows a thumbnail from a blob URL, original filename, and byte size. Press Convert to PNG to process pending or errored rows; if every row already succeeded, the same button re-encodes the full list so you can compare a compression preset change without re-uploading from disk. Watch the spinner while Canvas decode and PNG assembly run on the main thread—very wide or tall bitmaps may take noticeable time on older hardware, so close heavy tabs first. When rows complete, use per-file download buttons if your browser blocks multiple automatic saves, Download all (separate files) for a timed sequence, or Download ZIP for a single attachment. Read the inline percentage hint: negative numbers mean PNG is smaller than BMP; positive numbers mean the PNG structure outweighed zlib savings for that particular raster—rare but possible on tiny icons. After export, open the PNG Compressor if you want palette tricks or another lossless pass, the Image Resizer when dimensions must match Shopify or Open Graph cards, or the WebP Converter when production delivery wants modern raster containers. Return to Free tools whenever you need calculators, generators, and detectors in the same design system.
Limitations and best practices
Extremely large dimensions can still exhaust memory even under the hundred-megabyte file cap because decode expands to four bytes per pixel in RGBA Canvas paths—process giant bitmaps on desktop and close other tabs first. Animated BMP is uncommon; this tool treats each file as a still image. Embedded color management beyond sRGB is interpreted as the browser decodes it; prepress teams should verify ICC expectations in desktop suites. When PNG outputs grow rather than shrink, try zlib nine on flat graphics or disable alpha if you do not need it; if still larger, the source may already be inefficiently stored BMP with noisy photographic content where zlib helps less. Always retain originals when legal or archival policy requires immutable masters. SynthQuery does not replace legal review for licensing, model releases, or AI disclosure—use adjacent policy generators when publishing commercially.
Full catalog of AI detection, readability, plagiarism, humanization, and media utilities.
Frequently asked questions
Often much smaller for typical screenshots, diagrams, and UI captures because BMP stores largely uncompressed pixels while PNG applies lossless zlib to filtered scanlines. The exact ratio depends on image content: flat colors compress well; already noisy photographic BMPs may see modest savings. Use the on-page byte comparison to see your real delta per file rather than trusting generic marketing ratios.
Yes for the RGB or RGBA samples you encode. Neither BMP (in common 24/32-bit modes) nor PNG applies JPEG-style lossy quantization. Changing zlib level only affects how hard the DEFLATE stage searches for redundancy—it does not discard detail.
When Preserve alpha channel is enabled, thirty-two-bit BMP sources with alpha decode through Canvas and re-encode as RGBA PNG. When disabled, semi-transparent pixels composite onto white and the tool writes an RGB PNG, which is smaller and easier for tools that mishandle alpha.
PNG is widely optimized on the web, supports lossless compression, handles alpha cleanly, and usually yields smaller files for many bitmaps. BMP remains valid but is heavier for distribution, less common in responsive image pipelines, and often awkward for email and chat attachments.
Yes. Queue up to twenty BMP files, convert them sequentially, then download individually, as separate timed downloads, or inside one ZIP archive.
Decoding relies on your browser’s BMP support, which covers common Windows DIB layouts including many legacy bit depths. Obscure OS/2 variants, corrupted headers, or truncated files may fail with a row-level error—repair or re-export from a desktop tool and try again.
Level six is the default balance of speed and size. Use lower levels (1–3) for quick drafts or huge batches when CPU time matters. Use higher levels (7–9) when you will store or redistribute PNGs and want the smallest lawful DEFLATE payload your patience allows.
Conversion runs locally in your browser: BMP files are not uploaded to SynthQuery servers for processing. You still download the web app like any site, but image payloads stay on your device unless you choose to share the outputs elsewhere.