Clavem

Free tool

Ed25519 key pair generator

Generate an Ed25519 key pair with your browser's Web Crypto and copy both keys as base64url or PEM. Use it to test code that signs or verifies license tokens. Nothing leaves the page.

Test keys only. A private key made in a browser can be seen by extensions, by other people on a shared computer and by clipboard tools. For a key that protects real licenses, generate it offline on a machine you control.

Key pair

Generating a key pair.

Public key share

Private key secret

Sign a test token

Signs the claims below with the private key above and gives you a token in the Clavem format (sgt1.<payload>.<signature>). Paste it into your own verifier together with the public key.

How it works

The page calls crypto.subtle.generateKey with the Ed25519 algorithm, then exports the keys. The public key is exported as 32 raw bytes and as an SPKI structure. The private key is exported as a PKCS#8 structure, whose last 32 bytes are the seed, the secret number that defines the key. Base64url shows the raw bytes on one line without padding. PEM wraps the longer structure in -----BEGIN ... KEY----- lines for OpenSSL and servers.

After generating, the page signs a short message and verifies it with the public key, so you know the pair works before you copy it. If your browser has no Ed25519 support, the tool says so and shows the OpenSSL commands that do the same. Ed25519 is in Web Crypto from Safari 17, Firefox 129, Chrome 137 and Edge 137.

Testing a Clavem-style verifier

Clavem signs every activate and validate response with a private key that belongs to the product and never leaves Clavem. Your app verifies tokens with the public half. To test your verification code without a real license, sign a token here: you control the claims, including expired and revoked cases, and you check that your code accepts the good token and rejects a changed one. The token decoder can verify the same token in the browser, so you have a second opinion on your own result.

The format and the checks your app should make are described in offline verification.

Questions

Is it safe to generate a private key in a browser?

The key is made by the browser's own cryptography code and stays in the page, but browser extensions, shared computers and clipboard managers can read what you see and copy. Treat keys from this page as test keys. Make a production signing key offline, on a machine you control, and keep it out of source control.

What is the difference between base64url and PEM?

Both encode the same bytes. Base64url is the raw 32-byte key as one line without padding, which is what Clavem uses for public keys. PEM wraps a longer standard structure (SPKI for public keys, PKCS#8 for private keys) in header lines, which is what OpenSSL and many servers expect.

Can I use this key pair with Clavem?

Clavem creates a key pair for each product and keeps the private half, so you do not bring your own. Use this page to test your verification code with tokens you sign yourself. A token signed here will not verify against the public key of a Clavem product.

Why does my browser say Ed25519 is not supported?

Ed25519 in Web Crypto arrived in Safari 17, Firefox 129 and Chrome and Edge 137. Older versions throw an error when asked for the algorithm. Update the browser, or use the OpenSSL or Node commands shown by the tool.

Keep reading in the offline verification guide, or generate random license keys with thelicense key generator. More tools are listed under free tools.