The practical answer
Static and dynamic QR images both contain fixed information. A dynamic code points to a managed redirect, so its final destination can be edited. A static link can still show updated webpage content when the webpage keeps the same address.
Choose by what needs to change
| Your situation | Suitable approach | Keep in mind |
|---|---|---|
| Update dishes at the same /menu page | A direct static link can be enough | Maintain the domain and that page address. |
| Move between booking providers | A managed dynamic link may help | The redirect provider and your account must remain available. |
| Share a WiFi password or contact fields | A static WiFi or vCard payload | Changing embedded details requires a new printed code. |
| Need campaign reporting for a team | Assess a provider with those specific features | Our current dynamic tool does not include scan reports or team permissions. |
The pattern always contains fixed information
A printed QR pattern cannot change. The useful distinction is what is encoded. A static website code typically contains the destination address directly. A dynamic service encodes an intermediate address and changes where that address redirects. Both patterns are fixed; the second has an editable step behind it.
Static does not mean the linked page is frozen
Imagine a café prints a code for example.com.au/menu. The café can update the dishes at that address without changing the printed image. It cannot make that image encode a different address. If you own the domain, you may also manage a redirect at the encoded path. You are then responsible for keeping that domain and redirect working.
Dynamic adds flexibility and a dependency
A managed redirect can let a team change destinations and access scan reports. Availability, fees, limits, data collection and what happens after cancellation vary by provider. Read the current plan terms rather than assuming all dynamic codes expire or all paid plans behave alike. Check whether you can use your own domain and export your destination list.
A request count is not a people count
Redirect analytics may include repeated scans, browser previews, bots or security checks. A static destination page may also record its own visits. Avoid treating either figure as an exact count of unique people. Decide what you want to learn and explain any tracking to the people using the code.
Choose for ownership and maintenance
For a business card linking to a homepage you control, a direct static code is often sufficient. For packaging distributed for several years, an editable destination may be useful, but only if someone will maintain the redirect and account. The cheaper option on day one is not necessarily easier to maintain over the life of the artwork.
What this site provides
Our static tools work without an account. The free dynamic generator offers 10 editable links per account, with pause and resume and printable downloads. Dynamic links rely on this service staying available. Scan analytics and team permissions are not included. Sign in with Google, a private email link or a username and password. Existing username accounts can link Google or email in Account settings; keep the recovery key for an unlinked username account.
Example: moving a menu between services
A café has printed a direct QR for a menu on one platform. Moving the PDF to another platform does not change the old QR. If the old URL cannot be maintained or redirected, the café must replace that print. Had the café created a managed dynamic link first, it could change the destination in the account. This is a planning choice to make before distribution, not a way to rewrite an existing physical pattern.
Illustrative example, not a customer case study.
A checklist to use on your next code
- Decode a sample and record the actual URL in the pattern.
- Identify who controls the encoded domain.
- Check access recovery, limits and what happens if the service changes.
- Keep a list linking code names, destinations and physical placements.