Convert SVG to PNG High-Res
Convert scalable SVG vector files to standard raster PNG images.
How to convert SVG to PNG — 3 steps
- 1
Add your SVG
Drop in the vector file. It is rendered in your browser, so logos and brand assets for unreleased work are not uploaded.
- 2
Choose the output size
This is the decision that matters. An SVG has no inherent resolution, so you are choosing how many pixels the PNG will contain — pick the largest size it will ever be displayed at.
- 3
Download the PNG
Save the rendered image. Transparency is preserved, so a logo drawn on no background stays free of one.
Vector and raster are different kinds of thing
An SVG is not a picture in the ordinary sense; it is a set of instructions. It describes shapes mathematically — this circle here, that curve there, filled with this colour — and whatever displays it draws those shapes at whatever size is asked for. That is why a vector logo is perfectly crisp on a business card and equally crisp on the side of a van: there are no pixels until something renders it, so there is no resolution to run out of.
A PNG is the opposite: a fixed grid of pixels, decided once when the file is made. Converting from SVG to PNG therefore means committing to a size, and that commitment is permanent. Render at 200 pixels wide and the logo will be soft the moment anyone displays it at 400 — the detail simply is not in the file. This is the reverse of the usual conversion problem, where you are limited by the source; here the source is unlimited and the choice is entirely yours.
So render generously. Choose the largest dimension the image will realistically be used at, and if it might be used on high-density screens, double it — a logo shown 300 pixels wide should be rendered at 600 to look sharp on a modern display. Making it smaller later is easy and lossless; making it bigger is not possible.
When to convert, and what can go wrong in the render
Keep the SVG wherever it works, because it is almost always the better file: smaller, infinitely scalable, and styleable with CSS. Convert when the destination cannot handle vectors, which is more often than you might expect. Social media platforms, most email clients, office documents, marketplace listings, video editors, app icon pipelines, and many content management systems all want a raster image. Some of these reject SVG outright for security reasons, since an SVG can contain scripts.
One rendering issue accounts for most surprises: fonts. An SVG that references a typeface by name relies on that font being available when the file is rendered. If it is not, the text is drawn in a substitute and your carefully spaced wordmark comes out in something else entirely. The reliable fix is to convert text to outlines in your design tool before exporting the SVG, which turns the letters into shapes that cannot be substituted.
Two smaller things to check. Transparency carries across, so make sure that is what you want — a logo rendered on no background will show whatever sits behind it, which is usually right for a website and wrong for a document where you expected white. And confirm the SVG has explicit dimensions or a viewBox; without one, renderers have to guess at the intended size, and results vary between tools.
Your files never leave your device
The vector is rendered in your browser, so brand assets, icon sets, and design work for unlaunched projects never leave your machine.
Most online PDF sites upload your document to their servers, process it there, and keep a copy for minutes, hours, or longer. PilotPDF works differently: the page downloads a small processing engine into your browser, and your file is opened and edited in your device's memory using WebAssembly. Nothing is transmitted, so there is nothing for a server to store, leak, or scan. You can even disconnect from the internet after the page loads and the tool keeps working.
Read more about how this works in our privacy-by-design explainer.