This is a short but important security habit if you use Electrum on Windows. Verifying the Electrum installer signature helps confirm that the file you are about to install really came from the official Electrum project, not a phishing site or tampered download. If you are using Electrum without a hardware wallet, this matters even more because your computer is handling sensitive software directly.
The setup takes about 15 minutes once. After that, verifying a download usually takes only a couple of clicks and about a minute. That small effort can save you from installing fake wallet software.
Why verify Electrum downloads?
A phishing site can look almost identical to the real Electrum website. It may offer an installer that looks normal but contains malicious code or points your wallet to attacker-controlled servers. If you install it, you could lose funds before you even realise anything is wrong.
Signature verification gives you a technical check: did the file match the signature produced by the official signing key? If yes, and if you have correctly verified the key fingerprint from an independent source, you can be much more confident that the download is genuine.
The goal in this guide is simple:
- Install GPG4Win on Windows.
- Check the GPG4Win installer’s publisher certificate against the official site.
- Download the Electrum installer and its signature file from electrum.org.
- Import Thomas V’s signing key into Kleopatra.
- Confirm the key fingerprint against the Electrum documentation.
- Certify the key locally.
- Verify the Electrum package.
- Only install if you get a green, successful verification result.
Step 1: Download GPG4Win and check its integrity
Start by going to the official Gpg4win website and downloading the Windows installer. While that is downloading, use the “Check integrity” link on the site.

This step matters because you are trying to protect yourself from fake software. If your network, DNS, or browser were compromised in some way, you could be redirected to a fake GPG4Win site. Checking integrity helps confirm that the package you downloaded matches what the official site says it should.
The check-integrity page shows code signing certificate details for the Gpg4win installer. Write down the important values before running the installer, because Windows may show the publisher information in a prompt where it is not easy to read carefully.

Step 2: Verify the GPG4Win installer publisher certificate
When you run the GPG4Win installer, Windows may show a User Account Control prompt. Do not just click “Yes” without looking. Expand the additional information and view the publisher’s certificate.

Compare the certificate details shown by Windows with the values listed on the official Gpg4win integrity page. In particular, check that the serial number and other identifying information match what you wrote down.
If the certificate does not match, stop. Do not install the software. If it matches, continue.
Step 3: Install GPG4Win with defaults
For basic download verification on Windows, you can usually keep the GPG4Win installation simple. Use the default settings unless you have a specific reason to change them.
Once installed, Kleopatra is available for managing keys and verifying files. You do not need to become an OpenPGP expert to use this workflow. The important parts are: import the correct key, verify the fingerprint, certify it locally, and then verify the file.
Step 4: Download Electrum and its signature file
Now go to the official Electrum website at electrum.org and download the Windows installer. On the same page, also download the separate signature file for that installer.

You need both:
- The Electrum installer executable.
- The matching
.ascor PGP signature file for that exact installer.
Be careful when saving the signature file. Some browsers can behave unexpectedly when you choose “Save target as,” especially if the filename is not obvious. Make sure you do not accidentally overwrite the installer with the signature file, or save the signature under a confusing name. If needed, save it somewhere safe and rename it so it clearly belongs to the Electrum package.
After GPG4Win is installed, files in your Downloads folder may show new GPG-related icons and right-click options.

Step 5: Import Thomas V’s signing key into Kleopatra
Electrum’s official download page states that sources and executables are signed by Thomas V. You need to import Thomas V’s public signing key before you can verify the package properly.
Right-click the downloaded Thomas V key file, choose the GPG EX options, and select “Import keys.”

Kleopatra should confirm that a new certificate was imported. It may ask whether you want to mark it as certified. This is where the fingerprint check becomes critical.
Step 6: Check the fingerprint against the Electrum documentation
Before certifying Thomas V’s key, verify its fingerprint against the official Electrum documentation. The documentation at electrum.readthedocs.io includes instructions and the expected fingerprint information for verifying signatures.

In Kleopatra, look at the fingerprint of the imported Thomas V key. Compare it carefully with the fingerprint published in the Electrum documentation. These two values must match exactly.
This step is not optional. A phishing site could serve a different key that looks plausible but was not created by the official project. Your network or browser environment could also be compromised in a way that substitutes files. Checking the fingerprint from an independent, trusted source helps protect against that kind of attack.
If the fingerprints do not match, do not certify the key and do not install the file.
Step 7: Create a local OpenPGP certificate if prompted
When you first use Kleopatra to certify keys, it may ask you to create an OpenPGP certificate for yourself. This is only needed once on that computer.
The key pair created here lives locally on your machine. It does not need to be public or tied to a real identity in any special way. You can use simple local details and set a password as prompted. Choose a strong password, but do not reuse passwords from important accounts unnecessarily.
This local certificate is used so you can mark other keys as trusted for yourself on that computer.
Step 8: Certify Thomas V’s key locally
After confirming the fingerprint, certify Thomas V’s key. You can choose to certify it only for yourself rather than making a broader trust declaration.

You will be asked for the password you set when creating your local OpenPGP certificate. Once finished, the key should appear as certified in Kleopatra.
Do not import and certify random keys without checking them. Be selective about which signing keys you tell GPG4Win to trust. You are explicitly saying that this key is acceptable for verifying software on your machine.
Step 9: Verify the official Electrum download
With Thomas V’s key imported, fingerprint-checked, and certified locally, verify the Electrum installer.
Right-click the Electrum setup file, choose the GPG EX options, and select “Verify.” Kleopatra will check the signature against the downloaded signature file and the signing key.
If everything is correct, you should get a green result indicating that the signature was made by Thomas V and that the file matches the signature. That is the result you want before installing Electrum.
What an invalid or missing-key result means
It helps to know what failure looks like. If you verify a package from an unofficial source, you may see a red “invalid” or “bad signature” result. That means the file and its signature do not match in the expected way, or the package was not distributed by the official Electrum team. Do not install it. Delete it and go back to electrum.org for the real download.
You may also encounter an error saying that the signing key is unavailable or could not be certified. That usually means you have not imported and trusted the correct developer key for that version of the file.

The rule is simple: you are looking for a clear green verification success. Red, invalid, bad signature, missing key, or untrusted key results mean stop and do not install the file.
Practical checklist
Before installing Electrum on Windows, run through this quick list:
- Download GPG4Win from the official site.
- Check the GPG4Win package integrity page.
- Compare the installer publisher certificate with the official details.
- Install GPG4Win using defaults for basic verification.
- Go to electrum.org and download the Windows installer.
- Download the matching signature file from the same official page.
- Import Thomas V’s key into Kleopatra.
- Compare the imported key fingerprint with the Electrum documentation.
- Certify the key locally only after the fingerprint matches.
- Verify the Electrum installer.
- Install only if you get a green verification result.
Final thoughts
This process is not complicated once it is set up, and it gives you much more confidence that your wallet software is genuine. If you are using Electrum directly on a computer—especially without a hardware wallet—verifying downloads is one of the most practical security habits you can build.
The key point is not just “did I download from electrum.org?” It is: did the file verify successfully against an independently checked signing key? That extra step protects you from phishing sites, tampered files, and compromised networks that might otherwise trick a normal user into installing fake software.
Questions from viewers
Common questions from the comments on this video, with my answers.
Is verifying the SHA-256 checksum enough, or do I need to use PGP/GPG signatures?
It depends on where you get the checksums. If an attacker compromises the website, they can change both the download link and the listed SHA-256 hash. That’s why some projects distribute a signed file with the hashes instead of just listing them on the page. Using PGP allows you to verify that the list of hashes is authentic.
Why does Kleopatra say the signature is valid but not show the green box anymore? Do I need to verify all three Electrum signers?
Electrum recently moved to using multiple keys for verification. Unless you have all three imported and certified in Kleopatra, you won't get the full green box. However, one verified signature (like ThomasV's) is enough to trust the download. You don't need to verify the other two unless you want extra peace of mind, though doing so requires verifying their fingerprints through a separate chain of trust. (Apps and tools change, so check the current version if something looks different.)
I'm getting the error 'could not determine whether this is an S/MIME or an OpenPGP signature'. What am I doing wrong?
This usually means you are downloading the wrong file or the files aren't set up correctly. Make sure the signature file (.asc) is in the same folder as the executable file you are trying to verify. The filenames should be identical apart from the .asc extension on the signature file. If you right-click the exe and select verify, it should work if the corresponding signature is present.
How do I verify an Electrum download on Mac or Android?
For Mac, the process is essentially the same as Windows but uses different software; there are guides available online that walk through the specific steps for macOS. For Android, the GPG tools available generally don't support verifying files directly on the device. The best approach is to verify the download on a PC first and then copy the verified file over to your tablet.
Why should I trust the readthedocs.io website for the fingerprint?
You aren't trusting the documentation itself as much as you are trusting the digital signature. The goal is to ensure you are using the correct signing key by cross-referencing the fingerprint from the official documentation against the key you import.
Should I also verify hardware wallet firmware updates?
Generally, no. Hardware wallets will only accept updates signed by the vendor. They typically provide a hash for the update that you can check, but the device itself enforces the signature verification.
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.







