Initializing... drag & drop files here
Supports: DOCX
BMP is Windows' plain-bitmap format: a header, an optional colour table, and a raw grid of pixels with no compression in its most common form. That makes it the format legacy Windows software, embedded viewers, and some imaging SDKs still ask for — and it makes the files enormous if you convert without thinking about resolution first. This tutorial covers the two decisions that matter when turning a Word .docx into BMP page images: the render DPI, and the Quality Preset, which on this page changes the colour depth and compression of the bitmap rather than the usual quality dial.
.docx onto the drop zone or click "Add Files". Pagination is resolved first, so each page of the document comes back as its own bitmap.BMP has no JPEG-style quality knob, so the preset selects a different encoding strategy entirely. This is why the usual "Target file size" and "Image Quality (%)" controls do not appear on this page — there is nothing continuous to tune.
| Quality Preset | What it writes | Colours | Compression | Use it when |
|---|---|---|---|---|
| High (default) | 16-bit RGB555 bitmap | 32,768 | None — raw pixel data | You want the closest match to the rendered page and file size is not a concern |
| Medium | 8-bit palette bitmap, Floyd–Steinberg dithered | 256 | RLE | The pages are mostly text and you need the files to be a manageable size |
| Low | Reduced palette, Floyd–Steinberg dithered | 86 | RLE | Size matters more than fidelity — simple black-on-white documents only |
Medium and Low both dither, which scatters pixels to simulate colours the palette cannot hold. On plain text that is invisible; on pages with photographs, gradients, or subtle brand colours you will see stippling if you look closely.
At the High preset each pixel occupies two bytes and nothing is compressed, so the file size of a page is predictable from its dimensions alone.
| Conversion Quality | A4 page pixels | Approximate size per page at High |
|---|---|---|
| 96 DPI | ≈ 794 × 1123 | ≈ 1.8 MB |
| 150 DPI | ≈ 1240 × 1754 | ≈ 4.3 MB |
| 300 DPI (default) | ≈ 2480 × 3508 | ≈ 17 MB |
| 600 DPI | ≈ 4961 × 7016 | ≈ 70 MB |
| 1200 DPI | ≈ 9921 × 14031 | ≈ 278 MB |
Multiply by the page count and the problem is obvious: a 20-page document at 300 DPI is roughly a third of a gigabyte of bitmaps. If those numbers are unworkable, either drop a DPI step, switch to the Medium preset, or use a compressed format such as DOCX to PNG.
.docx files cannot be opened for rendering. Remove the protection in Word, re-save, and upload again.Reach for BMP only when something downstream demands it. For anything web-facing it is the wrong choice — browsers do display image/bmp, but the files are many times larger than an equivalent PNG for no visual gain, which is why Mozilla's own image-format guidance recommends avoiding BMP for site content. For archives and print workflows, DOCX to TIFF offers lossless compression (pick LZW there) and the tagged metadata those systems expect. And if what you really need is a shareable, searchable copy of the document rather than pictures of it, DOCX to PDF keeps the text as real characters at a tiny fraction of the size.
Because BMP has no continuous quality parameter to expose. Each preset maps to a genuinely different encoding — 16-bit uncompressed, 256-colour RLE, or a smaller palette with RLE — so the presets that exist on lossy formats ("Highest", "Very High", "Lowest") have nothing to map onto and are hidden. For the same reason the "Target file size" and "Image Quality (%)" controls do not appear on this page.
Yes. The document is paginated first, then each page is rendered and written as its own bitmap, numbered in order. When there is more than one output file, a "Download All (Zip)" button appears so you can download the whole set at once.
The encoding is: neither the uncompressed High preset nor the run-length compression used by Medium and Low discards any of the pixels handed to the encoder. But Medium and Low reduce the image to 256 and 86 colours first, and that colour reduction is very much a loss. Only the High preset keeps the full rendered page, and even then at 5 bits per channel rather than 8.
Not in any way you can rely on. The classic bitmap header has no alpha channel, and while the later BITMAPV4HEADER and BITMAPV5HEADER variants can describe one, most software ignores it. This converter sidesteps the question by compositing every page onto a solid colour, White by default, which you can change under "Image Transparency".
No. Converting to any image format rasterises the page — words become pixels, so nothing can be selected, searched, or read by a screen reader. Keep the .docx, or export a PDF, when the text has to stay live.
Our pipeline lays the document out with LibreOffice on the server, prints it to an internal PDF so pagination matches what Word would print, rasterises each page at the DPI you selected, and then encodes each page image as a bitmap using the preset you chose. Nothing about the original document's structure survives that last step — the output is purely a picture of each page.
Because the layout is done by LibreOffice, not Word. Any typeface the document references that is not installed on the server is replaced with a metrically similar substitute, so pagination and line breaks normally hold while individual glyph shapes can differ. Embedding fonts in the .docx, or sticking to widely installed families, gets you the closest match.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. No sign-up, no watermark, and files are never shared or made public.