Free tool · no signup · no tracking

QR Code Generator & API

Type a URL, get a QR code as PNG or SVG. The same thing is available as a plain HTTP API you can call from a script — no key, no account, no rate-limit gymnastics for normal use.

API live at qr.lifestep.io

Developer guide: command-line recipes →

GET /qr — live

How it works

  1. The API accepts data from 1 to 2000 characters and validates format, scale, border, and six-digit RGB color parameters.
  2. It generates a standard QR Code with medium error correction rather than choosing a Micro QR symbol for short values.
  3. A successful request returns raw PNG bytes with image/png or an SVG document with image/svg+xml, plus an inline filename header.
  4. Color syntax is validated, but contrast and scan reliability are not; very long values may still exceed QR capacity and return HTTP 422.

Frequently asked questions

Can this generator create both PNG and SVG QR codes?

Yes. Set format to png or svg. The response content type is image/png or image/svg+xml.

What can I encode in a QR code?

The data field accepts text or a URL from 1 to 2000 characters, subject to the QR symbol's actual encoding capacity.

What do scale and border control?

Scale sets pixels per QR module from 1 to 20. Border sets the quiet zone from 0 to 16 modules and defaults to 4.

Are custom colors checked for scan reliability?

No. The API validates six-digit RGB syntax but does not measure contrast or guarantee that a scanner can read the result.

Does the API require an account or API key?

No. The current service accepts GET or POST requests without account authentication.

Use it from the command line

curl --fail-with-body --get "https://qr.lifestep.io/qr" \
  --data-urlencode "data=https://example.com" \
  --data "format=png" \
  --data "scale=6" \
  --output qr.png

Response sample for that request:

HTTP status: 200
Content-Type: image/png
Content-Disposition: inline; filename="qr-code.png"
Body prefix: 89 50 4e 47 0d 0a 1a 0a
Body length: 316 bytes

Privacy

The service generates the image in memory and immediately returns the bytes. The application code has no database, response cache, or persistence layer.

Generating QR assets in an agent-run publishing flow? Verify the artifact, not just the HTTP status.

Use the agent verification guide to add content checks, output-type checks, and a real scan step before QR assets reach labels, documents, or campaign pages.