Comparison
The best QR code APIs
For a free QR API, the credible options are qrserver (the decade-old veteran, PNG-focused), QuickChart (charts plus QR, self-hostable), and UseQR (keyless, SVG/PNG/PDF, typed payloads, decode and verify endpoints, 1,000-item batches, OpenAPI and MCP). qrserver wins on track record; UseQR on capability; a paid SLA only matters for revenue-critical paths.
The criteria, stated up front
An API roundup written by an API vendor should show its scoring rubric before its scores. Ours, in the order that predicts real-world pain:
- Auth friction. Every key is signup, storage, rotation and a leaked-secret risk. For generating public QR images, keys buy the provider rate-limit control and buy you nothing. Keyless is strictly better for the caller.
- Formats. PNG for screens, SVG for print, PDF for documents, and ideally the raw matrix as JSON for custom rendering.
- Payload support. URL-in, image-out is the easy 90%. WiFi escaping, UPI field rules and IBAN checksums are the hard 10% where integrations actually fail.
- Decode and verify. Can the API read codes back and prove an image scans? Generation without verification is trust without evidence.
- Machine-readability. OpenAPI, llms.txt, an MCP server — this decides whether AI agents can use the API unaided, which is quickly becoming the main consumer of QR APIs.
- Track record. Uptime history you can only earn with years.
The free field
| qrserver (goqr.me) | QuickChart | UseQR | |
|---|---|---|---|
| Keyless | Yes | Yes (hosted free tier) | Yes |
| PNG / SVG / PDF | PNG, limited SVG | PNG, SVG | All three + matrix JSON |
| Typed payloads | No | No | 28, spec-validated |
| Decode endpoint | Yes | No | Yes |
| Verify endpoint | No | No | Yes |
| Batch | No | No | 1,000 per call |
| OpenAPI / MCP / llms.txt | No | Partial docs | All three |
| Self-hostable | No | Yes (open source) | Yes (MIT) |
| Track record | 10+ years | Years | New |
qrserver is the veteran and still a fine answer for "give me a PNG" — the
full head-to-head covers it, including the fact that UseQR
accepts qrserver's parameter names for drop-in migration. QuickChart is really a
chart API with a good QR endpoint; if you already use it for charts, using it for QR too
is sensible, and being open source it shares the self-hosting escape hatch. UseQR
wins on capability surface; the shortest call is https://useqr.app/q/hello.png and the
contract is in the OpenAPI document. A broader survey sits at
free QR API comparison.
The track-record caveat, kept honest
We are the new entrant in that table and the column is not decoration. qrserver has served embeds for over a decade; we cannot claim that and will not imply it. Three mitigations are structural rather than promised: static codes you download owe nothing to our uptime; the whole stack is MIT-licensed and self-hostable, so the API can outlive the domain; and for embeds meant to survive a decade untouched, we advise downloading the image rather than hotlinking any API — Google's shutdown is the standing lesson.
When a paid API is worth it
Paid QR APIs bundle the API with a dynamic-codes platform, and that is the honest framing: you pay for managed redirects and analytics, not for the encoding. Reasonable triggers: a contractual SLA for a revenue-critical path, dynamic codes you actually need, or procurement that requires a vendor relationship. Note the access details, though — QRCodeKIT locks API access to its $150/mo Enterprise tier, with v1 keys requested by email. QRFY includes its API in every plan, with a roughly $117/quarter minimum. For pure static generation, paying is paying for arithmetic; the free options above cover it.
FAQ
What is the best free QR code API?
qrserver for simple PNGs with a long track record; UseQR for SVG/PDF output, spec-validated payload types, decode and verify endpoints, 1,000-item batches and agent-readable docs — all keyless. QuickChart is a good fit if you already use it for charts.
Is there a QR code API without an API key?
Yes — qrserver, QuickChart's hosted tier and UseQR are all keyless. For static QR generation a key adds friction without adding capability; treat mandatory signup for static output as a pricing signal.
How do I know an API's QR codes actually scan?
Use an API with a verify endpoint — it renders the code, decodes it back and confirms the round trip — or decode samples yourself in CI. Styling options and dense payloads are where generated codes silently fail.
Which QR API works best with AI agents?
The measurable criteria are an OpenAPI document, llms.txt and an MCP server, with keyless access so the agent needs no credential handling. UseQR ships all three; among incumbents only paid, account-gated MCP servers exist.
Try it — free, no signup
Related
- UseQR vs the qrserver / goqr.me API — api.qrserver.com is the long-standing free QR API and it works well for plain PNGs. UseQR adds SVG and PDF output, typed payload builders with real spec…
- UseQR vs the Google Charts QR API — Google's Chart API QR endpoint was deprecated in 2012 and shut down in 2019, breaking embeds everywhere. What it teaches, and the one-line migration.
- The best bulk QR code generators — Criteria for judging bulk tools — input format, output format, limits, cost per 1,000 — and the free routes: client-side bulk UI, batch API, spreadsheet formulas.
- The best self-hosted QR code generators — What self-hosting actually protects — payload privacy and permanence — the credible options from libraries to full products, and the honest ops cost.