iPhotoEditor

Every tool runs in your browser. Your photos never leave your device — see how that works.

Convert SVG to PNG

Vector graphics scale forever, but half the destinations that matter - app stores, social profiles, email signatures, older tools - insist on pixels. Rasterize your SVG here at precisely the size required, free and without the file travelling anywhere: your browser's built-in vector renderer draws it on your machine.

Loading the tool…

How it works

  1. Drop in the SVG file or paste raw SVG markup directly.
  2. Set output dimensions - exact pixels, or a multiplier like 2x or 4x of the intrinsic size.
  3. Choose transparent or solid background for the PNG.
  4. Render and download; repeat at other sizes without re-adding the file.

Worth knowing

The rendering engine here is the one you already trust: the browser itself. Whatever your SVG looks like in a browser tab - gradients, masks, filters, CSS-styled shapes, text - is what the PNG captures, because the same engine paints both. This avoids the classic failure of server-side converters built on standalone libraries, which support a narrower slice of the SVG spec and quietly drop the filter effects and font styling that make your graphic look right.

Size is where rasterizing demands actual thought, because it is a one-way door: the PNG contains pixels, not maths, and enlarging it later means blur. The rule is to render at the largest size you will ever display, or generate each required size directly - which is why the size controls sit front and centre and why re-rendering the same SVG at a second and third size takes one click. For high-DPI screens, produce assets at 2x their CSS display size; for icon sets, render each catalogue size separately rather than scaling one master PNG down repeatedly.

There is one honest limitation, and it is the browser's security model rather than a converter bug: when an SVG is loaded as an image for rasterizing, the browser refuses to fetch anything the file references externally. An <image> tag pointing at a URL, a stylesheet link, a font loaded from a CDN - none of them will be fetched, and the affected parts render blank or fall back to default fonts. Competing tools hit the identical wall and simply let your logo render wrong without comment. The fix is an SVG with everything inlined: embed images as data URIs and convert text to outlines (or inline the font as base64) before exporting from your design tool.

Backgrounds behave the way vector people expect: SVG has no canvas colour, so output defaults to transparent PNG, with an optional solid fill when the destination cannot composite alpha.

If your SVG renders with missing images or wrong fonts, the cause is usually the browser's same-origin rule for SVG-as-image: external references inside the file are deliberately not fetched during rasterization. Inlining assets as data URIs or outlining text fixes it - a failure mode most converter pages leave you to discover alone.

Verify it yourself: open your browser's DevTools, switch to the Network tab, and use this tool — you will see no upload request. Or load the page, go offline, and it still works.

What this tool will not do

  • It will not fetch external resources referenced by the SVG - linked images, remote stylesheets and CDN fonts are blocked by the browser during render, so they must be inlined first.
  • It will not repair malformed SVG; a file with broken markup renders exactly as broken in the PNG as it does in a browser tab.
  • It cannot rasterize SMIL or scripted animation - the PNG captures the static initial state only.

Common raster sizes to generate from one SVG

DestinationRecommended PNG sizeBackground
Favicon source512 x 512Transparent
App store icon1024 x 1024Solid (stores reject alpha)
Social profile image400 x 400 or largerSolid
README / docs logo2x displayed sizeTransparent
Print at 300 DPIPhysical inches x 300Solid white

Questions people ask

What size should I export my SVG to PNG at?

Match the largest final display size, doubled for high-DPI screens - a logo shown at 200 pixels wide should be exported at 400. When several sizes are needed, render each from the SVG directly instead of downscaling one big PNG through multiple steps.

Why does my SVG render blank or with missing parts?

Almost always because the file references something external - a linked image, stylesheet or web font - which browsers refuse to fetch when rasterizing SVG for security reasons. Re-export the SVG with images embedded as data URIs and text converted to outlines, and it will render completely.

Will the PNG keep the transparent background of my SVG?

Yes, by default - areas the SVG does not paint stay fully transparent in the PNG. A solid background colour is one toggle away for destinations like app stores that require opaque images.

Why do the fonts look different in the converted PNG?

The SVG names a font that is not embedded in the file, so the renderer substitutes whatever system font is available - and external font links are blocked during rasterization. Convert the text to paths in your design tool, or embed the font as a base64 data URI, and the PNG will match exactly.

Can I make a PNG larger than the SVG's stated size?

Yes, and it stays perfectly sharp - vectors have no native resolution, so rendering a 24-pixel icon at 4096 pixels is legitimate and crisp. Multiplier presets from 1x to 16x cover the common cases, with a custom pixel field for exact targets.

Does converting affect the original SVG file?

No - the SVG is only read, and a new PNG is generated from it. Keep the SVG as your master; it remains the editable, infinitely scalable source you re-export from whenever a new size is needed.

Usually the next step

More in Convert

This page processed nothing on any server — there is no server. The technical explanation.