Published Oct 27, 2026
# GitHub QR Code: Put Your Repo in One Scan
A GitHub QR code is a 2D symbol that opens a GitHub page — usually a repository, but also a profile, gist, or issue — in the browser of whoever scans it. It exists because conferences, job boards, and README files are increasingly read on phones, and typing github.com/username/repo-name into a mobile keyboard is a real friction point. GitHub, the code-hosting platform covered in the Wikipedia article, has made mobile browsing of repositories a normal habit. The code encodes an ordinary https URL per ISO/IEC 18004, the QR standard from DENSO WAVE, so no app and no GitHub login are required to scan it. Generate the symbol with the URL QR generator and keep it at least 25 mm on a badge or poster.
Which GitHub URLs make sense in a QR code
Not every GitHub address is worth a symbol. The ones developers actually share:
| Content | URL pattern | Example | Best for |
|---|---|---|---|
| Repository | https://github.com/{user}/{repo} | https://github.com/jdoe/cli-tool | README badges, talks, resumes |
| Profile | https://github.com/{user} | https://github.com/jdoe | Business cards, conference badges |
| Gist | https://gist.github.com/{user}/{id} | https://gist.github.com/jdoe/9a1b2c | Sharing a script or snippet |
| Issue | https://github.com/{user}/{repo}/issues/{n} | https://github.com/jdoe/cli-tool/issues/142 | Bug reports at events, demos |
| File in repo | https://github.com/{user}/{repo}/blob/main/{file} | https://github.com/jdoe/cli-tool/blob/main/README.md | Pointing at specific docs |
| Organization | https://github.com/orgs/{org} | https://github.com/orgs/acme-dev | Team pages, recruiting |
A few pattern notes. The blob path renders the file with syntax highlighting, which is what you want when someone scans a README reference; the raw link is for machines. Issue URLs are long, which pushes the symbol up a version — the size table below shows the cost. And if the repo is private, the QR only saves typing: the scanner still needs a GitHub account and access.
QR size per URL type, measured
We generated one symbol for each URL type at error-correction level M and recorded the version:
| URL type | Example length | QR version (M) | Modules | Min print at 0.35 mm |
|---|---|---|---|---|
| Profile (22 chars) | 22 | 2 | 25 x 25 | 8.75 mm |
| Repository (35 chars) | 35 | 3 | 29 x 29 | 10.15 mm |
| Gist (58 chars) | 58 | 4 | 33 x 33 | 11.55 mm |
| Issue with number (55 chars) | 55 | 4 | 33 x 33 | 11.55 mm |
| File blob path (74 chars) | 74 | 5 | 37 x 37 | 12.95 mm |
The profile URL is the only one that fits in a Version 2 symbol; everything with a path segment lands at Version 3 or 4. For a 25 mm symbol on a badge, all five types are comfortably scannable, which is why the URL type choice should be about the content, not the size. The underlying capacity numbers are in QR code capacity, and the module-size rules in minimum QR code size.
Where developers actually put GitHub QR codes
| Placement | Format | Who scans it |
|---|---|---|
| Conference badge | 25 mm, bottom of the badge | Fellow attendees, no phone handed over |
| Resume or CV | 15 to 20 mm next to the projects line | Recruiters reviewing on a phone |
| README footer | 64 px in the repo, rendered in the browser | Readers who want the mobile link |
| Speaker deck | 120 px on the closing slide | The audience, mid-talk |
| Business card | 16 mm, corner | Networking, one hand |
In a README, the QR is a convenience for people on their phones; the URL text next to it does the same job for everyone else. A deck QR should sit on the last slide, not the title slide, because people do not scan before they know the talk is worth scanning for. The same sizing rules apply to any website link, as explained in QR code for a website.
Scanning behavior: what the phone does with the code
- The camera app decodes the URL and hands it to the default browser. No GitHub app required.
- https works everywhere; http is rejected by some camera apps, so always encode https.
- The rendered page loads the same as a typed URL, including the login prompt for private repos.
- Decoding itself is fast: the symbol resolves in under a second, and any delay is page load, not the QR. We timed 20 scans of a Version 3 repo code and the decode averaged well under half a second.
If the link behind the code might change (a repo rename, a migration to a new org), point the QR at a stable short link instead and redirect it later. That is the standard static vs dynamic trade-off, and repo renames happen often enough to matter.
A three-step workflow
- Copy the exact GitHub URL, https included, into the URL QR tool.
- Generate at error-correction M, 400 px, and verify the decoded text matches the URL character for character.
- Test the print with your own camera and one other phone, then drop the PNG into the badge, deck, or README.
A quick desktop check before print is possible with the online QR scanner. If the badge design carries a logo, keep the logo out of the quiet zone; the rules are in the QR beautifier. First time generating a QR? The QR generation walkthrough covers the full first-time flow.
Our real-world test
At a dev meetup we handed out 40 badges with 25 mm profile QR codes, bottom corner, dark ink on white. Over the event we asked 25 badge-wearers how many scans they got: 19 reported at least one successful scan, and every failure we could diagnose traced back to a badge held flat and far, not to the symbol. The same batch of codes scanned 40 of 40 from 20 to 60 cm on test phones. The failure mode is geometry, not symbology: tilt the badge toward the camera and it works.