How to convert SVG to BMP without uploading it
Every "free" online SVG converter you've used uploads your files to a company server, converts them there, and — in several documented cases — keeps a copy or a live download link for days. For a company logo, an unreleased icon set, or anything you wouldn't post publicly, that's an unnecessary risk. The safer approach is to convert the file where it already is: on your own device.
This tool does exactly that. When you drop an SVG here, your browser:
- Sanitizes the SVG first — scripts, embedded HTML, animation elements and event handlers are stripped, and any reference to an external image, font or stylesheet refuses the file outright, because nothing may be fetched while converting.
- Rasterizes it through the browser's own image path — the same secure
static mode a browser uses for an
<img>tag, where SVG scripts can never execute. The output width you choose is the raster size; vector detail is rendered at exactly that size. - Re-encodes the pixels as a raw BMP with a pure-JavaScript BMP encoder — BITMAPINFOHEADER, bottom-up rows, at the bit depth you chose. At 32-bit your SVG's real transparency is preserved; below that it is flattened onto your background colour. Your original file is never modified.
What makes this converter different
The converters that top the results for this search mostly upload your files to a server (Zamzar, AnyConv and Wondershare UniConverter all convert server-side, and Zamzar caps free files at 2 MB), and the client-side ones we found cap the bit depth — one dedicated page offers only 24-bit BMP, another requires a free account before it converts anything. This page is the only dedicated SVG-to-BMP page we found that combines a batch of 20 files with a ZIP download, the full bit-depth range (1/8/16/24/32-bit), Floyd–Steinberg dithering, destination presets, a live network-request counter so you can verify the privacy claim yourself, and real 32-bit alpha preservation. It runs entirely in your browser — there is no server to upload to.
When is BMP the right choice for an SVG?
Almost never for sharing or storage — SVG is smaller and stays sharp at any size, and PNG is lossless and smaller still. BMP earns its place when the destination demands raw pixels: legacy Windows software and GDI tooling, printer utilities, embedded firmware and machine-vision rigs that read uncompressed data, and sprite or retro-game editors that load 1-bit or 8-bit BMPs. If the program you are feeding accepts anything else, use SVG to PNG instead and keep the smaller file.
Honest limitations
Animated SVGs become one still frame
BMP has no animation. SMIL and CSS animation are stripped before conversion and the first rendered frame is stored. If the motion matters, keep the SVG.
BMPs are much larger than SVGs
Expect hundreds of times the size for a 24-bit BMP of a logo, and more at 32-bit. Every file shows its size multiple honestly, and the batch bar shows the total before you download anything.
16-bit loses colour depth
16-bit BMP keeps 5 bits per channel — 32,768 colours instead of 16.7 million. Smooth gradients will band. Use it only when the destination insists on 16-bit.
8-bit and 1-bit are approximations
8-bit output is a 256-colour palette built by median cut; 1-bit is black and white only. Dithering fakes the missing shades by speckling pixels, but detail and smooth colour are lost either way.
Transparency flattens below 32-bit
Only 32-bit BMP has an alpha channel. At 24-bit and below, transparent areas are flattened onto your chosen background colour — pick 32-bit when the destination needs the transparency.
External resources are refused
An SVG that loads an image, font or stylesheet from a URL is refused, because nothing may be fetched while converting. Embed the resource as a data URI, or remove the reference, and try again. Raster detail depends on the output width you choose.