QR error correction is a real trade-off: level H recovers from 30% damage but needs a denser code in the same space. Generate the same payload at all four levels and see how much the module size changes.
What you can control
- Five payload types, including the Wi-Fi and vCard formats that phones recognise natively.
- Four error-correction levels, so you can compare density before printing anything.
- Five symbologies covering both 2D codes and the linear barcodes still used in retail.
- Custom payloads take any string, for testing what happens when a code carries far more data than expected.
Testing ideas
- Payload types. Generate URL, Wi-Fi and vCard payloads to test a scanner app's parsing of each.
- Error correction. Compare L and H levels; H survives a logo overlay, L does not.
- Symbologies. Code 128, EAN-13, Data Matrix and PDF417 images test label layouts with different aspect ratios.
- External service. Images are rendered by a public QR service; for offline tests, render the payload with a local library.
What this is not
Image URLs point at third-party rendering services. For production, generate codes locally — a checkout page that depends on an external service to draw a barcode has an outage waiting.