Private keys never leave your browser
CertKit reads your .pfx, PEM or DER file in the tab you are looking at. The key is not uploaded, because there is no server step in the tool. Below: what that means, how other converters handle the same file, and how to confirm it yourself in about a minute.
What “client-side” means in practice
When you choose a file or paste a key, the browser hands those bytes to JavaScript running in this tab. That is the whole pipeline:
- The file is read with the browser’s File API. It stays in this tab’s memory; no form is posted.
- A local copy of node-forge 1.4.0, served from this domain, parses and decrypts the container.
- The result is written into the page: textareas you can copy, and downloads built as in-memory blobs.
- No request carries the file, the password or the key. The only network calls the tools make are for their own code, plus the optional “Load sample” button, which fetches a throwaway fixture from this site.
“Server-side” is the other arrangement: your browser posts the file to a web server, that server decrypts it, and the key exists for a moment in a process you do not control. It works, and plenty of tools do it, but it is a different trust decision. A server-side converter can also log request bodies, keep temporary files or sit behind a proxy you have never heard of. CertKit removes that decision from the list.
You do not have to take our word for any of this: the site source, the vendored library and the browser tests are public in therepository.
Where each converter processes your key
Every cell below is taken from the vendor’s own page, fetched on 22 October 2026. Nothing here says another tool is malicious. It says where the key is processed, which is a question you can answer for yourself.
| Tool | Where the key is processed | Upload required | Account required | Price | Source (checked) |
|---|---|---|---|---|---|
| CertKit (this site) | In your browser tab. No request carries the file; the parser runs from scripts served by this domain. | No | No | Free | Site source plus the DevTools check below · 22 Oct 2026 |
| SSL Shopper SSL Converter | On their server. The form ismethod="post" enctype="multipart/form-data" to/assets/snippets/sslshopper/ajax/ajax_convert.php, withkeyFile and pfxPassword fields. Their own note says the key “is sent to the server”. | Yes | No | Free, ad-supported | sslshopper.com/ssl-converter.html · 22 Oct 2026 |
| certkit.io PEM decoder | In the CertKit API, server-side. Their page states: “The contents of the PEM file will be sent to the CertKit API for decoding.” | Yes | No for the free tool; sign-in for the product | Free tool; product from $99/mo | certkit.io/tools/pem-certificate-decoder · 22 Oct 2026 |
Name collision worth knowing: certkit.io is a commercial certificate-lifecycle product from TrackJS LLC, unrelated to this site. Both are called CertKit; only one runs in your browser.
How to verify it yourself
This is a checkable claim, not a trust badge. Do it on a throwaway key the first time, then on the tool you actually intend to use.
- Open PFX → PEM and press F12 (or right-click → Inspect) to open DevTools. Switch to the Network tab and clear it.
- Run a conversion, or paste a test PEM intothe certificate decoder.
- Watch the request list. There is no new request during processing, and no request body contains BEGIN RSA PRIVATE KEY or the base64 body of your key. Use the Network filter box to search for a distinctive string from your file; a server-side tool matches, this one does not.
- The stronger test: load the page, then disconnect from the network (airplane mode, or DevTools → Network → Offline). The tools keep working, because the engine is already in the tab.
- Run the same steps on a converter you are comparing against. On SSL Shopper you will see the POST to ajax_convert.php carrying the key file, which is the behaviour their page describes.
Note the one exception: the “Load sample” button does fetch a fixture file from this site. It is a test file we ship, never yours.
What browser-local does not protect you from
Client-side processing moves the trust boundary, it does not delete it. These limits are real and worth stating plainly.
- The page itself is code you have to trust. If this site were compromised or served maliciously, the JavaScript could be changed to upload your key. “Runs locally” describes the code that is running, not a guarantee about every future version. Mitigations: the site is static files with no server-side code path, deploys come from the public repository, and you can read the source before you paste anything sensitive.
- Verify the domain. The address should belocalcertkit.pages.dev with a valid certificate. Bookmark it rather than following a link from a search result or a message. A lookalike domain can serve different JavaScript.
- There is one third-party request on the page. Cloudflare Web Analytics, a cookie-less visit counter, loads fromstatic.cloudflareinsights.com. It receives no file, key or password, and it is the only script not served from this domain. It is disclosed in theprivacy note.
- Your browser and machine are part of the boundary. A malicious extension, a compromised browser profile or malware on the device can read anything on the page. For production keys, use a clean browser profile on a machine you control, and prefer working offline.
- This is not a key-management policy. Local processing does not decide whether a key should exist in a browser at all. Handle production keys on the systems that own them, keep backups, and rotate anything that has travelled further than it should have.
Start with a throwaway key
Convert a test file, watch the Network tab, and only then bring a real one. Everything here is free and needs no account.
Convert a PFX to PEMDecode a certificateAll tools
Related: key and certificate match ·privacy note · roadmap