PDF to BMP Converter
Convert PDF pages to BMP bitmap images at custom DPI. Client-side processing — your files never leave your browser.
How to Use
Convert any PDF to BMP bitmap images in four steps:
- Upload your PDF — Drag and drop the file into the dropzone or click to browse your device. The tool reads the document locally and displays the page count and file size. No data leaves your browser at any point during the process.
- Select a DPI setting — Choose 72 DPI for screen-resolution images suitable for previews and web use, 150 DPI for general-purpose output that balances quality and file size, or 300 DPI for high-fidelity prints and archival scans. A US Letter page at 300 DPI produces a 2550 × 3300 pixel image.
- Click "Convert" — The tool renders each PDF page to an in-memory canvas, reads the pixel data, and constructs BMP files with proper BITMAPFILEHEADER and BITMAPINFOHEADER structures. A progress indicator tracks page-by-page conversion so you know exactly where the process stands.
- Download your BMP files — For single-page PDFs, click download to save the BMP directly. For multi-page documents, download individual pages or use the "Download All as ZIP" button to get every page in a single archive.
The entire pipeline runs in your browser using PDF.js for PDF rendering and the Canvas API for pixel extraction. Your PDF is never uploaded to any server, making the tool suitable for confidential documents, legal filings, and medical records.
About This Tool
BMP (Windows Bitmap) is one of the oldest raster image formats, dating back to Windows 2.0 in 1988. The format stores pixel data without any compression algorithm — every pixel occupies exactly 3 bytes (one each for blue, green, and red channels) in a 24-bit BMP. This makes BMP files significantly larger than PNG or JPEG equivalents but guarantees zero quality loss and zero decoding complexity. Any image viewer, operating system, or embedded system can open a BMP without needing a decompression library.
The BMP file structure consists of three parts. First, a 14-byte BITMAPFILEHEADER containing the 'BM' signature, total file size, and the byte offset to pixel data. Second, a 40-byte BITMAPINFOHEADER specifying image width, height, color depth, and DPI resolution. Third, the raw pixel array. BMP stores rows bottom-to-top (the first row in the file is the bottom of the image) and uses BGR byte order rather than the RGB order common in other formats. Each row is padded to a 4-byte boundary, which means some rows contain 1-3 zero bytes after the last pixel.
This tool renders each PDF page through the browser's Canvas API, which produces RGBA pixel data in top-to-bottom, RGB order. The processor then transposes this data into BMP's bottom-to-top BGR layout, constructs the binary headers, and assembles the complete file. Since the Canvas API cannot natively export BMP files (it supports PNG, JPEG, and WebP), the entire BMP construction is implemented from scratch using typed arrays and DataView for precise byte-level control over the little-endian header fields.
Resolution directly controls the output dimensions and file size. A standard US Letter page (8.5 × 11 inches) at 72 DPI produces a 612 × 792 pixel image occupying roughly 1.4 MB as a 24-bit BMP. The same page at 150 DPI yields 1275 × 1650 pixels and about 6.3 MB. At 300 DPI, the image reaches 2550 × 3300 pixels and approximately 25.2 MB. Memory consumption during rendering scales with the square of DPI, so 300 DPI requires four times the pixel buffer of 150 DPI. This tool processes pages sequentially, releasing each canvas after encoding, to keep peak memory usage manageable.
For related PDF conversion workflows, the PDF to Images tool produces PNG or JPEG output with much smaller file sizes. If you need to flatten a PDF into image-based pages while keeping it as a PDF, use Rasterize PDF. To reduce color PDFs to black and white before conversion, try the PDF to Greyscale converter.
Why Use This Tool
Despite its large file sizes, BMP remains relevant in specific technical and professional contexts where uncompressed data is either required or preferred:
- Legacy system compatibility — Industrial automation equipment, older medical imaging software, and embedded display controllers often require BMP input. These systems may lack the processing power or libraries needed to decode PNG or JPEG compression. BMP's simple, headerless pixel layout makes it trivial to parse even on microcontrollers with limited firmware.
- Pixel-perfect accuracy — BMP's zero-compression guarantee means every pixel is preserved exactly as rendered. Unlike JPEG (which introduces compression artifacts around text edges) or even PNG (which uses lossless compression that some strict workflows distrust), BMP provides a byte-for-byte faithful representation of the original rendering. This matters in forensic document analysis and quality assurance testing.
- Windows application pipelines — Many Windows-native applications, print drivers, and batch processing scripts expect BMP input. The Windows GDI/GDI+ subsystem handles BMP natively with zero overhead, making it the natural interchange format for Windows-centric document workflows that extract pages from PDFs for further processing.
- Scientific and research data — Researchers sometimes require uncompressed image exports of published PDF figures for measurement, color analysis, or computational processing. BMP ensures no compression algorithm alters the pixel values between the PDF rendering and the analysis software.
- Print and pre-press proofing — Pre-press workflows occasionally use BMP as an intermediate format when verifying page rasterization at exact DPI settings before sending documents to commercial printers. The uncompressed format eliminates any variable introduced by compression algorithms.
Processing PDFs locally is particularly important for BMP conversion because the uncompressed output files are very large and slow to transfer over a network. A 10-page document at 300 DPI produces roughly 250 MB of BMP data. Uploading the PDF to a server, converting, and downloading the results would consume significant bandwidth and time. Local processing eliminates this bottleneck entirely. For additional post-processing, use PDF Compress to reduce the source PDF first, or PDF Split to convert only the pages you need.