No. Static QR codes never expire. The URL is encoded directly into the image; as long as your URL is live, the QR works.

Not from a pure static QR. If you want analytics, point the QR at a URL on your own domain with UTM parameters — the destination's analytics captures the scan.

Can I edit the destination later?

Not without reprinting. To change destinations, point the QR at a redirect URL on your own site and update the redirect target on the server.

Does the URL have to start with https?

Yes, ideally. Modern browsers show a warning for plain http, and some corporate networks block non-https destinations.

How long can the URL be?

QR codes handle up to ~2900 alphanumeric characters, but practical scanning above 200 characters requires larger prints. Keep URLs short for posters and business cards.

Will the QR still work in a couple of years?

Yes. There is no server, no shortlink, no expiry — the QR keeps working as long as the URL stays live.

Can I use an IP address instead of a domain?

Yes — the QR encodes whatever you put in. Domains are still better for user trust and moving servers later.

Does the destination site see the scan?

It sees the visit like any other browser hit — same referrer rules and analytics as if the user typed the URL themselves.

URL QR Code Generator

Turn any web link into a static QR code that works forever. No account, no expiry, no tracking — just your URL encoded into a clean QR you can print or share anywhere.

Your files never leave your device. No upload. No sign-up.

Running locally

A URL QR code encodes any web address directly into the QR image. When scanned, the phone opens the URL in the default browser — one tap, no redirect, no expiry. Because the URL is baked into the pixels (not a shortlink pointing to a tracking server), the QR keeps working forever as long as the destination stays live, and no one sees the scan except the destination's own analytics. The trade-off is that the destination is fixed at print time: if the page moves, the code is dead. The mitigation is to point it at a URL you control and redirect server-side rather than at a third-party shortener that could shut down. Keep the address short — every character adds modules, and dropping https:// plus tracking parameters can take a code from a dense 45×45 grid to a sparse 29×29 that scans from further away and prints smaller.

Website URL

QR color

#1E293B

Background

#FFFFFF

Generic QR generator

How does a URL QR code work?

This is the simplest QR type: the payload is the raw URL string, encoded using standard QR alphanumeric or byte mode. Any modern smartphone camera recognises URLs and offers the ‘Open in Safari/Chrome’ prompt automatically. Length matters — under 40 characters yields a small dense-friendly QR that scans from ~1 cm across; 100+ character URLs need larger prints or bigger error correction to stay reliable. If you also want analytics, point the QR at a URL on your own domain that redirects with UTM parameters — you keep control of tracking without depending on a third-party shortlink service that could shut down.

Common mistakes and limitations of URL QR codes

Static QRs can't be edited after printing — if the destination URL changes, the QR is dead. There's no built-in tracking either. Very long URLs (200+ characters) produce dense QRs that are hard to scan at print sizes below ~4 cm; consider a short URL on your own domain. Some Android launchers still open non-https links with a security warning, so always encode the fully qualified https:// form.

Where URL QR codes get used in practice

This is the most widely deployed QR type and the one most often deployed badly. Packaging, menus, museum labels, posters, event signage, product manuals and payment terminals all use URL QRs, and the difference between the ones that work and the ones that do not is almost always whether the destination is mobile-appropriate. Restaurant menus were the mass deployment that taught the industry this: a QR pointing at a PDF menu is technically functional and practically miserable on a phone, whereas one pointing at a responsive page works. The operational discipline that matters is owning the redirect. Encoding a URL on your own domain that redirects to the real destination costs one extra hop and buys two things a raw URL cannot: the ability to change the target after the artwork is printed, and analytics on scans. Organisations that skip this end up reprinting when a campaign page moves. The related discipline is keeping the printed URL short, because payload length directly determines how small the code can be printed and still scan.

Printing a URL QR code so it actually scans

URL payload length varies enormously and it is the single biggest factor in whether a printed QR works. A 25-character domain produces a sparse version 2 code readable from 1.5 cm; a 200-character URL with UTM parameters produces a version 12 or higher code with fine modules that needs 4 cm or more and good print quality. This is a strong argument for using a short URL on your own domain rather than a long tracked one. A redirect on your own server keeps the printed code sparse and robust while still letting you attach analytics and change the destination later — the practical answer to the fact that static QRs cannot be edited. For outdoor and large-format use, apply the ten-to-one rule: scan distance is roughly ten times the code's width. A billboard QR intended to be scanned from five metres needs to be about 50 cm across, which is far larger than most designs allow for. If that is not feasible, a short memorable URL printed as text often outperforms an undersized QR.

Questions8

URL QR code FAQ

Will this QR expire?: No. Static QR codes never expire. The URL is encoded directly into the image; as long as your URL is live, the QR works.
Can I track scans?: Not from a pure static QR. If you want analytics, point the QR at a URL on your own domain with UTM parameters — the destination's analytics captures the scan.
Can I edit the destination later?: Not without reprinting. To change destinations, point the QR at a redirect URL on your own site and update the redirect target on the server.
Does the URL have to start with https?: Yes, ideally. Modern browsers show a warning for plain http, and some corporate networks block non-https destinations.
How long can the URL be?: QR codes handle up to ~2900 alphanumeric characters, but practical scanning above 200 characters requires larger prints. Keep URLs short for posters and business cards.
Will the QR still work in a couple of years?: Yes. There is no server, no shortlink, no expiry — the QR keeps working as long as the URL stays live.
Can I use an IP address instead of a domain?: Yes — the QR encodes whatever you put in. Domains are still better for user trust and moving servers later.
Does the destination site see the scan?: It sees the visit like any other browser hit — same referrer rules and analytics as if the user typed the URL themselves.