Guide

THE TOOLBOX / SECURITY UTILITIES

Generate & convert JWK
and PEM keys locally.

Generate ECDSA P-256, RSA-OAEP 2048, and Ed25519 keypairs or convert between RFC 7517 JWK, JWKS, and SPKI/PKCS#8 PEM formats 100% locally in your browser.

OPERATION & ALGORITHMRFC 7517 JWK · PKCS#8 / SPKI PEM
All cryptographic operations run locally via window.crypto.subtle. Private keys never leave your browser—clear the workspace when finished.
Key Algorithm

Select an operation and click Run to generate or convert keys locally.

KEY MATERIAL OUTPUTReady

THE DETAILS

RFC 7517 JSON Web Keys, SPKI/PKCS#8 PEM, and JWKS publishing.

1. Browser-Native Web Crypto Keygen

Keys are generated using your OS cryptographically secure random number generator through crypto.subtle.generateKey—no third-party server ever sees your key material.

2. One-Click JWKS Endpoint Format

After generating a keypair, switch to the JWKS Endpoint tab to grab a ready-to-host public {"keys":[...]} document for OIDC or JWT signature verification.

3. Bidirectional PEM ↔ JWK Conversion

Convert OpenSSL-generated SPKI/PKCS#8 PEM keys into JWK JSON for Cloudflare Workers, Jose, or Auth0, or convert a JWK back into PEM for backend services.

Frequently Asked Questions

What is the difference between JWK, JWKS, and PEM key formats?

PEM (Privacy-Enhanced Mail) stores DER-encoded ASN.1 keys as Base64 text wrapped in BEGIN/END headers (used by OpenSSL, Nginx, and Node.js). JWK (RFC 7517) represents the same key parameters in JSON for OAuth 2.0, OIDC, and JWT libraries. A JWKS wraps one or more public JWKs inside a {"keys": [...]} array for /.well-known/jwks.json endpoints.

Are generated private keys ever transmitted over the network?

No. Key generation and PEM ↔ JWK conversion execute entirely inside your browser’s Web Crypto API (window.crypto.subtle). Zero key bytes leave your device.

Which cryptographic algorithms are supported?

The tool supports ECDSA P-256 (ES256), RSA-OAEP 2048-bit with SHA-256, and Ed25519 (where supported by your browser’s Web Crypto implementation).

What PEM header types work for PEM-to-JWK conversion?

Standard unencrypted SPKI public keys (-----BEGIN PUBLIC KEY-----) and PKCS#8 private keys (-----BEGIN PRIVATE KEY-----). Legacy PKCS#1 RSA keys or passphrase-encrypted PEM blocks should be converted to PKCS#8 first.

Can I publish the JWKS output directly for JWT verification?

Yes. Switch to the JWKS Endpoint tab after generating a keypair to copy only the public key wrapped in a standard {"keys": [...]} payload—never publish the private PEM or private JWK fields (d, p, q).