HEIC stores high-efficiency photos and image sequences in an ISO base media container.
BMP stores raster pixels with little or no compression in a bitmap container.
The source is decoded as one image.
Transparent input requires a selected background color before encoding.
The destination encoder can change pixel values, bit depth, color representation, or file size.
The worker applies EXIF orientation, converts pixels to 8-bit sRGB, and removes source metadata before encoding.
HEIC is common on recent Apple devices, while BMP remains useful for older Windows software, imaging equipment, and workflows that ask for an uncompressed bitmap. Converting the file changes its container and pixel representation. It does not improve the source resolution or restore detail that the HEIC image did not contain.
BMP files are usually much larger than HEIC files because the formats make different storage tradeoffs. Check available disk space and any upload limit at the destination before converting a batch. PNG is often a smaller lossless alternative when the receiving application accepts it.
The private image worker reads the HEIC container, applies the stored orientation, removes source metadata, and writes BMP output. It validates the generated file as BMP before returning the download. The output contains rendered pixels, not the original HEIC metadata or compression structure.
Open the downloaded bitmap in the software that requested it. Confirm width, height, orientation, color, and any background applied where transparency cannot be represented. Keep the HEIC original because converting to BMP is not a reversible preservation workflow.
Set an optional width or height, preserve or change the aspect ratio, and choose output quality. Transparent input requires a selected background because the destination has no alpha channel.
One image is processed per request. Animated WebP, GIF, and multi-page TIFF retain all frames only when the destination also supports multiple frames. The input limit is 25 MB.
The web application validates the file before forwarding it to a private worker. The worker validates the signature again, processes the file inside a unique temporary directory, validates the output, and removes the job directory in a guaranteed cleanup path. Files are not written to the database or retained for analytics.
When you import from a URL, the application fetches only a validated public HTTP or HTTPS address, checks the downloaded file in memory, and applies the same worker cleanup rules. The URL, filename, and file contents are not sent to analytics.