SVG to PNG Converter

There is no quality slider, because PNG is lossless — it discards nothing regardless of setting. The only decision that affects how the result looks is the output width.

Sensible sizes for common uses:

• Favicons and small icons — 32 to 256 px. Very small sizes often need a purpose-drawn version rather than a shrunk one, because fine detail turns to mush below about 32 px.
• Web images and logos — 512 to 1024 px. Roughly twice the size it will be displayed at, so it stays sharp on high-density screens.
• Presentation and documents — 1024 to 2048 px.
• Print — as large as practical. 300 pixels per printed inch is the usual target, so a 6-inch-wide graphic wants around 1800 px.

Fonts are worth checking. If your SVG references a font by name rather than converting the text to outlines, the renderer has to substitute whatever it has available, and the result may not match what you saw in your design tool. If the text matters, convert it to paths before exporting the SVG — most design tools have a "convert to outlines" or "object to path" command.

If the resulting PNG is larger than you would like, PNG compression works particularly well on vector-derived images, which usually contain few distinct colours. Converting to WebP instead is generally better still for web use.

When you need a PNG instead of the SVG

• A platform rejects SVG. Many social networks, marketplaces, email clients and older content systems accept PNG only — frequently for the same security reasons discussed below.
• App icons, favicons and store listings, which almost always specify exact pixel dimensions.
• Email. SVG support in email clients is poor and inconsistent; PNG is universal.
• Placing into a document or presentation, where some software renders SVG unpredictably or not at all.
• Print workflows that expect a raster file at a known resolution.
• The SVG uses fonts or effects that render differently elsewhere. Rasterising fixes the appearance so everyone sees the same thing.

When to keep using the SVG

For anything on a website you control, the SVG is usually better: it is often smaller than the PNG, and it stays sharp at every screen density without you generating multiple sizes. Every current browser displays SVG.

Convert when you need a fixed-size raster for somewhere that will not take the vector.

How we handle SVG safely

SVG is unusual among image formats: it is a document with a structure, not a block of pixels, and a maliciously written one can attempt things a JPG never could — reading files from the server, making outbound network requests, or embedding scripts.

Two things make that a non-issue here.

First, you receive a PNG, never the SVG. Anything embedded in the file cannot run in your browser, because your browser never sees the file.

Second, every uploaded SVG is screened before anything parses it. Files containing document type declarations, entity definitions, scripts, event handlers, or references to external resources are refused outright rather than repaired — rewriting a hostile file and then trusting the result is a much harder problem than declining it. Embedded images as data URIs and internal references such as gradients are unaffected, so ordinary SVGs exported from design tools convert normally.

Rendering a whole icon set

Add as many SVGs as you like; each is rendered separately at the size you chose, with its own download. If you need the same icon at several sizes, run the batch once per size — the vector is re-rendered each time rather than scaled, so every size is equally sharp.