Certificate Conversion
Convert certificates and key material between common formats quickly and securely
Input
Paste certificate content or upload a file to convert it into another format
-
-
Conversion Options
Secure handling
Paste or upload your certificate content, convert it, review the result, then copy or download it immediately.
Format guide
Base64 text format commonly used for certificates, keys, and chains.
Binary encoding often used where raw certificate bytes are needed.
PKCS#12 package that can contain certificate, chain, and private key.
PKCS#7 bundle used mostly for certificate chains without private keys.
Quick notes
Auto Detect
Best for most inputs
Private Key
Needed for PFX/P12
Passphrase
For encrypted output
Converted Output
Ready when you are
No conversion yet
Paste or upload certificate content, choose the target format, then convert
Detected Input
-
Output Format
-
File Name
-
Learn more & FAQ
What does a certificate converter do?
SSL/TLS certificates and keys are stored in several incompatible formats - PEM, DER, PFX (PKCS#12), and CRT - depending on which server or platform issued or needs them. This tool converts between those formats entirely in your browser, so you can move a certificate from one web server stack to another without a command-line tool.
How to use the converter
Upload your certificate (and private key, if required), choose the source and target formats, and the converter produces the file in the new format for download. If your source file is a PFX bundle, you'll need its passphrase to unlock it before conversion - that passphrase, the certificate, and the key never leave your browser.
Frequently asked questions
What's the difference between PEM, DER, PFX and CRT certificate formats?
PEM is a Base64 text format (the most common on Linux/Apache/nginx), DER is its binary equivalent, PFX (PKCS#12) bundles a certificate and private key together in one encrypted file (common on Windows/IIS), and CRT is usually just a certificate file in either PEM or DER encoding depending on the platform that produced it.
Why do I need to convert my certificate at all?
Different servers and platforms expect different formats - moving a certificate issued for IIS (PFX) to an nginx server (PEM), for example, requires converting it first. Mismatched formats are one of the most common reasons a TLS setup fails after a migration.
Is it safe to convert a private key using a web tool?
Converting a PFX that contains a private key means handling sensitive material - this tool performs the conversion entirely in your browser, so the certificate and key are never uploaded to a server.
What does a PFX passphrase protect?
A PFX/PKCS#12 file encrypts its contents, including the private key, with a passphrase you set when it was created. You'll need that same passphrase to open or convert the file - there's no way to recover it if it's lost.
Can I convert a certificate chain, or just a single certificate?
You can convert a full chain (leaf certificate plus intermediates) as long as it's bundled in the source file - the output preserves every certificate in the chain in the target format.