Change PFX (P12) Password
or drop your .pfx / .p12 file anywhere on this page
or drop your .pfx / .p12 file anywhere on this page
Open or drop the .pfx/.p12 — if it is password-protected, enter the current password when asked.
Type the new password, or tick "remove the password" for a blank one.
Click "Re-password & download" and import the new file wherever it is needed.
Vendors and CAs love to ship .pfx files protected with a throwaway password pasted in the same email — and then a compliance checklist asks you to change it. The openssl way is a two-step extract-and-repack that briefly leaves your private key in loose PEM files; this tool does the repack in one step, in memory, in your browser.
Open the file, unlock it (blank passwords are tried automatically), and set the new password — or remove it entirely for automation contexts that expect a passwordless archive. The re-packed file keeps the whole chain and the key together, ready for Windows, IIS, Azure or Java.
100% private“The archive is unpacked and re-packed entirely in this tab’s memory — the private key inside never touches disk in plain form and never leaves your device, unlike online converters that receive the file and both passwords.”
No. Certificates and key pass through byte-identical — only the encryption wrapper around the archive (and its integrity MAC) is rebuilt with the new password.
Yes — tick "remove the password". Some import wizards (notably Windows) prefer a password, but automation and appliances often want a blank one; Azure Key Vault, for example, hands out passwordless PFX files itself.
Make sure you are importing the newly downloaded certificate.pfx, not the original file — the old archive keeps its old password. Also watch for keyboard-layout differences when the password was typed on another machine.