You can make a working QR code for a website link in about two minutes: open the URL in Chrome, tap the three-dot menu, choose Share, then Create QR Code. Copy the image or use Download to save it as a PNG. Chrome generates the code on your device, so the destination never passes through a third-party tracker.

That last point matters more than most guides admit. The visible QR pattern is fixed at creation, but whether your printed code works in five years depends entirely on who controls the redirect behind it. Here's how every major path actually works.

Why Chrome's Built-In QR Generator Beats Most QR Websites

The fastest consumer route to a static code is already installed on your phone. Chrome 88 and later on iOS and Android places Create QR Code inside the share sheet β€” one tap past the three-dot menu β€” and the resulting image can be saved straight to your camera roll through the browser's Download or Save Image option.

What you get is a static QR code, meaning the URL is encoded directly into the pattern with no intermediate redirect. A phone camera pointed at it resolves the destination without any server answering on your behalf. For a restaurant menu, a shirt tag, or a flyer you'll reprint anyway, that's the right trade.

The limitation shows up in printing. Chrome's saved square tops out around 1,000 pixels wide, which is comfortable for a poster viewed at arm's length but soft on a 6-foot banner read from 20 feet away. Vector output matters at that scale, and Chrome doesn't offer SVG export.

The browser also refuses to encode anything that isn't a fully formed http or https address, which is a quiet benefit. Half the "my QR code doesn't work" complaints online trace back to a missing https:// prefix, and Chrome eliminates that failure by construction.

The 60-Second Chrome Quiz: Steps That Actually Match the Current Menus

Here's the exact path, in order, on a phone running current Chrome. The menu labels below are the ones you'll see today; Google reshuffled this around the Android 12 era and older screenshots mislabel it.

1: Open the website you want to encode so the address bar shows the final URL. 2: Tap the three-dot menu in the top-right corner. 3: Choose Share β€” not "Share with QR Code," which appears on some Android builds instead. 4: Tap Create QR Code in the share sheet. 5: Tap the QR image or the Download icon, then Save to your photos.

Failure handling, in order of likelihood: if Create QR Code is missing, your Chrome build predates version 88 β€” update through the Play Store or App Store. If the code scans to the wrong page, you were probably viewing a mobile variant; check the address bar rather than trusting the share preview. And if the saved image comes out blurry on a large print, that's the resolution ceiling described above, and it's your cue to switch tools.

Build a Static Code Fast at Any Free Generator Site

When you need a downloaded PNG at a specific pixel size or a format Chrome won't produce, a free generator site gets you there in under a minute. The workflow is identical across the major ones: paste the full URL including https://, choose the output format, then download.

Start at a generator like QR Code Monkey. Paste the address, pick PNG for screens, SVG for print, or JPG if a platform demands it. Set the size explicitly β€” 1,000 Γ— 1,000 pixels is safe for social avatars, and you want at least that for anything printed. Click the generate button, then download.

The difference between a static and dynamic code appears right here, at the choice screen. Static encoders write your URL straight into the pattern and typically finish in seconds with no account. Dynamic encoders give you a short redirect link and ask you to register, because the platform now sits between the scan and your site.

Free static generators rarely expire, but they also ask for nothing but the URL. If a tool demands an email before producing anything, you're on the dynamic path and you've just taken on a dependency. Close the tab and use another one.

Why Your "Free" Dynamic QR Code Expires and Static Ones Usually Don't

This is the risk nobody spells out clearly enough. A dynamic QR code contains a short platform URL β€” something like qrco.de/abc123 β€” and that short link is what actually resolves when someone scans. The platform owns the redirect, and the platform decides when it stops.

QR Code Generator's own pricing documentation states that trial codes stop working after 14 days, with the code deactivated after a seven-day grace period. The free tier of that same platform caps scans on its basic dynamic plan, and several competitors do the same. You picture a plaque in a hotel lobby; the platform pictures a subscription renewal.

The failure mode is ugly because it's slow. A dynamic code on a parked domain doesn't break loudly on day 15 β€” it keeps scanning fine, opens a browser, and then lands on an expired-campaign page or a payment prompt. If that code is etched into a sign, reprinted on 10,000 menus, or mounted at a trailhead, you're now paying whatever the platform asks, because replacing the physical thing costs more.

Static codes have the opposite profile: no expiry on most generators, no scan caps, no account, and no ability to edit the destination. That last part is the price of independence. A typo in a static code means a reprint β€” full stop.

Static or Dynamic: Pick With the Same Five Criteria on Both

The decision comes down to whether you need to change the destination after printing. That single question usually settles it, but the secondary criteria break ties.

Criterion Static code Dynamic code
Who hosts the redirect Nobody β€” URL encoded directly The QR platform's servers
Editable destination No, reprint required Yes, from a dashboard
Typical free lifespan No expiry on most free generators 14 days on QR Code Generator's trial; scan-capped on free tiers
Scan count and analytics None Yes, usually including device and location
Cost for a permanent code $0 on most free generators Recurring plan, price varies by platform
Failure risk Typo survives in print Platform shutdown or lapse kills the code

The verdict splits cleanly. Choose static if the destination won't change and the code will live longer than a campaign β€” signage, packaging, business cards, museum labels. Choose dynamic only if you'll genuinely need to swap the URL, and only if you're prepared to keep paying for as long as the code is in public.

One row deserves a caveat. Several boutique dynamic platforms have folded over the years, and when they do, every code pointing at their domain dies at once. Before you print a dynamic code on anything expensive, check whether the platform publishes a data-export or redirect-migration path. If it doesn't, treat the code as rented.

The 30% Rule That Keeps a Printed Code Scannable

Contrast governs whether a camera can read your code, and the threshold is unforgiving. Guidance from the QR spec β€” covered in detail by DenSO's technical explainer on QR code contrast β€” recommends a light module background near 100% reflectance and dark modules near 0%, effectively treating a 30% or better luminance difference as the floor for reliable scanning under normal light.

Concretely, that rules out the two designs people reach for first: a pastel foreground on white, and cream modules on a tan background. Both look elegant on a proof and fail under a phone camera in a dim hallway. Dark modules on a near-white background is the setting that survives.

Size is the second axis. There's no universal minimum pixel count, but physical dimensions dominate: a code printed at 1.5 centimeters square works at close range on packaging and fails on a poster meant to be read from 10 feet. Scale the printed size to the viewing distance, and keep at least four blank modules of quiet zone around the pattern β€” a border that designers routinely crop.

Two more settings you'll see at any generator, and what they mean: error correction at H level survives about 30% of the code being obscured, which is why a logo dropped in the center still scans, at the cost of a denser pattern that needs a bigger print. Version numbers run from 1 to 40 under the ISO/IEC 18004 standard; a plain website URL typically lands in the single digits, so spec sheets quoting "Version 40" describe a theoretical maximum, not your file.

Five Ways to Break a QR Code Before It Reaches Print

Most non-working QR codes trace back to a handful of causes, and each one is preventable at the creation step.

Encoding the wrong URL is the most common. You were browsing the staging version of your site, or you copied a link with tracking parameters attached, and now 2,000 flyers point somewhere unintended. Open the encoded address in a clean browser window before you commit to anything.

Missing protocol comes second. example.com is not https://example.com, and plenty of generators won't silently fix it. Check the address starts with https:// before you press generate.

Test with the camera app, not just a QR app. iOS and Android both read codes natively since roughly 2018, and that's what your users will reach for. If the native camera fails but a third-party scanner works, something about your design β€” usually contrast β€” is marginal.

Watch the URL length. Dense codes with dozens of characters shrink each module, and every tracking parameter you append makes the pattern harder to read at small sizes. Strip parameters you don't need.

Reprint consistency is the last trap. If you're printing the same code across screen and offset litho, export one master file and use it everywhere. A code regenerated mid-project can come out with different error correction or a shifted version number and scan identically β€” until it doesn't.

Turn a Phone Photo Into a Print-Ready File in Three Formats

The file format you download determines what you can do with the code later, and the differences are practical.

Format Best for Key constraint
PNG Social media, digital documents, quick sharing Fixed resolution; blurs if scaled up
SVG Print, signage, anything resized Vector; editable in design software
JPG Platforms that reject PNG uploads Loses edge sharpness; avoid if possible
EPS Professional print workflows Overkill for most users

Reach for SVG when the code will be printed at more than roughly 10 centimeters and someone else is laying out the artwork. A vector file scales without soft edges, and your printer can adjust color profiles without re-rendering. For a restaurant table sticker viewed at 15 centimeters, PNG is fine.

Generate the file at a sensible starting size and never "enhance" it afterward. Upscaling a 300-pixel PNG with an AI sharpener can distort module edges enough to confuse a scanner, even though the image looks crisper on screen.

Keep the master file wherever you keep brand assets. The single most common printing headache is a code nobody can find again β€” the original was made on a departed employee's phone, and reprinting means regenerating a code that no longer matches the one etched on the sign.

The placing of a QR code changes what it should contain, and a few categories behave differently enough to deserve their own note.

Wi-Fi access. Never encode a Wi-Fi password in a plain website QR code. The phone-camera pipeline treats it as a URL and fails; use the WIFI: payload format that handset software recognizes. Contact cards. vCard payloads work on both platforms, but older Android builds sometimes refuse them. Test on the oldest phone in the room. App store links. Point at the plain store URL rather than a deep link. Deep links break when the app is missing, and a QR code that opens a dead screen reads as broken. Shortened URLs. Visually easier to scan, but now the shortener owns the redirect β€” the same dependency risk as a dynamic platform. Mobile-only destinations. Remember the scanner is always a phone. A desktop-only checkout page will frustrate every single scan.

There's No App Gap: iOS and Android Scan These Identically

A persistent myth holds that iPhones can't scan QR codes without a third-party app. That was true before iOS 11, and it hasn't been true for years β€” the native Camera app reads codes on current iPhones the same way Android's Camera does.

The practical consequence is for testing. You only need one phone to verify a code, but verify on both platforms if your audience splits. Occasional quirks show up in how each system handles unusual payloads and in how quickly a camera focuses at close range. Samsung's camera handles very close scans slightly differently from Google's stock app, worth knowing if your code sits on a tiny product label.

If a code scans on your Android test device but not your colleague's iPhone, change nothing about the code first. Wipe the lens, move to brighter light, and hold the phone 15 to 20 centimeters back. Camera lens smudges cause more "broken QR code" reports than any encoding error.

FAQ

Can I make a QR code without downloading an app?

Yes β€” Chrome on iOS and Android generates codes inside the browser with no install, and desktop Chrome can send a page's QR code to a phone signed into the same Google account. Paste-a-URL generator sites are the other no-install path. Both produce static codes, so nothing expires on you.

Do free QR codes expire?

Most static generators impose no expiry, but check before you print. The trial tier at QR Code Generator deactivates codes after 14 days, and its free dynamic plan caps scans, so "free" and "permanent" are different promises depending on which plan you're on. A static code from a no-account generator is the safest interpretation of free.

Why does my QR code say the URL is invalid?

Nearly always a missing protocol. The generator expects https://example.com, not example.com, and some tools encode the partial string and produce a code that no scanner can resolve. Add the scheme, regenerate, and test with a phone camera before distributing anything.

Can a QR code be too long for a phone to scan?

A long URL creates a denser pattern, and dense patterns need more print size or closer scanning. Strip tracking parameters you don't need, or accept a larger printed code. The QR spec's version range tops out at version 40, so length isn't a hard ceiling β€” readability at your physical size is.

How much does a permanent dynamic QR code cost over five years?

Pricing varies by platform and changes often, so check each vendor's current plan page. The structural point holds regardless: dynamic codes are subscriptions, and a code on a five-year sign needs five years of payments. A static code costs nothing after creation but can't be redirected.

Can I put my logo in the middle of a QR code?

Yes, if error correction is set to level H, which tolerates about 30% occlusion. Keep the logo under roughly a fifth of the code's area and leave every module outside it intact. Test the result with a phone camera at arm's length before printing anything.

What's the minimum size I can print a website QR code?

There's no fixed pixel minimum; physical viewing distance sets the requirement. A code at 1.5 to 2 centimeters square works for close scans on packaging, and poster-sized codes need to scale up with the reading distance. The 30% contrast rule and a four-module quiet zone matter more than raw size at small prints.

Why do some generators ask me to sign up before creating a code?

Because they're selling dynamic codes. Registration ties a short redirect link to your account, which enables editing and analytics and creates a subscription relationship. If you only need a static code, any tool that forces signup is the wrong tool for the job.