SVG → PNG
Converting locally: nothing is uploaded
Vectors pinned at the size you choose: free, and finished on your machine.
Drop your SVGs in the drum
or , and nothing leaves this tab
READS JPG · PNG · WEBP · GIF · BMP · SVG · AVIF
CYCLE →
WASH TEMP
OUT OF ORDER — JAM REPORT
The SVG → PNG cycle
Icon submissions, app-store forms and image hosts that reject SVG all want raster at a fixed size. This cycle renders your vector crisply and pins it down.
Transparency survives the cycle: both stocks carry a full alpha channel. PNG is lossless, so weight follows content: graphics shrink, photos grow. Either way, re-encoding through the canvas collects EXIF like lint: camera model, GPS coordinates and timestamps are stripped from the folded copy.
SVG is described by shapes rather than pixels, so it can be drawn at any size. A PNG is fixed at one size, which means you should decide the size you need before converting. App stores, social profiles and email clients commonly want a specific pixel width.
If the result looks different from the SVG, the usual cause is text. Fonts that are only referenced by name will be replaced with a default if the browser does not have them. Converting text to outlines in your design tool before exporting the SVG avoids this.
Need the other direction? Other routes into JPG → PNG, WebP → PNG, GIF → PNG, BMP → PNG.
Questions at the counter
What resolution do I get?
The SVG’s intrinsic size (or 1024 px wide when it declares none) rendered at device-quality with vector sharpness. Need another size? Scale it in any editor first; vectors resample perfectly before rasterising.
Is transparency preserved?
Fully. SVG sits on a transparent canvas by nature, and PNG keeps every soft edge and shadow exactly where the vector drew them.
Why does my SVG look different rasterised?
Fonts and external references are the usual culprits: a vector that depends on installed fonts or linked images renders differently outside its home. Inline your fonts or convert type to paths for faithful results.
Is the conversion really private?
Yes, architecturally. This page is static files; there is no server to receive an upload. Your SVG is decoded and re-encoded inside this tab by your own machine, and you can watch the absence of network traffic in your browser’s developer tools.
Before you convert
A converter can change the container. It cannot tell you whether that was the right call for this particular image. These cover the decision itself. They were written from building the encoders that run on this page, and are checkable against your own files.