An SVG has no pixel size. It is a set of drawing instructions — move here, curve there, fill this shape — that a renderer executes at whatever scale you ask for. So converting to PNG is not really a conversion; it is a render, and the only decision that matters is what resolution to render at.
Pick the size deliberately
This is why the control above says output width rather than resize. There is nothing to shrink: you are choosing how many pixels to produce from something that has none. Render too small and the PNG is soft when scaled up later, because once it is a bitmap the crispness is gone for good. Render enormously and you get a file far heavier than the job needs.
- Favicons and small UI icons: 512 is plenty, and downscales cleanly to every size you need.
- Web images and blog graphics: match the display width, then double it for high-density screens.
- App store icons and press assets: 1024 or higher, since these get reused at sizes you cannot predict.
- Print: work backwards from physical size at 300 dpi — a 4-inch-wide graphic wants 1200 pixels.
Transparency comes through intact
Anything the SVG leaves unpainted becomes transparent in the PNG, with a full alpha channel rather than a hard on-or-off mask. Anti-aliased curves and soft edges stay smooth, which is exactly what you want for a logo that will sit on a coloured background. If you need a solid background instead, convert to JPG, which forces the question and lets you choose the colour.
What can go wrong
SVGs that reference external resources will not render here. If the file pulls in a font from Google Fonts, links to a bitmap sitting on a server, or imports another SVG by URL, those requests are blocked — deliberately, because this page does not make network requests during conversion. Text set in a linked font falls back to a system font or vanishes.
The fix is to make the SVG self-contained before converting: convert text to outlines in your editor, and embed any referenced images as data URIs. Most vector editors have a "convert text to paths" or "flatten" option that does the first part in one click, and it is worth doing anyway — it makes the SVG render identically everywhere rather than depending on what fonts the viewer has.
The render happens in this tab using your browser’s own SVG engine, the same one that draws it on screen. Nothing is uploaded, which matters for unreleased logos and client artwork.