The short answer
A standards-compliant static QR code does not contain a timer, renewal date, or account status. Its black-and-light pattern represents data. If that pattern remains readable, scanners can continue decoding the same data years later.
What happens after decoding is a separate question. A URL can lead to an expired domain, deleted page, private file, or discontinued service. A managed or dynamic QR provider can disable its redirect. Printed material can fade or become damaged. People often describe all of those failures as an expired QR code, even though the underlying causes differ.
Static codes do not depend on a QR provider
A static URL QR code stores the destination itself. When someone scans it, the scanner reads that address and offers to open it. The generator does not need to stay online after the file is downloaded, and there is no subscription check built into the symbol.
Static does not mean the destination is permanent. If you encode https://example.com/menu and later delete that page, the QR code still decodes correctly—it simply points to a page that no longer works. Keeping the same stable URL while updating its content is the most practical way to preserve long-lived printed codes.
Dynamic codes rely on a redirect service
A dynamic QR code usually stores a short URL controlled by a service provider. The provider receives the scan and redirects the visitor to the current destination selected in an account dashboard. That design can support destination changes and scan analytics, but the printed code depends on the redirect domain, account, plan, and service continuing to work.
If a trial ends, a subscription lapses, a provider closes, or a redirect is suspended, the code may stop reaching its target. The QR pattern still decodes; the managed link is what failed. Before using a dynamic product for permanent signage, understand its retention, pricing, export, and redirect policies.
Five reasons a QR code appears to expire
Most failures can be traced to the destination, an intermediary, or the physical symbol. Separating those layers makes troubleshooting much faster.
- The encoded domain expired or its DNS configuration changed.
- The page, PDF, profile, or shared file was removed or made private.
- A dynamic redirect account or plan became inactive.
- The print faded, scratched, folded, or lost contrast against its background.
- The code was printed too small or altered in a way that damaged modules or quiet space.
How to build for a long lifespan
Use a domain and URL path you control when possible. A stable address such as yourdomain.com/guide can remain constant while the content behind it changes. Avoid temporary file-sharing URLs, preview links, session-based pages, and destinations that require your personal login.
Keep the payload short, export SVG for professional print, preserve the four-module quiet zone, and choose materials suited to the environment. Maintain a simple inventory of permanent QR placements and test them on a schedule, especially after website migrations or domain changes.
- Use the final HTTPS URL and verify it in a private browser window.
- Prefer a stable page on a domain your organization controls.
- Redirect that stable page at your own web host if content must move.
- Keep source files and a record of the encoded payload.
- Re-scan permanent signs after web, hosting, or branding changes.
How to diagnose a code that stopped working
First, scan the code with a reader that displays the decoded content before opening it. If it cannot decode at all, try the original digital file; a successful digital scan points to print damage, size, contrast, or lighting. If the payload decodes, copy the URL into a browser and inspect the error.
A domain or page error needs a website fix. A permission screen needs a public-sharing change. A third-party redirect warning belongs to the dynamic provider. This layered check tells you whether the QR image must be replaced or the destination can be repaired without reprinting.
Put it into practice