How to Use QR Codes on Business Cards

A business card QR has a strange constraint that other deployments do not: the code only matters in the four-second window between handoff and the moment the other person puts the card in a pocket. Get that moment wrong and the card joins the dead pile in someone’s desk drawer, never to be touched again.

What the code encodes shapes the entire interaction

Four destination types dominate, and each has a different fit. A vCardA standard text format for contact information (name, email, phone, address, organization) defined by RFC 6350. Read more → encoded directly into the QR opens a native “add to contacts” sheet on most modern phones, which is the fastest possible path to a saved contact. The downside is data length. A complete vCard with name, title, two phone numbers, two emails, an address, and a URL pushes a QR to VersionThe size of a QR codeA 2D matrix barcode that encodes data in a square grid of black and white modules. Read more →, numbered 1 (21×21 modules) through 40 (177×177). Higher versions store more data but require more printed space. Read more → 6 or higher, which means more modulesA single black or white square in the QR grid. The number of modules per side scales with the QR version, from 21×21 modules for version 1 up to 177×177 for version 40. Read more → and a physically larger code than a 2.5 cm card can comfortably hold. Stripping the vCard to name, primary email, primary phone, and one URL keeps the code at Version 2 or 3, which fits a 2 cm square cleanly. Use the URL-to-SVG generator for vector output if you want crisp module edges at small print sizes; raster from the URL-to-PNG flow is fine for prints above 2.5 cm.

A LinkedIn profile URL is the second common choice. The advantage is content depth; the recipient lands on a fully built professional page they can act on later. The disadvantage is that LinkedIn URLs often hit Version 4 or 5 unless you have a custom vanity slug, and the recipient still has to log in or sign up to take any action beyond viewing. A personal landing page on your own domain is the third option, and it is the most flexible. You control what appears, you can update it without reprinting cards, and you can add a single clear call to action like “book a meeting” or “send me an email.” The fourth option is a direct action: an email-to-PNG QR, phone-to-PNG QR, or SMS-to-PNG QR that opens a pre-composed message. These work well for sales and recruiting roles where the desired next step is obvious.

The handoff moment is everything

Networking events have a predictable physics. Two people meet at a booth, a coffee station, or in a hallway between sessions. They talk for two to ten minutes, exchange cards, and move on. The card that gets scanned right then converts at maybe 40 percent into a saved contact or follow-up action. The card that gets pocketed and looked at later converts at under 5 percent. Anything that adds friction to the in-the-moment scan kills the pickup rate.

Three things drive in-moment scanning. First, the QR has to be visually obvious from a quick glance at the card; a 1 cm code tucked into a corner gets missed. Second, the code needs to scan from a comfortable holding distance. The recipient is holding the card in one hand and a phone in the other, usually 25 to 35 cm apart. A 2 cm code at Version 2 scans cleanly from that distance under decent lighting; smaller codes force the recipient to bring card and phone close together, which feels awkward in conversation. Third, the destination has to be obviously useful within two seconds of landing. A LinkedIn page works because the recipient already understands what LinkedIn is. A custom landing page works only if the page loads fast and shows something immediately actionable.

Conference lighting is the silent killer. Trade-show floors are typically lit with a mix of overhead fluorescents and booth-level spots, and color rendering is uneven across a single venue. A code printed in dark navy on a cream card photographs beautifully but fails under tungsten spots that shift the cream warmer and crush the contrast ratio. Stick to true black on near-white backgrounds for any card you intend to deploy at events. The QR design best practices explain the contrast math if a designer pushes back on the safe palette.

Single-purpose versus multi-purpose: legibility wins

A single QR with one clear action outperforms a card with three QRs offering different actions, every time. The reason is cognitive load in the four-second window. A recipient looking at three small codes labeled “vCard,” “LinkedIn,” and “Calendly” will scan none of them, because choosing takes more attention than they want to spend on a stranger’s card. A single code labeled “scan to connect” gets scanned because the action is obvious.

The multi-purpose temptation usually comes from wanting to give the recipient options. The fix is to build those options into the destination, not the print. A single QR pointing to a personal landing page can offer “save my contact,” “book a meeting,” and “view portfolio” as three buttons on the page itself. The recipient scans once, sees the menu of choices, picks one. This pattern sustains role changes and company moves cleanly: when your title changes, you update the landing page, not the card. The event check-in playbook covers a related pattern for codes worn on conference badges, and the WhatsApp leads playbook shows how to wire an instant-message handoff for sales contexts.

Aesthetic placement without compromising scan reliability

The card design tension is real. A QR is geometrically obtrusive against a clean typographic layout, and most designers want to hide it. The compromise that holds up across hundreds of card designs: put the QR on the back of the card, at one of the lower corners, with at least 4 mm of quiet zoneThe unprinted margin of at least four modules' width that must surround every QR code. Read more → around it. The quiet zone is non-negotiable; reducing it to 2 mm to fit a slogan adjacent to the code drops scan rates noticeably under the autofocus behavior of mid-range phones. The front of the card stays clean for name, title, company, and contact essentials.

Keeping human-readable contact info on the card alongside the QR is worth the printing cost. Not every recipient will scan in the moment, and a card with only a QR is useless to anyone whose phone battery is dead, who is wearing gloves at an outdoor event, or who simply prefers to type the name into a CRM later. Print the email and phone in legible 8 to 10 point type. The QR adds an option for the people who want it; the typed contact info preserves the option for everyone else. For broader execution context, the overview of business QR use cases extends the same principle across other touchpoints.

Updating destinations without reprinting cards

The longest-lived business card sits in someone’s wallet for two years. The longest-lived job title rarely lasts that long. If your QR encodes a vCard directly, every job change means a reprint and a card-handout exercise that is logistically painful. If your QR encodes a stable URL on your own domain that redirects to whatever profile page is current, you reprint never (or only when the visual design needs refreshing) and the destination updates instantly when you change roles.

This is the strongest argument for a personal-domain redirect over a vCard or LinkedIn URL. You own the redirect target. When you change companies, the cards in circulation still work; the URL points to your new contact info within minutes. The trade-off is that you need to maintain the domain and the redirect, which adds a small annual cost (usually under $20). For anyone who hands out more than a few hundred cards a year, the calculation is obvious. The static versus dynamic QR comparison covers the broader trade-offs, the business card QR vs Linktree comparison goes deeper on the link-aggregator alternative, and the event organizer playbook shows how to scale the same approach across a team’s worth of cards.