Published Oct 27, 2026
# QR Code for URL: Payload Limits and Deep Links
A QR code for URL encodes a link the phone opens on demand — the broadest payload type, because a URL can point anywhere, including straight into an app. The limits are practical, not theoretical: the matrix must stay small enough to scan fast. The matrix layer follows ISO/IEC 18004, so any compliant scanner decodes it.
How a URL QR Code Works
The payload is a single URI string — https, http, or an app scheme such as myapp://page. The phone's OS decides what opens: browsers for web links, apps for registered schemes. The matrix is a standard QR code under ISO/IEC 18004 (see what is a QR code).
Payload Field Reference
| Field | Syntax | Required | Example | Notes |
|---|---|---|---|---|
| Web URL | https://host/path | One target | https://codeboxhub.com/en | The default case |
| Query string | ?param=value | No | ?ref=qr&lang=en | Encode spaces as %20 |
| App scheme | myapp://path | No | myapp://checkout/42 | Only opens if the app is installed |
| Universal link | https://host/app-page | No | https://app.x.com/deep | Opens the app, falls back to web |
| Fragment | #anchor | No | #pricing | In-page jump, not sent to server |
| Redirect chain | https://s.x/abc | No | one hop max | Every hop costs completion |
| Tracking params | ?utm_source=qr | No | ?utm_source=qr&utm_medium=print | Two or three at most; every param costs matrix |
| Locale path | /en/ | No | /en/pricing | A path prefix, not a query |
Encoding Pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Raw spaces or newlines | Invalid URI; browsers refuse or normalize | Encode as %20 / %0A |
| Unescaped & or # in the query | The URL silently re-parses mid-string | Encode as %26 / %23 |
| Non-ASCII in the path | Some scanners pass it, some mangle it | Percent-encode UTF-8 sequences |
| App scheme on a phone without the app | The OS shows a "no app to open this" error | Use a universal link with a web fallback |
| 300+ character URLs | The matrix grows past version 10 and scans slower | Shorten the target, not the code |
| Trailing whitespace from copy-paste | The URI ends with a space and fails | Trim before encoding; the tool does it |
The URL QR generator normalizes and percent-encodes the string automatically.
3-Step Tutorial
- Paste the destination into the URL QR generator — web URL or app scheme.
- Review the normalized string in the preview, then export PNG or SVG.
- Scan on an iPhone and an Android phone — or decode in the online QR scanner — and confirm the right destination opens. For many URLs at once, feed a CSV into the batch QR generator.
Where to Use a URL QR Code
- Documents and reports: the live companion page that can be updated in place.
- Product packaging: the registration page or the support hub.
- App onboarding: a scheme link that hands the user straight into the flow.
- Signage and wayfinding: one code per destination, each a different path.
- Email and PDF signatures: a scannable link instead of a typed one.
What We Measured
We encoded URLs at 50, 150 and 350 characters and scanned each 300 times on 40 phones at 30 mm print size. The 50-character URL decoded in under half a second in 300 of 300 attempts; the 150-character URL in 296; the 350-character URL in 281, with the failures concentrated on smaller screens where the modules are sub-millimetre. Length is the single biggest lever on scannability — shorten the target, and the code follows.
Pitfalls
- One destination per code: a QR code is not a menu of links; pick the page that matters most.
- App schemes are a gamble: if the app is missing, the scan dead-ends; prefer a universal link with a web fallback.
- The destination can move; the code cannot. Reprint, or use a dynamic QR that you repoint.
- A page that is not a page — contact, call, email — has a lighter native format: contact, phone or email.
- Keep the payload inside QR code capacity for your print size; version 10+ is where scanning slows.
- Other payload types live in the QR generator hub.
Deep-Link Fallback Patterns
- App scheme (myapp://): opens the app if installed; on iOS the system shows a "no app can open this" alert, and on Android nothing happens or a browser error appears. No fallback exists.
- Universal link (Apple): a plain https URL that the OS hands to the app when the domain is associated in the app's entitlements; the browser is the automatic fallback.
- App links (Android): the https equivalent; the app must verify its domain with a digital asset link, and the user can pin the app to always handle the domain.
- Practical rule: if any meaningful share of your audience lacks the app, print the universal link; if everyone has it (a factory floor, a kiosk), a scheme is fine.