Convert SVG to PNG in your browser
An SVG has no size of its own, so you pick one. Render it at 4096 wide for a print asset or 32 for a favicon, with the transparency kept and nothing uploaded.
or browse your device. Everything is processed on this device
No SVG to hand?
If the destination reads SVG, it stays sharp at every size and is usually far smaller than any PNG of it. The SVG optimiser cleans out editor cruft without changing the drawing.
Compress the SVG insteadHow to convert SVG to PNG
One or a hundred. They are read into this tab and rendered by your own browser, the same engine that draws them on a page.
This is the decision. Match whatever the PNG is for: a favicon, a slide, an email signature, a print asset. The height follows the artwork.
Transparent where the SVG was transparent. Come back and render it again at another size whenever you need one.
Why an SVG has no size, and what to pick
An SVG is a set of drawing instructions rather than a grid of pixels. Asking how many pixels wide it is has no answer: it is as wide as you draw it, which is the entire point of the format and the reason it stays sharp on any screen. A PNG is the opposite, so converting means choosing a size, and the choice is yours rather than the file’s.
Pick from what the PNG is for. A favicon wants 32 or 64. An email signature or an inline logo wants two or three times the space it will occupy, so it stays sharp on a high-density screen: 512 covers most of these. A slide or a document image wants 1024 to 2048. Anything going to print wants the largest you are offered, and even then a PNG is a poor substitute for sending the SVG itself.
Rendering larger costs nothing in quality, because there is no original resolution to exceed. It costs bytes, quickly, since a PNG grows with the square of its width. If the result is bigger than you expected, drop the palette before you drop the size: most SVGs are flat artwork with a few colours, where 32 colours is often pixel-identical to 256.
SVG to PNG FAQ
What size should I convert at?
Whatever the PNG is for. 32 or 64 for a favicon, around 512 for a logo on a page or in an email signature, 1024 to 2048 for slides and documents, and the maximum for anything heading to print. There is no quality penalty for going larger, only file size.
Will transparency survive?
Yes. PNG has a full alpha channel, so anything transparent in the SVG stays transparent in the PNG. If you need it on a solid background instead, add a filled rectangle behind the artwork in the SVG before converting.
What about fonts and text in the SVG?
Text renders with the fonts your own machine has, because your browser is doing the drawing. If the SVG refers to a font you do not have installed, it falls back to something else and the PNG will show that. Converting text to outlines in your editor before exporting avoids the problem entirely.
Does it load external images or stylesheets?
No. The SVG is rendered from a local blob, so anything it references over the network is not fetched. That keeps the promise that nothing leaves your device, and it means an SVG built from remote assets will render without them.
My SVG has no width or viewBox. What happens?
There is nothing to reason from, so it is rendered as a square at the width you chose. Adding a viewBox to the file is the real fix and takes one attribute.
Are my SVG files uploaded to convert them?
No. The SVG is decoded and the PNG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.
Does this remove EXIF, GPS and AI metadata?
Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.
Related
Same format joins the queue. Anything else re-routes to its own tool.