An SVG has no size until you give it one
A photo is a fixed grid of pixels the moment it is taken; an SVG is a set of mathematical shape instructions with no inherent resolution at all. That is the whole point of a vector format — the same file can draw a crisp 16-pixel favicon or a crisp 4000-pixel banner, because there is nothing to lose by scaling it. A PNG, once created, does not have that freedom: whatever resolution you export at is locked in permanently. Picking that resolution deliberately, rather than accepting whatever a converter defaults to, is the one decision this tool exists to make easy.
Two ways to size it
Scale multiplier takes each file's own native size and multiplies it — 2× doubles it, matching how design tools export "at 2x" for retina displays. This is the natural choice for a batch of icons that are already sized correctly relative to each other, since it preserves that relationship.
Exact width instead sets every file to the same pixel width, with height calculated from that file's own aspect ratio. Useful when you need a specific dimension regardless of how the source files were originally sized — a fixed banner width, a specific print dimension, a platform's exact upload requirement.
Picking a resolution that actually fits the job
| Use | Guidance |
|---|---|
| Web icon, standard display | Match the display size exactly |
| Web icon, retina/high-density | 2× the display size |
| App icon store listing | Follow the platform's exact pixel spec |
| ~300px per inch of final physical size |
A 4-inch logo destined for print wants roughly 1200 pixels; a 32-pixel toolbar icon that needs to look sharp on a retina laptop screen wants 64. The preview updates with the exact export dimensions before anything is generated, so there is no guessing whether the number you typed produced what you expected.
Why rendering resolution matters more than it sounds
Naively drawing an SVG onto a canvas at a size larger than the browser happens to load it at is a common way converters produce blurry output: some browsers decode the image once at a small default size and then stretch that already-rasterized bitmap, rather than re-drawing the vector data fresh at the larger size. This tool avoids that by rewriting the SVG's own width and height to the exact target resolution before it is ever decoded, so the browser renders the vector data natively at that size from the start — not a small bitmap stretched afterward.
This does mean the SVG file needs to be self-contained. If it references an external font, image or stylesheet that is not embedded inside the file itself, that reference cannot be resolved here - or in any tool operating outside a full browser page context - and the rendered output will differ from what a design tool shows you. Exporting with "embed fonts" or "embed images" enabled avoids this entirely.
Transparency, or a solid background
SVGs are transparent by default unless they explicitly draw a background shape, and PNG output keeps that transparency intact. Choosing JPG output instead requires a background colour, since JPG has no transparency channel at all - a colour picker is provided rather than silently defaulting to black.
Nothing is uploaded, and nothing runs
The SVG is loaded as an image, not inserted into the page or executed - browsers never run scripts embedded inside an SVG that is loaded this way, so there is no risk from a file containing something unexpected. Rendering happens entirely on canvas, inside your browser; the file is never sent anywhere.