Website QR codes
Connect print to your website
Turn a website address into a scan-ready link for packaging, posters and business cards. Use a complete HTTPS address and a page that works well on a phone.
Make it useful from the first scan.
A static website code stores your URL directly. Its destination cannot be edited after printing. For campaigns that change, create a managed code in your workspace and update its destination there.
Choose the link that should survive the print run
A website QR image carries an address from a physical object to a browser. Start with the exact page a visitor needs, rather than sending everyone to a homepage. A product instruction label should open instructions; an appointment card should open booking information. Use a complete HTTPS address and visit it on a phone while signed out. A destination that works only for your staff account is not ready for public printing.
A static code contains the address itself. Changing your website content at that address is possible, but changing the encoded address requires a new image. A managed code instead uses a redirect maintained in the workspace. This extra dependency is useful when a campaign destination may move. Keep ownership of both the workspace and the destination clear, particularly when an agency hands a campaign to a client.
Long addresses usually produce denser symbols. Avoid unnecessary tracking parameters, but do not remove parameters that the destination actually requires. Keep a generous blank border and strong dark-on-light contrast. Export SVG when a designer needs to scale the artwork; use a sufficiently large PNG for a document workflow. Never assume that a code which scans on your monitor will scan from a glossy printed label. Test the final physical sample, including any laminate, folds and surrounding artwork.
A worked example
A bicycle workshop prints a maintenance card linking to its brake adjustment guide. The team opens the guide without signing in, checks that the diagrams fit a narrow screen and scans a paper proof from two phones. Because the guide is moving during a website redesign, they choose a managed destination and record who will update it. After the move they change the destination, then scan the original card again. The printed card remains the test artifact throughout the handover.
Common mistakes to avoid
- Sending a specific campaign to an unrelated homepage.
- Cropping the blank border to make the artwork fit.
- Printing a staff-only preview URL.
Prepare, test, then publish.
- Choose the destination and check its details.
- Generate your code and preserve its white border.
- Test the artwork at the intended size, on a real phone.
Keep an accessible alternative such as a short written website address alongside the code. A QR image should make information easier to reach.
Frequently asked questions
Can I edit a static code?
The encoded URL cannot change. You can update the page served at that URL if you control it; otherwise create a new image or use a managed workflow before printing.
How big should it be?
There is no universal size. Density, camera distance, material and lighting all matter. Start with a readable paper proof and increase the size until your intended audience can scan comfortably.
Does a static code count scans?
This generator does not track static scans. Your destination website may have its own analytics, which should be explained by its operator.