Pick the size at conversion time, not after
An SVG has no fixed resolution — it is instructions, not pixels. The moment you convert, you freeze it at one size, and enlarging that PNG afterwards only blurs it. So export at the size you actually need, or larger.
For screen assets, 2× is the safe default: it covers Retina and high-DPI displays, where a 1× export looks soft. For print, work from the physical size and the target DPI — a 2-inch logo at 300 DPI needs 600 pixels.
Transparency and why JPG turns black
PNG and WebP carry an alpha channel, so transparent areas stay transparent. JPG has no alpha at all, and an unhandled transparent region usually renders as black. This converter fills a white background automatically when you pick JPG, which is nearly always what you wanted.
Choose a background colour explicitly if the icon will sit on a known colour — it avoids the faint halo you get from anti-aliased edges composited against the wrong ground.
When conversion fails
SVGs that reference external resources — a webfont, a linked image, a stylesheet — will not rasterise. The browser blocks those loads for security reasons during conversion, and there is no way around it from a web page.
The fix is to make the SVG self-contained first: convert text to outlines, and embed any images as data URIs.
Frequently asked questions
Can I convert PNG back to SVG?
Not meaningfully. Converting vector to raster throws away the shape information, and going back requires tracing — which guesses at shapes and rarely reproduces the original. Keep your SVG source.
Are my images uploaded?
No. The SVG is rendered by your own browser, which is also what makes the result match how it will look on a page.
Something wrong with this tool, or an idea for it? Tell us