Free URL QR Code Generator

The URL QR is the backbone of every print-to-digital campaign that's ever worked. Someone scans it, the OS sees a web URL, the default browser opens the page. There's no platform layer in between, no decoder app to install, no proprietary scheme. It's the single most reliable QR type and the one that runs unchanged on a 2015 Galaxy S6 or a 2026 iPhone 17.

EZQR generates URL QRs free. Paste your HTTPS link, brand the code with your colors and logo, download PNG, SVG, or PDF. No watermark on any plan including the free tier, no signup wall, no expiration. The QR encodes the URL directly into the pattern, so the link works whether EZQR exists tomorrow or not, that's how static QR codes work everywhere, not a feature we built.

For links that need to change after printing, a landing page that'll get redesigned, a campaign URL that'll rotate, a destination you might move to a new domain. Use a dynamic QR on the $5/mo Lite plan. The printed code stays the same; you repoint the destination from the dashboard. One reprint avoided pays for the year.

Almost every "QR code for X" is a URL code underneath. There is no separate format for a Facebook code or a Spotify code. You encode the platform's own web address and the phone does the rest, opening the app if it is installed and the web view if it is not.

What trips people up is which address to encode. The one in the browser bar is often not the one you want, and a few platforms hand you a proprietary code that only reads inside their own app.

A sizeable share of people searching for a platform QR code are not trying to make one at all. They are trying to sign in by scanning. That flow runs the opposite way round. The service puts a short-lived, single-use code on the screen in front of you, and the app already signed in on your phone reads it and approves the session. The code is a token the service issued and will check against its own records seconds later. Nothing a generator produces can stand in for it, which is why there is no tool here, or anywhere, that makes one.

It also matters that the flow does not exist everywhere people look for it. Two of the platforms most often searched alongside "log in with QR" do not offer it at all.

A URL code looks like the simplest thing on this site, and the part worth understanding is what the phone does with it.

The camera decodes the text, sees it begins https://, and hands it to the operating system. The OS checks whether an installed app has claimed that domain (Apple calls this a Universal Link, Android an App Link) and if one has, the app opens directly at that content. If not, the default browser opens the page. You do not choose between those two outcomes; the platform does, based on what the scanner has installed.

Three consequences that matter before you print:

• Always include https://. Without a scheme the code is plain text, so the phone displays the characters and opens nothing. This is the single most common broken URL code.
• The link must work logged out. A scanner is a stranger with no session on your site. Anything behind a login, a paywall or an internal network resolves to a sign-in screen for them.
• Shorter is physically smaller. The encoded string sets the grid size, so a long URL with tracking parameters produces a denser code that has to be printed wider. The QR code examples page shows the module counts for each length.

Strip the platform's parameters, then decide about your own. UTMs are worth having, without them every scan lands in your analytics as direct traffic and the campaign reads as a failure. But they are characters, and characters are modules. We encoded the same landing page with each layer added, at error correction M, and measured the grid.