Skip to content
English

For professionals and sales teams

Business card QR code generator

Handing someone a card transfers paper; it does not transfer data. The gap between the two shows up a week later, when the person who wanted to call you is typing your number off a card balanced on their knee, transposing two digits. A vCard square closes that gap: one scan and your name, title, organisation, number, email and website land in their address book as a saved contact, spelled the way you spelled them. The studio above is preset with a sample card — replace the fields with your own details and watch the pattern rebuild as you type. Nothing you enter leaves this page, which matters more here than on most tools, since what you are typing is precisely the personal data you would not paste into a random website.

Leave blank to keep the code smaller and easier to print small.

Include the country code so the number works when scanned abroad.

QR code options
Appearance

Generated on your device. Nothing you type is sent anywhere.

This is the vCard QR code generator with its fields preset for professionals and sales teams — the tool page has worked examples, pitfalls and the full format detail.

Scenarios

Where it earns its place

  • The conference stack that survives the flight home

    Trade-show cards die in hotel-room bins because transcribing them is a chore nobody does on a Tuesday after travel. A card whose corner scans straight into contacts gets captured in the aisle, while the conversation is still warm. You will still hand over paper — the ritual matters — but the data now travels separately from the object.

  • A team's cards that stay consistent

    Sales teams accumulate inconsistency: one rep abbreviates the company name, another uses a personal mobile, a third has the old office address. Generating each person's square from the same field template enforces one format across the whole team, and because the tool is free and account-less, onboarding a new hire is five minutes with no seat licence.

  • Email signatures and slide decks

    The same vCard square works anywhere a phone camera can see a screen: the closing slide of a pitch, a webinar outro, the corner of a PDF proposal. On screens the scan is trivially easy — perfect contrast, no print distortion — so this is also the setting where a dense, many-field card is safest to use.

  • The card redesign that stops mattering

    Rebrands orphan drawers full of stationery. When the visual identity changes, the square is the one element that migrates untouched — its contents are your details, not your colour scheme. Some professionals go further and print minimal cards that are little more than a name and the square, which sidesteps the redesign treadmill entirely.

Workflow

From setup to first scan

  1. Fill in only the fields you would say out loud

    Every field you add makes the pattern denser and harder to scan at card size. Name, one number, one email, one website is the sweet spot. Leave out the fax number nobody has dialled since 2009.

  2. Watch the density as you type

    The preview rebuilds with every keystroke, and you can see the grid tighten as the payload grows. If the modules start looking like fine sandpaper, cut a field — that visual check is a genuine predictor of print scannability.

  3. Set error correction with the print process in mind

    Cards get scuffed in wallets and pockets. A step up in correction level buys tolerance for wear, at the cost of a slightly denser grid — worth it on paper, unnecessary for a version that only lives in slides.

  4. Export SVG for the print run

    Send your printer the SVG alongside the artwork so the square is placed as vector geometry, not a pasted screenshot. Ask them not to recolour it; a dark-on-light square is the safe default every phone reads.

  5. Proof-scan the actual printed card

    Scan the printer's proof, not your monitor. Check that the saved contact opens with every field intact and correctly spelled — this is the last moment a typo in your own phone number is cheap to fix.

Deployment

Printing, placement and materials

On an 85 × 55 mm card, give the square at least 18 mm of side length and respect its quiet margin — the white breathing room around the grid is part of the format, and cramming a logo against it is the most common reason card codes fail. Back of the card is the conventional home; if it must share the front, anchor it in a corner away from the fold of a cardholder. Uncoated and matte stocks scan more reliably than gloss laminate, and textured letterpress papers deserve a proof-scan before the full run, because deep impression distorts fine modules. Foil, spot-UV and metallic inks belong anywhere except over the code. If your details are long — double-barrelled organisation names, international numbers — prefer trimming fields over shrinking modules: an incomplete contact that scans beats a complete one that does not. And print a small human-readable email under the square; the one person without a working camera still needs a way to reach you.

Common questions

What does scanning the card actually put in someone's phone?

A pre-filled new-contact screen: name, organisation, title, number, email and website already in their fields, waiting for the person to tap save. The payload is a vCard — the same format address books have exchanged for decades — so nothing needs installing and no app is involved beyond the camera. The person always sees what will be saved before it is saved; the format cannot silently write to their contacts.

If my job title changes, do the printed cards still work?

They keep scanning, but they save the old title — a static vCard carries its data inside the pattern, so print is a snapshot. This cuts both ways: nothing can break or expire, and nothing can update. Order card runs in modest quantities, and treat a role change like a reprint trigger the way an address change always was. For a version you can update freely, the square in your email signature costs nothing to regenerate.

Why does my card's square look so much busier than a website code?

Because it carries perhaps ten times the characters. A short link is thirty-odd characters; a filled contact card runs to several hundred, and the grid must add modules to hold them. This is why field discipline matters at card scale — every optional line you include is paid for in module size. The website-only version of you is a much simpler square; the full CV of you may not scan from a wallet.

Can the whole team use this without buying licences?

Yes. There is no account, no seat count and no billing relationship — each person opens the page, enters their details and downloads their files. For consistency, circulate a short internal note fixing the format questions once: company name spelled which way, direct line or switchboard, which website address. The tool enforces the technical format; the note enforces the editorial one.

Is it safe to type my personal details into this page?

The details never leave your device — the pattern is assembled by JavaScript running in your own browser, and you can watch the network panel stay silent while you type. That is a stronger privacy position than most card-generator sites, which build the code on their server and therefore see every name and number entered. Here there is no server involved in the generation at all.

Should I use a link to my details instead of embedding them?

A link makes a simpler square and lets you update details after printing, but it adds a dependency: the page must stay online, and the person ends up on a website rather than in their address book. The embedded vCard works offline, in airplane mode, in a basement conference hall. For cards, embedded wins; for a signature block that you can edit weekly anyway, either is fine.

Read before you print

Related use cases

Browsing more broadly? The Contact QR codes hub groups every generator this kind of work leans on.