PNG or SVG: Which QR Code File to Use for Print vs a Website

QR code generator downloads in either format from the same live code, and the right choice comes down to one question: is this going somewhere that has a fixed, known size, or somewhere it might need to scale up later?

PNG: for a known size, used as-is

A PNG is a fixed grid of pixels, generated at whatever download size you set (200 to 1,000px). It's the right choice whenever the code is going into a document or a webpage at roughly that size and staying there - a business card, a flyer laid out in a page editor at a fixed dimension, a slide, an email signature. Every image editor and every website understands PNG natively, and at the size it was generated for, it looks exactly as sharp as the SVG version would.

SVG: for anything that might get scaled up

An SVG doesn't store pixels - it stores the actual shapes (the individual modules) as drawn instructions, redrawn fresh at whatever size it's displayed at. That means a QR code exported as SVG can be dropped into a huge event banner, a storefront window decal, or a large-format poster and it stays perfectly crisp - there's no resolution ceiling to hit, because there's no fixed resolution to begin with. It's also the better choice for a print shop workflow, since professional print software typically expects vector art for anything going to a large physical size.

Where the difference actually matters

For a website favicon-sized or thumbnail-sized code, or anything embedded at a modest, known size, PNG is simpler and works everywhere without a second thought. For a printed poster, a vinyl decal, a banner, or anything where the exact final size isn't locked in yet, SVG removes the guesswork entirely - there's no wrong size to have generated, because it was never generated at a fixed size in the first place.

One thing neither format changes

The color contrast warning and the error-correction level are decided before you download, and both formats encode the exact same underlying code - choosing PNG over SVG (or the reverse) never changes what the code scans to or how much damage it can tolerate. The format choice is purely about how the image behaves once it leaves this tool, not about the data inside it.

The two file sizes aren't close, and it rarely matters

An SVG storing a QR code is typically a small file - it's describing a grid of simple squares as coordinates and dimensions, not compressing millions of pixels, so it stays lightweight even though it can scale infinitely. A PNG at a large download size is comparatively heavier, since it's storing an actual pixel for every point on the grid at whatever resolution was chosen. In practice this almost never decides which format to pick - both are small enough that neither noticeably affects a page's load time or an email's attachment size - but it's a real, verifiable difference between the two if file weight ever does matter for a specific use.

Which everyday tools actually expect which format

Word, PowerPoint, Google Docs, and most email clients handle a PNG without any friction - drag it in and it displays exactly as generated, at whatever size you place it. Design and layout software built around vector artwork - Illustrator, Figma, most print-shop prepress software - generally expects an SVG (or accepts one far more gracefully than a raster image scaled past its native resolution), because that's the format the rest of the artwork on the page is usually built in too. Picking the format that matches where the code is actually going avoids a second, avoidable step of converting one into the other later.

Where this fits

QR code generator offers both formats with one click each, generated fresh at export time so a large SVG or a high-resolution PNG never slows down the live preview while you're still adjusting colors and content. The background covers why a QR code beats a printed link, and the how-to guide covers the full process including error-correction levels.