01 / Local
Processed in your browser
Generation happens on your device, without a QR API.
Free, private and static
No signup. No watermark. Static QR codes do not expire. Your QR data stays in your browser.
Enter the destination, then adjust the colours and reliability settings if you need to.
02 / Preview
Your QR code
Nothing is generated from the placeholder text.
03 / Download
Downloads become available when the QR code is ready.
04 / Local quality checks
Four clear modules around the code is the dependable default.
Medium balances resilience and QR density for a normal URL. Compare the levels.
Your destination is generated, checked and downloaded locally. It is not saved or sent to a QR service.
Designed to work
A QR code is only useful if a camera can read it. Every generated code is checked locally, with each result explained in plain English.
Useful signals, honestly described
Private by architecture
Static QR generation is designed to happen in your browser. The content you enter does not need to be sent to our server or an external QR service.
01 / Local
Generation happens on your device, without a QR API.
02 / Private
URLs, Wi-Fi passwords and contact details are not sent to our server.
03 / Simple
There is no login, project history or subscription layer.
Check, scan and plan
Creating the image is only one part of the job. These focused tools will help you inspect destinations, diagnose problems and prepare artwork for the real world.
01
Find common reasons an existing QR code may be difficult to scan.
02
See what a QR code contains before choosing to open it.
03
Choose a sensible physical size before sending artwork to print.
04
Build a destination with clean UTM tracking for GA4 and offline campaigns.
Practical guidance
Short, useful guides explain what matters, why QR codes fail and how to test important work without a sales pitch.
01
Why static codes last, and what can still stop a destination working.
02
Work through contrast, size, damage, print and quiet-zone problems.
03
Understand the practical trade-off between resilience and density.
04
Protect important patterns and avoid covering too much of the code.
05
Use clear UTM parameters for useful offline campaign attribution.