How This JWK to PEM Converter Works
Paste a JWK or a PEM key, pick the algorithm it uses, and this jwk to pem converter, a jwk pem converter online covering both directions from one screen, imports it with the Web Crypto API and re-exports it in the other format instantly, a genuine convert jwk to pem online free workflow with nothing sent to a server. Flip the direction toggle to go the other way, a pem to json web key conversion, without retyping anything, the same panel layout just swaps roles. Whether you're staring at a json web key to pem conversion task or the reverse, this tool covers both.
When You'd Need to Convert JWK to PEM (or Back)
OAuth and OIDC identity providers publish their signing keys as a JWKS (JSON Web Key Set) endpoint, a list of JWKs, but most non-JavaScript crypto libraries, openssl, and many older JWT verification libraries expect PEM instead. Pulling one key out of a JWKS response and turning it into PEM is exactly what a jwks to pem converter is for, paste the single JWK object from the set, not the whole {"keys": [...]} wrapper, and convert it directly. Going the other direction, pem to jwk converter mode, comes up just as often, generating a JWKS to publish from an existing PEM key pair, or converting a key for a JavaScript library that only accepts JWK input.
Matching the Algorithm, Hash, and Curve to Your Key
The Web Crypto API needs to know exactly what kind of key it's importing before it can process it correctly, it can't infer an RSA key's hash algorithm or an EC key's curve just from the key bytes themselves. That's why an rsa jwk to pem conversion needs the right hash, usually SHA-256, matching RS256 or PS256, selected to match the key's actual alg field, and an ec jwk to pem or ed25519 jwk to pem conversion needs the matching curve, P-256, P-384, P-521, or Ed25519's fixed curve, picked before converting. Pick the wrong hash or curve and the import fails, not because the key is invalid, but because the algorithm parameters don't match what the key was actually generated for.
Common Uses
Converting a JWKS-published signing key into PEM so an openssl command or a non-JavaScript service can verify a JWT, generating a JWK to publish at a JWKS endpoint from an existing PEM key pair, and converting a key between two libraries that expect different formats are the most common reasons developers reach for this tool. It's also useful for inspecting what's actually inside a JWK, converting to PEM and back can reveal a key's real size or curve when a JWKS response doesn't make it obvious at a glance.