Open your .p7b/.p7c file — binary or Base64 form both work.
Paste the private key that belongs to the certificate; add its passphrase if the key is encrypted.
Choose a password for the output file and pick .pfx or .p12.
Click Create and import the downloaded file into Windows, IIS, Azure or your Java keystore.
Windows certificate authorities often deliver a .p7b bundle — your certificate plus its chain, but no key — while the machine you are moving to wants a single .pfx/.p12 with the key included. This tool combines the two: open the .p7b, paste the private key that belongs to the certificate, set a password, and download a ready-to-import PFX.
The bundler finds which certificate in the bundle your key actually matches and puts it first (the order importers expect), packs the rest as the chain, and encrypts the file under your password — all in this browser tab. Your private key is never uploaded anywhere, which is the whole reason to do this conversion here rather than on a converter site.
100% private“The .p7b, your private key, and the finished PFX exist only in this browser tab’s memory — nothing is uploaded, and you can run the conversion with your network disconnected. Certificates are public; the key is the secret, and it stays with you.”
PKCS#7 bundles carry certificates only — the key never left the machine where the certificate request was generated. A PFX by definition contains both, so the key must be supplied from your side. If you cannot find it, look on the server where the CSR was created.
The tool compares your key against every certificate in the bundle mathematically. No match means this key belongs to a different certificate (perhaps an older renewal). Locate the key generated alongside the CSR for THIS certificate.
The in-browser bundler currently packs RSA keys. For an EC key, extract the certs with the P7B → PEM tool, then run: openssl pkcs12 -export -out certificate.pfx -inkey key.pem -in certs.pem