Email signature QR codes — the door at the bottom

An email signature QR code is the small square at the bottom of every message you send that turns a passive sign-off into a scannable hook — a Calendly slot, a vCard, a portfolio, a Google review form, a press kit, whichever single next step the relationship is asking for. Almost no one does it on purpose. The default signature is two lines of name and title, maybe a phone number, occasionally a banner. A 100-pixel QR added to that block changes the economics of every email you send, because the person reading you on a laptop can scan it on the phone in their other hand without typing a thing.

This post covers why an email signature QR code converts in the specific moments where a text link doesn't, the size and placement rules that decide whether mail clients strip it or render it, what to point the QR at depending on what you do for a living, and how to track which emails actually generated calls. The pattern is older than most of the people using it — Microsoft Outlook 2003 already supported image signatures — but the use case is genuinely modern, because the laptop-screen-to-phone-camera scan that makes the QR work didn't exist as a habit until smartphones were everywhere.

The signature QR works because the screen and the camera are different devices#

Most marketing links assume the same device reads the email and clicks the link. The recipient gets your message on their phone, taps the link, the phone's browser opens. Fine. But a large share of business email is read on a laptop or desktop — the inbox is open in a tab, the recipient is at a desk, the device with the camera is in their pocket or face down next to the trackpad. A text link in that context is friction. They have to copy, paste into a phone, or remember to follow up later. They almost never do.

The QR is a bridge between the two devices. The laptop renders the code, the phone scans it, the destination opens on the device the recipient was going to use anyway for whatever you're asking them to do — a phone call, a calendar booking, saving a contact card. The conversion happens because the QR makes a two-device workflow feel like one tap, and the two-device workflow is what business reality actually looks like.

Three other reasons the signature surface specifically pays out.

Volume. A salesperson sends 60-120 emails a day. A founder sends 30-50. A consultant sends 80. Multiply by working days and the signature gets ~15,000-30,000 impressions a year per individual. No paid surface is that cheap. Half the people on your team already have a signature; adding a QR to the same block is a one-time edit that compounds for the rest of the year.

Intent. Email is a thinking surface. The recipient is reading something you wrote that's relevant enough they opened your message. Whatever the QR points at is being offered in the most context-rich moment in your business relationship — they've just read your name, your company, what you do, and one specific reason to engage. The scan is on-topic by construction.

Permission. A signature QR is not interruptive. It's there if the reader wants it, invisible if they don't. Banners, popups, retargeting ads all push; the signature pulls. Conversion-quality on that asymmetry is consistently higher than on equivalent paid traffic.

What the QR should point at — by role#

The QR's job is to be the single shortest path from "this email made me curious" to "I did the thing you wanted me to do." That destination changes by role.

Sales and business development — Calendly, Cal.com, HubSpot meeting link, SavvyCal. The whole reason a salesperson is sending the email is that they want a call; the QR removes the meeting-link copy-paste and the "let's find a time" back-and-forth. Use a dynamic short link so you can repoint it when you change meeting tools, change duration, or rotate between reps.

Support and customer success — the help centre's mobile-optimised search, a ticket-submission form, or a "what's broken" feedback page. Support emails are read in moments of frustration; the goal is to point the recipient at the answer they need rather than starting another email chain. The QR is most useful when the user's question is "where do I find the docs that explain this," which the phone-camera flow shortens to one scan.

Recruiters — LinkedIn profile, careers landing page, or a vCard that the candidate can save. Recruiting emails often land in personal inboxes read on phones, so the device-bridge value of the QR is smaller, but the vCard pattern is still useful because candidates routinely want to save a recruiter's contact for later without typing it into a phone manually. The vCard QR codes — the modern business card post covers the format details.

Freelancers — portfolio site, a single best case study, a tip-jar or invoicing page when relevant. Freelance emails are often read on laptops by clients deciding whether to bring you in; the QR points at the version of you that closes the loop without making them search for it. Pair with a visible URL so the QR doesn't replace the link — it accompanies it.

Executives, founders, partners — press kit, one-page company overview, investor deck (gated where needed), or a vCard during conference season. The exec signature is the highest-impact version of the pattern because every email goes to someone potentially valuable. Rotate the destination quarterly to match what you're actively trying to surface — a launch, a fundraise, a hiring push.

If you're not sure what to point yours at, the widget below walks the most common pairings and saves your choice so the answer's still there when you come back.

The picker isn't authoritative — your situation might pair differently — but the role-to-destination mapping reflects what works on actual signature blocks across hundreds of campaigns we've watched run.

Size and placement — the part that quietly breaks signatures#

A signature QR that mail clients strip, render at the wrong size, or push below the fold isn't doing any work. Three rules cover the failure modes.

Size: aim for 120 × 120 pixels. Below 100 pixels the code is too small for most laptop screens to render with enough sharpness for a phone camera to lock on at a casual 30-40 cm distance. Above 150 pixels and the signature block visually dominates the email — the QR becomes the message instead of accompanying it. 120 is the sweet spot for laptop reading.

Placement: bottom-right of the signature, not centred. Eye-tracking studies on email signatures consistently show readers scan left-to-right and top-to-bottom; the bottom-right corner is the natural "end of message" landing point. A QR there reads as "here's what to do next" without interrupting the message content. Centered QRs look like banners — and banners get ignored.

File format: PNG, not SVG, and not a remote URL. Most mail clients strip SVG entirely for security reasons. Remote URL images (pointing to a hosted PNG) get cached, sometimes blocked by privacy-protecting clients, and load late or not at all on poor connections. Embed the PNG inline — base64 in the HTML signature — so the QR travels with the message and renders even when external images are blocked. Most signature managers (Exclaimer, Gimmio, WiseStamp, Newoldstamp) handle this correctly; the manual export-from-Outlook path often doesn't.

Two more placement details worth holding on to. First, don't put two QRs in the same signature — they crowd each other and confuse the reader about which one is the point. If you have multiple things to offer, point one QR at a hub page that lists them. Second, the visible URL below or beside the QR isn't optional. About 8-12% of recipients read your email on a single device with no separate camera to hand — they need a clickable fallback. The QR is for the laptop-plus-phone case; the URL handles everything else.

Will Gmail strip the QR — and the rest of the deliverability question#

Image-stripping is the question every signature manager gets asked first. The honest answer: well-formed signature images don't get stripped by any modern client, but several specific mistakes get them flagged, downgraded, or replaced with a placeholder.

Gmail, Outlook (web and desktop), Apple Mail, and Yahoo Mail all render inline base64-embedded PNG images by default. Gmail caches the image through Google's proxy on inbound delivery — which is what makes the proxy-routing on the tracking links in email — what you can know walkthrough behave the way it does. The cached version is what the recipient actually sees, but it's still a PNG of your QR, still scannable, still doing its job.

The strip cases that bite are when the QR is hosted remotely on an HTTP (not HTTPS) URL, when the alt text is missing or too long, when the surrounding HTML tries to use deprecated tags like <font> for the signature block, when the message lacks DKIM and SPF authentication (some clients downgrade unauthenticated mail to plain text), and when the QR is wrapped in a tracking pixel from a third-party signature tool — overzealous spam filters sometimes flag the bundle. Test on Gmail, Outlook, and Apple Mail with both image-loading on and off before rolling out across a team.

Mailing-list software is a different conversation. Your individual outbound from you@company.com is fine. A bulk newsletter through Mailchimp or ConvertKit using the same signature gets routed through their image-rewriting pipeline, which can re-encode the PNG at lower quality. For broadcast email, generate the QR specifically for that send rather than reusing the signature-block PNG.

Tracking which emails generated calls#

The whole point of putting a QR at the bottom of every email is the chance that one of them earns a meeting. Without tracking, you have no idea which one. With basic tracking, you can tell which email type, which recipient list, sometimes which individual conversation got the scan.

The minimum useful setup is a branded short link with trust and click tracking baked in, encoded into the QR rather than the destination URL directly. Every scan logs a row. Three patterns from there.

Per-role tracking. One QR design per role on the team — sales links use one slug, support uses another, exec another. Compare scan rates across roles to learn which signature blocks are doing the work. If support signatures scan twice as often as sales signatures, your support team is sending into more curious inboxes — useful prioritisation data.

Per-campaign UTMs. Layer utm_source=email&utm_medium=signature&utm_campaign=<campaign> onto the destination URL so when the recipient hits your site or Calendly, the analytics there see the signature origin separately from cold-link traffic, social, paid. The combination of slug-level scan logs and UTM-level destination logs gives you a two-sided view of the funnel.

Per-recipient tracking, carefully. A small share of senders mint unique slugs per recipient — every email contains a slightly different signature QR that ties scans back to a specific inbox. That's the how to track who clicks your short link pattern applied to signatures. Useful for high-touch sales where one named scan changes the next conversation. Less useful for broadcast, where it crosses into territory recipients aren't expecting. The trade-off is honest — disclose, or don't do it.

What the scan log actually carries — country, device class, OS family, timestamp, slug, UTM bundle — is described field-by-field in what every scan in your QR code analytics tells you, and the same fields apply here. The signature-specific signal worth watching is the time-of-scan-to-time-of-send delta: scans that fire within minutes of you sending are the recipient acting immediately, and that's a different conversation than a scan three days later from a forwarded thread.

A connected pattern worth knowing: if your role is a freelancer or solo operator collecting reviews, swap the signature QR to a Google review link encoded as a QR after a successful project for a month. Same surface, different ask, much higher review-conversion rate than a follow-up email asking for the same thing.

Five small mistakes that kill a signature QR#

A signature QR that's wrong scans into nothing useful. The five most common failures.

Pointing at a heavy desktop landing page. The whole conversion path runs on a phone. A QR that opens a 4 MB hero image on a phone-hostile site is a wasted scan. Test the destination on a mid-range Android over a cellular connection before printing the QR into 60 emails a day.

Static QR with a destination that changes. A static QR bakes the URL into the bitmap. Change the destination — your Calendly URL, your portfolio domain — and every previously-sent email becomes a 404. Use dynamic short links for anything in a signature.

No visible URL beside the QR. Eight to twelve percent of recipients can't scan because they're on a phone reading the email and can't aim a camera at themselves. The visible URL line handles that case.

Logo overlay too big. Tempting to drop a centred company logo on the signature QR. Past 20% logo coverage at level Q error correction, the QR stops scanning reliably. Keep the logo under 18% if you absolutely must brand the code, or skip the overlay entirely — a small QR with no logo scans more reliably than a small QR with a centred mark.

One QR per person, never updated. People change roles, change calendars, change companies. A signature QR set up two years ago and never revisited is pointing at a Calendly the salesperson no longer uses. Audit every six months — the signature manager or a quick scan-test from your own phone catches the dead destinations.

Where the signature QR doesn't earn its place#

A few cases where the signature QR adds noise without adding value.

One-off threads with people who already know you. If you're emailing a vendor you've worked with for three years, the signature QR is decoration. They're not scanning to find out who you are.

Internal company mail. Your colleagues don't need to scan to reach your Calendly. They have your Slack, your phone, your internal directory. Save the signature QR for external mail.

Highly regulated industries. Finance, healthcare, and legal email is often archived, compliance-reviewed, and subject to retention rules that don't play well with dynamic-content links. Check with your compliance team before adding tracked QRs to outbound mail in those settings.

Mass-broadcast newsletters. A newsletter sent through Mailchimp or Beehiiv already has its own CTAs, its own tracking, and a recipient population at a different intent level than direct one-to-one mail. The signature QR pattern doesn't transfer cleanly. The tracking links in email post covers broadcast-side measurement separately.

For everything else — direct B2B email, outbound sales, recruiter outreach, support tickets, freelancer pitches, founder one-on-ones — the signature QR is the highest-return zero-effort marketing surface most teams aren't using.

Where to build one and what to know about the underlying system#

Build the QR once with the free QR code generator, point it at a short link you control, embed the resulting PNG into the signature blocks across your team. The QR codes platform docs cover the design and dynamic-link details; the short-links docs cover the redirect side and the per-link analytics; the analytics docs cover what the scan dashboard shows for each link.

Two extra notes worth holding on to. First, the QR design and the destination are separate concerns — the same QR can stay in the signature for years while you change what it points at quarterly. That's the entire reason dynamic short links exist as a category. Second, branded short links (yourdomain.com/something) earn higher scan rates than generic shortener URLs encoded into the QR, because trust travels with the visible domain even before the scan resolves. The trust effect of branded short links on click-through walks the click data behind that — same effect applies to scans.