The short answer
A static QR code stores its destination directly in the pattern and cannot be changed after creation. A dynamic QR code points to a redirect URL, so its destination can be updated later.
Static codes: direct and fixed
A static code is a good fit for content that is unlikely to change, such as plain text, Wi-Fi details, or a permanent URL you control. The code itself contains the encoded information, so it can work without a redirect service for URL changes.
The trade-off is that the destination is fixed. If a URL changes, the printed code cannot be edited; you need to generate and distribute a replacement. Static QR codes also do not provide redirect-based scan analytics by themselves.
Dynamic codes: editable destinations
A dynamic code points to a redirect URL. The redirect service then sends visitors to the current destination. When the campaign page changes, you can update the destination while keeping the same printed pattern in circulation.
Dynamic codes are useful for menus, event signage, packaging, and campaigns where details may change or where scan activity should be measured. Their redirect domain and service must remain available, so keep account ownership and renewal details current.
Make the decision before production
Ask whether the destination could change, whether scans need to be measured, and whether a third-party redirect dependency is acceptable for the life of the printed material. Consider how long the material will remain in use and who will maintain the destination.
If you use a dynamic code, record the intended destination, owner, and campaign. If you use a static code, verify the final URL carefully before export because edits will require replacing the code.
WORKED EXAMPLE
- Static flow
- QR pattern → fixed destination
- Dynamic flow
- QR pattern → redirect URL → current destination
A repeatable workflow
- 1
Decide if the destination is fixed
If it must remain editable, choose a dynamic code. If the encoded information is final and simple, a static code may fit.
- 2
Choose the payload
Select the destination or information type, then confirm that it matches the campaign and audience.
- 3
Test before distribution
Scan the exported file from the intended distance and confirm the final visitor experience.
Before you publish
- Choose based on whether the destination may change
- Record who owns the redirect destination
- Test the final code and visitor flow