Print-Ready and Verified QR Code
A QR code can look perfect on screen and still fail on paper. This path generates the code, scales it to your print size, shrinks the file enough for an upload and then reads the result back. Only when the reader gives the text back is the code truly print-ready. Everything runs locally in your browser.
Your progress is stored only in your own browser (localStorage) and is not transmitted to our servers. Third-party resources (e.g. advertising and analytics from Google/Cloudflare) may transfer data when loaded.
This workflow guides you through the following steps:
- 1. Generate QR code Enter your link or text, pick error correction and border, then download the graphic.
- 2. Scale to print size Set the width in centimeters or pixels. Rule of thumb: at least 2 cm per side, otherwise the code becomes unreliable to scan.
- 3. Compress as GIF/PNG Compress only as far as the edges stay sharp. A QR code lives on crisp edges, not on a small file size.
- 4. Read the result back Load the finished file here. If the text comes back clean, the code is print-ready. If you see 'no QR code found', it got too small or too soft.
Interactive workflow loading …
What you get at the end
A QR code file at print resolution, small enough to upload, plus confirmation that it still reads back.
Why these steps in this order
Generate, then scale, then compress, then verify. In this order every stage stays fixable: after scaling you can change the size, after compressing you can go back to a larger file. The check comes last on purpose, because only the final file counts, not the code on your screen.
Frequently asked questions
Where is my data stored?
Your playbook progress is saved in your own browser using localStorage. Nothing you enter is uploaded to our servers. Clearing your browser data resets the workflow.