—
—
Compare
Compare
The comparison tool now walks the user through each proof step before surfacing the verdict.
QR A
Upload the expected or original QR image.
QR B
Upload the QR you want to verify against QR A.
Comparison
StaticQR compares exact decoded text first. URLs and wallet addresses then receive extra interpretation without hiding the raw payload difference.
Results
The verdict appears once both QR codes decode successfully.
Upload QR A and QR B to check whether their payloads match exactly, differ only in formatting, or point somewhere different.
—
These notes explain the comparison without changing the exact decoded payloads.
This table helps explain whether a web destination changed in protocol, host, path, query, or fragment.
| Part | QR A | QR B |
|---|
Highlighted text shows where the decoded payloads stop matching.
Why Compare?
Compare the original QR against a flyer, menu, sign, or export to confirm the encoded payload did not change.
Different URLs or crypto wallet addresses are surfaced clearly so a swapped QR does not quietly slip through.
Copy decoded content, send either QR into the Safety Lab, or rebuild a clean replacement without starting over.
FAQ
Yes. The primary verdict uses the exact decoded payload, including letter case, punctuation, paths, query strings, and wallet-address capitalization.
Yes. QR appearance can differ because of styling, logos, exports, or error correction. Compare focuses on what the QR code actually decodes to.
StaticQR keeps the exact raw payload verdict, then adds a browser-normalized URL view and a component table so you can see whether protocol, host, path, query, or fragment changed.
No. QR images are decoded in your browser by this static website. StaticQR does not store the images you compare.
Proofing workflow
Two QR codes can look different and still lead to the same destination. Compare helps verify whether the decoded payloads match before you approve packaging, signage, wallet addresses, or campaign files.