Why we built a QR code generator, not a QR code platform

By Qrop Team · 18 July 2026

If you shop around for a QR code generator, you'll quickly notice that most of the well-known ones don't really sell you a QR code. They sell you a subscription to the infrastructure behind it — a redirect service that sits between your printed code and your destination URL, logging every scan along the way.

Qrop is built differently. We generate the code and hand it to you. What you do with the destination URL — where it points, who tracks it, what analytics you run on it — is entirely up to you and entirely on your own infrastructure.

That's a deliberate product decision, not an oversight. Here's the reasoning behind it, the trade-offs it involves, and how to replicate every 'platform' benefit on your own stack — usually for free.

What 'connected services' actually means

When a QR code company talks about 'dynamic codes,' 'scan analytics,' or a 'management dashboard,' they're describing a redirect layer that sits between your code and your content. The printed QR code doesn't point to your website — it points to the company's redirect server, which then forwards the visitor to you.

That redirect layer is what they're charging for. It's what lets you 'update' a code after printing (by changing where the redirect points), and it's what captures the scan count, device type, and country of every person who scans it.

The service is real. The problem is the dependency it creates: your printed codes stop working the moment you stop paying, the company shuts down, or their servers have an outage. Every code you've ever printed is held hostage to the continuity of a third-party business.

The hard part is the image, not the redirect

We set out to solve what's actually technically difficult about QR code generation: producing a high-quality, correctly-structured code that works reliably at scale.

That means a custom SVG renderer that handles module shapes (squares, dots, rounded), styleable finder patterns, and outer radius — not just a default library output. It means contrast checking that blocks unscannable colour combinations before a credit is consumed. It means logo compositing that automatically sets error correction to level H and enforces a 25% size cap. It means a batch API that generates up to 100 codes per request with consistent output across all formats — PNG, SVG, and PDF.

None of those problems have anything to do with where the code points. Bundling redirect hosting into the pricing would make the generation product more expensive without making it better. We'd rather keep the two concerns separate.

Data you generate shouldn't live on someone else's server

Scan analytics from a third-party QR service don't belong to you in any meaningful sense. You can view them in the dashboard, but you can't join them with your own customer data, run queries against them, or take them with you if you leave. They're locked into the platform's data model.

More practically: if your codes are on product packaging, retail displays, or printed marketing materials, the data about who scans them is commercially sensitive. A QR redirect service is a third party sitting in that data flow, logging every interaction.

When the scan hits your own URL — your own domain, your own analytics stack — that data is yours. It lives in whatever analytics tool you've chosen, queryable however you need, and remains yours if you ever change QR providers.

How to get 'dynamic' behaviour without a redirect subscription

The actual benefit of a dynamic QR code is redirectability: the ability to change where a printed code points after it's already distributed. You can get this entirely without a paid QR service, as long as you point your code at a URL you control.

Point your static QR code at a path on your own domain — say, yoursite.com/menu, or yoursite.com/campaign/spring-2026. Keep that URL alive and update the page or its redirect target any time the destination changes. Every printed code keeps working, because the URL embedded in the code never changes.

This is exactly the same mechanism a paid dynamic QR service uses — except the redirect server is your own infrastructure, under your control, with no monthly fee and no risk of the service shutting down.

Point codes at yoursite.com/r/campaign-name rather than directly at the destination. A one-line server-side redirect can then be updated without touching any printed code.
For teams without a server, a Notion page, a Google Sites page, or even a Linktree page at a stable URL gives you the same editability — you just update the page content rather than the redirect.
Append UTM parameters to the destination URL before encoding it: yoursite.com/landing?utm_source=poster&utm_medium=qr&utm_campaign=launch. Any analytics tool will then segment scans by campaign automatically.

Replicating scan analytics on your own stack

Scan counts, device types, countries, and timestamps — everything a paid dynamic QR dashboard shows you — can be captured on your own stack at no additional cost.

Google Analytics 4 — free, records page views with country, device, and time as standard. Add UTM parameters to the URL before generating the code and every scan is tagged with the campaign.
Plausible Analytics — a privacy-first alternative to GA that records the same signals without cookies or personal data. Open-source self-hosted version is free; the hosted version starts at $9/month.
Server-side logging — if the URL is on a server you control, a middleware log entry per request captures timestamp, IP (for geolocation), and user-agent with zero client-side script. The scan data never touches a third party at all.
Vercel Analytics, Cloudflare Analytics — if your site is deployed on Vercel or behind Cloudflare, both platforms provide page view analytics out of the box at no extra cost, with no scripts to install.

Who a generation-only tool is right for

Qrop is designed for teams and developers who want to generate high-quality codes at scale, not teams who want a third-party to manage their redirect infrastructure.

Developers integrating QR generation into a product — a SaaS platform, a logistics system, an e-commerce checkout — where generation happens programmatically via API and the destination URL logic lives in the application.
Designers and agencies generating branded codes for client deliverables — the codes go into the client's materials, the client owns the destination infrastructure.
Teams with an existing analytics and infrastructure stack who don't want scan data siloed in a third-party dashboard.
Anyone generating codes for content encoded directly in the code — Wi-Fi credentials, vCards, email addresses, phone numbers — where there's no URL to redirect and 'dynamic' behaviour is meaningless.
Businesses with specific data-residency or privacy requirements where routing scan traffic through a third-party service isn't acceptable.

Who should use a QR platform instead

A full QR code platform makes sense in specific situations, and we'd rather say so clearly than pretend our model fits every use case.

Non-technical teams who need redirectability through a dashboard, managed by someone without server access. If updating a redirect means filing a ticket with your IT department, a managed dashboard may genuinely save you time.
Codes printed on expensive or difficult-to-replace surfaces — vehicle wraps, building signage, large-format retail — where redirectability is operationally critical and you don't have a stable URL infrastructure to point the code at.
Multi-location retail or franchise environments that need centralised code management across hundreds of locations by non-developers. The platform's management layer has real value at that scale.

The pricing argument

QR platform subscriptions typically start at $5–$15 per month for a small number of 'active' codes, and scale up quickly. At $15/month you're paying $180/year for redirect infrastructure — for codes that cost pennies to generate.

Qrop's credit model charges for what's actually expensive: the generation itself. A credit costs R0.13–R0.20 depending on the pack size. A single generation is a fraction of a cent. If you generate a thousand codes a year, you're spending a few rands, not a monthly subscription that continues whether you generate zero codes or a thousand.

For API customers with high volume, the subscription model is equally straightforward: a monthly plan with a credit allocation, overage at a flat rate, no redirect fees embedded in the pricing. The cost reflects the generation work, not the infrastructure dependency.

Frequently asked questions

Can I still update where a Qrop-generated code points after printing?

Yes — by pointing the code at a URL you control rather than the final destination directly. You then update the page or redirect on your own infrastructure. The printed code never needs to change because the URL encoded in it stays the same; only what that URL serves changes. This gives you the same redirectability as a 'dynamic' code service, with no third-party dependency.

Does Qrop offer scan analytics?

No — scan analytics require a redirect layer sitting between the code and the destination, which Qrop deliberately doesn't provide. You can capture equivalent data by pointing your code at a URL on your own domain with UTM parameters appended, and using any standard web analytics tool (Google Analytics, Plausible, Cloudflare Analytics) to track visits. The data lives on your stack, not ours.

What happens to my codes if Qrop shuts down?

Nothing — a static QR code is just an image. It works forever, regardless of what happens to the company that generated it, as long as the URL it encodes remains live. Because Qrop doesn't sit in the redirect path, there's no dependency to break. This is a meaningful advantage over codes from services that encode their own redirect URLs.

How is Qrop different from free QR code generators?

Most free online generators produce a basic black-and-white code with no customisation and no API access. Qrop's generator supports custom colours, module styles, logo compositing with automatic error-correction enforcement, contrast validation before generation, and PNG/SVG/PDF output up to 2048px. The API adds batch generation of up to 100 codes per request, Bearer key authentication, and metered usage tracking. The generation quality is the difference, not the pricing model.

Is a generation-only model better for privacy?

For the people scanning your codes, yes. When a QR code points at a third-party redirect service, that service logs every scan — IP address, device, timestamp — by design. When the code points directly at your own URL, scan data only reaches your own analytics stack. You control what's collected, where it's stored, and who can access it.

Does Qrop support batch generation?

Yes. The API's batch endpoint (/api/v1/generate/batch) accepts up to 100 codes per request, each with independent data, format, and style settings. A single logo can be applied across all codes in the batch. Batch generation is an API-plan feature — it's designed for programmatic workflows, not the web UI.

Ready to create your QR code?

Generate a free QR code in seconds — custom colours, logos, and PNG, SVG or PDF output.

Open the generator