FAQ
QRViz is designed for creating static QR codes in the browser without the overhead of a complex dashboard. This FAQ explains what the generator does, what it does not do, how exports work, and which limitations matter before you publish or print a QR code.
This page answers the most important questions about how QRViz works in practice: what kind of QR codes it creates, how local uploads behave, what happens during export, and what you should verify before using a QR code in the real world.
It is meant to help you avoid common misunderstandings before you publish, print, or share a code.
This FAQ is useful for anyone creating QR codes for links, contact cards, Wi-Fi credentials, PDFs, menus, packaging, posters, events, and other stable destinations.
It is especially helpful if you want to understand the limitations of static QR codes before relying on them in print or production.
No. QRViz creates static QR codes. It does not manage redirect rules, scan analytics, or changes to the destination after the code has been published or printed.
A static QR code points directly to the final data or destination encoded in the code itself. That makes its behavior simple and predictable, but it also means you cannot change the destination later without generating a new code.
No. QRViz lets you create and export a QR code without turning the process into an account-based dashboard.
No. Uploaded logos stay in the browser and are used only for local preview and export. They are not part of a server-side upload flow.
Yes. The generator stores its configuration in the URL, so you can share the same QR type and design settings with someone else. Uploaded logos are not included in the shareable link.
No. Because these are static QR codes, the destination is fixed once the code is created. If you need to change the destination later, you will need to create and publish a new QR code.
No. PDF export places a high-quality raster image inside the PDF. If you need a vector result for scaling or print workflows, use SVG instead.
That depends on your workflow, but SVG is usually the safer choice when you need a vector file that scales cleanly. PDF can still be useful, but it does not preserve the QR code as a true vector in this export flow.
Often, yes, but only if the code remains easy to scan. The logo should not take up too much space, contrast should remain strong, and the final result should be tested on real phones before publishing or printing.
Test the final exported file, not just the preview. Make sure the code scans on real devices, the destination opens correctly on mobile, the size is appropriate for the surface, and the contrast remains strong in the real environment where the QR code will be used.
A static QR code is a good fit when the destination is stable and the expected result after scanning is clear. Good examples include website links, Wi-Fi credentials, contact cards, PDF files, menu pages, event details, and other destinations that do not need to be edited later.
If you need scan analytics, editable destinations after printing, redirect control, or campaign management across many codes, a dynamic QR platform may be a better fit. QRViz is intentionally focused on the static workflow.