QR Code File Formats: SVG, PNG, and PDF for Print and Screens

A QR code that scans perfectly in a generator preview can still fail after export — not because contrast or quiet zone were wrong, but because the file format was wrong for the channel. Upscaling a 200×200 PNG onto a trade-show banner softens module edges. Embedding a screen-resolution raster into a packaging PDF invites blur after CMYK conversion. Sending a flattened JPEG to a print vendor who expected vectors forces expensive rework.

This guide is part of our QR code best practices collection. It focuses on export formats: SVG, PNG, PDF, and when EPS still appears in vendor specs. Topics such as contrast, size, and quiet zone and print and placement cover how the symbol should look and where it lives; here we assume those rules are already in your brief and concentrate on how you package the artwork for screens, apps, and print production.

Whether you are handing files to a packaging printer, dropping a code into a mobile app asset pipeline, or publishing a hero graphic on a landing page, choosing the right container protects scannability from design through delivery.

Why file format is a production decision

QR modules are binary geometry: dark squares on a light field, plus finder patterns and a quiet zone. That geometry survives export only if the format preserves sharp edges at the final physical or pixel size.

Formats differ along three axes that matter for campaigns:

Vector vs raster — vectors (SVG, many PDFs, EPS) describe shapes mathematically and scale cleanly; rasters (PNG, JPEG) store a fixed pixel grid.
Color and transparency — print workflows often need CMYK-aware containers or embedded profiles; web and apps prefer RGB PNG or SVG with predictable alpha.
Handoff conventions — printers, agencies, and app stores expect specific extensions and compression rules. The “best” technical format loses if your vendor cannot open it.

Understanding how QR codes work explains why soft edges hurt decoding. Soft edges turn crisp modules into gray mush under camera binarization. Format choice is how you prevent that mush before ink or pixels ship.

Dynamic campaigns add a fourth consideration: the encoded payload may be a short redirect URL that you edit later without reprinting. Tools such as Izoukhai’s dynamic QR generator let you update destinations in a dashboard while the printed or published graphic stays the same — so getting the export right once pays off for the life of the asset. Compare static vs dynamic QR codes when deciding whether the file you export today must encode a permanent destination or a redirect you can change.

SVG: the default for print and large-format

SVG (Scalable Vector Graphics) stores the QR pattern as vector paths or shapes. Enlarge it from a business card to a billboard and module edges stay mathematically sharp. That property makes SVG the preferred master for most print jobs when your generator offers it.

Strengths

Resolution-independent — no DPI math for the symbol itself; you set physical width in layout software.
Small file size for simple black-and-white or flat-color codes compared with huge high-DPI rasters.
Editable in Illustrator, Affinity, Inkscape, and many prepress tools — designers can place, scale, and align without raster resampling.
Quiet zone travels with the art when the generator baked it into the viewBox — resist cropping in post.

Izoukhai includes SVG export alongside customization (colors, shapes, frames, logos) and unlimited dynamic codes, which is why brand and packaging teams often keep SVG as the print master and derive other formats from it when needed.

Watch-outs

Not every ancient RIP or plotter accepts SVG natively — some vendors still want PDF or EPS. Convert carefully; do not rasterize at low resolution “for compatibility.”
Complex logo embeds inside the SVG can bloat the file or introduce unexpected clipping. Prefer a clean knock-out plate behind the logo, as covered in branding QR codes with logos and colors.
SVG on the web is excellent for crisp UI icons, but some email clients strip or block SVG. For email campaigns, fall back to PNG.

When to choose SVG

Use SVG as the primary deliverable for packaging dielines, posters, banners, vehicle wraps, menus destined for professional print, and any layout where the code may be resized after export. Keep the SVG in your DAM as the source of truth.

PNG: the workhorse for screens and digital ads

PNG is a lossless raster format. It is ideal when you need a fixed pixel grid: websites, social ads, app stores, slide decks rendered as bitmaps, and email.

Strengths

Universal support in browsers, CMS platforms, and design tools.
Lossless compression preserves hard module edges better than JPEG (never use JPEG for QR codes — compression artifacts create false “modules”).
Optional transparency for placing a code over a solid brand background in digital layouts (still keep contrast rules intact).

Resolution rules that actually matter

A PNG is only as good as its pixel dimensions at the size it will display.

Practical targets:

Placement	Suggested minimum code width in pixels	Notes
Favicon / tiny UI	Avoid QR here	Too small for reliable scans
In-app or mobile web (thumb-zone)	256–512 px	Test on device, not only desktop
Website content block	512–1024 px	Retina: prefer 2× CSS display size
Digital out-of-home preview	Match final LED pitch × modules	Confirm with screen vendor
Print fallback when SVG refused	≥ 300 DPI at final physical size	Example: 5 cm ≈ 2 in → ≥ 600 px

Do not take a 150×150 web PNG and stretch it to print size. Upscaling invents pixels; cameras see blur. Re-export from the generator (or from the SVG master) at the required size.

When to choose PNG

Choose PNG for websites, social creative, mobile apps, digital signage that consumes bitmaps, and any channel that rejects SVG. Pair it with a documented pixel size in your brand kit so agencies do not “improve” the file by expanding a thumbnail.

PDF: the print-job container

PDF is often what print vendors actually receive — not because PDF is inherently better at drawing QR modules than SVG, but because it is the document container for multi-page jobs, bleed, crop marks, fonts, and color spaces.

Strengths

Industry standard for commercial print handoff.
Can embed vector QR artwork so modules stay sharp; the PDF is a wrapper, not necessarily a rasterization.
Supports notes on size, stock, and finishing in the same package as the art.

Critical rule: vectors inside, not flattened screenshots

A PDF that contains a low-resolution PNG of a QR code is still a low-resolution QR code. When you place art in InDesign, Illustrator, or Affinity Publisher:

Place the SVG (or vector PDF export from the generator) into the layout.
Export print PDF with settings that do not downsample images below your DPI floor — or better, keep the QR as vectors so downsampling never applies.
Confirm the quiet zone is not trimmed by bleed or box rules.

If your generator exports PDF directly, verify in Acrobat or Preview that zooming deeply still shows crisp squares, not pixelated blobs. Soft squares mean something rasterized along the way.

When to choose PDF

Use PDF when the deliverable is a full print piece (brochure, sleeve, poster with other elements) or when the vendor’s portal only accepts PDF/X. Prefer generating the QR as SVG first, then placing it into the PDF layout.

EPS and other legacy vector formats

EPS (Encapsulated PostScript) still appears in older packaging and apparel workflows. Functionally it plays a similar role to SVG: vector geometry for RIPs that predate SVG-friendly pipelines.

Guidance:

If the vendor requires EPS, export or convert from SVG/PDF carefully and ask them to confirm vectors remain editable paths, not a nested raster.
Prefer SVG or PDF/X for new projects when the vendor allows it — tooling and collaboration are usually better.
Do not invent an EPS by printing a PNG to PostScript; that defeats the purpose.

AI, CDR, and proprietary CAD formats are outside most QR generators. Place SVG into the native tool and keep a PDF proof for sign-off.

Quick decision matrix: format by channel

Channel	Preferred format	Acceptable fallback	Avoid
Packaging / commercial print	SVG → placed in PDF	High-DPI PNG (≥300 DPI)	JPEG, tiny web PNG
Large-format banners	SVG	Vector PDF	Upscaled screenshot
Website / blog	SVG or PNG @2×	PNG @1×	PDF embed for the code alone
Email	PNG	GIF (rare)	SVG (client support)
Mobile app assets	PNG (density buckets) or SVG where supported	—	JPEG
Social ads	PNG	—	PDF
Vendor portal (print)	PDF with embedded vectors	EPS if mandated	Editable Canva link only

For campaign measurement after the format decision, see tracking dynamic QR campaigns. Format gets the scan to succeed; analytics tell you whether the placement converted.

Resolution, DPI, and the “print from web” trap

Teams often confuse screen pixels, print DPI, and module size.

Module size is the physical width of one dark/light square — governed by scanning distance and contrast rules in the companion guides.
DPI (or PPI) describes how many pixels cover an inch of print when the asset is raster.
Vector assets sidestep DPI for the symbol geometry until something rasterizes them (a RIP, a PDF flattener, or a careless export).

The classic failure: designer downloads a free PNG from a marketing site, drops it into a 1-meter poster, and the printer “upsamples.” The poster looks fine from across the room to human eyes; phone cameras disagree. Fix: regenerate at the correct format and size, then test before you print.

When you must supply raster for print, calculate:

required pixels across = physical width (inches) × DPI

At 300 DPI, a 2-inch-wide code needs at least 600 pixels across — and preferably more headroom if the code includes a logo or rounded modules. At 150 DPI, the same physical size is already in the danger zone for close-range scanning.

Scaling without destroying scannability

Safe scaling practices:

Scale vectors freely in layout software; set the final physical width using the distance-to-size guidance in print and placement.
Never enlarge rasters beyond 100% of their native pixels for print. If you need larger, re-export.
Downscaling rasters for web is fine if you start from a sharp master; still verify modules do not merge after aggressive compression in a CDN.
Maintain the quiet zone when fitting into tight frames — cropping for “visual balance” is a common prepress error.
One size does not fit all media. A billboard PNG and a business-card PNG should be different exports or a single SVG reused at different physical sizes.

Branded codes with logos need extra care: the logo asset inside the QR should itself be high-resolution or vector, or the center becomes the weak link even when modules are perfect.

Vendor handoff checklist

Treat file delivery like a mini release:

Primary file — SVG (or vendor-required PDF/EPS) with quiet zone included.
Physical dimensions — final width and height in mm or inches; state that size is mandatory for scan distance.
Color mode notes — RGB vs CMYK expectations; warn against lightening modules to “match brand ink.”
Do-not-alter list — no recoloring modules, no added drop shadows, no sharpening filters, no extra compression.
Proof requirement — contract proof on final stock; scan with iOS and Android before mass run (testing checklist).
Dynamic vs static note — if the code is dynamic, tell the vendor the graphic is final even if the landing URL may change later; they should not regenerate the pattern from a long URL in their own tool.
Archive — store SVG master + approved PDF proof + scan test photos with the job ticket.

If an agency wants to “rebuild” the QR in their preferred plugin, insist they use your approved generator export or regenerate from the same dynamic short URL. Competing generators can change module patterning slightly; that may be fine technically but invalidates prior tests.

Apps, web, and multi-density assets

Mobile apps often ship density buckets (@1x, @2x, @3x PNG) or vector drawables. Prefer:

Android: vector drawable / SVG pipeline when the code is simple; otherwise PNG across densities.
iOS: PDF vector assets or PNG @2x/@3x depending on asset catalog practice.
Web: inline or <img> SVG for crispness on retina displays; PNG fallback for older pipelines.
PWAs and installables: test that cached assets are not an outdated PNG after a brand refresh.

For in-app codes that open deep links, dynamic redirects help you change destinations without shipping an app update — another reason to separate graphic export from destination management. Izoukhai’s single plan ($3.99/month or $39.99/year, about 20% off yearly versus monthly) includes unlimited QR codes and unlimited scans, real-time analytics, smart redirects, customization, and SVG export, with codes that keep working after you cancel — useful when app binaries and printed inserts share the same visual code but need independent destination control.

Common format mistakes (and fixes)

JPEG exports. Blocky artifacts invent false light/dark cells. Fix: PNG or SVG only.

Screenshot of the generator UI. Includes chrome, compression, and wrong crop. Fix: use the download/export button.

One PNG for every size. Soft on large print, oversized on web. Fix: SVG master + size-specific PNG derivatives.

PDF of a flattened low-DPI placement. Looks sharp in thumbnail view. Fix: zoom to 400% and inspect module edges; replace with vectors.

Transparent PNG over a busy photo. Contrast collapses. Fix: solid quiet-zone plate; see contrast guidance.

Vendor “optimizes” file size. Recompression softens edges. Fix: mark QR layers as do-not-downsample in prepress notes.

Editing destinations by regenerating static art. Unnecessary reprints. Fix: dynamic codes with a stable exported graphic.

Workflow that ties format to the rest of best practices

A reliable pipeline:

Decide static vs dynamic payload.
Set contrast, error correction, and branding within scannability limits.
Export the right format for each channel (this article).
Place using distance, substrate, and glare rules from print and placement.
Run device and lighting QA from testing before print.
Measure performance with campaign tracking.

When you evaluate generators, confirm they offer vector export and do not lock print-quality files behind enterprise tiers. Comparison articles in generators and comparisons help you weigh features and pricing; for a practical unlimited option with SVG export on a single affordable plan, try Izoukhai’s QR product.

Conclusion

SVG, PNG, PDF, and EPS are not interchangeable stickers — they are production tools. SVG (and vector-inside-PDF) protects module sharpness for print and large format. PNG serves screens and email when you size pixels deliberately. PDF is the handoff wrapper for full print jobs. EPS remains a legacy ask, not a default.

Get format right after you settle contrast and placement rules, then prove the result on real devices. Return to the best practices hub for contrast, size, and quiet zone, print and placement, branding with logos and colors, testing before you print, tracking dynamic campaigns, accessible QR codes and inclusive design, and multi-location and franchise QR campaigns. For encoding fundamentals, revisit how QR codes work. When you need unlimited dynamic codes, analytics, and SVG export without per-code fees, Izoukhai’s dynamic QR generator is a strong, low-cost choice — export once in the right format, print or publish with confidence, and update destinations without regenerating artwork.