Convert SVG to PNG at any resolution. Rasterize vector graphics for social media, email, and platforms that reject SVG. Runs in your browser.
Drop SVG file here
or click to browse · paste from clipboard (Ctrl/⌘+V)
PNG, JPG, WebP, AVIF, GIF, BMP, SVG, HEIC, ICO · up to 20 files
SVG and PNG serve fundamentally different purposes. SVG is a vector format: it describes shapes with mathematical coordinates that render perfectly at any zoom level. PNG is a raster format: a fixed grid of pixels with a specific width and height. Converting SVG to PNG means choosing a resolution and freezing the vector artwork into pixels at that size.
This tool performs that rasterization in your browser using the Canvas API. No files leave your machine.
<img> elementdrawImage()toDataURL('image/png')The browser’s SVG rendering engine handles all the heavy lifting: anti-aliasing, text layout, gradient interpolation, and filter effects.
SVG is the ideal format for icons, logos, and illustrations on the web. But many contexts outside the browser reject SVG entirely:
Twitter, Facebook, LinkedIn, and Slack preview cards require raster images. If you set an og:image meta tag to an SVG URL, most platforms will either ignore it or show a broken image. You need a PNG (or JPEG) at the platform’s recommended dimensions, typically 1200x630.
Most email clients strip SVG tags and block SVG images for security reasons (SVG can contain JavaScript). PNG is the safe choice for email headers, signatures, and inline graphics.
iOS and Android require raster icons at specific sizes. If your source logo is SVG, you need PNG exports at each target resolution (e.g., 1x, 2x, 3x for iOS).
Many documentation tools and PDF renderers have limited or no SVG support. Converting to PNG at a high resolution (2x or 3x) ensures sharp output in generated PDFs.
Slack custom emoji, Jira avatars, Notion covers, and many SaaS platforms only accept PNG, JPEG, or GIF uploads. SVG is not an option.
The SVG viewBox defines the coordinate system but not the output size. When rasterizing, you choose the pixel dimensions:
| Use case | Recommended size |
|---|---|
| Social share image | 1200 x 630 |
| App icon (high-res) | 512 x 512 |
| Favicon (PNG fallback) | 32 x 32 or 48 x 48 |
| Email header graphic | 600 x 200 |
| Documentation figure | 2x display size |
Always maintain the SVG’s aspect ratio. If the viewBox is 0 0 24 24, export at square dimensions (256x256, 512x512). Stretching a non-square SVG to square dimensions distorts the artwork.
If the SVG uses custom fonts via CSS @font-face or Google Fonts links, those fonts must be available to the browser during rasterization. The safest approach is to convert text to paths in your vector editor before exporting.
SVGs that reference external images with <image href="..."> will render those images as blank if the external URL is not reachable. Embed images as Base64 data URIs inside the SVG using the Base64 Encoder.
SVGs without a viewBox attribute rely on width and height for sizing. If both are missing, the Canvas may render at an unexpected size. Always ensure your SVG has a viewBox.
A bloated SVG with unnecessary elements still rasterizes correctly, but a clean SVG loads faster in the tool. Run it through SVGO if the SVG came from a design tool.
Rasterizing an SVG is a one-way operation. You gain universal compatibility (every platform handles PNG), but you lose resolution independence. A 256x256 PNG looks blurry at 512x512. If you need multiple sizes, rasterize from the SVG source at each target resolution rather than scaling a single PNG.
For the reverse direction (encoding images for embedding), see the Base64 Encoder. For other format conversions, return to the Image Converter.
Nothing you paste leaves this tab. Every tool runs entirely in your browser — no upload, no server, no account.