Free · Fast · Privacy-first

QR Code for App Download

Drive app downloads from physical materials, presentations, conference stands, packaging inserts, and web pages using a single QR code that points users straight to your App Store listing, Google Play page, or a universal download landing page that detects the device platform and routes accordingly.

⚡

Links to App Store, Google Play, or any URL

🔒

Ideal for print, events, and packaging

✨

PNG and SVG export

⚡

No sign-up required

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this QR Code Generator to your website

Drop the QR Code Generator into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/utilities/qr-code-generator?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="QR Code Generator by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/utilities/qr-code-generator?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="QR Code Generator by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Driving App Downloads from Physical and Offline Touchpoints

App store discovery is fiercely competitive and getting more so each year as the catalogues swell into the millions of titles. Most apps are found through store search, app store optimisation, paid acquisition campaigns, and word-of-mouth referrals from existing users. But for apps with physical product companions, event tie-ins, retail presence, or hardware integrations there is a powerful offline acquisition channel that many developers underuse: the physical QR code. A QR code on your product box, at your trade show stand, on your printed marketing materials, or inside your physical retail location puts users one tap from your App Store listing at the exact moment they are most motivated to download because they are holding your product or engaging with your brand in person. This can achieve download conversion rates that even well-optimised paid digital channels struggle to match.

An app download QR code technically encodes a URL in byte-mode QR format because the App Store and Google Play URLs contain characters outside the alphanumeric mode set. The URL can point directly to an App Store listing such as apps.apple.com/app/idxxxxx or a Google Play listing such as play.google.com/store/apps/details?id=com.yourapp. However, for physical materials used by a mixed iOS and Android audience, a platform-detection redirect page is almost always the better approach. This is a lightweight web page that reads the User-Agent header sent by the scanning device and redirects iOS devices to the App Store and Android devices to Google Play. Services like Branch.io, AppsFlyer OneLink, Adjust, or a simple custom redirect on your own domain can handle this elegantly.

Measuring app download QR code performance requires setting up attribution infrastructure before any QR code goes to print, because adding tracking retroactively to deployed materials is impossible. Both the App Store via Apple Search Ads Campaign IDs and App Analytics custom campaign URLs and Google Play via referral UTM parameters in the store URL support source tracking that survives the install event. For cross-platform redirects, use a measurement tool such as Branch, Adjust, or Firebase Dynamic Links that tracks the full journey from QR scan through redirect through store visit through install and into first session. Set this up before printing any materials so you have clean comparable data from the first deployment of every code.

A final consideration that often surprises first-time deployers is the importance of post-install context. The user who scans your QR code at a trade show and lands on the App Store still needs to install, open, and orient themselves inside the app without the context that brought them to scan in the first place. Design a first-run onboarding flow that acknowledges where the user might have come from, perhaps detecting the campaign attribution and showing a relevant welcome screen, so the connection between offline interest and in-app value is preserved. Without this, your perfectly tracked QR-driven installs may stall at the second or third session and your conversion-to-active rates will disappoint.

Apple App Store Connect: App Analytics Google Play Console: UTM tracking guide

How to use this tool

💡

Enter your App Store, Google Play, or universal app landing page URL to generate an app download QR code.

How It Works

Step-by-step guide to qr code for app download:

1
Get your app store URL
Copy the URL of your app from the App Store listing in apps.apple.com or from your Google Play listing in play.google.com/store/apps. For cross-platform deployments use a universal landing page URL hosted on your own domain or through a service such as Branch or Adjust that handles platform detection and attribution in one step rather than juggling two separate codes.
2
Paste and generate
Enter the URL into the FixTools QR Code Generator input field. The live preview shows the resulting QR pattern as you type. Click Generate when satisfied and download as SVG for any print job that needs to scale crisply such as packaging artwork or large event signage, or PNG for digital placements like slide decks and ads.
3
Test on target devices
Scan the generated code on an actual iPhone with the App Store app installed to verify the App Store listing opens cleanly in the right region, and on an actual Android device with the Play Store app installed to verify the Google Play listing loads correctly. Test the full flow including any redirect interstitials so you know exactly what users will see.
4
Deploy in marketing materials
Download the QR code and add it to your packaging, advertising creatives, conference stands, slide decks, or event materials with clear branding around the code showing it is a download QR. Include Apple and Google store badge graphics nearby so scanners understand at a glance what the code delivers and recognise it as legitimate.

Real-world examples

Common situations where this approach makes a real difference:

Connected device companion app onboarding

A connected home device manufacturer includes a printed QR code insert inside every product box linking to their companion app via a platform-detection redirect that handles both stores. The QR code reduces the friction of finding and installing the right app during initial device setup, and companion app adoption increases by roughly thirty-five percent, which materially improves their long-term customer engagement and feature adoption metrics.

Trade show demo station app install

A mobile productivity app company places a clearly labelled QR code at each demo station at a major industry trade show, linking to a campaign-tagged App Store and Play Store redirect. Interested visitors download the app on the spot to try it themselves on their own device during the demo, and the team captures meaningfully higher install attribution from the show than they did the previous year using business card handouts and email follow-ups.

Bus stop outdoor advertising campaign

A consumer fitness app includes a large prominent QR code on their bus stop outdoor advertising campaign linking to a platform-detection landing page wrapped with Branch attribution. The code appears across five hundred bus stops in three major cities and drives a significant measurable spike in downloads during the campaign window, with bus stop installs showing higher retention than typical paid social acquisition.

When to use this guide

Use this in marketing materials, on product packaging, at events, or on your website to drive mobile app downloads from physical or digital touchpoints.

Pro tips

Get better results with these expert suggestions:

Use a platform-detection redirect for mixed iOS/Android audiences

A single redirect URL that reads the User-Agent string and sends iOS users to the App Store while sending Android users to Google Play eliminates the need for two separate QR codes on the same material. This simplifies design, avoids audience confusion about which code to scan, and keeps your packaging or signage clean. Build a simple redirect on your own domain or use a service such as Branch.io that also handles attribution and deferred deep linking.

Set up attribution before printing

Once physical materials are printed at scale, adding attribution to the QR code destination retroactively is impossible because you would have to reprint everything. Set up Apple App Analytics Custom Campaign IDs and Google Play referral UTM parameters carefully before generating the final QR code URL and committing to print. This ensures every scan and resulting install from that code is tracked from the very first day of deployment with no gap in your data.

Test on both App Store and Google Play before going to print

Test the QR code on an iPhone with the App Store app installed to confirm it opens the correct listing in the right region, and on an Android device with the Play Store app installed to confirm the correct Play Store page loads cleanly. For universal redirect URLs, also test from each device type that the redirect correctly identifies the platform and routes accordingly without any error or interstitial that might lose impatient users.

Include store badge graphics alongside the QR code

Apple and Google both provide official Download on the App Store and Get it on Google Play badge graphics that are visually familiar to almost every smartphone user worldwide. Placing these badges alongside your QR code on packaging, slides, or marketing materials sets clear expectations for what scanning will deliver and removes any ambiguity about what kind of QR code this is. The badges also signal that you are a legitimate developer and not a phishing operation.

Use a universal link that detects platform

Rather than generating separate iOS and Android QR codes, create a single landing page that detects the user's device and redirects to the appropriate store. Tools like linktr.ee or a custom redirect page can handle this.

Add your app icon next to the QR code

Placing your app icon and a "Download on App Store / Google Play" badge beside the QR code signals exactly what will happen when someone scans it, significantly increasing scan rate.

Track downloads with UTM parameters

Append UTM parameters to your app store link (where supported) or route through a tracking link to measure how many downloads originate from each physical QR code placement.

FAQ

Frequently asked questions

Use a universal landing page that detects the user's operating system and redirects to the appropriate store automatically. This lets you use a single QR code across all materials rather than creating separate iOS and Android codes that crowd your design and confuse scanners. The redirect logic is straightforward, the resulting URL is short which keeps the QR pattern low-density, and attribution services such as Branch provide the redirect alongside install tracking in a single integration.

Yes, absolutely. TestFlight beta links are standard URLs that can be encoded in a QR code without any special treatment. This is a common way to distribute beta test invites at developer events, in product research sessions, or to a controlled user research panel. The same approach works for Google Play internal testing tracks where the link is a play.google.com URL with the testing track parameter. Just confirm the link is accessible to the people you intend to scan.

Both the App Store via Campaign IDs in App Analytics custom product page URLs and Google Play via UTM tracking parameters in the store URL support source tracking that survives the install. For cross-platform measurement, use Branch, Adjust, AppsFlyer, or Firebase Dynamic Links to attribute installs from QR scans to the specific campaign and placement. Set up tracking before generating your QR code so every scan is attributed correctly from day one and you never have data gaps.

An App Store link QR code opens the app listing page for download, which is the right destination for acquisition campaigns aimed at users who do not yet have your app installed. A deep link using URL schemes such as yourapp://path or Universal Links on iOS opens a specific screen inside an already-installed app, which is right for re-engagement and onboarding of existing users. Use App Store links for acquisition and deep links for re-engagement of your existing user base.

Not directly to a public store listing because the listing does not exist yet. For unreleased apps, encode a TestFlight beta URL for iOS or an internal testing URL for Android, both of which work without public publication and only invite users you have explicitly added to the test panel. For general pre-launch interest capture during a buzz campaign, link to your app's landing page on your website with a sign-up form that you can later notify when the app actually goes live.

Print at a larger size of at least six to eight centimetres on the longest side and ensure high contrast between the dark QR modules and the white or very light background. Avoid printing on coloured paper or dark backgrounds without first testing scan reliability under realistic lighting. Bright LED backlighting behind a printed QR code display or printing on white acrylic with edge lighting both help dramatically in dark venue conditions and improve scan rates noticeably.

For most app store link use cases, a static QR code with the URL pointing to a redirect or attribution service is sufficient and avoids subscription dependencies. App Store and Google Play URLs are stable and rarely change once an app is live. Use a dynamic QR code service only if you need to swap the destination URL after print without reprinting, which is rare for app store deployments unless you anticipate a rebrand or app consolidation.

A single QR code encodes one URL. To serve both iOS and Android users with one code, encode a redirect URL that detects the device platform via User-Agent and sends each user to the appropriate store. This is the recommended approach for any physical materials used by a mixed audience because it keeps the design clean, reduces decision fatigue for scanners, and lets you collect unified scan analytics across both platforms from one source.

You can absolutely use a marketing landing page as the QR destination, and for some campaigns this performs better than going straight to the store because you can warm up cold scanners with social proof, feature highlights, and trust signals before asking them to install. Add prominent store buttons on the landing page so committed users can install in one tap. Measure both paths if you can, because the right answer depends on your audience and campaign context.