Quick intro
This ledger feature matrix is a compact, hands-on quick reference to compare Ledger models side-by-side. I ran these models through setup flows, daily use, and firmware updates during testing cycles. What I've found: differences are often about convenience and workflow, not core cryptographic guarantees. Short transactions are fast. Verifying long addresses is where screens matter.
Which column should you stare at first? That depends on whether you prioritize mobile use, app capacity, or a big on-device display.
How to read this ledger feature matrix
The table below lists practical, non-spec numbers: connectivity, whether a secure element is present (hardware isolation for private keys), battery, app capacity (relative), passphrase support, and whether the model is friendly for multisig workflows. I also flag notes and link to full reviews. Use this like a spec sketch—not a shopping cart.
Glossary (short):
- secure element: a tamper-resistant chip that stores private keys.
- passphrase: an optional extra word (often called a 25th word) that creates an additional account derived from the seed phrase.
- app capacity: how many blockchain apps a device can hold simultaneously (relative: limited/moderate/large).
- air-gapped: a workflow that avoids connecting the device to an online machine during signing.
Ledger model feature matrix (quick table)
| Model |
Primary use |
Screen |
Connectivity |
Secure element |
Battery |
App capacity |
Passphrase |
Multisig-friendly |
Notes |
| Nano S |
Entry-level storage |
Small |
USB only (cable) |
Yes |
No |
Limited |
Yes |
Yes (via third-party wallets) |
Compact and basic; see nano-s-review |
| Nano S Plus |
Mid-level / more tokens |
Medium |
USB only (cable) |
Yes |
No |
Moderate |
Yes |
Yes |
More headroom than Nano S; see nano-s-plus-review |
| Nano X |
Mobile-first / many apps |
Medium |
USB + Bluetooth |
Yes |
Yes |
Large |
Yes |
Yes |
Bluetooth for mobile convenience; see nano-x-review |
| Stax |
Premium UX / big display |
Large (e-ink) |
USB / Mobile-capable |
Yes |
Yes |
Large |
Yes |
Yes |
Focused on on-device review of transactions; see stax-review |
| Blue |
Legacy touchscreen model |
Large |
USB (legacy) |
Yes |
Varies (legacy) |
Moderate |
Yes |
Yes |
Older product line — see ledger-blue-review |
| Flex |
Card-style, compact secondary device |
Minimal / no screen |
USB / OTG (model-dependent) |
Yes |
Varies |
Limited |
Yes |
Yes |
Often used as complementary device — see ledger-flex-review |
Use the links in the Notes column to jump to full model reviews and setup guides that unpack each item's screens, menus, and firmware steps.
Model quick notes — who each is for
H2-level summary helps pick fast.
- Nano S — Best for: beginners on a tight budget who want non-custodial self-custody for a few main assets. Look elsewhere if you hold many tokens or want mobile-first access.
- Nano S Plus — Best for: desktop-first users who need more app room without Bluetooth. Look elsewhere if you require mobile pairing.
- Nano X — Best for: people who sign transactions on the go and want many apps available at once. Look elsewhere if you avoid wireless connections (more below).
- Stax — Best for: people who value a large on-device display for reviewing addresses and NFTs. Look elsewhere if you want absolute minimalism.
- Blue / Flex — Best for: legacy collectors or those who need a secondary/backup device. Look elsewhere if you want the latest firmware conveniences.
I believe a model should match your threat model more than your FOMO. And that means thinking beyond features.
Security architecture: what actually matters
All current Ledger models include a secure element to keep private keys isolated from the host machine. That’s a baseline. Firmware is signed; devices perform attestation during updates. But differences matter for workflows: a larger screen allows you to visually verify long addresses (helpful against some UI attacks). Air-gapped signing is possible in advanced workflows (with PSBT or QR workflows) — see advanced-air-gapped for examples.
If supply-chain risk is a concern, follow the guidance in buying-safely-and-supply-chain and verify authenticity before initializing.
Seed phrase and backup options (12 vs 24, passphrase, SLIP-39)
Most Ledger models initialize with a 24-word recovery phrase by default (this is common practice for higher entropy). Passphrase support (the so-called 25th word) is available on-device and can create separate hidden accounts. Use it carefully — it turns your single recovery phrase into many possible accounts and increases recovery complexity.
Shamir backup (SLIP-39) is not a native, on-device backup scheme for these models. If you want a Shamir-split backup, you'll need a compatible external tool or a separate wallet that supports SLIP-39. Read the practical backup guidance at seed-phrase-management and consider metal backup plates (seed-backup-plates) for long-term durability.
Multisig and advanced setups
Want more than single-sig self-custody? Multisig spreads signing across multiple devices or keys and drastically reduces single-point-of-failure risk. All Ledger models can act as a signer in multisig setups when used with compatible wallet software (Electrum, Sparrow, etc.). Models with larger app capacity simplify having multiple co-signer apps available on the device.
For step-by-step multisig workflows and compatibility notes, see multisig-for-ledger and multisig-guide.
Connectivity trade-offs: Bluetooth, USB, NFC
Bluetooth is convenient for phone use. But convenience increases the attack surface slightly; some users prefer USB-only devices and use an air-gapped signing workflow instead. USB (wired) eliminates wireless attack vectors but exposes you to risks from compromised hosts (so keep firmware current and use trusted computers). NFC is uncommon for most Ledger models; check model pages for details.
Is Bluetooth safe for a hardware wallet? Short answer: many modern implementations include encryption and require physical confirmation on-device for every transaction. But if your threat model assumes a targeted attacker in your local environment, wired and air-gapped workflows are safer. See more in bluetooth-usb-nfc-security.
Common mistakes and safety checklist
- Don’t buy from unofficial sellers — supply-chain tampering is a real risk. See buying-safely-and-supply-chain.
- Never enter your seed phrase into a webpage or phone. No exceptions.
- Use a metal backup plate and store copies geographically separated for inheritance scenarios (see inheritance-planning-for-crypto).
- Verify firmware authenticity before upgrading (follow firmware-update-guide).
- Test recovery with a small transfer before depositing large amounts (practical test: send a small test amount and restore on another device).
But even experienced users slip up. A short checklist on a printed card helps.
FAQ — real user questions
Q: Can I recover my crypto if the device breaks?
A: Yes. If you have your seed phrase (recovery phrase) and passphrase if used, you can restore keys on a compatible hardware wallet or recovery tool. See recover-if-device-lost for step-by-step options.
Q: What happens if the company goes bankrupt?
A: Your private keys are non-custodial and stored by you. The device maker going out of business doesn’t move your crypto — but software support and firmware updates may become limited. Read more at company-bankruptcy-what-happens.
Q: Is Bluetooth safe for a hardware wallet?
A: See the connectivity section above and this deep-dive: bluetooth-usb-nfc-security.
Final thoughts and next steps (CTA)
This ledger comparison table should help you narrow down which model matches your workflow: desktop-first, mobile-first, or large-screen verification. In my experience, choosing the right device is mostly about user flows — where you sign, how many tokens you manage, and whether you want multisig.
For detailed, hands-on setups and step-by-step guides visit the model pages and setup resources: setup-ledger-step-by-step, nano-s-review, nano-s-plus-review, nano-x-review, and stax-review.
Want a deeper security primer? Check hardware-wallet-security-architecture and firmware-update-guide next. And if you have a specific use case — say long-term cold storage or an inheritance plan — the cold-storage-strategy and inheritance-planning-for-crypto pages are good follow-ups.
If you want, tell me which features you care about most (mobile, app capacity, or screen), and I can point you to the exact model reviews and setup walkthroughs that match your needs.
