Trezor released Suite 26.10.2 on October 21, 2026, listing support for passphrases up to 128 characters. That headline is not an instruction to lengthen the phrase for an existing wallet. Before using the expanded limit, check the device model, firmware and permitted input together; the current documentation retains a different limit for Model One.
The compatibility question has more than one version number
The official October announcement separates Suite from device firmware and warns that application updates arrive in stages. Its core-model firmware section names 2.13.0 and describes a 128-byte maximum. Model One has its own firmware section. Reading only the desktop release number leaves part of the compatibility question unanswered.
The following matrix describes the model limits in Trezor's current passphrase guide. It is not proof that an arbitrary device still running an older configuration already supports the expanded limit. Identify the versions actually installed before relying on a newly announced capability.
| Device group | Documented passphrase maximum | Check before adopting a new length |
|---|---|---|
| Model T, Safe 3, Safe 5, Safe 7 | 128 ASCII characters | Applicable firmware and the entry method you intend to use |
| Model One | 50 characters | Its separate model limit rather than the Suite headline |
| A second device or recovery setup | Depends on that setup's compatibility | Whether it can reproduce the same wallet without editing the phrase |
Characters in a headline do not mean every alphabet is supported
The detailed Suite instructions specify the standard ASCII set. Do not reinterpret the headline as permission to use 128 arbitrary Cyrillic letters or emoji. Equally, do not silently translate, transliterate or trim an existing phrase to fit another interface. A changed secret does not establish access to the wallet you intended.
An expanded limit does not upgrade an existing secret
Trezor explains that the exact passphrase selects the associated wallet and that a typo can lead to a different, apparently empty wallet. An application update does not make a longer spelling equivalent to the previous one. Keep the existing phrase intact when checking access; a new maximum is a capability, not a requirement to change it.
For example, imagine a user adds a space because a refreshed field now accepts more text. The question is no longer simply whether the update installed successfully. The entered value has changed. This is a hypothetical reading error, not a reported customer incident or a recommendation for constructing a secret. Never place your real phrase in a public counter, screenshot or support ticket to investigate length.
Review the workflow before putting value behind a new setup
- Identify whether you are reopening an existing passphrase wallet or considering a genuinely new setup.
- Record only non-secret information: device model, installed Suite version and applicable firmware version.
- Read the model's length and character rules, including the entry method you will actually use.
- For an existing wallet, preserve the exact original phrase and verify that you reached the intended wallet before sending or receiving.
- For a new setup, follow the manufacturer's access-testing instructions before funding it; do not assume another model or old recovery setup accepts the same length.
The Suite instructions distinguish entering a passphrase on supported devices from entering it on the connected computer. Model One does not provide on-device passphrase entry. That distinction matters when planning a backup workflow: do not describe a path your model cannot perform. Keep passphrases and wallet-backup words out of email and messaging conversations about an update.
Exported trade records answer a different question
The same Suite release adds CSV trade-history export, including status and transaction identifiers. That can help organize a support record about a transfer, but a historical trade row is not a test of a passphrase backup. Keep the export's operational purpose separate from proving that a recovery setup opens the intended wallet.
Use the correct wallet before starting a separate swap
Once access to the intended wallet is established, an ordinary swap remains a separate operation. Review the supported coins and exchange process for its actual route. Suite's new trading features do not establish KOT.CASH integration, support for a particular token or a different order deadline.
The useful result of this release review is a compatible, understood workflow rather than the longest possible phrase. Recheck the official model documentation before adopting a new setup. No device, firmware installation or real wallet recovery was tested for this article.
FAQ
Does the Trezor passphrase length increase apply to Model One?
The current model documentation retains a 50-character limit for Model One. Do not apply the 128-character headline without checking the particular device and configuration.
Should I extend my existing Trezor passphrase after the update?
No change is required simply because a larger maximum is announced. The exact existing phrase opens its associated wallet; changing it does not lengthen the same wallet's password.
Does an empty Trezor passphrase wallet prove the update erased funds?
No: the guide explains that a mistyped phrase can open a different wallet. Verify the intended wallet and configuration before attributing an empty view to the release or attempting another transfer.