You add a QR code to your email signature, send it out to four hundred people, and half of them see a grey box with a broken image icon. Nothing you did was wrong. The guide you followed skipped the step that matters most.
Email clients block remote images by default. If your code lives on a server and gets pulled in when the message opens, it will not appear for a large chunk of your recipients. Embedding it fixes that.
Why your signature image is blocked by email clients
Most signature guides tell you to upload the image somewhere and link to it. That is the version that fails.
A linked image is a request back to a server, which tells the sender that you opened the message and roughly where you were. Clients block that by default to protect the reader, and Outlook, Apple Mail and Gmail all do it in some form.
The alternative is embedding: the image travels inside the message. It always displays, needs no server, and costs a few kilobytes per email. For a small code that is a trade worth making every time.
Outlook embeds automatically when you insert a picture into a signature rather than pasting a link. Gmail is fussier and often uploads to its own storage instead, which is generally fine.
How to embed a vcard in your Outlook signature
Generate the code first. Keep it to name, mobile, email and company, because a dense code in a small image is the other way this fails.
- Export a PNG. Not an SVG, which most email clients refuse outright.
- Open signature settings and place the cursor where the code belongs.
- Insert it as a picture, at the size you actually want it displayed.
- Wrap it in a link to your website, so phone readers have a route too.
- Send a test to an account on a different provider and open it on a phone.
Insert at the right size rather than dropping in a large image and dragging the corner. Outlook keeps the original and scales it on display, and the re-rendering blurs fine detail enough to break a dense code.
How to size a signature qr code so it still scans
Between 120 and 150 pixels square, displayed. Export at roughly double that so it stays crisp on a high-resolution screen.
Below 100 pixels, phone cameras start failing on anything but the sparsest code. Above 200, it takes over a signature nobody wanted to read in the first place.
Density decides the floor. A code carrying 200 bytes survives being small; one carrying 1,500 bytes needs noticeably more room. The size meter on our vCard QR code generator shows where you are before you export.
The honest case against bothering
We would rather say this than sell the idea. A QR code in an email signature is less useful than it looks.
Think about who reads your email. A large share are on a phone, and they cannot scan the screen they are reading. For them the code is decoration.
It earns its place in one situation: someone at a laptop with a phone in reach who wants your details on that phone. That is a real scenario and a narrow one.
So keep your typed contact details in the signature. The code is a shortcut for some readers, never a replacement for text that everyone can read and copy.
What to put in the code, and what to leave out
Work number, work email, name and company. That is the whole list.
Leave out the home address. A signature reaches everyone you email plus everyone they forward to, and a postal address in a scannable code is a strange thing to hand a stranger.
Leave the photo out too, for a reason that is not about privacy: it will not fit. A card with a headshot runs past 40,000 bytes against a ceiling under 3,000, and we went through the numbers in why a vCard QR code will not scan.
Static codes, and why we do not offer the other kind
A dynamic code holds a short link to a server that stores your details and redirects. The pitch is that you can change your details without changing the code.
In a signature that argument collapses. Updating your signature is already trivial, and every future email carries the new code the moment you save it.
What you would be adding is a dependency and a log: a service that has to keep running, and a record of every person who scanned. Neither buys you anything here.
Test before you roll it out
Send to a different provider than your own. A Gmail signature that looks perfect inside Gmail can arrive quite differently in Outlook.
Open the test on a phone and a laptop. Check that the image appears without clicking anything, which is the whole point of embedding.
Then scan the printed-out or displayed code with a second phone and read what comes back. Confirm the contact your recipients will actually save, and if you also plan to send the file itself, build it with the vcard generator and check the result before it goes out — the steps for getting a contact file onto a phone cover what happens at the other end.
