QR codes can carry arbitrary text, so valid JSON can be encoded directly. The difficult part is not syntax—it is density. Pretty-printed JSON, long property names, and embedded blobs quickly produce a dense code that is hard to scan.
Use JSON to QR Code for the direct operation. This guide explains when direct encoding is sensible and when the QR should contain a short URL or opaque token instead.
Prepare the JSON for a reliable scan
Validate the JSON, remove unnecessary whitespace, and keep only the fields the receiving app actually needs. Minification reduces payload length without changing the data. Prefer concise values, but do not rename fields unless the decoder expects those names. Avoid base64 images or documents; they make the code too dense for practical scanning.
Capacity is not the same as usability
QR specifications allow thousands of characters under ideal conditions, but real reliability depends on physical size, camera quality, viewing distance, contrast, and error-correction level. As payload grows, the module grid becomes denser. A code that scans from a monitor may fail when printed small or photographed at an angle.
Treat QR payloads as visible data
A QR code is encoding, not encryption. Do not include passwords, private API keys, long-lived access tokens, personal records, or confidential configuration. For sensitive workflows, encode a short-lived opaque token or HTTPS URL and enforce authorization when it is redeemed.
Direct JSON encoding is a good fit for compact, non-secret handoff data. For larger or sensitive objects, put the data behind an authenticated endpoint and encode only a short reference. Create the direct code with JSON to QR Code, then test it under the same print size, screen size, and lighting your users will encounter.