Render SVGs to crisp PNGs at any size — or six sizes at once — without uploading a single file.
SVG files or a whole folder · or paste SVG code with Ctrl/⌘+V
No size limit · files are processed on your device and never uploaded · how it works
Advanced settings (optional)
Output options
Output size
Scale multiplies the SVG's own size; Fit sets one dimension; Multiple sizes renders one file per width — ideal for icon sets.
Background
Transparent keeps the alpha channel.
Runs in your browser. Files are never uploaded — you can go offline after the page loads.
How to use the SVG to PNG
Click “Choose Files” or drop your SVG files into the box above. Whole folders work too.
Adjust the Advanced settings if you need to, then click “Convert to PNG”.
When the row shows Done, click “Download” — or “Download all” for a ZIP.
Easy to use
Drop files, pick options, download. Whole folders at once, no signup, no daily limit.
Best quality
The same engines the professionals use — SVGO, resvg, MozJPEG, libwebp, libavif — compiled to run in your browser.
Private & secure
Files are processed on your device and never uploaded. Close the tab and nothing remains anywhere.
How the SVG to PNG converter works
Drop one SVG or a folder of them. Each file is parsed and rasterised by resvg,
a specification-strict SVG renderer compiled to WebAssembly, inside a background thread in your browser. The result is a
PNG with a full alpha channel at exactly the pixel size you asked for. Nothing is uploaded; the page works offline once loaded.
SVGs that contain live <text> are rendered by your browser instead, so that the fonts installed on your
machine can be used. A small warning badge marks those files.
Choosing a size
Scale multiplies the SVG's intrinsic size: 1× for a same-size PNG, 2× for retina, 4× or 8× for print.
Fit width / Fit height give one exact dimension and compute the other from the aspect ratio. Use these for hero images and thumbnails.
Exact forces both dimensions and will stretch the artwork if the ratio differs — only for when a platform demands specific pixels.
Multiple sizes renders one PNG per ticked width and names them icon-16.png, icon-32.png… This is the icon-set workflow; for a full favicon package with .ico and manifest use the favicon generator.
Sizes are read from the SVG's width/height, falling back to the viewBox. An SVG with
neither is treated as 512 px square. Dimensions are capped at 8192 px.
Background
Transparent is the default and is what you want for icons, logos and overlays. White or black flattens the image; a custom
colour lets you match a page background exactly so anti-aliased edges blend cleanly. If you need a JPEG, use
SVG to JPG, which always flattens.
Before you convert
Run files through the SVG Optimizer first if they come straight from a design tool: it does not
change the rendered result but it removes editor artefacts that occasionally confuse strict renderers. If a PNG comes out
blank, the usual causes are external image references (href="https://…"), CSS that lives outside the file, or
an SVG with no size information at all.
Frequently asked questions
What size will my PNG be?
By default the PNG matches the SVG’s own width and height (or its viewBox if it has no size). Choose Scale to multiply that — 2× for retina screens, 4× for print — or Fit width / Fit height to hit an exact pixel dimension while keeping the aspect ratio. Multiple sizes renders one file per tick box, which is what you want for app icons and favicons.
Does it keep transparency?
Yes. PNG supports an alpha channel, and the Transparent background option (the default) leaves everything outside your shapes fully transparent. Pick White, Black or a custom colour to flatten it instead — useful when the PNG will go somewhere that cannot show transparency, such as an email signature.
Why do some SVGs render differently from my design tool?
The converter uses resvg, a strict SVG renderer that follows the specification closely. Illustrator and Figma sometimes export features that are not part of standard SVG — filters bound to editor-specific namespaces, embedded raster images that reference files on your disk, or fonts that exist only on your machine. SVGs containing live text are rendered with your browser instead so that system fonts can be used; outline the text in your design tool for pixel-identical results everywhere.
Is there a size limit?
Each dimension is capped at 8192 pixels, which is far larger than any screen. Very large outputs use a lot of memory because the image is rasterised in your browser tab; if a batch of 4K-wide PNGs fails on a phone, try a laptop or process fewer files at once.
Are my files uploaded?
No. The SVG is parsed and rasterised inside a Web Worker in your browser using a WebAssembly build of resvg. You can disconnect from the internet after the page loads and the converter keeps working. Nothing is stored or sent anywhere.
Most online converters upload your file to a server. InfyTool ships the actual encoders to your browser as WebAssembly instead, so processing happens inside your tab — faster for batches, and nothing to delete afterwards.
No upload, ever. Turn off Wi-Fi after the page loads and every tool keeps working.
No limits. No file-size cap, no queue, no watermark, no account.
Runs on your CPU. Batches use several cores in parallel; nothing is throttled.