Do QR Codes Expire? Static, Dynamic, and Permanent QR Codes Explained

QR codes do not all expire for the same reason. A static QR code can keep scanning for as long as the printed pattern is readable, but the page, file, or phone number inside it can still become useless. A dynamic QR code can keep the same printed pattern while the destination changes, but it depends on a redirect service, account, domain, billing status, and platform rules.

That difference matters when the QR code is going on something physical: packaging, menus, business cards, signs, direct mail, manuals, equipment labels, product inserts, stickers, event badges, or anything else that may stay in circulation after the first campaign is over.

Use this guide to understand what "permanent QR code" can honestly mean, what makes QR codes stop working, and how to make a QR code that does not expire in the practical sense: the scan path stays controlled, documented, and recoverable.

The short answer

A QR code pattern does not contain a built-in expiry date. If the code is printed clearly and the data inside it is still useful, a scanner can keep reading it.

But the scan can fail for reasons outside the square:

• The destination page is deleted.
• A PDF, file share, or form link expires.
• A domain is not renewed.
• A short link is disabled.
• A dynamic QR trial or account ends.
• A provider pauses the redirect because of billing, abuse, or plan limits.
• The printed code is damaged, cropped, too small, or low contrast.

So the real answer is:

• Static QR codes do not expire because of the QR provider, but the encoded destination can break.
• Dynamic QR codes can be long-lived, but only while the redirect link remains active and controlled.
• A permanent QR code is usually an operations decision, not just a generator setting.

If you are still deciding whether you need an editable destination, start with how to create a dynamic QR code. This article focuses on expiration risk and how to avoid orphaned printed codes.

Static QR codes: the pattern can last, the destination might not

A static QR code stores the final data directly in the pattern. If it encodes https://example.com/menu, every scanner reads that URL from the squares. There is no dashboard, account, redirect server, scan analytics, or subscription in the middle.

That is why static QR codes are often described as permanent. The generator is not needed after export. If you download the file, keep the artwork, and print it correctly, the QR image itself can keep scanning.

The catch is that the QR code only preserves the data you encoded. It does not guarantee that the destination will still be useful later.

Common static QR problems:

• A restaurant prints a static PDF menu link, then replaces the PDF with a new file path.
• A business card points to a personal profile that gets renamed.
• A product insert links to a help article that is moved during a website rebuild.
• A flyer points to a form that closes after the event.
• A code uses a third-party short link that the team no longer controls.

In each case, the printed QR code still works technically. It scans. It opens the encoded destination. The problem is that the destination is no longer the right place.

Static is safest when the encoded data is stable by design: a permanent website URL on a domain you own, a Wi-Fi network credential, a vCard whose details are unlikely to change, a plain text instruction, or another low-change destination. For campaign links, menus, files, and forms, static can become fragile because the physical code cannot be edited after printing.

Dynamic QR codes: the printed code can stay, the service must stay active

A dynamic QR code stores a short redirect URL instead of the final destination. In DuoQR, the printed code points to a managed r.duoqr.com URL. When someone scans it, the resolver checks the current destination and sends the scanner there.

That model solves the biggest static problem: you can update the destination without changing the printed QR pattern. If a menu URL changes, a campaign page moves, or a typo slips into the first destination, you update the code in the dashboard and scan the same printed square again.

Dynamic QR codes are useful because they separate two things:

• The printed asset, which is hard to replace.
• The destination, which may change during normal work.

But dynamic also adds dependencies. The first URL in the scan path must keep resolving. The account must remain accessible. The provider must keep the code active. The redirect domain must be trusted and maintained. If the platform has trial, scan, billing, or policy limits, those limits can affect a printed code.

Before you trust a dynamic QR code for long-lived print, check:

• Does the code keep working after the free trial or launch period?
• What happens if the account is downgraded, deleted, or unpaid?
• Can the destination still be edited later?
• Who owns the dashboard record?
• Can another team member access it if the creator leaves?
• Is the short domain stable enough for your audience?
• Can you pause or retire the code intentionally instead of leaving it broken?

For a setup walkthrough, read how to create a dynamic QR code. For printed codes that already need an update, use the guide to changing a QR link after printing.

Why free QR codes sometimes "expire"

People often search "do QR codes expire" after a free QR code stops working. The failure is usually not inside the QR standard. It is usually the business model or link lifecycle around the code.

A free static QR code should not depend on the generator after export. If the generated code directly encodes your final URL, the provider cannot expire that image later. The risk is the destination you chose.

A free dynamic QR code is different. It often depends on the provider's short link. Some tools let you create a dynamic code free, then limit editability, analytics, scans, export quality, or continued activation. Others create trial redirects that are not meant to be permanent unless you keep an account or plan active.

Before printing a free dynamic code, prove the lifecycle:

1. Download the file you plan to print.
2. Scan it from a phone.
3. Change the destination in the dashboard.
4. Scan the same downloaded file again.
5. Confirm it opens the new destination.
6. Check the account for trial, expiry, scan limit, watermark, billing, or upgrade warnings.
7. Document who owns the code and how to keep it active.

If you cannot answer those questions, do not put the code on expensive print. The guide to free QR code generator hidden costs has a broader checklist for evaluating free tools before you rely on them.

What "permanent QR code" should mean

"Permanent QR code" is not a magic type. It is a promise about the full scan path.

For a static QR code, permanence means:

• The printed pattern is scannable.
• The encoded data is stable.
• The destination is on a domain or system you control.
• The page, path, file, or contact details will be maintained.
• You have a recovery plan if the destination needs to move.

For a dynamic QR code, permanence means:

• The printed short link remains active.
• The QR platform keeps resolving the code.
• The account, billing, and workspace access are maintained.
• The destination can be changed without reprinting.
• Someone owns the code operationally after launch.
• The code can be paused, redirected, or retired on purpose.

The strongest pattern for long-lived public materials is often: a stable printed QR code, a controlled first URL, clear ownership, and a destination that can be updated when reality changes.

That first URL can be a static URL on your own domain, a dynamic QR short link from a provider you trust, or a branded short domain your team controls. The important part is that the first hop is not a mystery link nobody can manage later.

How to create a QR code that does not expire in practice

Start with the surface, not the generator.

If the QR code is going on a disposable handout, a temporary classroom note, or an internal test, a static code may be enough. If it is going on packaging, signage, a menu, an asset label, a business card, direct mail, or anything that may stay in the world, plan for the destination lifecycle.

Use this workflow:

1. Decide what the scanner should get today.
2. Decide what might change later: URL, offer, file, language, location, owner, analytics, or campaign.
3. Choose static only if the destination is stable and low-risk.
4. Choose dynamic if you need editability, scan analytics, pausing, or recovery from mistakes.
5. Use a URL or redirect domain your audience can trust.
6. Name the code by placement, such as box-insert-setup or front-window-menu.
7. Download a print-ready file.
8. Scan the downloaded file before it enters artwork.
9. Put the code into the final design and scan again at real size.
10. Save the owner, destination, print date, and update process somewhere your team can find later.

If the QR code points to a website URL, make the QR code from a clean URL. Avoid staging links, preview URLs, expiring file shares, and third-party short links unless you intentionally want that dependency.

If the code is going to print, use the high-resolution QR code print guide. A permanent destination will not help if the printed square is too small, low contrast, cropped, or damaged.

When static is the better permanent choice

Dynamic is not automatically better. Sometimes the best way to make a QR code that does not expire is to remove the middle service.

Choose static when:

• The encoded data is meant to be permanent.
• You do not need scan analytics.
• You do not need to edit the destination later.
• The QR code may need to work without relying on a redirect provider.
• The destination is controlled by you and unlikely to move.

Examples:

• A QR code for a permanent public homepage.
• A Wi-Fi QR code for a venue card.
• A vCard for a long-term role or generic office contact.
• A plain text equipment note.
• A label that points to a stable documentation path on your own domain.

Even then, avoid fragile destinations. Do not encode a temporary Google Drive link, expiring form link, vendor short URL, campaign preview, or page path that may disappear during the next website cleanup. Static QR codes are only as permanent as the data inside them.

When dynamic is the safer long-term choice

Dynamic is safer when the printed surface may outlive the current destination.

Choose dynamic when:

• The QR code is expensive or slow to replace.
• The destination might change.
• The code supports a campaign, menu, product, event, or operational flow.
• You need scan analytics.
• You may need to pause, reroute, or retire the code later.
• Several teams need access to manage the code.

Examples:

• Restaurant table tents and window signs.
• Product inserts and setup cards.
• Direct mail campaigns.
• Retail signage.
• Event badges and booth materials.
• Property signs.
• Customer support stickers.
• Packaging that may remain in warehouses or homes.

In DuoQR, that means creating the code as dynamic before printing, keeping the printed r.duoqr.com pattern stable, and managing the destination in the dashboard. You can create a DuoQR account when the job requires editable destinations, scan visibility, and a safer recovery path after print.

Expiration checklist before you print

Before you call a QR code permanent, answer these questions:

• Is it static or dynamic?
• What is the first URL or data value inside the code?
• Who controls that first URL?
• What happens if the destination page moves?
• What happens if the account owner leaves?
• Are there trial, billing, scan, or plan limits?
• Does the code depend on a third-party file share or short link?
• Can the destination be edited without reprinting?
• Can the code be paused or retired intentionally?
• Is the exported file print-ready?
• Has someone scanned the final artwork at real size?

The practical answer to "do QR codes expire?" is not just yes or no. The QR pattern can be stable while the destination fails. A dynamic redirect can be editable while the account behind it is neglected. A static code can be permanent when it points to a maintained URL you own.

Treat the QR code as a small piece of infrastructure. Pick the right type, control the first hop, test the print file, and leave enough ownership context for the person who has to maintain it next year.