Every part of the tool is built around one goal: getting a working, saveable contact code with as little effort as possible.

Two formats: switch between vCard 3.0 for the full set of fields and MeCard for a short, broadly compatible code. The preview and payload update the moment you change the format.

Rich contact fields: first and last name, organization, job title, a mobile number, a work number, email, website, a structured postal address and a free-text note.

Live contact card and QR preview: a mock-up of the saved contact sits above the code, so you can see exactly how the name, title and contact lines will read before you print anything.

Encoded data panel: the exact vCard or MeCard string is shown in a read-only box. Check it, copy it, or use it to diagnose a scan that will not save - special characters are escaped for you.

Output controls: choose an image size from 128 to 2048 pixels, an error-correction level, a quiet-zone border, a module shape and foreground and background colours.

Four exports: download a high-resolution PNG for screens and quick sharing, a scalable SVG for print, a .vcf file that imports straight into any address book, or print a ready-made contact card.

Helpful warnings: the tool asks for at least a name or a phone number, flags low-contrast colours, and notes when MeCard will leave out a field it cannot store.

If the details are too long to fit at the selected error-correction level, the tool tells you instead of producing a code that will not scan.

Generating a code takes less than a minute:

1. Choose a format. Pick vCard 3.0 for the richest contact card, or MeCard for the shortest code and the broadest scanner support.
2. Fill in your details. Enter at least a name or a phone number, then add any of the other fields - organization, title, a second phone number, email, website, address and note.
3. Check the live preview. The contact card and the QR code redraw as you type, so you can spot a typo before it reaches a print run.
4. Verify the encoded data. The read-only box shows the exact vCard or MeCard string that will be stored in the code.
5. Adjust the look. Set the size, error-correction level, quiet zone, module shape and colours for the surface you will use.
6. Export. Download PNG or SVG for the code, download a .vcf to import the contact yourself, or print the contact card for a desk or counter.
7. Test before you print in bulk. Scan the result with an iPhone and an Android phone and confirm the details save correctly, then send it to print.

Both formats store the same kind of information, but they trade richness against size. A shorter payload makes a less dense code, and a less dense code scans more easily when it is printed small or scanned by an older device.

vCard 3.0 (recommended for most people): the full standard used by contact apps, email clients and .vcf files. It has dedicated fields for a job title, two labelled phone numbers, a structured postal address and a note, so nothing is squeezed together. It is the right choice for business cards, resumes, badges and any contact you want to look complete. Its only drawback is a longer payload, which produces a slightly denser pattern.

MeCard (best for compactness and compatibility): a lightweight format that phone cameras understand and that many older Android scanners handle well. It stores the name, phones, email, website, organization, address and note, but it has no dedicated job-title field, so the title is left out (put it in the note if it matters). MeCard codes are noticeably simpler, which helps when the code has to be printed very small.

If you are not sure, start with vCard 3.0 and test the scan. Switch to MeCard only if you need a smaller or more forgiving code.

First and last name: stored as a single full name plus the separate parts, so apps can sort the contact either way. At least a name or a phone number is required. Example: Elena and Marchetti.

Organization and job title: the company and the role, shown on the contact card under the name. Example: Forge & Flint Ceramics and Studio Manager.

Mobile and work phone: two numbers with their own labels, so the saved contact can tell them apart. Example: a mobile of +1 503 555 0178 and a work line of +1 503 555 0142.

Email and website: the address the phone opens a new message to, and the link it opens in the browser. Example: elena.marchetti@forgeandflint.example and https://forgeandflint.example.

Postal address: entered as separate street, city, region, postal code and country fields so each part is stored in the right slot, not as one run-on line. Example: 412 Alder Street, Portland, OR, 97205, United States.

Note: a short free-text line for anything the fixed fields cannot hold - opening hours, a preferred contact time, a second role or a department. Example: Studio open Tue-Sat, 10am-6pm..

A vCard QR code is not proprietary or magic. It encodes the same plain text that a .vcf file contains, one field per line, starting with BEGIN:VCARD and ending with END:VCARD. The card for the example above looks like this:

BEGIN:VCARD
VERSION:3.0
N:Marchetti;Elena;;;
FN:Elena Marchetti
ORG:Forge & Flint Ceramics
TITLE:Studio Manager
TEL;TYPE=CELL:+1 503 555 0178
TEL;TYPE=WORK:+1 503 555 0142
EMAIL:elena.marchetti@forgeandflint.example
URL:https://forgeandflint.example
ADR;TYPE=WORK:;;412 Alder Street;Portland;OR;97205;United States
NOTE:Studio open Tue-Sat, 10am-6pm.
END:VCARD

N: the structured name, written as last name, first name and three empty slots for middle names, prefixes and suffixes.

FN: the display name shown at the top of the saved contact.

TEL;TYPE=CELL and TEL;TYPE=WORK: the two phone numbers, each with a label the phone understands.

ADR;TYPE=WORK: the address in its fixed seven-part order. The two leading semicolons are the empty post-office-box and extended-address slots.

MeCard uses the same idea in a single compact line. The same contact, minus the job title, becomes:

MECARD:N:Marchetti,Elena;ORG:Forge & Flint Ceramics;TEL:+1 503 555 0178;TEL:+1 503 555 0142;EMAIL:elena.marchetti@forgeandflint.example;URL:https://forgeandflint.example;ADR:412 Alder Street,Portland,OR,97205,United States;NOTE:Studio open Tue-Sat, 10am-6pm.;;

Because commas and semicolons separate the parts of a structured field, and a line break would end the line, they cannot simply appear inside a value. The tool escapes them with a backslash: a note reading Ask for the weekend slot, Tue;Wed only is stored as Ask for the weekend slot\, Tue\;Wed only. MeCard uses the same idea, escaping semicolons inside a value. This is why you should always let the tool build the payload instead of typing one by hand - a single missing backslash is enough to corrupt the contact, and it is the first thing to check if a scan saves the wrong details.

Networking and conferences: put a code on your badge or phone lock screen so a new contact saves your details in one tap. No card to carry, no number to type, and nothing to lose at the bottom of a bag.

Resumes, portfolios and email signatures: add a code that saves your contact to a recruiter's phone while they are still looking at your work. A .vcf download is a useful fallback for anyone reading on a desktop.

Shop counters, salons and trades: a small framed card lets customers save your number and email instead of asking for a card. It is equally handy for a plumber's van, a market stall or a food truck.

Team and staff listings: print a code beside each name in a reception area or on a shift-board so colleagues, suppliers and visitors can save the right person quickly.

Property, vehicles and equipment: attach a code to a for-sale sign, a car window or a loaned tool so an enquiry reaches the person responsible without a search.

Personal sharing: send a single image that carries your mobile, email and address to family or a new neighbour - much easier than typing it all into a text message.

Test before you print in bulk: scan the code with an iPhone and an Android phone and check that every field saves in the right place. Only then order a full print run.

Keep the payload short where you can: a long address and note make a denser code. Leave out fields you do not need, especially on small formats like a business card.

Size and print: for a phone at normal reading distance, keep a printed code at least 2 x 2 cm (0.8 x 0.8 inches). Print at 300 DPI or higher and use the SVG export for design work so the edges stay sharp.

Contrast and quiet zone: keep dark modules on a light background and leave the white border at four modules. Low contrast or a cropped quiet zone are common reasons a code will not scan.

Keep a digital copy: save the PNG or SVG somewhere safe, and keep the .vcf as well, so a lost or damaged card can be reprinted without re-entering your details.

Think about who can scan it: a contact QR code is meant to be shared, but it is still your real phone number and email. Do not add private information to the note, and only put the code where you are happy for anyone nearby to save your details.

The code is not being recognised: make sure the whole code, including the white border, is inside the camera frame, and hold the phone steady. Increase the size, keep strong contrast and switch the module shape back to square if you styled the code heavily.

The phone shows text instead of a contact: a few older scanners do not act on the vCard automatically and simply display the raw BEGIN:VCARD text. This is a scanner limitation, not a broken code - a newer phone or a dedicated QR app will offer to save it.

Some fields are missing: if you chose MeCard, the job title is not stored because the format has no field for it. Switch to vCard 3.0 to include it. On some phones an empty optional field is simply left blank, which is expected.

The details are wrong: open the encoded-data box and compare it with the fields. A QR code is fixed data, so a typo made before generation is printed into the pattern - correct the field and export a fresh code.

The content is too long: a long note plus a full address can push the payload past what fits at a high error-correction level. Shorten the note or lower the error-correction level, then try again.