One scan and your details are in their phone, spelled right.
You hand over a card, the other person means to type your number in later, and later never arrives. A vCard code carries your name, phone, email and company inside the pattern, so a scan opens a contact preview and one tap saves it, spelled the way you spelled it.
Tip: Ctrl+C or “Right click\Copy”
Displaying the logo on the QR code may take some time. Just wait for it to load.
When some colors are combined on the QR code, it may not work correctly. Don’t
forget to check before posting!
A vCard code holds a small text record, the same format your phone already understands when somebody emails you a contact. Name, phone, mobile, email, company, job title, website, fax and a postal address, each on its own line inside the code. The phone recognises the format, shows a contact preview and waits for a tap on save, with no page load anywhere in the process, which is why it behaves the same on a plane as it does in the office. If the version selector means nothing to you, pick 3.0. Version 2.1 is ancient and 4.0 is still refused by a few address books.
A vCard code cannot be edited once it is printed, and it cannot be counted. Change job, change number, and every card in circulation is quietly wrong. It holds no photograph and no social profile, only the fields you filled in. On top of that, the ordinary print failures apply: keep the four-module quiet zone around the pattern rather than cropping to the black, keep it dark on a light background because inverted codes fail on older readers, and use Q or H error correction if you drop a logo in the middle. Take the SVG or EPS to the printer, since a 300 px PNG stretched across a card edge will show soft edges that a scanner reads as noise. Test the proof on somebody else's phone, not the one you designed it on.
Every field you fill adds characters, and more characters mean a finer grid of squares in the same patch of card. Name, one phone number, an email and a company sits near 120 characters and prints cleanly at 2 cm. Add a six-word job title, a website, a fax number and a four-line postal address, and you are past 300 characters: the grid tightens, and at 2 cm on uncoated stock the ink starts filling the gaps between modules. The card still looks right to you on screen. It fails for the person holding it under a hotel bar light.
So keep one phone number rather than three. Use a job title of one or two words, or leave it out. Drop the street address, because nobody posts anything any more and a map app will find the office from the company name. If every field really has to stay, print at 2.5 cm or larger and accept the space it takes. Then scan your own proof from about 20 cm before the run goes ahead.
Two different things get called a digital business card. This one puts the details inside the pattern: no signal needed, still working in five years, and nobody can change what it says or count who scanned it. The other kind is a code pointing at a profile page, which you can edit after printing and which dies the day that page moves or the hosting lapses. If your title and number will change, print a code that points at a page you can edit and accept the dependency. If they will not change, the contact record inside the code is the more durable of the two. For a card that only has to open a blank email to you, an email code holds a fraction of the characters and prints far smaller.
No. The contact record is written into the pattern itself, so the phone reads it from the ink and shows a save prompt with aeroplane mode on. That is the main practical difference from a code that points at an online profile, which needs a connection every single time.
Not on this type. The details are inside the pattern, so editing them means generating a new code and reprinting. If your details move around, use the editable link code instead, where you can repoint the destination, and put a profile page behind it.
Choose 3.0 unless you have a reason not to. It is the version nearly every phone and address book reads without argument. Version 2.1 is older than most of the handsets it would run on, and 4.0 is correct but still unevenly supported, which shows up as missing fields rather than a failed scan.
About 2 cm for a short record with four or five fields, read at arm's length. The rule of thumb is scanning distance divided by ten. Below 2 cm it stops being dependable, and a long record with an address needs 2.5 cm or more to stay readable.
No. The code carries the text fields on the form and nothing else, so no photograph and no social handles. A photo would push the record into thousands of characters and make a grid too dense for a business card. Put a social link on a separate code if you need one.
No, and nothing here can tell you. The data never leaves the paper, so there is no request to log. Counting exists only on the editable link code, which routes through a redirect we host and counts the scans for you.
