SVG to PNG — Render a Vector at Any Size, In Your Browser
You have an SVG — a logo, an icon set, a designer-export — and you need a PNG. Most of the time the reason isn't aesthetics; it's that the destination only accepts raster images. Email clients, slide decks, social media, e-commerce thumbnails, print services. SVG is the cleaner format on the way in, but PNG is the format your destination understands.
The technical name for this is "rasterizing": picking a target pixel size and rendering the vector at that resolution. SVG describes the image as a tree of shapes; PNG stores it as a fixed grid of pixels. The conversion is one-way (you can't get the SVG back from the PNG), so the resolution choice matters.
Convert in your browser
Buncha's Bulk Image Converter handles SVG → PNG client-side. Drop the SVG, pick PNG and a target size, download. Nothing uploads.
The browser does the rasterization itself: load the SVG into a <canvas>, set the canvas size to the target dimensions, draw, export as PNG. No external library, no quality loss beyond the resolution you picked.
What size to pick
This is the only decision that matters. The SVG renders cleanly at any size — but once it's a PNG, the size is fixed and zooming will pixelate.
- Email signature / favicon — 64×64 to 128×128 px. Small file (~5–20 KB).
- Avatar / profile picture — 256×256 or 512×512 px. ~30–80 KB.
- Web image / blog header — 1200–1600 px wide. Match the rendered display size if you can.
- Social media post — 1080×1080 (square) or 1080×1350 (portrait) for Instagram; 1200×630 for OpenGraph / LinkedIn.
- Print — 300 DPI × physical size. A 4-inch logo on a printed flyer = 1200 px wide.
If you're not sure, pick double the size you think you need. Modern screens are high-DPI (Retina, 4K), and an undersized PNG looks soft on those displays. Doubling the resolution doubles the file size, which is fine — PNG of a logo or icon is small to begin with.
Backgrounds
SVGs default to a transparent background unless they explicitly draw one. PNG handles transparency, so the resulting PNG keeps the see-through pixels. This is what you want most of the time — the logo / icon sits cleanly on whatever you put it on top of.
If you want a solid-colour background baked in, the bulk converter lets you set one before exporting. Useful for dark-background designs that need to display correctly on a light page or vice versa.
JPG vs. PNG for vector-source content
Don't convert SVG to JPG unless you really know why. JPG's compression artefacts cluster around sharp edges — exactly where an icon or logo lives — and they're visible immediately. The compression haloes around letterforms in a JPG-converted logo are the classic sign of "designer didn't do this on purpose". Stick with PNG.
The exception is a vector illustration that's mostly soft gradients and photographic content. In that case JPG behaves fine. For 99% of SVG-source content (icons, logos, charts, diagrams), PNG is correct.
Animated SVGs
SVG supports animation via SMIL or CSS. Converting to PNG flattens this — you get a still image of the first frame. To preserve motion you'd need to convert to GIF or APNG (animated PNG), which most browser-side tools don't do well. For animated content, keep the SVG.
The transparent-on-transparent gotcha
If an SVG has a transparent background AND uses a colour that happens to match the destination background, the PNG comes out looking blank. This is rare but easy to spot — re-export with a different background colour and the issue is obvious.
The shortest path
Open the converter, drop the SVG in, pick PNG and your target size, download. If you have a folder of SVG icons, drop the lot — each is converted to a same-name PNG and packaged as a ZIP.