How the SVG to PNG converter works
Drop one SVG or a folder of them. Each file is parsed and rasterised by resvg, a specification-strict SVG renderer compiled to WebAssembly, inside a background thread in your browser. The result is a PNG with a full alpha channel at exactly the pixel size you asked for. Nothing is uploaded; the page works offline once loaded.
SVGs that contain live <text> are rendered by your browser instead, so that the fonts installed on your
machine can be used. A small warning badge marks those files.
Choosing a size
- Scale multiplies the SVG's intrinsic size: 1× for a same-size PNG, 2× for retina, 4× or 8× for print.
- Fit width / Fit height give one exact dimension and compute the other from the aspect ratio. Use these for hero images and thumbnails.
- Exact forces both dimensions and will stretch the artwork if the ratio differs — only for when a platform demands specific pixels.
- Multiple sizes renders one PNG per ticked width and names them
icon-16.png,icon-32.png… This is the icon-set workflow; for a full favicon package with.icoand manifest use the favicon generator.
Sizes are read from the SVG's width/height, falling back to the viewBox. An SVG with
neither is treated as 512 px square. Dimensions are capped at 8192 px.
Background
Transparent is the default and is what you want for icons, logos and overlays. White or black flattens the image; a custom colour lets you match a page background exactly so anti-aliased edges blend cleanly. If you need a JPEG, use SVG to JPG, which always flattens.
Before you convert
Run files through the SVG Optimizer first if they come straight from a design tool: it does not
change the rendered result but it removes editor artefacts that occasionally confuse strict renderers. If a PNG comes out
blank, the usual causes are external image references (href="https://…"), CSS that lives outside the file, or
an SVG with no size information at all.