How to use Detached Public-Key Signature Verifier
- Choose the original file or paste the exact message text. Text is encoded as UTF-8; spaces, line endings and a trailing newline affect verification.
- Supply one public JWK or a one-key JWKS from a source you trust independently. Private and symmetric keys are refused.
- Choose RS256 or ES256 and the signature encoding. Paste the detached signature or select its UTF-8 signature file; a selected signature file replaces the pasted value.
- Run Verify detached signature. Read the byte count, SHA-256 and valid/invalid result for this key and these bytes. A match does not establish who owns the key.
Example: Detached Public-Key Signature Verifier
Verify the supplied demo message with its matching public ES256 key and base64url signature.
Options
- Local UTF-8 signature file (optional)
- Up to 256 KiB; selected file replaces the pasted signature. Public data only.
- What to verify
- The exact bytes are hashed. A file is read as it is stored, so a text file with a trailing newline is hashed with that newline.
- Text
- Used when the source is text. The exact characters are hashed, including spaces and line breaks.
- File
- Used when the source is a file. The limit is 32 MB. The file stays on this device.
- Public JWK
- Paste the public key you trust, as a JWK or one-key JWKS. Private and symmetric keys are refused.
- Expected algorithm
- The algorithm the signature was made with. It must match the key "alg" when the key declares one.
- Signature encoding
- How the detached signature is written. The two encodings are not interchangeable, so pick the one the signature actually uses.
- Detached signature
- The signature bytes, written in the encoding you chose. A detached signature is separate from the message.
Supported inputs and limits
- RS256 or ES256 verification with one supported public JWK or a one-key JWKS.
- Message input is at most 32 MiB as file bytes or encoded UTF-8 text.
- An optional UTF-8 signature file is at most 256 KiB and replaces pasted signature text.
- Use the original bytes; no newline or BOM conversion is performed.
- No signing, private/symmetric keys, trusted-publisher discovery or key-ownership check is included.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Verify the same bytes that were signed
A file is verified as its exact bytes. Text mode encodes the entered text as UTF-8, so line endings, spaces and punctuation can change the result. A correct digest is useful for comparing the artifact, but the digest alone does not authenticate it. Establish the public key’s source separately.
Questions about Detached Public-Key Signature Verifier
Why can copied text fail?
Copying can change line endings or spaces. Verify the original file when the signature was made over file bytes.
Is the byte hash a signature?
No. A digest does not identify its publisher. The signature check uses your separately supplied public key.
Are files uploaded?
No. The tool reads the selected file locally in the browser.