QR Codes in Marketing Emails: When They Help and When They Don't
By OwnQR · Published · Updated
A QR code in an email makes sense when it transfers a task between devices or when the recipient shows a code on a phone for staff to scan, such as at event check-in. When readers merely want to open a website on the same phone, a normal clickable link is usually simpler. For how symbols encode destinations, see our QR code overview.
This is not merely a matter of aesthetics. Images can be hidden or altered by email clients, the code may be hard to interpret without context, and malicious QR-based messages have made some recipients understandably cautious. A good email campaign should work even when nobody scans the QR. This guide is about placing a QR image inside an email; a QR that opens a pre-addressed email draft uses a mailto: payload instead. For that separate task, see the email QR code tool.
What official guidance says
The U.S. Department of Energy's QR Code Standards and Best Practices advises against putting QR codes on websites, social media and emails, where clicking an ordinary link is generally more straightforward. That is one agency's design guidance, not a universal legal prohibition. Its underlying accessibility and user-effort logic is valuable: do not force a camera interaction where a direct digital link already works.
A narrow exception can be useful. Imagine a conference attendee reading a registration confirmation on a laptop while using a phone to join a venue Wi-Fi page or open a check-in destination. A QR displayed on the laptop can bridge two devices. The important condition is that scanning solves a real cross-device task, rather than being a decorative substitute for a link.
Use this decision sequence:
| Reader situation | Better primary action | QR role |
|---|---|---|
| Email opened on phone; reader needs to open a website on that same device | Clickable link or button | Usually unnecessary |
| Email opened on phone; staff must scan an event pass or coupon from its screen | Displayable pass, plus a text or account-ID fallback | The QR can be the primary scan target for staff |
| Email opened on desktop; action needed on phone | Direct link plus optional QR | Potentially useful |
| Image loading disabled | Readable text link | QR cannot be assumed visible |
| Sensitive sign-in or payment request | Clearly identified official destination | Avoid an unexplained QR as the sole route |
When the email QR is a pass to show someone else
A recipient who reads an event ticket, pickup confirmation or coupon on their phone may show the QR on that screen to a staffed scanner. That is different from asking them to point their own camera at their own email. In this use case, label the QR with the venue and purpose, give the recipient a way to save or reopen the pass, and provide a readable booking or order reference as a fallback. Check that the counter's approved scanner can read the actual display and that the venue has a documented alternative when the image will not load. Increasing screen brightness may help visibility, but it does not replace testing or the venue's access-control rules.
A pass can be sensitive. Avoid exposing account identifiers or customer information in a publicly forwardable QR, and do not infer that merely seeing a symbol proves the holder is authorized to redeem it. No real ticket-redemption or email-client rendering test was conducted for this guide.
A code displayed on a ticket is not, by itself, a proof of identity or a one-time-use guarantee. Anyone who can access the image may be able to reproduce it; a redemption service must decide whether a pass can be reused. See can a QR code be copied? for the difference between a duplicate image and the authorization rules behind it. The venue's own validation workflow remains essential.
How to attribute newsletter resends
If a newsletter is resent, record the original send and resend as separate campaign events before comparing QR visits. Use distinct, documented campaign parameters for each send's QR destination and for each send's clickable fallback; Google's Analytics campaign URL guidance describes the utm_source, utm_medium and utm_campaign parameters used to identify traffic sources. A resend-specific utm_content value can help distinguish links or creative variants within a campaign. Keep a dated mapping of the parameters, send identifiers and intended destination; do not interpret a page visit as a unique reader, a successful pass redemption or proof that the resend caused a conversion. If the original and resent messages use the identical QR URL, destination analytics alone cannot reliably assign their visits to one send. No newsletter resend attribution experiment was conducted for this guide.
Why security teams pay extra attention to QR codes in email
A QR can conceal the destination from casual visual inspection because the address is encoded in an image. Attackers can use that to move a person from an email onto a phone's browser or a fake login page. Microsoft has documented QR-related phishing campaigns; the FBI and FTC have warned about deceptive QR uses more generally.
A legitimate sender should reduce that ambiguity rather than asking users to trust a mystery square. Microsoft's phishing analysis describes QR lures that may use sparse explanatory text, brand impersonation, attachments or redirecting destinations; these patterns are warning signs in context, not proof that every QR redirect is malicious. Place a clear text explanation next to the symbol, show the expected organization and destination, and provide a normal link to the same content. Avoid instructions that urge readers to bypass security warnings. Do not imply that a QR image is inherently safer than a hyperlink or that using a redirect guarantees delivery.
Before sending a campaign: name the sender and destination plainly; use the same expected destination in a visible text link; explain why the recipient would scan rather than click; avoid unexplained redirects and deceptive urgency; and verify that an attachment or image does not impersonate another organization's sign-in. These are practical responses to risk signals described in Microsoft's research, not a claim that following the checklist guarantees inbox delivery.
Build a QR email that still makes sense without images
Use the QR only as an enhancement. The primary content should make sense in a text-only reading order:
- State what the reader can do: “Open your event check-in page.”
- Give a normal, descriptive link to that destination.
- If a second-device scan is relevant, introduce the QR as an optional alternative.
- Give the image meaningful alternative text, such as “QR code opening the event check-in page,” not “image123.” Section508.gov's accessible QR guidance recommends describing the action and providing an adjacent usable link for people unable to scan it.
- Keep the destination consistent between the QR and the visible link.
- Send a small internal test to the email clients your audience actually uses.
A sample copy block might read:
Ready for the event? Open your check-in page. If you're reading this on your computer and want the page on your phone, you can also scan the QR code below.
The sample URL is illustrative, not an OwnQR-hosted event product.
For a fuller review of the QR itself, including a route that does not need the camera, a text alternative, contrast, size and placement, use our accessible QR code checklist.
Image width, margins and dark-mode uncertainty
A QR's modules form a square grid. If a source symbol spans 41 modules including its surrounding quiet zone, a 410-pixel image gives an average of 10 pixels per module before any resizing. That is a simple pixel calculation, not proof that Gmail, Outlook or Apple Mail will preserve every module boundary.
| Symbol width including quiet zone | Example display width | Average pixels per module |
|---|---|---|
| 29 modules (Version 1) | 290 px | 10 |
| 41 modules (Version 4) | 410 px | 10 |
| 57 modules (Version 8) | 456 px | 8 |
Software arithmetic only: For QR Versions 2–6, a symbol with four quiet-zone modules per side spans the grid widths below. In the recorded calculation, none of the example display sizes 150, 200, 250 or 300 px was an exact integer multiple of those total widths. If you want whole-number source pixels per module before any email resizing, the following illustrative exports are exact:
| QR version | Width including quiet zone | Exact-width examples |
|---|---|---|
| V2 | 33 modules | 198 px (6 px/module), 264 px (8 px/module) |
| V3 | 37 modules | 185 px (5), 222 px (6), 259 px (7), 296 px (8) |
| V4 | 41 modules | 205 px (5), 287 px (7) |
| V5 | 45 modules | 180 px (4), 270 px (6) |
| V6 | 49 modules | 196 px (4), 294 px (6) |
These numbers describe grid arithmetic, not recommended minimum image dimensions or a Gmail/Outlook/Apple Mail scan result. Exporting at a multiple of the final intended width may help retain source detail, but email templates can still rescale the image.
Keep the four-module quiet zone clear; compression, template resizing and dark-mode transformations can change how the image appears. Use high contrast and test the rendered template in the clients your audience uses. Dark-mode and image-handling behaviour differs among clients and settings.
Classic Outlook for Microsoft 365, Outlook 2024, 2021, 2019 and 2016 blocks automatic downloads of internet-hosted pictures by default, according to Microsoft Support. Recipients can choose to download pictures or change settings, and other Outlook clients behave differently. That is a concrete reason to put the usable text link before an optional QR image.
Test the whole email journey
An image decoding correctly on your laptop is not the same as a recipient completing the intended action. Before a campaign, send the message to representative accounts and inspect the actual email in both desktop and mobile reading contexts. Check: image displayed or not; alternative text; clickable fallback; dark and light appearance; URL after scanning; and the final action. Record failures by client version rather than claiming a universal result.
Keep a record of the client and version, device, image-loading state, appearance and destination. A controlled test across Gmail, Outlook and Apple Mail is still needed before claiming compatibility for a particular template.
Measuring email responses without inventing QR performance
If you use both a link and a QR, give them distinguishable campaign parameters when appropriate. Your destination website may be able to record page visits or conversions, but a decoded symbol is not automatically a recorded purchase. Do not infer that a QR improves deliverability or open rates without campaign evidence. Likewise, a redirect address can be a legitimate architecture, but redirection by itself is not a security or inbox-placement guarantee.
OwnQR's QR code generator can encode an ordinary URL. It is not an email campaign platform, email delivery system or spam-filter service. Generate the symbol only after deciding that the email genuinely benefits from a cross-device route.
Frequently asked questions
When can a QR reduce steps in an email?
When the reader is on a laptop but the next task is on a phone—for example, opening a check-in page on a mobile device. On the phone itself, a normal link is usually easier.
Why might Outlook show no QR image?
Classic Outlook blocks automatic downloads of externally hosted pictures by default. A recipient may need to allow the image; a direct text link avoids making the call to action depend on that step.
Is an embedded QR safer than a clickable link?
No. The QR encodes a destination that can still be malicious. Identify the expected domain and make the same destination available as a transparent hyperlink.
Should my QR image be attached or externally hosted?
Either approach can render differently across email clients and settings. If you use a remotely hosted image, the recipient's picture-loading policy may prevent it from appearing. If you embed an image, check the email platform's rendering and attachment handling. In both cases, the primary call to action should remain a readable, clickable link.
Will adding a QR code send my email to spam?
There is no reliable yes-or-no rule based on the presence of one QR image. Inbox filtering considers many factors; a QR can also make a message harder to trust if its destination is hidden or the content resembles phishing. Use legitimate sending practices, a visible destination and a working text alternative, and measure your own delivery outcomes rather than assuming QR images improve or ruin deliverability.
What if a dark-mode email template changes the QR colors?
Test the rendered message in your target clients and keep a clear, conventional high-contrast source image. Do not assume any one client reproduces the source identically.
Sources
Preparation and review: Prepared by the OwnQR editorial team with AI assistance; last updated November 10, 2026; not independently reviewed by a human expert. The pixel analysis was a software calculation, not testing in Gmail, Outlook or Apple Mail.
- U.S. Department of Energy, QR Code Standards and Best Practices — publication date: NOT_PROVIDED; study/event period: NOT_APPLICABLE (design guidance); checked October 2026.
- Microsoft Security Blog, QR-code phishing research — publication date reported as November 4, 2024; study/event period: 2024 phishing analysis; accessed October 2026.
- FTC, Scammers hide harmful links in QR codes — published December 6, 2023; study/event period: 2023 consumer warning; checked October 2026.
- FBI Internet Crime Complaint Center, QR advisory — published January 18, 2022; study/event period: 2022 advisory; checked October 2026.
- Microsoft Support, Block or unblock automatic picture downloads in classic Outlook — publication date: NOT_PROVIDED; study/event period: NOT_APPLICABLE (classic Outlook application guidance); accessed November 10, 2026. Covers classic Outlook, not all Outlook products.
- Section508.gov, Accessibility Bytes No. 8: Accessible QR Code Implementation — publication date: NOT_PROVIDED; study/event period: NOT_APPLICABLE (accessibility guidance); accessed November 10, 2026. Addresses functional alt text and adjacent links.
- Software module-versus-pixel alignment calculation, Versions 2–6 and 150/200/250/300 px, performed November 2026; study/event period: 2026 software calculation. No empirical rendering test was conducted.
- No independent Gmail, Outlook or Apple Mail rendering tests were performed for these examples.