QRCodeBrain

URL → CHECKS → FILE

From a URL to a deliverable file

A generated image is only an intermediate artifact. The delivery path ends after the source URL is validated, the final file is read back independently, and the printed size is checked.

Start single validation

Static QR workflow

Validate the source input first, read back the final result independently, then verify the files format by format. A preview, one successful decode or one passing format cannot stand in for the rest.

  1. 01 · URL

    URL requirements

    Empty, relative and non-HTTPS addresses, embedded credentials, raw control characters, local hosts, literal IPs, self-loops and over-long URLs are rejected before encoding.

  2. 02 · READBACK

    Independent readback

    The rendered file is decoded again through a separate path and compared character by character with the normalized URL. Looking right is not passing.

  3. 03 · PRINT

    Print preflight

    Total modules, the requested size in millimetres and the print DPI give whole dots per module. Below four the download is blocked and the minimum safe size is shown.

  4. 04 · FILES

    Final-file verification

    PNG and SVG are rendered and decoded separately. A PNG that passes does not clear a vector file that failed or was never checked.

Choose by what must happen after print

Three QR types answer different questions. The static and bulk paths are open; the dynamic one is not.

STATIC

Destination will not change

The normalized HTTPS URL is encoded straight into the matrix. There is no redirect through this site, no scan log, and no way to edit the destination later.

Available now. It needs no account and writes nothing to a server.

DYNAMIC

Destination must change after print

A stable short code resolves to the current destination, so the printed code stays fixed while the target behind it is edited.

Create and manage dynamic QR codes after signing in.

My QR codes

BULK

Many codes from one list

Every row is validated on its own, and a row that fails stays attached to that row instead of failing the whole file.

Open now. The CSV is read in your browser and never uploaded.

Open the bulk tool

Three illustrative scenarios

These scenarios are written to explain the choice above. They are not customer records, case studies or usage data.

MENU

A restaurant menu

The dish list changes far more often than the printed card does. That is the situation where a destination you can edit after printing is worth the extra dependency.

POSTER

An event poster

A poster is read from a distance, so the printed size and the preflight result decide whether the code is usable at all. Pick the size before the file, not after.

PACKAGING

A packaging insert

For different URLs on different packages, upload a CSV to the bulk tool, check each row and download the results.

What this does not prove

  • An independent readback proves the file decodes. It does not prove that every device, material or lighting condition will scan it, so still check the real printed proof on an actual device.
  • The destination site, its domain and the printed material can each fail on their own, independently of the code.
  • A shared short domain is not portable. Codes printed with the platform domain depend on this service. Paid accounts can bind their own subdomain in Settings. Only codes created on that domain from the start can move to another service using the exported mapping.
  • We do not promise that a code will scan everywhere. What this page claims is limited to the checks the tool actually runs and shows you.