An SVG has no pixels, so this is rendering, not converting
Every other converter on this site moves pixels that already exist. This one does something different, and the difference is the reason the page is worth reading. An SVG holds no image at all. It holds instructions: draw a circle here, fill this path with that gradient, put text at these coordinates. Turning it into a PNG means running those instructions at a size you pick. Nothing is stretched and nothing is guessed, because there is no original pixel grid to stretch or guess from.
Why you probably need the PNG at all
The format is excellent and almost nothing accepts it. Email clients will not display an SVG. Office fights you when you embed one. Social networks and most upload forms reject it outright, and software outside the design world tends to treat it as a text file, because technically it is one. PNG is the version everyone takes.
Big costs you nothing here
Upscaling a photograph invents pixels that were never captured, which is why it goes soft at 2x and turns to mush at 10x. Rendering a vector has no such ceiling. A 24 pixel icon rendered at 1024 pixels is not a blown-up 24 pixel icon; it is the same drawing executed again at 1024, with every curve and edge computed for that size. We tested exactly that: a 24 by 24 icon came back at 1024 by 1024 with its colours identical to the source values, byte for byte, and smooth anti-aliased edges rather than stair-steps.
The practical advice follows from that. Render at the largest size you will actually use, not the smallest, because the PNG you get is a fixed grid from then on. Going bigger costs you nothing but a few milliseconds.
You choose the size, or the file does
Type a width and the drawing is fitted to it with its proportions locked. Ask a 2:1 logo for 400 by 400 and you get a crisp 400 by 200, never a squashed square. There are one-click presets at 256, 512, 1024 and 2048, and an Original option that renders at whatever size the SVG itself declares. On a file declaring 200 by 100, Original returned exactly 200 by 100. The ceiling is 16,384 pixels per side and 64 megapixels overall, which covers an 8000 by 8000 render.
Transparency, including the partial kind
PNG carries a real alpha channel, so a logo with a transparent background comes back with a transparent background, ready to sit on a slide or a product page without a white box around it. The part that separates a good renderer from a careless one is partial transparency: soft shadows, faded edges, anything set to half opacity. On a shape declared at 50 percent opacity, the output measured an alpha value of 128, which is exactly half. Every render came back as a true RGBA image. If you would rather flatten the transparency, switch the background setting to a solid colour and pick the exact shade you want from the colour picker.
Text and gradients, the two things that usually break
Server-side SVG rendering fails in two predictable places. Fonts go missing, so text vanishes or lands in the wrong typeface. And gradients defined once and referenced by id are not resolved, so shapes come back flat or black. We checked both. Text rendered with clean anti-aliased glyph edges, and a linear gradient referenced with url() rendered as a proper sweep from one colour to the other. If a file asks for a font the server does not have, a substitute is used and the result says so, instead of leaving you to notice it later.
Uploading someone else's SVG is safe here
An SVG can legally contain JavaScript and can point at resources elsewhere on the internet. That is why email providers block the format, and it is a real reason to be careful with a file a stranger sent you. Rendering here runs through a dedicated vector engine rather than a headless browser: scripts are never executed and external references are never fetched. Nothing inside the file can run, call home, or read anything. What you get back is the drawing's true static state, which is also why animations render as their first frame rather than moving.
Fast, and repeatable
The classic Ghostscript tiger, 94.5 KB of dense bezier paths and the usual torture test for SVG renderers, rendered to a 512 pixel PNG in 53 milliseconds. Rendering the same file twice produces byte-identical output, so a result can be reproduced exactly rather than approximately. Compressed .svgz files are read directly, and the format is detected from the file's own bytes, so a renamed file or one with no extension still renders.
A set of icons in one go
Several files render with the same settings and come back as a single ZIP under their original names. Three different files all called icon.svg return as icon.png, icon_1.png and icon_2.png rather than two of them quietly disappearing. A damaged or non-SVG file in the batch is skipped and named in the result instead of failing everything else.
What you get
- A PNG rendered at your chosen size, not an upscaled copy of a small one
- Proportions locked, so nothing comes back stretched or squashed
- Full alpha, including half-opacity shapes and soft shadows, or any background colour you pick
- Text and gradients rendered rather than dropped, with font substitutions reported
- No scripts executed and no external references fetched, so an unknown SVG is safe to upload
- No account, no watermark, and files deleted from the server an hour later
What's next?
A 4000 pixel render is a large file, so Compress PNG is the usual next step before it goes on a page, and PNG to WebP takes it further for the web. If you are keeping the vector as well, Compress SVG strips the editor junk out of it first.