SVG to PNG Converter

An SVG to PNG converter draws a vector graphic onto a grid of pixels and saves the result as a PNG. SVG, the W3C format for Scalable Vector Graphics, describes shapes as geometry: paths, circles, gradients and text. That keeps a logo sharp at any size, but it also means there are no pixels until something draws them. Social profile uploads, office documents, email signatures, app store listings and many content systems want pixels, so the SVG has to be rendered first.

Here the rendering is done by your browser's own SVG engine, the same one that draws SVGs on web pages. The size comes from the file. When the SVG sets a width and height, those are used, with units such as mm, pt or in converted to pixels. When it only has a viewBox, the viewBox size is used, and when it has neither, it is drawn at 1024 x 1024. An SVG whose longest side comes out under 512 pixels, a typical 24 x 24 icon for example, is enlarged in proportion until that side is 512 pixels, because a vector loses nothing by being drawn bigger. The SVG scale option then multiplies the size by 1, 2 or 4, and the note under each file's row says what size was used and why. Changing the scale converts every added SVG again at the new size.

A run looks like this. You drop logo.svg, which declares width="240" height="80", and pick 2x. The logo is first enlarged to 512 x 171, then doubled, and clicking the row's thumbnail opens a preview captioned 1024x342, with the transparent background showing as a checkerboard. Anything the SVG does not paint stays transparent in the PNG, which is usually the point of choosing PNG over JPG.

Some SVG content cannot be drawn this way. An SVG rendered as an image is not allowed to fetch anything outside the file, so images and web fonts linked by URL are left out, and scripts inside the SVG do not run. Images embedded in the file itself are drawn. An animated SVG becomes a single still frame, and an SVG with an XML error is refused with a message.

Everything runs client-side and nothing is uploaded. SVG files over 50 MB are refused, and so is any output over 100 megapixels or wider or taller than 16384 pixels, in which case a smaller scale usually fixes it. The tool is free, no signup, with a daily conversion limit.

1. Read the size from the root svg element: width and height if both are set, one of them plus the viewBox proportions if only one is, the viewBox alone if neither is, and 1024 x 1024 if there is no viewBox either. Percentages and em values are ignored.
2. If the longest side is under 512 pixels, enlarge the drawing in proportion so the longest side is 512.
3. Multiply both sides by the Scale you picked: 1, 2 or 4.

• The SVG is drawn and the PNG is saved inside this browser tab, client-side. The file is never uploaded.
• The SVG is rendered as an image, so scripts inside it do not run and links to outside files are not fetched. Opening an SVG from an unknown source here does not let it reach the network.
• No WebAssembly decoder is involved, because browsers render SVG with their own built-in engine.
• The daily limit check sends the tool name, a device identifier and your account token if you are signed in. After a batch, only the file count, total bytes and output format are recorded, never file names or contents.
• Converted PNGs stay in the tab's memory until you remove them, press Clear All or close the page. No copy is kept on a server.