Reverse QR Code: What It Is & How It Works
The calculator for this page is switched off while it is checked. The formula is below, and the worked example in the article shows how to use it by hand.
A reverse QR code flips the usual scanning direction: instead of your phone camera reading a code on a screen or paper, the code itself is displayed on your device and a fixed scanner reads it. You enter the code’s data (often a ticket, boarding pass, or payment token) into the calculator below to see what the scanner actually decodes, or to convert between the text content and the visual pattern. The calculator works out the raw data payload and its size in bytes, which is what determines whether a code can be printed small or must be displayed large.
Formula
The core calculation is simple: the data bytes equal the number of characters in the text (for standard QR encoding, each character is roughly 1 byte, but numeric and alphanumeric modes compress more). The maximum capacity for a QR code at the largest version (40) with low error correction is 2,953 bytes. The formula is:
Data bytes = number of characters in the text
Capacity used = (Data bytes ÷ 2,953) × 100
Variables:
- Text content – the string you want to encode (e.g., a URL, plain text, or a vCard).
- Data bytes – the raw size of the content before error correction is added.
- Max bytes – the absolute limit for a QR code at version 40 with low error correction (L).
- Capacity used – the percentage of the maximum that your content occupies.
Worked Example
Using the default text https://example.com/event/2024:
- Count the characters:
https://(8) +example.com(11) +/event/2024(11) = 30 characters. - Data bytes = 30 bytes (assuming byte mode).
- Max bytes = 2,953 (version 40-L).
- Capacity used = (30 ÷ 2,953) × 100 = 1.0%.
The calculator returns 30 bytes and 1.0%, which matches the formula.
What Is a Reverse QR Code?
A reverse QR code is a QR code that is displayed on a device (like a smartphone or tablet) and scanned by a fixed reader, rather than the other way around. The term is not standard in official QR specifications; it is informal jargon used in ticketing, access control, and mobile payments. The official name is “displayed QR code” or “scanner-presented QR code.”
In a normal QR interaction, the phone has the scanner app and reads a code on a poster or screen. In a reverse setup, the phone holds the code and the scanner is a stationary device, like a turnstile reader or a checkout terminal. The phone screen acts as a digital ticket or payment token.
How Reverse QR Codes Work
The process is straightforward:
- The phone generates a QR code from a secure token or a static value (e.g., a ticket ID).
- The screen brightness is typically set to maximum to ensure the scanner can read it.
- The fixed scanner uses a camera or laser to capture the code.
- The scanner decodes the data and sends it to a backend system for validation.
Because the phone screen is reflective and can have glare, reverse QR codes often use error correction (levels M or H) to tolerate damage or blur. The scanner is usually optimized for close-range reading, often with a red LED or infrared light.
Where Reverse QR Codes Are Used
Common real-world uses include:
- Event ticketing – concert or cinema tickets displayed on a phone are scanned at the entrance.
- Boarding passes – airlines scan the barcode on your phone screen at the gate.
- Mobile payments – you show a QR code at a checkout counter and the terminal scans it.
- Access control – gym memberships or office badges displayed on a phone.
In each case, the phone is the source of the code, and the reader is fixed. This is the opposite of the typical “scan this poster” scenario.
Reverse QR vs. Standard QR
The difference is purely in the direction of scanning, not in the code structure. A QR code is a QR code; the same symbol can be read by a phone or a fixed scanner. However, the practical considerations differ:
- Screen glare – phone screens reflect light, so the scanner must handle specular reflection.
- Screen size – a phone screen is smaller than a printed poster, so the code must be sized appropriately.
- Dynamic content – reverse QR codes often change (e.g., a rotating payment token), while printed codes are static.
- Security – reverse codes can be refreshed to prevent replay attacks, which is harder with printed codes.
For users, the experience is reversed: instead of pointing the camera at a code, you hold your phone up to a reader.
Common Problems and Misconceptions
A frequent misconception is that a reverse QR code is a different type of barcode. It is not; it is the same QR standard, just displayed on a screen. Another issue is that some people think you need a special app to generate a reverse code. In reality, any QR generator works; the difference is in how the code is presented.
Common problems include:
- Screen brightness too low – the scanner cannot read the code. Fix: increase brightness.
- Glare – reflections make parts of the code unreadable. Fix: tilt the phone slightly.
- Code too small – if the content is long, the code becomes dense and unreadable. Fix: use a shorter URL or a higher error correction.
- Expired tokens – dynamic codes may be time-limited; refresh the code if it fails.
Another misconception is that reverse QR codes are less secure. They can be more secure if they use dynamic tokens, but static codes are just as vulnerable as printed ones.
How to Choose the Right QR Settings
When generating a reverse QR code, consider:
- Error correction level – use H (30%) for small screens or when the code might be partially obscured.
- Version – higher versions hold more data but become denser. Keep the content short.
- Encoding – use alphanumeric mode for URLs to save space.
- Size – the code should be at least 2 cm × 2 cm on screen for reliable scanning.
If you are generating a code for a ticket, use a short ID (e.g., a 10-digit number) rather than a long URL. This keeps the code small and easy to scan.
Safety and Security Considerations
Reverse QR codes are generally safe, but there are risks:
- Phishing – a malicious code could direct you to a fake website. Only scan codes from trusted sources.
- Replay attacks – if a static code is intercepted, it can be reused. Dynamic codes mitigate this.
- Screen privacy – someone could photograph your code and use it later. Keep your screen dim when not in use.
For payments, always use the official app and check the amount before confirming. For tickets, do not share the code publicly.
Frequently Asked Questions
Is a reverse QR code the same as a regular QR code?
Yes, the underlying code is identical. The term “reverse” only describes the scanning direction: the phone displays the code, and a fixed scanner reads it. There is no separate standard.
Do I need a special app to create a reverse QR code?
No. Any QR generator can produce a code that works in reverse. The key is to keep the content short and use a high error correction level for screen display.
Why won’t my phone’s QR code scan at the turnstile?
Common reasons are low screen brightness, glare, or the code being too small. Increase brightness, tilt the phone, and ensure the code is fully visible. If the code is dynamic, it may have expired.
Can I use a screenshot of a reverse QR code?
It depends on the system. Static codes (like event tickets) often work with a screenshot, but dynamic codes (like payment tokens) may be time-limited and will fail if the screenshot is old.
Are reverse QR codes more secure than printed ones?
They can be, because they allow dynamic tokens that change each time. However, a static reverse code is no more secure than a printed one. The security depends on the backend validation.
What is the maximum data a reverse QR code can hold?
The absolute maximum for a QR code is 2,953 bytes at version 40 with low error correction. For screen display, it is best to stay well below that to keep the code scannable.
Related
Formula used
in t | Text content | - | https://example.com/event/2024 | 0 out bytes | Data bytes | bytes | length(t) | 0 out capacity | Max bytes (QR version 40-L) | bytes | 2953 | 0 out pct | Capacity used | % | length(t) / 2953 * 100 | 1
Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.