SVG to PNG Converter — Any Size, Transparent Background

Convert SVG files to PNG — or JPG and WebP — at exactly the pixel size you need. Because SVG is vector, you choose the resolution: export a logo at 512×512 for an app icon or at 4× for a retina banner, with a transparent, white or custom background. The conversion uses your browser's own SVG renderer, so the result matches what you see on screen.

Paste the SVG markup directly if you have it in a code editor rather than a file. Nothing is uploaded.

How to use SVG to PNG Converter

Drop an .svg file or paste the code into the box. The intrinsic size (from width/height or the viewBox) is read automatically.
Choose the output size — 1×, 2×, 4× the intrinsic size, or type an exact width. The aspect ratio stays locked unless you untick it.
Pick a background: transparent (PNG/WebP), white, or a colour — JPG always needs one.
Convert and download.

Why the size is up to you

An SVG has no pixels; it has shapes described in coordinates. A "300×150" SVG is only a suggestion of its natural size. When you rasterise it, you decide how many pixels to spend, and every size comes out equally sharp — which is the whole advantage over resizing a PNG. For icons, export the exact sizes the platform wants (16, 32, 180, 192, 512). For images on high-density screens, export at 2× the CSS size you will display.

What survives and what does not

Everything drawn inside the file — paths, text in system fonts, gradients, filters, embedded data-URI images — renders as the browser would render it.
External references do not. Browsers rasterise SVG in a sandbox that blocks network requests, so an <image href="https://…">, a linked web font or an external stylesheet will be missing. Embed them as data URIs first. The tool warns when it spots such references.
Scripts never run — they are stripped before rendering, which is also why pasting an untrusted SVG here is safe.
Fonts render with whatever the browser has installed; a designer's font that is not on your machine falls back. Convert text to paths in your editor for guaranteed results.

PNG, JPG or WebP

PNG keeps transparency and is lossless — the default for logos and icons. JPG is smaller for photographic content but cannot be transparent, so the background is flattened to white or your chosen colour. WebP does both at smaller sizes and is supported everywhere modern; use it for the web, PNG for anything going into a document or an app bundle.

For the reverse direction — raster to vector — see the catalog; it needs tracing and is a different problem. To shrink the PNG afterwards, use the image compressor; for favicons in every size at once, the favicon generator.

Frequently asked questions

Why is my exported PNG blurry or blank?

Blank usually means the SVG references an external image or font by URL, which browsers refuse to load when rasterising — embed it as a data URI. Blurry means the output size is smaller than where you display it; export at 2× the display size for high-density screens.

What size should I export?

Whatever the target needs, exactly: 512×512 for an app icon, 1200×630 for a link preview, 2× your CSS pixel size for web images on retina screens. There is no quality penalty for large sizes — only file size.

Can I keep the transparent background?

Yes with PNG or WebP — leave the background set to transparent. JPG has no transparency and is flattened onto white (or the colour you choose).

The text in my SVG looks different — why?

Text renders in whatever font your device has; a font used by the designer but not installed here falls back to something similar. Convert text to outlines in your vector editor before exporting for a guaranteed match.

Is it safe to paste an SVG from the internet?

Yes. Scripts inside the SVG are removed before rendering, and the image is drawn in a sandbox with no network access. Nothing in the file can run or phone home.