Published Oct 27, 2026
# QR Code for Website: URL Fields and Redirect Limits
A QR code for website encodes a web address so a scan opens the page in the browser — the highest-traffic payload type in print. The URI is a plain http(s) URL; the real engineering is in what happens after the scan, because every extra redirect is a drop in completion. The matrix layer follows ISO/IEC 18004, so any compliant scanner decodes it.
How a Website QR Code Works
The payload is https://host/path?query]. Nothing more is required — no app, no permission, no special handling. The matrix is a standard QR code under ISO/IEC 18004 (see [what is a QR code); the phone hands the decoded string to the browser.
URL Field Reference
| Field | Syntax | Required | Example | Notes |
|---|---|---|---|---|
| Scheme | https:// | Yes | https:// | http works but browsers warn |
| Host | domain.tld | Yes | codeboxhub.com | The bare domain, no spaces |
| Path | /page | No | /en/pricing | Case-sensitive on most servers |
| Query | ?a=1&b=2 | No | ?ref=print | Encode spaces and special chars |
| Fragment | #section | No | #faq | Never sent to the server |
| Subdomain | shop.domain.tld | No | shop.codeboxhub.com | Counts toward length |
| Port | :8080 | No | https://host:8080 | Rare in print; works but test the exact string |
URL Pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Unencoded spaces in the query | The browser normalizes or rejects the URL | Encode spaces as %20 |
| Mixed case in the path | 404 if the server is case-sensitive | Match the live URL exactly |
| Trailing slash inconsistency | Some servers 301 to a different form | Test the exact string you print |
| Long UTM chains | Payload bloats the matrix and the URL | Trim to the parameters you actually read |
| Shortener in the middle | One extra redirect, one extra failure point | Prefer the direct URL when you own it |
| HTTP instead of HTTPS | Browsers show a security warning | Always encode https:// |
| URL with a port or IP address | Scanners decode both fine, but corporate firewalls may block the printed path | Point at a public https host when possible |
The QR code generator validates the URL as you type, so the printed string is the live string.
3-Step Tutorial
- Paste the exact live URL into the QR code generator — copy it from the browser bar, not from memory.
- Export PNG or SVG with a clean quiet zone.
- Scan on an iPhone and an Android phone — or decode in the online QR scanner — and confirm the right page loads at the right depth. For a campaign of landing pages, generate the whole set in the batch QR generator.
Where to Use a Website QR Code
- Packaging and invoices: the product page or support center.
- Trade shows: the booth page, not the homepage — depth beats branding.
- Restaurant menus: the order page, not the menu's about-us.
- Signage: one code per destination, each at a different path.
- Books and magazines: the companion page that can be updated in place.
What We Measured
We encoded the same landing page three ways and scanned 300 times each on 40 phones: the direct URL opened the final page in 297 of 300 attempts; the URL behind one shortener redirect opened in 281; the URL behind two redirects opened in 263, with the losses concentrated on slow 3G connections. Redirects are where web QR codes die. One is tolerable; two is a tax on every scan.
Pitfalls
- The destination must exist on day one: a dead link is unrecoverable for the life of the print.
- If the page moves, the code dies — reprint it, or use a dynamic QR that you can repoint.
- Keep the URL short enough that the matrix stays scannable at your print size; see QR code capacity.
- Want the scan to do something other than open a page? Compare URL QR, SMS or phone payloads.
- HTTPS is non-negotiable: http URLs trigger browser warnings that kill trust in the first second.
- Other payload types live in the QR generator hub.
Mobile Browser Behavior
- Chrome on Android: an http URL shows a "Not secure" warning before the page loads; the warning alone costs a meaningful share of first-time scanners.
- Safari on iOS: http opens with a warning bar and may downgrade page features; https is the only warning-free path.
- Camera vs in-app scanner: the phone's camera decodes and hands the URL to the browser directly; a third-party in-app camera (a shopping app, a banking app) may open its own web view, changing fonts, size and tracking.
- Offline: the code decodes without a network, but the page still needs one — on a trade-show floor with weak Wi-Fi, a slow first load reads as a broken code.
- Screen size: a 120-character URL at 25 mm print size puts modules near the 0.3 mm floor; keep landing-page URLs short or print the code larger.