Should you put a QR code on your resume in 2026?
Short answer: yes, if it serves a purpose your name and contact info don't already serve.
For most candidates — generalist white-collar roles, mid-career hires, traditional industries — a QR is optional. Recruiters will search your LinkedIn anyway. A vCard QR is a small lift over typing your contact info into their phone — but it's a real lift, and recruiters scanning 200 resumes a week notice the candidates who reduce friction.
For designers, developers, writers, photographers, video editors, architects — anyone whose work portfolio drives the hiring decision — a QR is strongly recommended. The recruiter scans, your portfolio loads on their phone, the work review happens in the moment. For roles where samples are the qualification, the portfolio QR is the highest-impact addition you can make.
The inverse: skip the QR if your resume is full and adding one pushes meaningful content off the page. A QR earns its real estate by replacing typing labor; it doesn't earn it by displacing your strongest experience line.
In 2018 a resume QR read as gimmicky. In 2026 it reads as professional baseline for portfolio-dependent roles and as a thoughtful touch elsewhere.
The four QR types worth considering — and which one to pick
There are four genuine QR types worth putting on a resume. Pick one as primary; consider a second only if the page layout has room.
| QR Type | What it does | Best for | Friction saved |
|---|---|---|---|
| vCard QR | Encodes name, phone, email, LinkedIn, title; scanner saves to contacts in one tap | Most candidates | High — replaces manual typing of 5 fields |
| LinkedIn profile URL | Opens your LinkedIn profile in browser or app | Senior hires, networking events | Low — recruiters search you anyway |
| Portfolio URL | Opens your portfolio website, GitHub, Behance, Dribbble | Designers, devs, writers, creatives | High — recruiter sees work samples instantly |
| Multi-URL QR | One code routes to vCard, LinkedIn, portfolio based on app installed or choice | Candidates wanting flexibility | Mixed — adds a decision step |
Tips
- **Default to vCard** for general roles, business roles, and senior hires where contact saving is the highest-value outcome.
- **Default to portfolio** for designers, developers, writers, photographers, video editors, architects, and any role where the work is the qualification.
- **Skip LinkedIn-only QRs** unless paired with vCard or portfolio. They add little — recruiters can search.
- **Skip multi-URL QRs** for resumes. The decision step they add is friction the recruiter doesn't want. One destination per QR is cleaner.
vCard QR — the contact-save shortcut
A vCard QR encodes a BEGIN:VCARD ... END:VCARD structured-data block. When a recruiter scans it, their phone recognizes the vCard format and prompts them to Add to Contacts — name, phone, email, LinkedIn URL, job title, all saved in one tap.
Without the vCard QR, the recruiter has to find your number, switch to contacts, tap New Contact, type your name, type your number, switch back to find your email, repeat for LinkedIn. The vCard QR collapses all of that into one tap. For a recruiter screening 50 resumes a day, that's the difference between 'I'll add this candidate to my pipeline' and 'I'll get to it later.' Later, in recruiting, is often never.
Include in the vCard:
- Name (required)
- Phone (the one you actually answer)
- Email (your job-search email, not your work email)
- LinkedIn URL (canonical: linkedin.com/in/yourname)
- Job title (current, or target if between roles)
Skip: home address (privacy), multiple emails (noise), photo (unprofessional in US/UK contexts).
Generate through EZQR's vCard generator, customize the colors subtly, and download as SVG for crisp print at any size.
Portfolio QR — the work-sample gateway
For any role where your work portfolio is the actual qualification — UI design, product design, illustration, photography, video editing, software development, technical writing, copywriting — the portfolio URL QR is the single most valuable addition to your resume.
The recruiter scans, their phone opens your portfolio in the default browser, and your work loads on the screen they're already holding. No URL typing, no browser tab switching, no 'I'll check it later.' The portfolio review happens in the moment, while the recruiter still has your resume in their other hand.
What to point the QR at:
Designers and creatives: portfolio site, Behance, or Dribbble. Pick the one with the strongest work, not the most. 12 hand-picked projects beats 80 unfiltered ones.
Software developers: GitHub profile, or your personal site if it surfaces your strongest projects with READMEs and live demos. Recruiters judge the average, not the best.
Writers and journalists: your site with bylined clips. PDF portfolios are worse than web portfolios for mobile-first QR-driven access.
Photographers and video editors: Squarespace, Format, Adobe Portfolio, or Vimeo. Mobile-optimized is non-negotiable.
The portfolio URL must be rock-solid permanent. Use your own domain (yourname.com) — platform URLs can shift when the platform rebrands. A static QR encodes the URL directly; if your URL changes after you print, the QR breaks.
Step-by-step: generate, place, size, and test a resume QR
The full workflow from picking a QR type to handing the resume to a recruiter:
Tips
- **Step 1: Pick the QR type.** vCard for most candidates; portfolio URL for designers/devs/writers/creatives. Don't include multiple QRs on one resume — pick the highest-value one.
- **Step 2: Generate the QR through [EZQR](/qr-codes).** Free static codes, no watermark, no signup needed. Use vCard generator for contact QRs; URL generator for portfolio QRs.
- **Step 3: Customize the colors subtly.** Dark gray or black on white reads professional. Match an accent color from your resume design only if the resume itself has color — most ATS-friendly resumes are monochrome.
- **Step 4: Download as SVG, not PNG.** SVG scales without pixelation at any print size. PNG is fine if you must, but SVG handles resume reprints, scale changes, and Adobe/Word imports cleanly.
- **Step 5: Place the QR in the header** next to your name and contact info. Top-right corner is the most common placement; left-aligned next to the name also works. Don't put it in a footer or sidebar where recruiters won't notice it.
- **Step 6: Size the QR at 2.5–3 cm (1–1.2 inches).** Smaller than 2.5 cm fails at arm's-length scan distance under office lighting. Larger than 3 cm looks visually heavy and crowds the page.
- **Step 7: Add a tiny prompt under the QR** — 'Scan to save my contact info' or 'Scan to view portfolio' in 8–9pt type. Naked QRs convert at half the rate of prompted QRs even with recruiters.
- **Step 8: Print a test copy and scan from a phone held 30 cm away under normal office light.** This is the actual recruiter scenario. If the QR doesn't decode reliably, increase the size by 5mm and retest.
- **Step 9: Export the resume as PDF with the QR embedded as a vector** (Word: keep as SVG; Adobe: embed). The QR must work both when the PDF is viewed on screen and when the PDF is printed and scanned in physical form.
- **Step 10: Send the resume.** ATSs parse the text fields and ignore the QR. The QR is for the human recruiter who opens the PDF after the ATS pass.
Will an ATS (Applicant Tracking System) read the QR code?
No — and that's actually fine.
Applicant Tracking Systems (Workday, Greenhouse, Lever, iCIMS, Taleo, BambooHR, and the rest) parse the text content of your resume PDF. They look for your name, contact info, work history, education, and keywords matching the job description. They do not decode QR codes in image data, and they do not follow URLs encoded in QR codes.
This matters for one reason: don't put critical information only in the QR. Your phone number, email, LinkedIn URL, and current title must appear in plain text on the resume regardless of whether you include a QR code. The ATS needs that text to populate its candidate database; if your phone number only exists encoded in a QR, the ATS won't have a phone number to call.
The QR is additive, not a replacement. It exists to reduce friction for the human recruiter who reads your resume after the ATS surfaces it. The ATS does the keyword-and-text parsing; the human does the QR scanning.
A related question: does including a QR code on the resume hurt ATS parsing? No. The ATS sees the QR as an image, ignores it, and parses the surrounding text normally. The QR doesn't interfere with name extraction, contact-info extraction, or keyword matching. It just sits there, invisible to the ATS, ready for the human reader.
If you're particularly worried, run your PDF through a free ATS-checker tool (Jobscan has one) and confirm the parsing extracts your contact info correctly. Practical answer: every test I've run, the parsing handles QR-embedded resumes identically to QR-free resumes.
Placement, size, and color — the visual discipline that determines whether the QR gets scanned
Three visual decisions make or break a resume QR. Get them right and the QR delivers; get them wrong and it's wasted real estate.
Placement. The header — next to your name and contact info — is the highest-conversion placement. Top-right corner is most common; left-aligned next to the name also works. The QR is part of the contact-info block, not a separate element off in a corner or footer.
Don't put the QR in a sidebar (recruiters scan top-down, not column-by-column on a quick first pass). Don't put it in a footer (often clipped in print, often skipped in screen scrolling). Don't put it next to a project description (the visual association is wrong — it reads as 'scan to see this project' rather than 'scan to save my contact').
Size. 2.5–3 cm (1–1.2 inches) square. The 10:1 scan-distance rule applies: a 30 cm scan distance (the natural arm's-length reading position for a printed resume) needs a code width of at least 3 cm to decode reliably under typical office lighting. Smaller codes fail; larger codes crowd the page.
On screen-viewed PDFs the same size works because recruiters zoom in if needed — but they zoom less than you'd think, and a 1.5 cm QR on screen is small enough that many recruiters skip the scan entirely rather than zoom.
Color. Black on white is the safe default — highest contrast, most reliable across every scanner. Dark gray (#222 or #333) on white is also fine and matches modern minimal resume designs. Avoid colors below 50% contrast — light blue on white is unscannable under bad lighting; light gray on light beige is unscannable everywhere.
If your resume has an accent color, you can use it for the QR — but test the scan reliability under multiple lighting conditions before printing 50 copies for a career fair. Most accent colors work; some (yellows, light greens) don't have enough contrast against white to scan reliably.
Prompt copy beside the QR matters more than people expect. 8–9pt type that says 'Scan to save my contact info' or 'Scan to view portfolio' lifts scan rate noticeably. Naked QRs leave money on the table.
Static vs dynamic — the static-is-correct decision for resumes
Every QR on a resume should be a **static code**. Not a dynamic code.
The rule is structural. A static QR encodes the destination — your vCard data, your portfolio URL — directly into the QR pattern. There's no server in the loop, no redirect, no subscription needed for the code to keep working. The destination URL is the QR.
A dynamic QR encodes a redirect URL that routes through EZQR's (or any provider's) server. The advantage is editability — you can repoint a printed code after it's already in circulation. The disadvantage is that the redirect server has to keep running for the code to keep working.
For resumes, you do not want the editability and you do want the static guarantee. Three reasons:
One: your contact info and portfolio URL shouldn't change after you print resumes. If they will, fix that first (lock down the URL, use a domain you control) before printing anything.
Two: your resume might be in circulation for years. A recruiter you met at a career fair in 2026 might fish your resume out of a pile in 2028 for a role that just opened up. A static QR still works in 2028; a dynamic QR works only as long as you're paying for the redirect.
Three: the cost story doesn't work. Static codes are free on every plan. Dynamic codes start at $5/mo. Paying $60/year so a recruiter you may or may not meet later can still scan your resume is the wrong trade-off.
For the verification workflow that confirms a downloaded static QR keeps working after cancellation, see our deep dive. The short version: generate the QR, download it, then test scanning it after closing the EZQR session entirely. If it still works (it will, for static codes), the QR is yours forever.
Common mistakes that cost interviews
Eight failure patterns I see repeatedly when reviewing resumes with QRs:
1. Too small. A 1.5 cm QR fails at arm's-length scan distance. Recruiters give up after one failed scan. Print at 2.5 cm minimum.
2. Wrong placement. A QR in the footer or sidebar gets skipped. Put it in the header.
3. No prompt copy. 'Scan to save my contact info' lifts scan rate noticeably. Don't print a naked QR.
4. Linking to LinkedIn when you should link to portfolio. For designers, developers, writers, photographers, the portfolio is the qualification — linking to LinkedIn instead is leaving the most valuable card on the table.
5. Linking to a portfolio URL that breaks in 6 months. Use your own domain or a permanent platform URL. Don't link to a side-project URL on a shared host that you might forget to renew.
6. Encoding a `bit.ly` shortened URL. The recruiter sees bit.ly/xyz in their browser before the redirect resolves — looks unprofessional and triggers spam filter heuristics on some corporate networks. Use the canonical URL.
7. Putting multiple QRs on one resume. One QR per resume. Multiple QRs read as a gimmick and add decision friction. Pick the single highest-value destination.
8. Skipping the print test. The PDF looks fine on screen, but when the recruiter prints it, the QR is too small or the contrast is wrong. Print one test copy on actual office paper and scan it from a phone held 30 cm away. If it fails, fix it before sending.
