b2KIT

Ed25519 Key Generator

Generate Ed25519 key pairs for high-performance digital signatures and SSH authentication.

Tested tool guide Tested browser tools Checked August 16, 2026

What Ed25519 Key Generator does and how it behaves

An Ed25519 key pair consists of a secret signing key and a public verification key. This generator creates both in the browser, so the private material is not uploaded. The public half can be distributed, while the private half must remain confidential. Ed25519 keys authenticate signatures; they do not encrypt messages or files. A common surprise is that exported keys can be longer than Ed25519's raw 32-byte values because SSH, PEM, or other containers add format information.

How the result is produced

1

Public-key derivation

Ed25519 begins with a 32-byte secret input. SHA-512 expands that value, specified bits are adjusted, and the resulting scalar is multiplied by the curve's standard base point. The encoded point is the 32-byte public key. This derivation is one-way in practical use: publishing the public key does not disclose the secret input.

2

Random generation

Each generation creates a new secret value and derives its matching public key. There is no fixed output that can be truthfully shown for a pasted input, which is why this profile has no worked example. Repeating generation should produce a different pair. Save the private result before leaving the page if the generated identity must remain usable.

Good uses

  • Create a new SSH identity for a developer, automation account, or isolated server login.
  • Generate a signing key pair for an application that creates and verifies Ed25519 signatures.
  • Make a separate development or test identity without copying a production private key.

Limits and checks

  • Confirm the encoding before importing a result. Raw bytes, hexadecimal or Base64 text, PEM containers, and OpenSSH key records are not interchangeable.
  • At the algorithm level an Ed25519 public key is 32 bytes, but an encoded public-key record can be longer because it includes type and container data.
  • Ed25519 is a signature scheme. An Ed25519 signing key should not be treated as an encryption key or assumed to work with software expecting X25519 key agreement.

Common questions

Can I regenerate the same private key later?

No, not from the public key or by pressing generate again. Normal key generation is randomized, and the public key does not contain enough information to reconstruct the private key. Retain a protected copy of the private output if the identity matters. If it is lost, generate a replacement pair and update every system that trusted the old public key.

Can the public result go directly into an SSH authorized_keys file?

Yes only when it is presented as an OpenSSH public-key record. Such a record uses the key type ssh-ed25519, followed by the encoded key data and optionally a comment. A raw, hexadecimal, PEM, or differently wrapped public key cannot simply be pasted into authorized_keys. The private half must never be placed in that file.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools