SVG or PNG for a QR code? The print quality answer
Vector for print, raster for screens — and the reason is specific to how QR codes are built. Plus the DPI numbers if you have no choice.
Most format advice is generic. For QR codes the answer is unusually clear-cut, and the reason is specific to how they are built.
Why it matters more than for other images
A photograph degrades gracefully. Scale it up and it goes soft, but a soft photograph is still recognisable.
A QR code is hard-edged squares with precise gaps. There is no graceful degradation. Scale up a raster QR code and the module edges blur; the black bleeds into the white; the scanner can no longer tell where one module ends and the next begins. It stops being a QR code.
That is why the format choice matters here more than for almost any other graphic.
The difference in one line
PNG is a grid of pixels. Fixed resolution. Enlarging invents pixels that were never captured.
SVG is a set of instructions. "Draw a black square at this position, this size." The renderer executes them at whatever size is asked, so the output is exact at 2 cm and exact at 2 metres.
What to use
| Where it goes | Format | Why |
|---|---|---|
| --- | --- | --- |
| Business card, flyer, poster | SVG | Vector, perfect at any size |
| Sent to a designer or press | SVG or PDF | Both vector; PDF if they insist |
| Print shop with an old workflow | EPS | Some still require it |
| Website or app | PNG or SVG | Both fine on screens |
| Slide deck | PNG at 1000 px+ | Simplest to place |
| Social media post | PNG | Platforms re-encode anyway |
| Email signature | PNG | SVG support in email clients is unreliable |
The rule: paper means vector.
The DPI numbers, if you must use PNG
Sometimes a workflow simply demands a raster file. The formula:
pixels = printed size in inches × 300
| Printed size | Pixels needed at 300 DPI |
|---|---|
| --- | --- |
| 2 cm (0,8 in) | 240 px |
| 5 cm (2 in) | 600 px |
| 10 cm (4 in) | 1200 px |
| 20 cm (8 in) | 2400 px |
| 50 cm (20 in) | 6000 px |
Always export at or above the target — never scale up afterwards. Exporting a 500 px PNG and stretching it to fill a poster is the single most common cause of a printed code that fails while the on-screen version worked.
When in doubt, export larger. A QR code is a small file even at 4000 px, because it compresses extremely well.
Why SVG is usually smaller too
Counterintuitive but true: a QR code SVG is often 2 to 8 KB, while the same code as a 2000 px PNG is 20 to 60 KB.
The SVG only stores instructions for a few hundred squares. The PNG stores every pixel. So the vector file is both higher quality *and* lighter — which is why paywalling it makes no technical sense. It is a pricing decision, not a cost.
What about PDF and EPS?
Both are vector, so both are correct for print. Which one depends on who receives the file.
PDF is the safest thing to hand a printer or a designer. It is universally accepted, self-contained, and can carry a fixed page size — which is why our export offers table tent and poster layouts rather than only the bare code.
EPS is an older PostScript format. Some print shops with established workflows still request it, particularly for packaging and large-format work. If nobody asked for EPS, you do not need it.
A caveat on PDF: a PDF can *contain* either vector or raster. If someone exports a PDF by placing a low-resolution PNG inside it, you get a vector wrapper around a bad image. Open the file and zoom to 800% — real vector stays perfectly crisp, a wrapped raster goes blocky.
Transparency and background colour
Worth deciding deliberately, because it causes real failures.
A transparent background is convenient for placing a code over a coloured panel — but only if that panel is light. Dropped onto a dark or busy background, a transparent code loses the contrast scanners depend on, and there is no quiet zone to find.
The safe approach for print is a solid light background baked into the file, with the quiet zone included. It removes any chance of a designer placing it somewhere that breaks it.
SVG and PNG both support transparency. PDF and EPS handle it less predictably across print workflows, which is another argument for a solid background when the destination is paper.
The paywall
Here is the industry pattern: design the code for free, then charge for the vector export. It works because the people who need SVG are the ones printing at volume — the ones with a budget.
QRWisp gives you SVG, PDF and EPS free, with no account. Not generosity — the site is funded by advertising on the content pages instead of by locking the download. The economics are just arranged differently.
Practical checklist before sending to print
- Export SVG (or PDF if the printer asked)
- Open it and confirm it renders — a broken SVG shows as blank, not as a bad code
- Check the quiet zone survived: 4 modules of empty margin on all sides
- Print one at final size, on the real material
- Scan it with an older phone, in the real lighting
Step 4 catches problems no file inspection will.
In short
- SVG for print. PNG for screens. That is the whole answer
- QR codes are hard edges, and hard edges are what raster scaling destroys
- If forced into PNG: printed inches × 300 = pixels, and never scale up after export
- Vector is smaller *and* better here — paying for it is paying for someone's pricing model
- PDF for handing to a printer; EPS only when specifically requested
- Prefer a solid light background for print rather than transparency