Electrum ETH
Docs Download
Downloads

Download Electrum ETH for desktop

Choose your build for Windows, macOS, or Linux. Electrum ETH is a non-custodial Ethereum wallet – keys stay on your device. On this page you can also find all builds and checksums, release notes, and a step-by-step guide for verifying downloads.

Stable builds are recommended for everyday use.
Always verify downloads before installing, especially on machines that hold significant value.
For detailed documentation, see Electrum ETH Documentation.

Jump to

All builds & checksums Release notes How to verify downloads Release model System requirements Installation & first run Install troubleshooting
Last updated: 21 January 2026

1. All builds & checksums All builds & checksums

This section explains how to find all available builds of Electrum ETH, and how to use checksums and signatures to ensure that the file you downloaded has not been tampered with.

1.1 What “builds” means

  • Platform: Windows, macOS (Intel / Apple Silicon), Linux (AppImage / packages).
  • Channel: stable vs. pre-release/beta (if offered).
  • Format: installer, portable image, or archive, depending on the OS.

The “All builds” view typically lists all supported combinations for a given release, including older versions that may still be relevant for compatibility or debugging.

1.2 Checksums and signatures

For each downloadable file, we aim to publish at least one of:

  • A cryptographic hash (for example, SHA256).
  • Optionally, a detached signature (for example, .asc file).

You can use these values to verify that the file you downloaded is exactly the file we published.

1.3 Typical layout of an “All builds” listing

Whether on this site or on GitHub, an “All builds” section usually provides a table or list per release, including:

File
e.g. electrum-eth-x.y.z-win64.exe
Platform
Windows / macOS / Linux
Checksum
SHA256: <hash>
Signature
Optional .asc with signing key
If you maintain a mirror or package Electrum ETH for a distribution, always refer users back to the official checksums and signatures so they can verify integrity themselves.

2. Release notes Release notes

Release notes describe what changed between versions: new features, bug fixes, security updates, and known issues. They help you decide when and how to upgrade.

2.1 What to look for

  • Breaking changes: items marked as breaking or requiring manual action (e.g. re-sync, new backup).
  • Security fixes: high-priority updates that address vulnerabilities. These are typically highlighted.
  • Routing & networks: additions or removals of supported networks, or changes in the routing engine.
  • UI/UX updates: improvements to the wallet view, activity lists, or settings.

2.2 Using release notes in practice

You can use release notes to:

  • Decide whether to upgrade immediately (e.g. security fix) or later (e.g. minor UI changes).
  • Understand why a behaviour changed after an update (for example, new route selection rules).
  • Track which version introduced a specific feature or bug fix.

For technical debugging, you can cross-reference release notes with commits on the project’s repository.

3. How to verify downloads How to verify downloads

Verifying downloads ensures that the file you install is the one we published, and that it was not corrupted or tampered with in transit. The exact commands may depend on your operating system, but the general process is the same.

3.1 Basic checksum verification

Generic workflow:

  • Download the installer or image file.
  • Download the corresponding checksum (e.g. SHA256 hash).
  • Compute the checksum locally and compare with the published one.

Example: Linux / macOS

In a terminal, navigate to the folder with the downloaded file:

sha256sum electrum-eth-x.y.z.AppImage

Compare the output hash with the one from the official checksums. They must match exactly.

Example: Windows (PowerShell)

In PowerShell, run:

Get-FileHash .\electrum-eth-x.y.z-win64.exe -Algorithm SHA256

Compare the resulting hash with the published SHA256 value. Any difference means the file must not be trusted.

3.2 Verifying signatures (if provided)

If Electrum ETH publishes detached signatures (e.g. .asc files), you can use a tool such as GPG to verify:

  • Import the official signing key.
  • Verify that the key fingerprint matches the one we publish on official channels.
  • Run a signature verification command (for example, gpg --verify signature.asc electrum-eth-x.y.z.AppImage).
If checksum or signature verification fails, do not install the file. Re-download from the official source and, if the mismatch persists, treat it as a potential security issue and contact security@electrum.eth.

4. Release model

Understanding the release model helps you decide which version to run in production, which to use for testing, and when to upgrade.

4.1 Stable vs. pre-release

  • Stable releases: tested builds intended for everyday use; recommended for most users.
  • Pre-releases / betas: include newer features and fixes but may have unresolved issues; recommended for testing, not critical funds.

4.2 Versioning

Typical versioning scheme:

  • Major (X): large changes, possibly breaking behaviour or major UI updates.
  • Minor (Y): new features and improvements, usually backwards compatible.
  • Patch (Z): bug fixes and small improvements, recommended if you are already on the same X.Y line.

5. System requirements

Electrum ETH is designed to run on mainstream desktop operating systems. Exact requirements may vary between versions, but the following are typical guidelines.

5.1 Operating systems

  • Windows: recent 64-bit versions (desktop editions).
  • macOS: supported macOS releases on Intel and Apple Silicon hardware.
  • Linux: common 64-bit distributions; AppImage builds are generally portable.

Check individual release notes for specific OS version support changes.

5.2 Hardware

  • Modern 64-bit CPU.
  • At least 4 GB of RAM recommended.
  • Sufficient disk space for the app and cache. Full node operation (if you run your own node) requires much more and is handled separately.

For the best experience, use SSD storage and a stable network connection.

6. Installation & first run

This section summarises typical installation flows. For detailed usage, see the main Documentation.

6.1 Windows

  • Download the 64-bit installer.
  • Verify checksum (and signature, if available).
  • Run the installer and follow the prompts.
  • Launch Electrum ETH from the Start menu.

6.2 macOS

  • Download the macOS build for your architecture.
  • Verify checksum/signature before opening.
  • If macOS flags the app as from an unidentified developer, use standard OS steps to allow it (e.g. via System Settings → Privacy & Security).
  • Drag the app into Applications if applicable.

6.3 Linux

  • Download the AppImage or distribution-specific package.
  • Verify checksum/signature.
  • For AppImage, mark it executable (chmod +x file.AppImage) and run it.
On first run, the wallet will guide you through creating or restoring a wallet. Make sure you understand Backups & recovery before moving significant value.

7. Install troubleshooting & FAQ

7.1 Installer does not start

  • Confirm that you downloaded the correct build for your OS.
  • Check that checksums match; if not, download again from the official site.
  • Ensure security software (antivirus, SmartScreen, Gatekeeper) is not silently blocking the file. If it is, verify the file again before allowing it.

7.2 App does not open or crashes on startup

  • Try launching from a terminal to see error messages (macOS/Linux).
  • Check release notes for known issues with your OS version or GPU setup.
  • Try a clean reinstall with a fresh download.

7.3 “Unknown developer” / notarization warnings

Some platforms show additional warnings for downloaded apps. Before bypassing these:

  • Always verify checksums and, if available, signatures from the official sources.
  • Proceed only if you trust the build and the source you downloaded from.

7.4 Getting help

You can get additional help from:

When asking for help, you can safely share error messages, OS versions, and checksums, but never your seed phrase or private keys.