Contact

Questions, scan-failure reports, and keepsake-style suggestions are all welcome.

A dedicated support inbox for KeepsakeCodes is being provisioned, and the address will be published on this page as soon as it is live. Corrections found through the review process described on the methodology page continue to be applied to every tool in the meantime.

Reporting a code that would not scan

To help us reproduce and fix a suspected problem quickly, please include:

• The tool and style you were using (for example, "Proposal Code — heart frame")
• The exact content you encoded (or its length and type, if it is private)
• Whether the on-page verification showed the "Verified scannable" badge or the cannot-verify warning before you downloaded
• What you scanned it with — phone model and camera or app — and from print or screen
• Your browser, if the problem looks like a display issue

Confirmed issues are corrected in the rendering engine and covered by a new automated decode-verification test so they cannot recur silently. See our methodology page for how KeepsakeCodes styles are built and verified.

What we cannot help with

KeepsakeCodes cannot recover content from a code we did not generate, cannot edit a code after it is printed (static codes contain their content directly), and cannot advise on printing services. For print-quality questions, your print shop is the right expert — bring a test scan.