Why convert SVG to PNG?
SVG is the right format almost everywhere on the modern web. But there are still places that need raster PNG:
- Email clients. Most email clients strip or fail to render SVG. PNG works in Gmail, Outlook, Apple Mail.
- Print / PDF embedding. Print shops and PDF tools handle PNG more predictably than SVG, especially with custom fonts.
- App icons. iOS and Android both want PNG at specific pixel sizes.
- Social media uploads. Twitter, Instagram, LinkedIn — none accept SVG.
- Office docs. Pasting SVG into older Word / PowerPoint is unreliable.
- Favicons (legacy). Modern browsers support SVG favicons, but older ones still need PNG fallbacks.
SVG vs PNG
| SVG | PNG | |
|---|---|---|
| Type | Vector (math) | Raster (pixels) |
| Scaling | Infinite, no blur | Fixed; blurry above 100% |
| File size | Tiny for shapes; huge for complex art | Predictable; grows with pixels |
| Transparency | Yes | Yes |
| Editable in code | Yes — XML | No |
| Email / print / app icons | Limited | Universal |
Picking the right export size
- 1× — when the PNG will replace the SVG at the exact intended display size (favicons, app icons with known dimensions).
- 2× — the default for UI assets. Retina displays render every CSS pixel as 4 physical pixels; 2× gives sharp results everywhere.
- 4× — for design files that will be downscaled later, or for marketing graphics that need to look perfect on 4K displays.
Transparent vs white background
Pick Transparent when the icon will sit on a colored UI background. Pick White when the PNG will be printed, embedded in a document, or used somewhere a dark background might bleed through (some email clients default to dark mode).
Privacy
The SVG is parsed by your browser’s DOM, rasterized by a sandboxed Canvas, and encoded to PNG locally. There is no upload, no server, no log.