What to compare in a QR code generator
A useful comparison starts with the job the code must do. A fixed URL QR sends people to one address. A dynamic QR sends them through a managed redirect. A Wallet card can present contact details for saving to a supported wallet or open a hosted website. These are different destinations, not interchangeable labels.
Next, ask how content will change and whether the physical code can be reprinted. Separate editing at a stable URL from changing the destination itself. Check analytics history, dynamic-code limits and website capacity. The QREasy QR code generators show the available creation options, while information about QREasy explains the broader platform.
- Destination: fixed URL, managed redirect or Wallet journey
- Content: webpage, PDF, contact card or embedded vCard
- Maintenance: content updates versus destination changes
- Reporting: amount of analytics history retained
- Capacity: websites, pages and QR-code allowances
Static and dynamic QR codes compared
A static URL QR encodes one fixed address. The content served at that address can still change without changing or reprinting the code. For example, a QREasy-hosted webpage can be updated, or a PDF can be replaced at the same URL. Only a change to the address encoded in the QR requires a new static code.
A dynamic QR encodes a managed redirect, so its final destination can be changed without reprinting, subject to the plan’s limits. This is useful when several printed codes must point to campaigns, menus or contact pages that will rotate over time. It adds a layer of redirection rather than embedding the final address directly.
Neither format guarantees scanning on every device, and neither should be confused with embedded static vCard data. A static URL QR that opens a profile page is not the same as a QR containing the contact record itself. The distinction is covered in the guide to static, dynamic and embedded vCard codes.
- Choose static when the URL stays fixed and content can be updated in place.
- Choose dynamic when the final destination must change after printing.
- Choose Wallet when recipients should save contact details or open a hosted site.
What content can a QR code link to?
The URL destination can be a QREasy-hosted website or a PDF available at a stable address. Editing a hosted page does not by itself require a dynamic QR. If you publish a new PDF at the same address, a static QR can continue to work. If the PDF must live at a new address, you need either a dynamic redirect or a replacement static code.
Wallet cards cover another journey. QREasy supports digital business cards for Apple Wallet and Google Wallet. Recipients can review and save contact details, or open a website created with QREasy when the card is website-linked. Start from the available website templates when planning a compact hosted site for that journey.
- Hosted website: editable content at one URL
- PDF: replace the file at the same URL
- Contact Wallet card: review and save contact details
- Website-linked Wallet card: open a QREasy-hosted website
How the QREasy plans compare
QREasy Free includes one website with up to one page, unlimited static QR codes, one dynamic QR code and seven days of analytics history. Contact Wallet cards are included. Website-linked Wallet cards are not available on Free; they require Lite SME or Business. The listed price is EUR 0.00 monthly or annually.
Lite SME includes three websites with up to four pages each, 50 dynamic QR codes, unlimited static QR codes and 90 days of analytics history. It also includes website-linked Wallet cards. The listed price is EUR 2.99 monthly or EUR 28.70 annually.
Business includes 33 websites with up to 10 pages each, 357 dynamic QR codes, unlimited static QR codes and 90 days of analytics history, plus website-linked Wallet cards. Its listed price is EUR 9.99 monthly or EUR 95.90 annually. Compare these allowances with the QREasy plans before committing.
Choose by editing needs and destination changes
If the code must point to a stable page that you can edit, start with a static URL QR. The page can be refreshed or replaced without touching the printed code. This also avoids using one of the dynamic-code allowances when the destination itself is unlikely to move.
If several printed pieces must lead to different destinations at different times, a dynamic QR is the better fit. Update the managed redirect instead of reprinting every piece; the plan's dynamic-code limit determines how many dynamic codes you can create, not how often a destination can be changed. For larger collections of sites and pages, the Business allowance may fit better than Lite SME.
- Edit the page but keep the URL: use a static QR
- Change the final URL: use a dynamic QR
- Save contact details in Apple Wallet or Google Wallet: use a Wallet card
- Open a hosted site from a Wallet card: choose Lite SME or Business
What to check before generating and distributing
Before distributing, open the exact destination on the phones and scanning apps your audience is likely to use. Check that the page or file loads, that the call to action is clear and that the Wallet journey behaves as intended. Neither QR type guarantees scanning on every device, so practical testing matters.
Then test the physical placement: check size, lighting and the surface around the code, and make sure your team can replace it if the destination fails. Keep a record of the QR type, encoded URL or redirect, linked content and last review date. For dynamic codes, monitor destination changes and available plan limits.
- Destination and permissions work
- Content loads without an unwanted redirect
- Static URL or dynamic redirect matches the future plan
- Printed code is readable in the intended setting
- Replacement and ownership details are recorded
