PEM certificate and key to a password-protected .pfx (PKCS#12), key never uploaded
Runs in your browser. Nothing you type is sent anywhere. Checked against sources on 16 Nov 2026.Checked against the tool’s code on 18 November 2026. Figures read from their sources on 16 November 2026. What we collect
Paste the certificate and its private key and this page builds a password-protected .pfx in your browser; the key is never uploaded. From the example it plans an RSA 2048 private key + certificate for shop.example.com + 1 chain certificate, checks the key matches first, then encrypts the key with AES-256-CBC and PBKDF2-HMAC-SHA-256.
| Part | How it is stored |
|---|---|
| Example contents | RSA 2048 private key + certificate for shop.example.com + 1 chain certificate |
| Private key | PBES2: PBKDF2-HMAC-SHA-256, 2048 iterations, 16-byte salt, AES-256-CBC |
| Certificates | Leaf first, then the chain; stored unencrypted (certificates are public) |
| Integrity check | HMAC-SHA-256, 2048 iterations |
| Friendly name | The certificate's Common Name |
Nothing is uploaded: this runs in your browser.
Paste the certificate, the private key and any chain certificates, or open the .pem, .crt and .key files.
Check the green line: the key must match the certificate, or no PFX is made.
Type the password that will protect the PFX.
Press Download .pfx and import the file into Windows, IIS, Azure or Java.
Linux servers (nginx, Apache, Let's Encrypt) keep the certificate and the private key as two PEM text files. Windows, IIS, Azure App Service, Exchange and many Java and .NET programs want one file instead: a PFX, also called PKCS#12 or .p12, which holds the certificate, its chain and the private key, protected by a password.
Most online converters ask you to upload the private key, which hands a stranger the key to your site. This page builds the file with your browser's own WebCrypto, and the key and password never leave it. It also refuses to build a PFX from a key that does not belong to the certificate, the commonest reason an imported PFX fails.
| Question | Answer |
|---|---|
| Input | A PEM certificate, its private key (PKCS#8, PKCS#1 or EC) and any chain certificates, in any order |
| Output | One .pfx file with the leaf certificate first, the chain, and the encrypted key |
| Encryption | AES-256-CBC with PBKDF2-HMAC-SHA-256 (2048 iterations), HMAC-SHA-256 integrity check |
| Reads it | Windows 10 version 1709 and later, Windows Server 2019 and later, macOS, Java 11 and later, OpenSSL 1.1.1 and 3 |
| Older systems | Windows Server 2016 and earlier need the legacy 3DES layout: openssl pkcs12 -export -legacy |
| Also | Each certificate as a binary .cer (DER) file |
Checked on 16 November 2026 against RFC 7292, RFC 8018 and the OpenSSL 3 pkcs12 manual. Page last updated on 16 November 2026.
The terminal equivalent is openssl pkcs12 -export -in certificate.pem -inkey private-key.pem -certfile chain.pem -out shop.example.com.pfx. To check a key and a certificate belong together without building anything, use the certificate key matcher; to read what a certificate says, the certificate decoder.
Paste the certificate and the private key on this page, or open the .crt and .key files, type a password and press Download .pfx. The file is built by your browser with WebCrypto, so nothing is installed and the private key is never uploaded. Chain certificates go in the same box.
Only when the key never leaves your device. Many converters upload the key to their server, which then holds a copy. Here the PEM text is read and encrypted inside the page; nothing is sent to any server or stored anywhere. Check the network tab in your browser to confirm.
None in content: .pfx and .p12 are two file extensions for the same PKCS#12 format. Windows and IIS usually say .pfx, Java and macOS often say .p12. Rename the downloaded file to .p12 if a program asks for that extension; the bytes stay the same.
Three usual causes: the private key does not belong to the certificate (this page refuses that case), the password is mistyped, or an old system cannot read AES-256. Windows Server 2016 and older need the legacy 3DES layout, which openssl pkcs12 -export -legacy writes.
Usually yes. Servers such as IIS send the chain to browsers, and a missing intermediate certificate gives some visitors a trust error. Paste the intermediate certificates from your certificate authority below the key; the page puts the leaf certificate first and the chain after it, whatever the order you paste.
Press Certificate as .cer (DER) to save each certificate as a binary .cer file, the form Windows and Java import. A .crt file is often just the PEM text with another name, so renaming .pem to .crt is enough when a program accepts PEM text.
Rates and rules change; check the source before you rely on a figure.
Still stuck? Ask about PEM to PFX Converter: Make a .pfx / .p12 in Your Browser and anybody who knows can answer. No account needed.
Same job, other tools: SSL Certificate Decoder – Decode a TLS certificate you already have and see every field a browser looks at · 2FA Code Generator – Get the current two-factor code from a setup key, without a phone · PEM Decoder – Work out what is inside a PEM file, whichever of the five things it turns out to be.
On the related tools: JWT Decoder – Paste a token to read its header, payload and expiry.
On the same topic: Certificate Key Matcher: Does the Private Key Match? – Check that a private key belongs to an SSL certificate or CSR; the key is never uploaded · Certificate Decoder – Read an SSL certificate, CSR or public key: names, dates, key size and fingerprints · CSR Generator: Create a CSR and Private Key in Your Browser – Make a certificate signing request and its private key on your device, no upload.