Completely FREE SVG to PNG converter. No upload, no signup, no watermark. Turn any SVG — a logo, an icon, an illustration — into a pixel-perfect PNG at exactly the size you need, transparency intact. Or click one button and get a complete favicon set, ready-to-paste HTML included.
Load an SVG file or just paste the markup straight in. Rendering uses your browser's own SVG engine, so what you get is precisely what the browser shows — and nothing you convert leaves your device.
Your data never reaches us
Nifty Utilities has no backend server, database, user accounts, or endpoint capable of receiving your tool inputs. Files and entries are processed inside your browser. We cannot view, capture, or store them.
Vector in, pixels out
An SVG is a set of drawing instructions — mathematically perfect at any size, which is why designers deliver logos in it. But large parts of the practical world only accept pixel images: Office documents behave better with PNGs, most upload forms reject SVGs outright (some for security reasons), email clients render them unreliably, and print shops often ask for a high-resolution raster. Converting to PNG freezes the vector into pixels at a size you choose, and because you choose it before rasterizing, the result is perfectly sharp — unlike stretching a PNG that was exported too small.
Pick the size that matches the job
The golden rule of rasterizing: export at the largest size you will actually display, because you can always scale a PNG down cleanly but never up. Leave the width blank to use the SVG's own declared size, or set an explicit width — height follows the aspect ratio automatically. A logo headed for a document does well at 1,000–2,000 pixels; a hero graphic for a site, at the largest width it will occupy on a large screen; artwork for print, at roughly 300 pixels per inch of physical size. Transparency is preserved throughout, so the PNG drops onto any background the way the SVG would.
The one-click favicon set
Favicons are the standard "I have an SVG logo, now what" problem, because browsers and devices want a small zoo of sizes. The favicon button renders your SVG at all six that matter in practice: 16 and 32 pixels for browser tabs, 48 for legacy Windows contexts, 180 for Apple touch icons, and 192 and 512 for Android and progressive web apps. Each is centered on a transparent square canvas, named conventionally (favicon-32x32.png, apple-touch-icon.png, and so on), and the tool prints the <link> tags to paste into your page's <head>. One genuine tip: check the 16-pixel version with your own eyes — detailed logos turn to mush at tab size, and the usual fix is a simplified mark just for the smallest icons.
Paste markup, skip the file
The paste box accepts raw <svg> markup directly, which is handy more often than you would think: an icon copied from a design tool's export panel, an inline SVG lifted from a page's source, a snippet from an icon library's documentation. If the markup lacks explicit dimensions, the tool reads the viewBox to establish proportions and defaults sensibly from there.
What can't render, and why
Conversion happens by drawing the SVG onto a local canvas, and for security the browser refuses to taint that canvas with cross-origin content. In practice that means SVGs that pull external images or remote web fonts will fail or render without them. The fix is self-containment: embed images as data URIs and convert text to outlines/paths in your design tool before exporting. Scripts inside SVGs never execute here — the file is treated purely as an image, which is safer for you, too.
Frequently asked questions
How do I convert SVG to PNG with a transparent background?
Just convert — transparency is the default. Anywhere the SVG doesn't paint stays transparent in the PNG, shown as a checkerboard in the preview. No setting required.
What size PNG should I make from my SVG?
Twice the largest size it will be displayed at is a safe rule (it covers high-density screens). For favicons, use the favicon button instead of guessing — the six standard sizes cover every device convention.
Why does my converted PNG look different from the SVG in my design app?
The tool renders with your browser's SVG engine, and a few advanced effects — certain filters, blend modes, or app-specific features — differ or degrade outside the design tool. If the SVG displays correctly when opened directly in a browser tab, it will convert identically here.
Important
SVGs that reference external images or web fonts cannot be rendered by the browser's offline rasterizer; embed those resources in the SVG first. Rendering fidelity follows your browser's SVG engine.
Support
Problem with this tool or suggestions for improvement? Please email support@niftyutilities.com.