What can change after a QR code is printed?
The useful distinction is what the image contains and which service a scan depends on. “Saved,” “protected,” and “dynamic” describe different behaviors; one does not imply the others.
The printed payload does not change
If a QR contains a phone number, Wi-Fi password, or contact name, changing the source form later does not change the paper. You need a new image when those values change. A downloaded file behaves the same way.
A static URL code contains an address. The page at that address can still change: a restaurant can edit its menu page while preserving its URL. This does not require an editable QR service. The constraint is keeping that address available and under appropriate control.
A redirect adds an editable step
With a redirect-based code, the image holds an intermediate address and that service chooses the final destination. That can let an operator change a destination without reprinting. It also introduces a dependency: if the redirect stops resolving, the print stops reaching the destination even if the final site is healthy.
This application does not operate an editable redirect service or track visits through one. It cannot report how often someone scans a paper code. The Local QR Activity page counts recently recorded downloads in your browser, not people opening a destination.
What saved and hosted features do here
Saved Projects stores a name, local alias, payload, and colors on this device. New project creates another record; Update project changes the active record. Neither operation changes an old print. The alias is an organization label, not a short link.
Digital business cards and multi-link pages use this site as a display page. Their content is in the URL query string, not in an editable hosted account. They require the site to be available when opened, and anyone with the URL can read that content.
Move saved projects to another browser
Saved Projects includes Backup and restore projects. Export backup downloads a JSON file containing saved project records; it does not include download history or create cloud sync. QR values in the file are unencrypted, including any Wi-Fi passwords or contact details. Keep it in private storage and avoid sending it as a public attachment.
Duplicate detection uses project IDs, not names or destination URLs. If a backup contains an older version of an existing project, Keep existing (skip duplicates) preserves your current record, Replace existing with backup version restores the older record, and Keep both as separate projects creates another copy. For example, importing a two-project backup into a browser already containing those two IDs leaves two projects with Skip or Replace, and four with Keep both.
- On the original browser, open Saved Projects and select Export backup. Export the destination browser’s existing projects too before replacing anything.
- On the destination browser, select Choose backup file and open the exported JSON. Files must be 2 MB or smaller. Review the names and duplicate count in Import preview; choosing the file alone does not restore it.
- Choose the Duplicate projects policy, then select Import projects. The final collection cannot exceed 50 projects. If an import is rejected for capacity, choose Skip where appropriate or deliberately remove unneeded records after keeping a backup; the tool does not silently discard them.
- After importing or cancelling, keyboard focus returns to Choose backup file. Check the resulting records and reload the page to confirm they remain. Changes to restored projects still do not update previously printed codes.
Protected links are a separate tradeoff
The protected tool encrypts a destination in the URL fragment. The unlock page derives a key from the supplied password and decrypts the value locally. The password is not included in the code. Keep it through a separate channel if the intended recipient needs it.
An optional expiry is checked by the visitor’s browser using its clock. It is not a server-side restriction, and a destination already copied can still be opened outside the unlock page. Use the destination service’s own access controls when you need revocation or authorization.
If something goes wrong
| What you see | What to check |
|---|---|
| A saved alias does not open as a short URL | Aliases are local labels. Encode an actual URL you control if you need an address people can open. |
| Local activity differs between computers | Each browser has separate records. There is no cloud sync or real-world scan counter. |
| An expired protected destination still works directly | Expiry governs the unlock page, not the destination website. Enforce access at the destination when that is required. |
About this content: written for QR Code Generator Tools with AI assistance, using the current implementation and the references shown where relevant. Examples are illustrative. Automated tests cover selected browser workflows; they are not a certification for every device or print material. Read the testing and editorial scope or report a correction.