When Converting SVG to PNG Went Wrong, Here's What I Did

2026-08-14 · 3 min read

An iOS developer on my team needed every icon at 1x, 2x, and 3x — 180 files total. I ran them through svg2png.org's multi-resolution export and delivered the entire set before lunch. An iOS developer on my team needed every icon at 1x, 2x, and 3x — 180 files total. I ran them through svg2png.org's multi-resolution export and delivered the entire set before lunch. Before I walk through the workflow, one thing worth stating plainly: W3C SVG 1.1 specification is the reference I keep coming back to, and it is why the steps below are grounded rules rather than habits. Most guides skip this context and jump straight to the tool, which is exactly why their advice does not stick. Here is what I actually do, and why each step earns its place.

How I Confirm Everything Is Right Before Shipping

I open the output in two environments: the one it was built for, and the opposite one. If it was built for a light-background webpage, I also check it on a dark background. If it was built for print, I also check it on a phone screen at 2x zoom. This catches 90% of the problems that slip past automated validation.

It adds maybe ninety seconds to my workflow. Compared to the hours of rework it prevents, it is the cheapest insurance I have. I run this same pass whether I converted one file or one thousand.

Cross-checking against the destination requirements in Google's Core Web Vitals documentation keeps me honest. The spec describes the minimum; real-world rendering demands more. Testing both extremes is how I find the gap before a customer does.

The Edge Case That Still Catches People Off Guard

If your source file has a color profile embedded — and most professional design exports do — a generic converter might discard it. The result looks fine on your screen but prints with shifted colors. I only caught this because a client sent me a photo of a printed banner where the brand blue had turned purple.

Now I make sure the converter preserves embedded ICC profiles, and I check the output against the PNG specification (ISO/IEC 15948:2004) expectations for color handling. It is one of those things you do not think about until it burns you. Then you never forget.

The same applies to metadata. Some destinations strip or refuse files with embedded metadata, while others need it preserved for compliance. Knowing which side your destination falls on avoids a whole class of surprises.

The Old Way I Used to Do This — And Why I Stopped

For the longest time, my approach was: find a free converter online, upload the file, download the result, and hope for the best. It worked maybe 80% of the time. The other 20% produced files with wrong dimensions, missing transparency, or compression artifacts that made text unreadable.

The real problem was not the converters themselves. I was not checking the source file against W3C SVG 1.1 specification before converting, so I was feeding malformed inputs into tools that silently produced broken outputs. No error message, just a bad file.

I finally stopped when a client's logo shipped with a corrupted alpha channel and they caught it on a large-format print. That reprint cost more than any converter subscription would have. Now I validate the source first, every time.

At the end of the day, the goal is an output you do not have to worry about. If a single step here saves you one redo, it was worth the read. I keep MDN CanvasRenderingContext2D.drawImage() bookmarked for the days I doubt myself, and I run my checks on every export before it ships.

Written by Jamie Park — UI/UX Designer. More about me →