QR Codes That Open Apps, Not Browser Tabs
Learn how to make a QR code open an app directly on iOS and Android in 3 steps — no browser tab, no login wall, and links that never stop redirecting.
⚡ Zippy: you printed 500 flyers and every scan opens a login wall. i've seen things.
To make a QR code open an app instead of a browser tab, point the QR code at a deep-link short URL — like a Zippy link — instead of the destination's normal web address. When scanned, the link detects the device and launches the installed native app, with a web fallback if the app is missing. Setup takes 3 steps and works on iOS and Android.
Why do QR codes open a browser tab instead of the app?
Because a QR code is just a URL, and a scanned URL goes to a browser by default. The phone's camera hands the address to Safari or Chrome, which loads the platform's mobile website — where your follower is usually logged out. They hit a "Sign in to continue" wall or a limp "Open in app?" banner, and most people bail right there.
It gets worse when the QR code is scanned inside another app — Instagram's built-in scanner, a QR inside a story, a scanner baked into some super-app. Then the URL doesn't even get a real browser; it gets an in-app webview with its own empty cookie jar. We wrote up the full autopsy in why your links die in the in-app browser.
Either way, the pattern is the same: the scan happened, the intent was real, and the conversion quietly didn't.
How do you make a QR code open an app?
You put a deep-link redirect between the QR code and the destination. Here's the whole setup:
- Create a Zippy link pointing at your destination — a YouTube channel, an Instagram profile, a TikTok video, a WhatsApp chat, a subreddit, a LinkedIn page, a Product Hunt launch, or an X post. Zippy supports all eight platforms.
- Download the QR code. Every Zippy link comes with a QR code, on every plan — including the free one.
- Put it anywhere. Flyer, poster, packaging, conference badge, screen at the back of a talk. When someone scans it, the Zippy link inspects the device and springs the installed native app instead of loading the mobile website.
That's it. There is no per-platform configuration on your end — the routing logic lives in the link, not in the QR code. If you're driving people to Instagram or TikTok specifically, the Instagram deep links guide and TikTok deep links guide cover the per-platform details.
⚡ Zippy: step 4 is watching someone scan your poster and land inside the actual app, logged in. it never gets old.
What actually happens on iOS vs Android when someone scans?
The scan resolves to the Zippy redirect, which uses each operating system's native mechanism for launching apps — and each OS does it differently:
| iOS | Android | |
|---|---|---|
| Mechanism | App URL schemes | intent:// URLs |
| Fallback | Timed fallback to the web page | Native fallback built into the intent |
| App installed | Native app opens, logged in | Native app opens, logged in |
| App not installed | Web page loads after the timeout | Web page loads via the intent's fallback |
| Worst case | Browser opens the page | Browser opens the page |
The worst-case row is the important one. If a platform changes something and a scheme stops matching, the link degrades to opening the destination in the browser — exactly what a normal QR code would have done anyway. A Zippy QR code can underperform its best case; it can never do worse than the status quo, and it can never be a dead scan.
What if the app isn't installed?
The person lands on the normal web page — the same place a plain QR code would have sent them. Nothing breaks, nothing errors, no blank screen. App-opening links are strictly additive: users with the app get the app, users without it get the web.
This matters more for QR codes than for social links, because QR scanners skew broad. A link in your Instagram bio is scanned by people who obviously have Instagram; a QR code on a coffee shop poster is scanned by everyone. The fallback isn't an edge case there — it's a meaningful slice of your traffic, and it has to just work.
Why does edit-after-posting matter so much for printed QR codes?
Because print is permanent and your campaign isn't. A link in a bio can be swapped in ten seconds. A QR code on 5,000 product boxes cannot. If the QR encodes the destination URL directly, the day that URL changes — new landing page, dead product, rebranded handle — every physical object you printed becomes garbage.
A QR code that encodes a Zippy link stays valid forever, because you edit the destination behind the link without touching the code. On the Hero plan ($19/mo, or $180/yr which works out to a flat $15/mo), links are living links: repoint last year's conference poster at this year's talk, swap a discontinued product for its replacement, fix a typo'd handle after the flyers shipped.
And underneath the editing sits Zippy's permanence law: links never stop redirecting. Not on the free plan, not after a trial ends, not after you cancel. Links over your plan's cap go read-only — you can't edit them anymore, but they keep their slug and keep redirecting. Clicks are never metered on any paid plan. For something physically printed into the world, that guarantee is the entire ballgame.
⚡ Zippy: a qr code outlives the intern who made it. plan accordingly.
Do you need a paid plan for app-opening QR codes?
No. The free Sidekick plan includes QR codes, app-opening platform targeting, and 5 active links — free forever, with random slugs, total click counts, and a small Zippy-branded interstitial. That's genuinely enough to test whether app-opening scans move your numbers.
Hero ($19/mo) adds the things print campaigns actually lean on: unlimited links and unlimited clicks, custom slugs, edit-after-posting, no branding, and full analytics — geo, device, platform, referrer, and time, which for QR codes doubles as a map of where in the physical world your scans come from. Legend ($49/mo) adds a custom domain, 3 seats, API access, bulk creation, and CSV exports — and if you're putting your own domain on printed materials, custom domain short links covers why that's worth it for scan trust alone.
Every plan starts with a 14-day full Hero trial, no credit card, soft downgrade to free. And if a link opens the in-app browser on a supported platform, the Actually-Opens guarantee refunds your month.
FAQ
Can a QR code open an app directly without any redirect?
Only if you encode the platform's raw app scheme into the QR code itself, which breaks badly: it fails for anyone without the app installed, behaves differently across iOS and Android, and can't be updated after printing. A redirect link that resolves the right behavior per device at scan time is the reliable approach.
Do Zippy QR codes work if they're scanned from inside another app?
Yes — that's the core product. Whether the URL arrives via a camera scan, an in-app scanner, or a tap inside Instagram, TikTok, LinkedIn, WhatsApp, Reddit, X, YouTube, or Product Hunt, the Zippy redirect routes it to the installed native app instead of leaving it in a webview.
What happens to my QR codes if I cancel my Zippy subscription?
They keep working, permanently. Zippy's permanence law means links never stop redirecting — over-cap links go read-only but keep their slug and keep resolving. Your printed materials never point at a dead end.
Can I self-host the redirect engine behind my QR codes?
Yes. Zippy's redirect engine is open source under AGPL, built on Cloudflare Workers and KV, and self-hostable from the GitHub repo — the full story is in why Zippy is open source. The hosted cloud at zipthe.link is the paid product; the engine itself is yours to run.
Is a QR code that opens the app better for affiliate links?
Meaningfully, yes. Affiliate conversions depend on the user reaching a page where they're logged in and attribution can survive; browser-tab scans shed both. See how to build affiliate links that convert for the full playbook.
Print it once, edit it forever — make your QR codes open the app at zipthe.link. ⚡