SVG to PNG Converter

No. The conversion runs entirely in your browser. The file is read into memory, processed by a JavaScript library running in the same tab, and the result is delivered straight to your downloads. Open DevTools while you convert — you'll see zero network traffic carrying your file. This matters for anything sensitive: contracts, drafts, financial documents, personal notes.

No fixed limit. The real ceiling is your device's memory. Most text and PDF files are small enough that this is never a concern — multi-megabyte documents convert fine on phones. Very large files (hundreds of MB) may struggle on older or memory-constrained devices.

Untouched. The converted file is a separate copy that lands in your downloads. Your original stays exactly where it was on disk.

Yes. Tap the drop zone to open your phone's file picker, choose a file from Files / Downloads / Drive / iCloud, hit Convert. The result downloads to your device's standard download location.

Those sites upload your file to their servers, run conversion server-side, and email you a download link. They get to read your document, log your IP, and store the file (for some period). This tool does none of that — everything runs in your browser tab. We don't even have an account system, so there's nothing to sign up for and nothing to log out of.

Depends on your use case. 1× matches the SVG's intrinsic size — good for matching pixel-perfect web layouts. 2× (recommended default) produces retina-quality output and is the right choice for most uses including social media uploads, mockups, and presentations. 4× is for print, large thumbnails, or anywhere you need room to crop in. 8× is overkill for most cases but useful if you're producing a single hero image at a billboard size.

Yes — PNG natively supports transparency (alpha channel). Anywhere the SVG is transparent (no fill, no background, transparent stroke), the PNG output is also transparent. If you need a solid background, use SVG → JPG instead (or open the result in any image editor and flatten the background yourself).

External resources won't load — when the browser renders the SVG for conversion, it loads the SVG as a static image, and that load context can't fetch external URLs (font files, embedded images via http://, etc.). The result: external resources appear as missing content (gaps where text would have been, broken-image markers where images were referenced). To preserve them, embed everything in the source SVG: convert text to paths in your design tool, or inline images as base64 data URLs. If the SVG was exported from Figma / Illustrator / Inkscape with default settings, this usually isn't an issue — those tools embed everything by default.

First it looks at the viewBox attribute (the most reliable source). If that's missing, it falls back to explicit width and height attributes on the <svg> root. If neither is present (rare but possible with hand-edited icons), it defaults to 800×600 — you can scale that up with the scale factor option. The output dimensions show in the result panel so you always know what you got.

The total pixel count is capped at ~50 megapixels for memory safety (that's about 16,000 × 16,000 pixels — well beyond anything reasonable). If your chosen scale factor would produce something larger, you'll get a clear error suggesting a smaller scale. Most users never hit this; it exists to prevent accidental browser crashes when someone picks 8× on an SVG with a 4000×4000 viewBox.

Canvas refuses to render SVGs with <foreignObject> containing HTML — it considers them "tainted" for security reasons (the canvas could leak rendered content from other origins). The export will fail with a clear error. To work around it, replace the foreign-object content with native SVG elements (text, paths) in your source.