b2KIT

Ed25519 Signature Tool

Generate Ed25519 key pairs, sign messages, and verify signatures using the EdDSA algorithm with Curve25519.

Tested tool guide Tested browser tools Checked August 16, 2026

What Ed25519 Signature Tool does and how it behaves

Ed25519 Signature Tool creates signing key pairs, produces Ed25519 signatures from a private key and message, and checks signatures using the corresponding public key. A valid signature establishes that the corresponding private key was used for the exact message bytes, but not that its holder personally approved the message; it does not encrypt or conceal the message. The most common surprise is that visually insignificant changes, including spaces, line endings, or Unicode normalization, create a different message and invalidate the signature. Because the tool runs in the browser, entered private-key material is not uploaded.

How the result is produced

1

Key pair roles

Key generation produces private signing material and a related public verification key. Keep the private value secret and distribute only the public key. Ed25519 public keys are 32 octets. Private-key representations vary among tools: some expect a 32-octet seed, while others expose a longer combined representation, so copied values must match the receiving field's expected format.

2

Signing and verification

Signing combines the private key with the exact message to produce a 64-octet Ed25519 signature. Verification evaluates the message, signature, and public key together and returns whether that combination is valid. Standard Ed25519 signing is deterministic, so an unchanged key and identical message bytes produce the same signature. Verification requires no private key.

Good uses

  • Generate a development key pair for testing an application that accepts Ed25519-signed requests.
  • Sign a small configuration file or release manifest and compare the result with another Ed25519 implementation.
  • Verify a received message and signature against a public key obtained through a trusted, separate channel.

Limits and checks

  • A valid result applies only to the exact message bytes. Added whitespace, changed line endings, character re-encoding, or Unicode normalization can make verification fail.
  • Key and signature text may be represented as hexadecimal, Base64, or another encoding. Correct cryptographic bytes entered in the wrong textual format will be rejected or interpreted differently.
  • Successful verification proves consistency among the public key, message, and signature. It does not establish the signer's real-world identity, authorization, signing time, message freshness, or confidentiality.

Common questions

Can I use an X25519 key in this tool?

No, not as a general substitution. Ed25519 is a signature scheme built on Edwards25519, while X25519 is used for key agreement and has different key semantics and encodings. Defined conversions exist in some protocols and libraries, but an X25519 key should not be pasted into an Ed25519 field with the expectation that it is interchangeable.

Does a valid signature prove who sent the message?

No. It proves that the signature matches the message and public key, which indicates access to the corresponding private key. Identity depends on how reliably the public key was associated with a person or system. The result also provides no timestamp or replay protection, so a valid signed message can still be old or reused.

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