Where the PNG size comes from
A PNG has fixed pixels, an SVG has none — so the first question when converting is how large the raster should be. This tool answers it from the file itself: width and height attributes first, then the viewBox, then a 1024 px fallback. Whatever the answer, the SVG is given that size explicitly before it is drawn, which is what keeps the output predictable.
That last step matters more than it sounds. Browsers have their own opinion about how big an unsized SVG should be — one that declares only a viewBox is drawn at about 150 px tall, with no warning. Reading the declared size and drawing at exactly that size is the difference between a usable PNG and an accidental thumbnail.
How the size is decided
JPG or PNG for an SVG?
What happens to transparency
PNG carries an alpha channel, so anything the SVG does not paint stays empty — and it stays empty through the conversion. That is what makes this pairing the default for logos, icons and interface artwork: a mark exported as PNG can sit on a white page, a dark header or a coloured button without a background rectangle giving it away.
The one thing to check is the SVG itself. A drawing that includes a full-size background rectangle is not transparent at all, however it is exported — the white you see is a shape somebody deliberately drew. If a background follows the artwork into the PNG, remove that rect from the source file rather than trying to strip it out afterwards.
Getting a bigger PNG out of a small SVG
- 1
Open the SVG in a text editor
It is a plain text file, and the opening tag usually declares width, height or a viewBox — that is where the size lives.
- 2
Add or raise width and height
Setting width="960" height="600" on a 320 × 200 drawing makes the tool render it larger, with the vector redrawn rather than stretched.
- 3
Convert again
Drop the edited file back in. The result is a genuinely larger PNG rather than an upscaled one, still under the 4096 px long-edge cap.
Frequently asked questions
What resolution will the PNG have?
The tool reads the SVG’s own size, in this order: the width and height attributes, then the viewBox, then a 1024 px fallback if the file declares neither. The PNG is rendered at exactly that size, so a 320×200 SVG comes back as a 320×200 PNG. Long edges are capped at 4096 px to stay inside browser canvas limits.
Is the background transparent?
Yes. PNG keeps the SVG’s transparency — anything the SVG does not paint stays transparent, and it stays that way through the conversion. If you need a solid white background instead, use the SVG to JPG converter, which flattens transparency onto white and writes a smaller file.
My SVG has no width or height. What happens?
The viewBox decides the size. This is the step browsers get wrong on their own: an SVG with only viewBox="0 0 480 300" is drawn by a browser at its default 150 px height, silently shrinking it to 240×150. This tool reads the viewBox and renders at the declared size instead.
Why is text or an image inside my SVG missing?
Fonts and images that the SVG references from outside the file are often unavailable at render time, so they get dropped or substituted. Inline the font and embed images as data: URLs to make the SVG self-contained.
Can I convert several SVG files at once?
Yes — up to 20 files per run, each up to 50 MB. They are rendered one at a time on your own device.
Are my files uploaded?
No. The SVG is turned into pixels by your browser and written to a canvas on your device. There is no upload step and no copy of your artwork on our side.
Why does my PNG look pixelated at a large size?
Because a PNG is a grid of pixels and an SVG is not. Once the vector has been rasterised, the PNG can only be displayed larger by stretching those pixels, and the edges give themselves away. Exporting a bigger PNG therefore means giving the SVG a bigger declared size before converting, up to the 4096 px long-edge cap that browser canvases allow.
Does the PNG carry a DPI value?
For screen use, DPI is irrelevant — what matters is the pixel count, and that comes from the size the SVG declares. A 320 × 200 SVG produces a 320 × 200 PNG whatever any DPI field says, because a browser canvas has no notion of physical size. Decide on the pixels you need and treat the file as exactly that many.
Can I export at 2× or 3× for a high-density screen?
Not with a scale control — the tool renders at the size the SVG declares, capped at 4096 px on the long edge. To get a 2× PNG, give the SVG twice the width and height first, or change the viewBox and set those attributes. It is a one-line edit in any text editor, and it is worth doing: a 2× PNG looks sharp on a phone screen where a 1× one looks soft.