QR Codes for Printed Marketing

Every print shop has slightly different file requirements, but a robust print-QR file set covers nearly all of them.

The primary file is SVG with no background fill (transparent zone). SVG is vector, infinitely scalable, and embeds cleanly in InDesign, Illustrator, Affinity Publisher, and every modern print workflow. Module edges stay crisp at any size; quiet zone is correctly preserved.

The fallback file is PNG at 2048×2048 with transparent background (PNG-32 alpha channel). Use this when the print shop's workflow does not accept SVG or when the QR needs to overlay a photograph rather than sit on a solid background. Resolution at 2048 means the code prints clean at any size up to billboard scale.

The CMYK file is only needed if your print shop specifically requests it. Most modern digital and offset printers handle RGB-to-CMYK conversion themselves. If they request CMYK, export from a tool that handles ICC color profiles correctly — Adobe Illustrator's PDF export with the correct profile is the safe path. EZQR's SVG export is RGB by default; the print shop converts.

Spot color: skip it unless the print shop specifically asks. QR codes do not benefit from spot-color printing — solid black on solid white is what scanners want, and that prints cleanest via standard CMYK or single-pass digital.

File naming convention: include the destination URL or label in the filename so the print shop can verify the right code is on the right asset. "qr-vcard-alex-smith.svg" beats "qr-final-v3.svg" when you have 500 different cards in a single job.

A QR on a business card is the most personal print-QR use case. The code carries your name, contact info, and brand presentation into every business interaction. Failure modes there reflect on you specifically.

Size: 0.5–0.75 inch on a standard 2 × 3.5 inch card. Below 0.5 inch you start losing scan reliability on older phones; above 0.75 inch the QR dominates the card visually and competes with your name.

Content type: a vCard 3.0 encoded directly is the right choice for most cards. Scanning opens the OS contact app with all fields pre-filled — two taps to save. Use vCard QRs unless you specifically need an editable destination (e.g., you change roles often), in which case a dynamic URL pointing to a contact landing page works.

Placement: bottom-right corner of the front, oriented for the recipient holding the card right-side-up. Avoid placing on the back if the back has heavy graphics — the contrast competes.

Logo embedding: a small brand mark in the QR center (under 12% area) at error correction level H is fine. Skip if your brand mark is not vector-clean — fuzzy logos at small print sizes look worse than no logo.

Color: navy, charcoal, burgundy, deep purple all work on white or cream stock. Black-on-white is the safe default. Skip metallic finishes on cards where the QR sits — the reflection breaks scans under fluorescent office lighting.

Test before printing 500 cards. The QR business card generator comparison covers which tools handle the small-print-size case best.

Most professional print-QR projects are bulk — 500 employee vCards, 5,000 product packaging codes, 1,500 event tickets with unique check-in URLs. Hand-generating each is not the workflow.

The bulk pattern: prepare a CSV with one row per QR. Columns include the unique data (URL, vCard fields, ticket ID) plus a label column for the output filename. Upload the CSV to EZQR Lite or Max, the generator produces a ZIP of PNG/SVG files, one per row.

For employee vCard cards, the CSV columns are: name, title, mobile, office, email, company, label. The label column becomes the output filename so the print shop matches each QR to each card in the print queue.

For product packaging, the CSV is one row per SKU. URL column points to the product's variant page; label is the SKU code. Bulk-generated files import into the packaging design template in InDesign as a data-merge.

For event tickets, the CSV is one row per attendee. URL points to a unique check-in token; label is the attendee ID. Print shop merges into the ticket template, prints the batch, ships to the event.

Throughput numbers: EZQR processes 1,000 static codes from a CSV in ~50 seconds. 5,000 takes ~3 minutes. The bulk generator comparison covers the per-vendor speed and the failure modes (silent row skipping, filename collisions, hidden per-code fees) to watch for.

Your print shop's QR experience varies wildly. A 30-year-old offset operation may have never run a QR-heavy job; a digital print shop targeting marketing agencies handles them daily. Ask before the file goes to press.

File format acceptance: confirm they accept SVG (vector). If they require PNG, ask the minimum resolution — anything below 300 DPI at print size is risky.

Color profile handling: ask how they handle RGB-to-CMYK conversion. If they convert at the prepress stage, your RGB SVG is fine. If they require pre-converted CMYK, get the ICC profile they prefer and export accordingly.

Proof copy: ask for a one-card or one-sheet proof before the production run. Most shops include one digital proof free; physical proofs cost $5–25 but are worth it for QR-heavy jobs. Scan the physical proof on three phones before approving.

Bleed and quiet zone: the QR's four-module quiet zone is sacred — confirm with the shop that bleed (their margin for trim variance) does not crop into it. For business cards, the QR needs at least 0.1 inch of space from the trim edge.

Batch verification: for bulk jobs (500+ cards each with a unique QR), ask if the shop will scan-verify a sample of the production run before shipping. Many shops will scan-test 10 cards from a 500-card run as a QA step. This catches print errors before they ship to your office.

Static QRs are the default for print — free, permanent, no vendor dependency. Dynamic codes earn their monthly cost in three specific cases.

Case 1: campaign tracking. If you print 5,000 direct-mail flyers across three different zip-code clusters and want to know which cluster converted best, you need per-asset dynamic QRs. Each cluster gets its own dynamic code; the scan analytics tell you the conversion difference. Without dynamic codes, YouTube Analytics / Google Analytics can't distinguish them.

Case 2: post-print URL changes. Product packaging printed today may need to point at a new product page in six months when the catalog restructures. Dynamic QRs let you update the destination without reprinting the inventory.

Case 3: A/B testing landing pages. Print two batches with the same QR but A/B tested landing pages. Dynamic codes let you measure which page converts better, then lock in the winner across the next print run.

The cost-benefit math: EZQR Lite at $5/mo handles 25 dynamic codes. For a 5,000-code campaign you'd need Max ($20/mo) for unlimited dynamic codes. Annual cost: $240. Worth it if the campaign generates more than $240 in measurable lift over a year — usually trivially true for any campaign of meaningful scale.

The trap: subscriptions that deactivate codes when you cancel. If you spin up a dynamic campaign for a one-time print run and then cancel, every printed code dies. Use vendors with permanent cancellation policy — EZQR and QR Tiger keep codes alive after cancel; Flowcode deactivates 30 days after.