A QR code is a visual encoding of data, not a link shortener or a security mechanism. The ByteKiln QR Code tool generates a downloadable code from text and scans codes from an image or camera in the page; camera frames are decoded locally and not recorded.
The most reliable codes use short, stable content, enough visual contrast, and an error-correction level appropriate for where the code will appear.
Decide what the code should contain
For a website, use the final HTTPS URL:
https://www.example.com/setup/Avoid temporary preview domains and unnecessary tracking parameters. Shorter input produces a less dense code that is easier to scan at small sizes. If the destination may change, point the code to a stable redirect that you control—but make that redirect transparent and maintain it for the expected life of printed material.
QR codes can also store plain text, email actions, phone numbers, Wi-Fi configuration, or contact data. Those formats have specific prefixes and separators. Test the result on both Android and iOS before distributing it because camera applications may interpret uncommon payload formats differently.
Choose error correction
QR error correction reconstructs data when part of a code is dirty or damaged:
- L recovers roughly 7% and produces the least dense code.
- M recovers roughly 15% and is a good general default.
- Q recovers roughly 25%.
- H recovers roughly 30% and is useful for harsh physical settings.
Higher correction is not automatically better. It creates more modules, which can make the code harder to scan when printed too small. Use M for ordinary digital and clean print use; consider Q or H for packaging, signs, or surfaces likely to be scratched.
Preserve the quiet zone and contrast
The empty border around a QR code is the quiet zone. Do not crop it or place text and borders against the modules. Use a dark foreground on a light, uniform background. Gradients, transparency, and low-contrast brand colors reduce reliability.
If you add a logo with another design tool, keep it small and use Q or H correction. ByteKiln generates the code without a logo so the encoded modules remain intact.
Test at the real output size
Download the generated PNG and test it under realistic conditions:
- Scan it from multiple phone models.
- Test at the intended printed size and viewing distance.
- Try dim light and an angled camera.
- Check a printed proof rather than only the design file.
- Verify the decoded text character for character.
- Confirm the destination is mobile-friendly and still valid.
For signage, a code that scans from a laptop screen at arm’s length may still fail once printed and viewed several metres away.
Scan files and camera input safely
The scanner accepts an image or a live camera feed. Camera access requires browser permission and a secure context. ByteKiln processes frames locally; granting camera permission still deserves the same care as any site permission. Stop the camera when finished and use the browser’s site controls to revoke access if the device is shared.
Treat scanned content as untrusted. Read the decoded URL before opening it, especially for codes found in public places. Attackers can place stickers over legitimate codes or encode lookalike domains.
Encoding is not encryption
Anyone who can scan a QR code can read its content. Do not embed passwords, private API keys, session tokens, or personal data unless the surrounding protocol specifically protects it and disclosure is acceptable. Base64 does not make sensitive content safe; it only changes representation. See the Base64 guide for the distinction.
When placing a URL inside another URL parameter before generating the code, use the URL Encoder for that nested parameter. Do not encode the entire destination unnecessarily, because a scanner should usually receive a normal URL.
Publication checklist
Before releasing a QR code:
- use a stable HTTPS destination;
- remove unnecessary parameters;
- choose correction for the physical environment;
- retain a clear quiet zone;
- use strong dark-on-light contrast;
- test the actual printed size and material;
- verify the destination on mobile;
- monitor the controlled destination without collecting more data than necessary;
- keep a human-readable URL nearby when practical.
A reliable QR code is part encoding and part physical design. Generate it early enough that the final artifact—not only the source image—can be tested.