Website URL QR Code Generator

Any publicly accessible URL works: https:// or http://, custom domains, subdomains, and URLs with query strings. The destination does not need to be your own site - Google Drive links, Eventbrite listings, and third-party booking tools all work, as long as the URL opens in a standard phone browser without requiring a separate app.

Scanning the code opens the URL in the phone's default browser, not inside any app. The destination needs to be a standard web page - not a native-app deep link - to work reliably across all devices. If you need app deep-linking, point the QR Cake destination to a smart-link service that handles the app-vs-browser routing.

Yes. QR Cake records every scan with timestamp, device type (iOS or Android), country, and city, available on both free and paid plans. Paid plans unlock longer data history and CSV export so you can import scan data into your own analytics stack.

QR Cake does not have built-in geo-routing within a single code. The standard approach is to create separate codes per region, each pointing to the relevant localised landing page. If you need programmatic per-scan routing, QR Cake's REST API at api.qrcake.com/v1/product lets you build custom redirect logic in your own infrastructure.

Because QR Cake uses dynamic codes, you can log in and redirect the code to a working page immediately - no reprint needed. If the destination is temporarily down, scanners see whatever the server returns (typically a 404). The QR code itself keeps working; the destination is the part that needs fixing. Uptime monitoring on your landing page is good practice for high-traffic print campaigns.

Create two separate QR Cake codes - one pointing to variant A, one to variant B - and split the print run between them. Each code reports its own scan count independently. There is no built-in randomised split-testing within a single code, but separate codes give clean, unambiguous data and can be redirected mid-campaign if one variant clearly outperforms the other.

Most phone cameras briefly show the QR Cake short redirect URL in a small banner before opening the page. The final destination URL then appears in the browser address bar. If showing a branded domain in the address bar matters, eligible paid plans support custom domain mapping - see qrcake.com/prices for details.

Before printing, open the destination URL on an actual phone and check that text is readable without zooming, buttons are at least 44 px tall, and the page loads in under three seconds on a 4G connection. Google's PageSpeed Insights (pagespeed.web.dev) gives a free mobile score. For long-form destinations, a dedicated landing page with a single clear call to action outperforms sending scanners to a full homepage.