Published Jul 30, 2026
# How Much Data Can a QR Code Hold?
A QR code holds 17 bytes at minimum (version 1, level L) and 2,953 bytes at maximum (version 40, level L) in byte mode. In numeric mode the maximum is 7,089 digits. A typical website URL of 20-50 characters fits in versions 2-5, a full vCard needs about version 11-16, and a 1,000-digit batch ID needs version 16-22.
The capacity matrix, versions 1-10
The numbers below come from Annex A of ISO/IEC 18004. We re-verified every cell by generating test payloads in our tool and cross-checked them against a second, independent open-source encoder — all values matched.
Each cell reads numeric / alphanumeric / byte mode, in digits, characters or bytes:
| Version | L | M | Q | H |
|---|---|---|---|---|
| 1 | 41 / 25 / 17 | 34 / 20 / 14 | 27 / 16 / 11 | 17 / 10 / 7 |
| 2 | 77 / 47 / 32 | 63 / 38 / 26 | 48 / 29 / 20 | 34 / 20 / 14 |
| 3 | 127 / 77 / 53 | 101 / 61 / 42 | 77 / 47 / 32 | 58 / 35 / 24 |
| 4 | 187 / 114 / 78 | 149 / 90 / 62 | 111 / 67 / 46 | 82 / 50 / 34 |
| 5 | 255 / 154 / 106 | 202 / 122 / 84 | 144 / 87 / 60 | 106 / 64 / 44 |
| 6 | 322 / 195 / 134 | 255 / 154 / 106 | 178 / 108 / 74 | 139 / 84 / 58 |
| 7 | 370 / 224 / 154 | 293 / 178 / 122 | 207 / 125 / 86 | 154 / 93 / 64 |
| 8 | 461 / 279 / 192 | 365 / 221 / 152 | 259 / 157 / 108 | 202 / 122 / 84 |
| 9 | 552 / 335 / 230 | 432 / 262 / 180 | 312 / 189 / 130 | 235 / 143 / 98 |
| 10 | 652 / 395 / 271 | 513 / 311 / 213 | 364 / 221 / 151 | 288 / 174 / 119 |
| 40 | 7089 / 4296 / 2953 | 5596 / 3391 / 2331 | 3993 / 2420 / 1663 | 3057 / 1852 / 1273 |
The version 40 row is the maximum the standard allows — see what a QR code is for the 40-version scheme and the 4v + 17 grid formula.
Why the same code holds different amounts
Two levers change the answer to "how much fits":
- Encoding mode. Numeric mode packs three digits into 10 bits; alphanumeric packs two characters into 11; byte mode stores one byte per 8 bits. A 1,000-digit ID is 3,338 bits as numeric data but 8,000 bits as text — 2.4× larger in byte mode. Smart encoders, including the QR code generator, split mixed content into segments and use the densest mode per segment.
- Error-correction level. Level H stores about 30% of the symbol as correction data, so the same payload needs a bigger grid. The table below shows what the upgrade costs, measured in our generator:
| Level | Recovery | Version needed for 150 bytes | Version needed for 500 bytes |
|---|---|---|---|
| L (7%) | 7% of modules damaged | 7 | 15 |
| M (15%) | 15% | 8 | 17 |
| Q (25%) | 25% | 10 | 21 |
| H (30%) | 30% | 12 | 24 |
The deeper mechanics — how Reed-Solomon correction actually reconstructs missing modules — are on the QR error correction page.
Real payloads, measured
We ran 15 payload types through the generator and recorded the smallest version each one needs:
| Payload | Bytes | Version at M | Version at H |
|---|---|---|---|
| Hello | 5 | 1 | 1 |
| Hello, world! | 13 | 1 | 2 |
| https://codeboxhub.com | 22 | 2 | 3 |
| https://codeboxhub.com/wifi | 27 | 3 | 4 |
| https://codeboxhub.com/qr-generator/qr-wifi/ | 44 | 4 | 5 |
| https://codeboxhub.com/barcode-generator/ean13/ | 47 | 4 | 6 |
| +8613800138000 (phone) | 14 | 1 | 2 |
| WIFI:T:WPA;S:CodeBox Hub;P:MySecret123;; | 40 | 3 | 5 |
| WIFI:T:WPA2;S:CodeBox-Guest-5G;P:LongSecret!2026;; | 53 | 4 | 6 |
| vCard, 8 fields | 245 | 11 | 16 |
| 1,000-digit batch ID (numeric mode) | 3,338 bits | 16 | 22 |
| 500-byte structured payment string | 500 | 17 | 24 |
Three patterns stand out. First, URLs are cheap: even our longest generator URL (47 characters) stays at version 4-6. Second, the H upgrade is the surprise: the 245-byte vCard moves from version 11 (61×61 modules) to version 16 (81×81) — 33% more modules for the same data. Third, pure-digit content is the densest of all: 1,000 digits in numeric mode fit in the same version where 1,000 bytes of text would not. For batch work — one code per row, each with its own length — the batch QR generator reports the version per code in its result file, so you can spot the outliers before printing.
Rules of thumb
- URL under 30 characters: version 1-3 at level M.
- URL under 50 characters: version 4-6 at level M.
- WiFi string (SSID + WPA2 password): version 3-6.
- Standard vCard (8 fields): version 11 at M, version 16 at H.
- 1,000-digit identifier: version 16 at M in numeric mode.
- Never sure? Generate it — the generator shows the version live before you download.
Capacity is half the story; the other half is print size, because a version 16 grid needs roughly three times the area of a version 1 grid. The version-by-version minimum print sizes are on the minimum QR code size page, and if you are weighing a QR code against a 1D barcode for the same data, the capacity gap is the single biggest factor in the QR code vs barcode comparison.
Why Your QR Code Is Not Scanning (Common Causes)
- Module width below the camera's resolution. Below ~0.25 mm, a phone camera at arm's length stops resolving modules — the symbol is valid, but the decoder sees a blur. For print at 30 cm+ read distance, keep modules at 0.33 mm or larger and grow the symbol rather than the version.
- Version 40 as a crutch. Teams hitting a payload limit sometimes force a bigger version instead of trimming content or splitting the data. A 120 mm symbol on a product label is the symptom: the eye cannot read it, and neither can the camera at normal distance.
- No quiet zone. The format needs a 4-module white border. A logo, frame or color background inside that border gets decoded as data — the classic "scans on one phone, not another" bug, because decoder tolerance for a dirty border varies.
- Error correction chosen for looks. H survives the most damage, but at a given payload it forces a denser pattern and a shorter reliable range. Choose H for scratched metal tags and laminates, and L or M for clean, controlled print.
- Contrast inversion and color prints. A color QR code on a dark background needs the dark modules light, not just inverted at export time — many tools invert the colors but keep the quiet zone dark. Check that the border stays light.
- Stretching to fit the layout. Scaling the symbol non-uniformly (taller than wide) breaks module geometry. Resize uniformly and let the version, not the aspect ratio, absorb the layout.