Standard Business Card Dimensions
| Region | Standard Size |
|---|---|
| UK / Europe | 85 × 55 mm |
| US | 89 × 51 mm (3.5 × 2 in) |
| Japan | 91 × 55 mm |
| Square (modern) | 55 × 55 mm |
For a standard UK business card (85 × 55 mm), the QR code can occupy 20–25 mm on the back face without dominating the design.
Recommended QR Sizes for Business Cards
| Card Face | QR Size | Notes |
|---|---|---|
| Back only | 20–25 mm | Sufficient for V1–V4 content |
| Front bottom-right | 15–18 mm | Small but functional for V1–V2 only |
| Half back (landscape) | 25 × 25 mm | Good design balance |
| Square card front | 25 × 25 mm | Square cards have more room |
Minimum recommended: 20 × 20 mm for a URL-only QR (V2–V3, Level M).
Note: A vCard with full contact information is V5–V8. At 20 × 20 mm, this may fail. For vCard QR codes on business cards, use 25 × 25 mm and Level M error correction.
Design Layout for Back-of-Card QR
Option A — Full back:
QR centred on the back face with CTA text above: "Scan to save my details / see my portfolio / view my work." Clean and impactful.
Option B — Bottom-right quadrant:
Text, social icons, or a secondary graphic on the remaining 75% of the back face. More information-rich but requires careful layout to avoid crowding the QR.
Option C — Front card with small QR:
Integrated into the front card design. Requires minimum 15 mm and V1–V2 content only (short URL or email).
Content Optimisation for Small QR
To fit a URL in a small QR (V1–V3):
1. Use a short URL — yourname.com or go.co/yourname rather than yourcompany.com/team/your-name-profile-page
2. Use a URL shortener: bit.ly or a custom short domain
3. Use HTTPS — the protocol adds characters but is non-negotiable for security
A 25-character URL generates a V2 QR — cleanly scannable at 20 × 20 mm.
A 100-character URL generates a V5–V6 QR — needs 25–30 mm minimum.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- Use the [QR size calculator](/qr-size-calculator) to match the printed size to the expected scan distance before you commit to a print run.
- Check print proofs with the [printed QR tester](/printed-qr-tester) so problems show up before a full run.
- The [QR size guide](/qr-size-guide) gives size recommendations for common placements.
- The [QR placement guide](/qr-placement-guide) covers height, lighting, glare, and surfaces that affect scan success.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- When a one-dimensional symbol fits better, the [barcode generator](/barcode-generator) covers retail and inventory formats.
