SVG to PNG Converter - Rasterize SVG at Any Size Online Free

Turn SVG vector files into PNG images at the exact pixel size you choose. Runs entirely in your browser, with no uploads and no fixed 150px output.

What SVG to PNG Conversion Does

SVG is not an image in the way PNG is. It is a text document describing shapes, paths, and text as mathematics — a circle is a centre and a radius, not a grid of coloured dots. PNG is the opposite: a fixed grid of pixels, decided once and unchangeable afterwards. Converting between them is therefore not a re-packaging but a rendering. The browser's own SVG engine draws the artwork afresh at the size you pick, and those rendered pixels become the PNG. That is why this tool asks for a width and height when nothing else on the site does. There is no 'original resolution' to preserve, because a vector does not have one. Ask for 512 pixels and every curve is computed at 512 pixels; ask for 4096 and the same file produces a crisp 4096-pixel image with no upscaling and no blur. The size you choose is the only thing that determines quality. The size control also exists to avoid a specific trap. An SVG that omits width and height on its root element has no intrinsic size at all, and a browser asked to draw it as a plain image falls back to a CSS default of around 150 pixels. Plenty of icon sets, Figma exports, and hand-written files are shaped exactly that way — they carry only a viewBox, which fixes the proportions but not the scale. Converted naively, a logo meant for a billboard comes back as a thumbnail. This tool reads the file first, tells you when the size is its own choice rather than the file's, and refuses to quietly rasterize at 150 pixels.

Why You'd Convert SVG to PNG

Almost always because something downstream cannot read vectors, or because you need one fixed rendering rather than one that varies by renderer.

Satisfy platforms that reject SVG uploads outright — app store assets, most social networks, marketplace listings, and email clients
Get a predictable result, since PNG renders identically everywhere while SVG depends on the viewer's font and filter support
Produce sized exports of an icon or logo — favicons, app icons, thumbnails — from one source file at 1x, 2x, or 4x
Drop artwork into software that has no vector support at all, from older office suites to game engines and photo editors

How to Convert SVG to PNG

The only real decision is the output resolution, so it is worth a moment's thought before you convert.

1

Add one SVG or a whole batch — the size you set is applied to every file in the batch

2

Check the width and height. They start from the SVG's own declared size when it has one, and the tool says so when it doesn't

3

Set the resolution you need, or tap 1x, 2x, or 4x. Keep the ratio locked unless you deliberately want the artwork stretched

4

Convert, check the preview, then download the PNG or take the whole batch as a ZIP

Frequently Asked Questions

Because an SVG has no pixels to preserve. Every other conversion on this site starts from an image with a fixed grid — a 1920x1080 JPG becomes a 1920x1080 PNG, and there is nothing to ask. A vector describes shapes as equations, so it has no resolution until something renders it. Converters that don't ask are simply picking a number without telling you, and when the file declares no size of its own the number they land on is usually the browser's 150-pixel fallback.
Whatever you set. The tool reads the file's viewBox to work out the proportions, then suggests 1024 pixels on the longest side and tells you plainly that the number came from us rather than from the file. That default is a safe starting point, not a recommendation — if the artwork is destined for an app icon or a print asset, type the size you actually need. What it will never do is fall through to 150x150, which is what a naive canvas conversion produces for exactly these files.
No, and this is the part that surprises people used to resizing photos. Enlarging a JPG stretches pixels that already exist, so detail smears. Rendering an SVG at a larger size recalculates every path from scratch, so a 4096-pixel export is exactly as sharp as a 256-pixel one — there is no upscaling involved. The only real cost is file size and rendering time. Embedded raster images inside the SVG are the exception: those are ordinary bitmaps and will soften if you render past their native resolution.
Keep the SVG whenever the destination accepts it. On the web it is usually smaller, stays sharp on any display at any zoom level, and can be restyled with CSS. Convert when the destination refuses vectors, when you need a guaranteed identical rendering across viewers, or when the SVG relies on fonts or filters the target renderer may not support. A common workflow is to keep the SVG as the master and export PNGs as needed — the vector remains the source of truth.
Yes. PNG has an alpha channel, and areas the SVG never paints stay fully transparent, so a logo with no background rectangle exports with none. If you find an unexpected white or coloured backdrop in the result, it is almost certainly a filled rect drawn in the SVG itself rather than something the conversion added. Open the file in an editor and remove that shape.
Because the alternative is worse. When an SVG is drawn as an image, browsers block it from fetching anything over the network, so a linked logo or web font simply never arrives — the export would come back with a blank gap where that artwork should be, and nothing would say so. Rather than hand you a quietly incomplete PNG, the tool stops and explains. Embed the image as a data URI, convert the text to outlines, or flatten the file in your editor, and it will convert normally.
No. The SVG is read, rendered, and encoded entirely inside your browser, and the file never leaves your device. That matters more than usual here, since SVGs are plain text and routinely carry layer names, comments, and internal identifiers from the design tool that produced them. None of that goes anywhere. The practical limit is your device's memory rather than any upload cap, which is why very large output sizes are blocked before they are attempted.
Browsers cap the canvas used for rendering — around 16384 pixels per side, with a total area ceiling that is lower still on phones. Past that limit a canvas does not raise an error; it hands back a blank bitmap, and the download would be an empty image. The tool checks your requested size against those limits up front and refuses with a message instead. For genuinely enormous output, render the SVG in desktop software such as Inkscape, which is not bound by the browser's canvas.

更多图片工具

探索其他强大的图片编辑工具