Initializing... drag & drop files here
Supports: 3G2, 3GP, 3GPP, ASF, AV1, AVCHD +31 more
BMP (Windows Bitmap, introduced with Windows 2.0 and OS/2 in the late 1980s) stores every pixel literally — no compression, no lossy approximation, no chroma subsampling. That makes BMP the wrong choice for most modern image use cases but the right choice for a specific set of pipelines that demand pixel-exact data.
| Property | BMP | PNG | JPG |
|---|---|---|---|
| Compression | None | Lossless DEFLATE | Lossy DCT |
| 1080p frame size (approx) | ~6 MB | ~1.5-3 MB | ~150-400 KB |
| Pixel exactness | Identical to source | Identical to source | Approximated |
| Alpha channel | 32-bit BMP supports it | Yes | No |
| Bit depth | 1, 4, 8, 16, 24, 32 | 1-16 per channel | 8 per channel |
| Best for | Vision/inspection/embedded | Web, archival, editing | Photos, sharing, thumbnails |
| Convert with | This page | Video to PNG | Video to JPG |
PNG gives you the same pixel-exact result as BMP at roughly half the file size, so most modern workflows pick PNG. Choose BMP specifically when the downstream tool needs an uncompressed bitmap header it can mmap straight into memory, or when you're feeding a system that was last updated in 2008.
| Bit depth | Colors | Typical use |
|---|---|---|
| 1-bit | 2 (black/white) | Faxes, dithered icons, e-ink |
| 4-bit | 16 | EGA-era graphics, simple UI assets |
| 8-bit | 256 (palette) | Indexed sprites, retro games |
| 16-bit | 65,536 | Embedded displays, GBA-style ROMs |
| 24-bit | 16.7 million | Photographic frames, default video frame export |
| 32-bit | 16.7M + alpha | Compositing source, UI assets with transparency |
For video-to-BMP, 24-bit is the standard output — it matches the 8-bit-per-channel color you get from almost every consumer video source.
Because BMP is uncompressed and video is heavily compressed. A 1-minute 1080p MP4 might be 50 MB. Extracted at 30 fps as 24-bit BMP, that's 1,800 frames × ~6 MB each = roughly 11 GB. If you only need a handful of stills, use the "Specific Frame" mode or set a sparse extraction interval (1 frame per second instead of 30). If you need every frame but not the size, output to Video to PNG — same pixel data, about half the bytes.
Pick "Specific Frame" in Frame Selection, then enter the time in seconds (decimals work — 4.5 means 4 and a half seconds in). Click Convert and you get a single .bmp file. This is the most common video-to-BMP workflow: grab one reference still for documentation, machine vision calibration, or as a thumbnail source.
Yes. Pick "Multiple Screenshots" and set the interval to 1 second, 1 minute, etc. The tool walks the video at that interval and outputs one BMP per sample point. For sports analysis and inspection work, 1 frame per second of source video is usually the right starting point; reduce to 1 per 5 seconds if you only want highlights.
Most online "video to JPG" tools quietly drop you into a re-encoding pipeline that loses pixel-level accuracy. Video-to-BMP keeps every extracted frame at the exact pixel values the decoder produced — no JPEG quantization, no PNG paeth filter, just raw RGB. For machine vision, inspection, and forensic chain-of-custody work this matters; for sharing a screenshot to a friend it doesn't.
By default xConvert produces 24-bit RGB BMP (no alpha) because almost no source video carries an alpha channel — H.264, H.265, VP9, and AV1 don't transport alpha in any consumer container. If you need 32-bit BMP with alpha (e.g., from a Hap Alpha or VP9 alpha source), convert to PNG instead via Video to PNG; PNG handles alpha cleanly and the alpha can be re-baked into a 32-bit BMP downstream.
BMP v4 and later (since Windows 95) support a 32-bit format with an alpha channel, but BMP has no animation and no layers. One BMP = one still frame. If you want an animated extract, use Video to GIF or Video to PNG (APNG-capable).
The extraction snaps to the nearest decoded frame at or after your timestamp. With most consumer video (29.97 fps / 30 fps), that's accurate to about 33 ms; with 60 fps source, ~16 ms. For sub-frame precision you'd need to slow-mo interpolate, which isn't a BMP-conversion task.
Two reasons. First, VLC may apply post-processing (deinterlace, deblock, scaler) that's enabled in its preferences; the BMP extract uses a clean decode path. Second, color-range handling — videos are usually limited-range (16-235), and some viewers stretch to full-range (0-255) on display. The BMP stores the actual pixel values from the decoded frame, so if your viewer was doing a stretch you may see a subtle contrast difference.
Yes — drop in as many video files as you want. Each is processed in parallel and outputs its own set of BMP frames. If you're extracting many frames per file, prefer downloading the per-file ZIP rather than 1,000 individual files. For just one frame per video (e.g., generating BMP thumbnails for a folder of videos), grab the "Specific Frame" mode and set the timestamp to 1-2 seconds — most videos have a usable frame by then.
The conversion runs server-side, so you're not limited by browser memory. Practical caps depend on output: extracting a single frame from a 4K, 2-hour film is fine; dumping every frame as 24-bit BMP would produce hundreds of gigabytes and isn't realistic. If you need pixel-exact extraction at full frame rate from a long source, Video to PNG is the more practical choice.