What counts as valid
Clavem keys are 25 characters in five groups of five, separated by hyphens, made of letters and digits. Clavem ignores case and reads I and L as 1, O as 0 and U as V, so a line such as sIgne-tdemo-… is valid and the checker shows what Clavem would read it as. A UUID has 32 hex digits in groups of 8, 4, 4, 4 and 12; version 4 also needs a 4 at the start of the third group and 8, 9, a or b at the start of the fourth. Lemon Squeezy keys are UUID-style strings in lower case, so upper-case ones are accepted with a note. With acustom regular expression, a line is valid if the whole line matches.
How duplicates are found
Keys are compared in the form Clavem would use to look them up. For Clavem-format keys that is upper case with the confusable letters replaced, so ABCDO and abcd0 are the same key. For everything else it is the trimmed line in lower case. Only valid lines are compared, and the report lists each duplicated key with every line number it appears on.
Using the result
Fix or remove the invalid lines, then copy the valid, unique keys for your import. Typical causes of invalid lines are a header row, a missing group, a typographic dash pasted from a document, a trailing comma from a CSV or an invisible character. The checker names the problem for each line. To bring existing keys into Clavem, seeImport existing licenses, and to check one key against the server use the validate call in theAPI reference. Format is not the same as validity: a perfectly formed key can still be unknown, expired or revoked.
Questions
Does this check that a key exists or is active?
No. It only checks that each line has the right shape and that no key appears twice. Whether a key belongs to a customer, is active or has devices left is something only the licensing server knows. Clavem's validate endpoint answers that.
Are my keys uploaded anywhere?
No. The check runs in your browser and nothing is sent. Reloading the page clears the list.
Why does Clavem read I, L, O and U differently?
Clavem's keys use the Crockford base32 alphabet, which has no I, L, O or U, because they are easy to confuse with 1, 0 and V when someone retypes a key. Clavem reads I and L as 1, O as 0 and U as V, and ignores case, so a mistyped key still matches.
How are imported keys such as UUIDs matched?
As written, after trimming spaces at both ends and converting to lower case. That is why UUIDs that differ only in case count as duplicates here.
Make test keys with the license key generator. More tools are listed underfree tools.