Free QR tools · Printed-code rescue
The code is printed.
The destination does not have to be.
A static QR code cannot be edited · its address is the pattern, and the pattern is on paper. But the address points at a machine, and if that machine is yours, one redirect hands every future scan to us. The flyers stay in the box.
reads in your browser · nothing uploaded · answers "no" when the answer is no
nothing uploaded · no signup to get an answer
Paste exactly what the code opens. If you are not sure, scan it with your phone and copy the address from the browser bar.
The physics
Nobody can change a printed code.
Everybody can change a redirect.
When a static code is generated for https://acme.com/summer, that string is encoded into the black and white squares. The pattern and the address are the same object. There is no server in the loop, no lookup, nothing to log in to · which is exactly why static codes are free and never expire, and exactly why no tool on earth can edit one after it is printed.
What has a server in the loop is acme.com. A scan of that code is an ordinary web request to your own machine, and you can answer it however you like. Answer it with a redirect to a dynamic code and the printed pattern never changes while the destination becomes something you edit from a dashboard, forever. One rule, installed once.
Six cases, four of them yes
It depends on one thing:
whose machine answers the scan.
- Your own domain, with server or CDN access · a redirect rule at the origin. The strongest version: it runs before your site does, so it survives the site being rebuilt or going down.
- Your own domain, but a website builder · Shopify, Wix, Squarespace, Webflow and WordPress all have a redirect setting. If yours genuinely has none, a script on that one page is the fallback, and we say out loud that it is the weaker mechanism.
- A subdomain you own · the cleanest case of all. One DNS record moves the whole hostname to our edge, so the printed address resolves with us directly · no rule to maintain and no second hop.
- A short link you created · Bitly, and also the dynamic QR platforms. The destination is a setting in that account: change it and every printed code follows. If you are leaving a QR vendor, this is your migration · no reprint, no downtime.
- A domain you do not control · no. Everything after the scan happens on somebody else's machine. If it belonged to an agency or someone who left, chase that access before you chase a reprint.
- A code that is not a web address · no. WiFi joins, contact cards and plain text carry their content directly, with no server anywhere. Nothing to redirect, so nothing to rescue.
The honest part
A rescue adds a hop,
and the hop is on your server.
This is not free of consequence and you should hear it before you set one up. The scan now goes to your origin first and to us second, so if your origin is down, the printed code is down · and there is nothing we can do about that from our side. A DNS-level rescue avoids it entirely, and an edge rule at a CDN comes close, because both answer before your application is ever involved.
The bigger risk is quieter. That redirect lives in your infrastructure, and in a year nobody will remember it is load-bearing · a site rebuild drops the rule and a code on physical packaging starts landing nowhere, with no error anywhere for anyone to see. So we keep checking it, every day, and email you the moment it stops reaching us. Watching for that is the actual product here. The redirect was the easy half.
also free: read what is in a code · the generator · static vs dynamic, in full