Convert SSL certificates between standard formats: PEM and PFX/PKCS#12. Essential for migrating certificates between IIS (Windows) and Apache/Nginx (Linux) servers.
File Extensions: .pem, .crt, .cer, .key
Encoding: Base64 ASCII
Common Use: Apache, Nginx, most Linux servers
Format: Text file with BEGIN/END markers
-----BEGIN CERTIFICATE----- MIIDXTCCAkWgAwIBAgIJAKL0UG... -----END CERTIFICATE-----
File Extensions: .pfx, .p12
Encoding: Binary
Common Use: Windows IIS, Microsoft servers
Features: Can contain certificate, private key, and entire chain in one file. Usually password-protected.
File Extensions: .der, .cer
Encoding: Binary
Common Use: Java platforms
Features: Binary format of PEM certificate
File Extensions: .p7b, .p7c
Encoding: Base64 ASCII
Common Use: Windows, Java Tomcat
Features: Can contain certificate and chain, but NOT the private key
Use Case: Migrating from Linux Apache/Nginx server to Windows IIS
Requirements: Certificate file, private key file, optional intermediate certificates
Result: Single .pfx file with password protection
Use Case: Migrating from Windows IIS to Linux Apache/Nginx
Requirements: PFX file and password
Result: Separate certificate and private key files
Use Case: Converting Java certificates to Apache format
Requirements: DER certificate file
Result: PEM formatted certificate
Use Case: Converting Apache certificates to Java format
Requirements: PEM certificate file
Result: DER binary certificate
â ī¸ Security Note: Your certificates and private keys are processed in real-time and are NOT stored on our servers. For maximum security, consider using OpenSSL command-line tools for production environments.
For advanced users, here are OpenSSL commands for common conversions:
openssl pkcs12 -export -out certificate.pfx -inkey privatekey.key -in certificate.crt -certfile ca-bundle.crt
openssl pkcs12 -in certificate.pfx -out certificate.pem -nodes
openssl x509 -inform der -in certificate.cer -out certificate.pem
openssl x509 -outform der -in certificate.pem -out certificate.der
PEM is a text-based format commonly used on Linux/Apache servers, while PFX is a binary format used on Windows/IIS servers. PFX can contain the certificate, private key, and chain in one password-protected file.
You can convert the certificate itself between formats (PEM â DER â P7B), but to create a PFX file, you need both the certificate AND the private key.
Different servers and applications require different certificate formats. For example, Apache uses PEM, IIS uses PFX, and Java uses DER or JKS.
While our tool processes everything in real-time without storage, we recommend using command-line tools (OpenSSL) for production certificates with private keys for maximum security.