BMP to AVIF Crop: Complete Conversion Guide for Web & Performance

By Bill Crawford  ·  March 2026  ·  9 min read  ·  Last updated March 11, 2026

Connect on LinkedIn →

What Is BMP and Why Is It a Problem for the Web?

BMP (Bitmap) is Microsoft's original raster image format, dating back to the early days of Windows. It stores raw, uncompressed pixel data — every single pixel takes up its full byte depth with no compression whatsoever. A 3000×2000 pixel BMP in 24-bit color occupies exactly 3000 × 2000 × 3 = 18,000,000 bytes, or about 17 MB, regardless of image content. There are no exceptions, no settings, no trade-offs. BMP files are always large.

This characteristic makes BMP completely unsuitable for web delivery. Page weight directly affects load time and Core Web Vitals scores, particularly Largest Contentful Paint (LCP). Serving a 17 MB BMP where a 300 KB AVIF would render identically is not a minor inefficiency — it is a serious performance failure. Legacy Windows applications, scanners with default BMP output, and older design software are common sources of BMP files that eventually need to reach the web.

What Is AVIF and Why Is It the Right Target Format?

AVIF (AV1 Image File Format) is a modern image container based on the AV1 video codec, originally developed by the Alliance for Open Media. It achieves compression efficiency that significantly outperforms JPEG, WebP, and PNG — typically reducing file size by 50% compared to JPEG at equivalent perceptual quality, and dramatically more compared to uncompressed BMP. AVIF supports lossy compression, lossless compression, transparency (alpha channel), HDR (high dynamic range), and wide color gamuts, making it a fully capable replacement for any legacy format.

Browser support for AVIF has matured substantially: Chrome 85+, Firefox 93+, Edge 121+, and Safari 16+ all support AVIF rendering. These browsers collectively account for the large majority of active web users as of 2026. For the remaining users, a simple <picture> element with a JPEG fallback provides complete coverage without serving BMP files to anyone.

Why Crop Before Converting?

Cropping before conversion is almost always the right sequence for several reasons. First, it eliminates pixels you do not need from the AVIF encoding step, producing a smaller output file. Second, it reduces encoding time — AVIF encoding is computationally heavier than formats like JPEG, and smaller pixel dimensions speed the process noticeably. Third, it allows you to deliver a file that is already correctly composed for its destination: a product image cropped to a standard 1:1 ratio, a header image cropped to the exact width and height your CMS expects, or an icon extracted from a larger design.

The BMP to AVIF Crop Converter combines both operations in a single browser-based step. You load the BMP, adjust the interactive crop handles, preview the result, and download the final AVIF — all without any intermediate file saves or server uploads.

When Should You Crop and Convert BMP to AVIF?

• Preparing scanned images for web delivery. Scanners often default to BMP output. If you are scanning documents, product photos, or artwork for a website, converting to AVIF after cropping scanner margins produces the smallest possible web-ready file.
• Migrating legacy Windows application assets. Older Windows software frequently generates BMP files. Any BMP destined for a web page, web app, or modern delivery pipeline should be converted to AVIF for size and compatibility.
• Extracting a specific region for web use. BMP files from screen capture tools, 3D render outputs, or CAD exports are often full-canvas size with the useful content occupying a specific region. Crop to that region and convert to AVIF in one step.
• Optimizing desktop app assets for web packaging. Electron and web-based desktop apps often inherit BMP assets from earlier native Windows versions. Converting those assets to AVIF significantly reduces package size.
• Reducing storage cost for large BMP archives. If you are migrating a file archive to cloud storage, converting BMP images to AVIF can reduce storage requirements by 90% or more while preserving full visual quality in the retained pixels.

BMP vs AVIF: Format Comparison

How the Crop Workflow Works in the Browser

The BMP to AVIF Crop Converter loads your file using URL.createObjectURL and decodes it with img.decode(). The img.decode() call returns a Promise that resolves only when the image is fully decoded and ready to paint — this ensures the canvas always receives complete pixel data and prevents the silent blank-canvas problem that can affect other loading strategies. Once decoded, the image is drawn onto an HTML5 Canvas scaled to fit your screen, with an SVG overlay providing the crop rectangle and handles.

When you drag a handle, the tool maps canvas coordinates back to the original image pixel dimensions using a scale factor. This means your crop is always at full source resolution, regardless of how the image is displayed on screen. When you click Convert & Download AVIF, an off-screen canvas draws only the selected pixel region, then encodes it to AVIF using the browser's native canvas.toBlob('image/avif') API. The resulting AVIF blob is downloaded directly to your device with no server round-trip.

AVIF vs WebP: Which Should You Use?

Both AVIF and WebP are far better choices than BMP for web delivery, but they differ in important ways. WebP achieves roughly 25–35% better compression than JPEG and enjoys universal browser support since Safari 14 (2020). AVIF achieves 50% or better compression versus JPEG and better still versus WebP, but has slightly less complete browser support and encodes more slowly. For a BMP-to-web workflow in 2026, AVIF is the correct choice for any image destined for modern browsers — its compression advantage is significant, and browser support is now broad. Use WebP only if you need to target Safari 13 or older, which is effectively a negligible user segment.

Frequently Asked Questions

Does cropping a BMP before saving as AVIF improve compression?

Yes — smaller pixel dimensions always produce smaller AVIF files because there are fewer pixels for the AV1 encoder to process. Cropping removes unwanted regions before encoding, so every byte in the output AVIF represents a pixel you actually need. The visual quality of retained pixels depends entirely on the source BMP content, which as an uncompressed format contains no pre-existing artifacts.

How much smaller will the AVIF be compared to the BMP?

AVIF typically achieves 90–98% file size reduction compared to an uncompressed BMP. A 36 MB BMP photograph becomes 0.5–2 MB as AVIF at near-identical visual quality. The exact ratio depends on image content — photographs with natural textures compress far better than flat solid-color graphics, which may only achieve 80–85% reduction.

Is the conversion really free with no file size limit?

Yes. Because processing runs entirely in your browser, there is no server to impose a limit. The only practical constraint is your device's available RAM. BMP files are often very large — a 24 MP BMP can exceed 70 MB — and modern desktop browsers handle these without difficulty. Mobile devices with limited RAM may process large BMPs more slowly.

What happens if my browser does not support AVIF encoding?

The tool performs an automatic compatibility check when the page loads. If your browser does not support canvas.toBlob('image/avif'), a warning banner appears and the download falls back to PNG format. Chrome 85+, Edge 121+, and Firefox 93+ all support AVIF canvas encoding. Safari does not currently support this API.