Convert HEIC to BMP
HEIC is a sensible camera-library format and a frustrating input for software that was built around Windows bitmaps. Converting HEIC to BMP gives an old editor, instrument, or upload form a simple raster file, but it also strips away the parts of a camera package that BMP cannot represent. Expect a large RGB bitmap containing the primary rendered photo, not a replacement for the original library asset.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your HEIC file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Converts the primary camera image for BMP-only applications
- Provides a simple uncompressed RGB bitmap for legacy readers
- Explains color, alpha, depth, and camera-library limitations
- No watermark and no sign-up
How to use HEIC to BMP
- 1
Choose the library photo
Add the HEIC still that an older program cannot open. Preserve the original in your photo library because a BMP cannot contain Live Photo motion, depth data, HDR gain information, or the other auxiliary images a phone may store beside its visible photograph.
- 2
Convert the primary image
The server decodes the primary HEIC image and writes its pixels to a BMP. The result keeps the source dimensions but uses a conservative bitmap representation. Transparent areas are flattened to white, and the output does not carry the HEIC container's extra camera layers.
- 3
Verify the old workflow
Open the bitmap in the exact editor, device utility, or upload form that needs it. Check skin tones, highlights, the white background, dimensions, and the larger file size before deleting the compatibility copy.
How it works
The server opens the HEIC container with an image decoder that understands the camera
image, selects the primary still, and expands it into pixels. Those pixels are then
written as a BMP with a header describing the canvas and color data. This is a real
decode and re-encode, not a filename change. The familiar .bmp suffix is useful only
because the output contains bitmap data that an older reader can parse.
HEIC is more than a small JPEG-like envelope around one flat picture in many camera workflows. A phone can include computational photography information that lets its library adjust a portrait blur, reveal highlight detail, or associate motion with a still. The primary image is what survives here. A BMP does not become a photo-library package merely because it came from one.
Why a library conversion needs a clear purpose
JPG, PNG, or WebP is normally a better sharing derivative for a camera photograph. HEIC-to-BMP is narrower: use it when a known application, measurement system, printer utility, or upload field supports BMP and rejects HEIC. The conversion can unblock an old workflow without asking the entire photo library to abandon its efficient source format. Make the bitmap from a copy and retain the HEIC for future exports.
The output is intentionally much larger. A 4032x3024 RGB bitmap needs roughly 36 MB of pixel storage before row padding and headers, regardless of whether the camera HEIC was a few megabytes. That cost can matter on removable media, email, device memory, or a server with strict upload limits. Downsize to the receiver's actual display or processing dimensions before conversion when full camera resolution is not part of the requirement.
Color and alpha boundaries
BMP readers tend to be old precisely when BMP is being requested. This route favors the conservative RGB form and flattens transparent regions onto white instead of writing an alpha channel that may be ignored. Check the destination's required bit depth and background assumptions. Some instruments need 24-bit color, while others expect indexed or monochrome data and will need a separate preparation step.
Finally, inspect the result in the program that rejected the HEIC, not only in a modern image viewer. A modern viewer may display a bitmap gracefully while the legacy consumer has a fixed dimension limit or a narrower color interpretation. The BMP is successful when that specific workflow can use it; the HEIC remains the authoritative camera-library file.
Examples
An iPhone photo for a laboratory archive tool
The archive tool now receives the bitmap it expects, but the result is not a complete camera original. HDR presentation data and library metadata stay in the HEIC workflow, while the BMP contains the decoded primary image. Resize a copy first if the receiving tool does not need the full camera dimensions.
A transparent HEIC illustration for a bitmap-only editor
The editor can import the file, but its BMP reader has no dependable alpha handling. The soft edge is rendered against white rather than left as an optional channel that the old program might ignore. Use a deliberate background color in the source workflow when white is not suitable.
Frequently asked questions
What part of a camera HEIC becomes the BMP?
The converter writes the primary rendered image, which is the ordinary photo a viewer expects to see. A phone may package depth maps, HDR gain data, a thumbnail, alternate images, or motion assets alongside that image. Those structures belong to the HEIC or photo-library workflow and have no place in a simple BMP. Keep the original if later editing, Portrait adjustments, or a Live Photo is important.
Will the HEIC colors remain exactly the same?
The visible decoded pixels are written to the bitmap, but the formats do not expose every modern camera color feature in the same way. Wide-gamut or HDR presentation can be simplified by the legacy RGB output and by the application that opens it. Compare highlights, saturated reds, and skin tones in the actual destination. Treat the BMP as a compatibility rendering, not as a color-managed archive master.
Can a transparent HEIC keep its alpha channel in BMP?
This route flattens transparency onto white for predictable behavior. BMP has a 32-bit alpha form, but support is inconsistent among the older programs that usually require BMP; some ignore the channel and others display unexpected results. A solid white background makes the output more portable. If the receiving surface is colored, prepare a version composited against that color rather than trusting an old reader to interpret alpha correctly.