What the web version is
Trezor Suite Web is the same application delivered by a web server instead of an installer. Accounts, the dashboard, send and receive, trade services and device settings all behave the way they do on the desktop. The differences are practical:
- Nothing to install — useful on a borrowed or freshly rebuilt machine.
- The browser is in the chain — extensions, saved passwords, autofill and typed addresses all become part of your risk surface.
- Device connection goes through the browser, which some browsers handle directly and others handle less smoothly.
- Local data lives in the browser profile, so labels and preferences may not survive clearing site data.
The security model itself does not change: keys stay on the device and every payment still ends with a confirmation on the hardware wallet's screen.
Reaching the real app
Phishing is the defining risk of a browser-based wallet interface, and it does not require any clever software — only that you land on a convincing copy of a login screen. Habits that actually work:
- Save the address as a bookmark the first time you use it, from the manufacturer's own website. Thereafter, open the app only from that bookmark.
- Never search for it and click the first result. Adverts for wallet software are bought by criminals as well as by legitimate companies.
- Check the padlock and the domain every session. A valid certificate proves encryption, not identity — look at the name, spelling included.
- Ignore links in email, chat and video comments, including ones that look like support replies to a question you asked.
If a page asks for anything other than connecting a device and approving an operation — recovery words, a "wallet validation", a "node sync" or a "migration" — close it. None of those exist in the real app.
How the browser reaches the device
Modern browsers can talk to USB devices directly through the WebUSB standard. In a Chromium-based browser — Chrome, Edge, Brave, Opera and similar — that usually means you plug the wallet in, the app asks for permission to access it, and you approve once.
Where a browser does not expose that capability, a small companion service installed on the machine (often called a bridge) provides the connection instead. Browsers and operating systems change these behaviours over time, so rather than trusting a tutorial written months ago, read the connection requirements shown in the app itself — the app tells you exactly which method it needs on the machine you are using.
Two things stay true regardless of the method: the browser never receives your keys, and every transaction is confirmed on the device screen.
Safe-use checklist
- Bookmark the real app and use only that bookmark.
- Use a personal browser profile, not a shared one, and log out of other services first.
- Disable browser extensions you do not recognise; crypto-targeting extensions exist.
- Apply operating system and browser updates before handling funds.
- Never enter recovery words on any web page — the real app never asks for them.
- Check the destination address on the device screen for anything sizeable.
- Avoid public computers for sending; viewing a balance there is already a trade-off.
More on the underlying protections, including PIN, passphrase and backup handling, is in the security and privacy guide.
Desktop vs web at a glance
| Desktop app | Web app | |
|---|---|---|
| Installation | Install once, updates itself | None — opens in the browser |
| Device connection | Direct USB, consistent across systems | Through the browser; may need a bridge helper |
| Network privacy | Built-in Tor option | Depends on browser and network setup |
| Local data | Stored by the installed application | Stored in the browser profile |
| Main added risk | Installing from a wrong source | Landing on a look-alike domain |
| Best for | Daily use on your own machine | Quick access away from your own machine |
Both versions sign the same way. Neither can move funds without you approving the transaction on the device, which is what makes the browser version a reasonable fallback rather than a reckless one.
When the web version is the right choice
- You need to check a balance on a computer you do not own.
- You have just reinstalled an operating system and want access before installing software.
- You are on a locked-down machine where you cannot install applications.
- You are travelling and the laptop you brought is not the machine the app is installed on.
In the reverse direction: if the wallet is used often, if you want Tor without extra configuration, or if the machine is shared, the desktop app is the calmer choice.
If the device is not found
- Unlock the wallet with the PIN first — a locked device does not appear to the browser.
- Reconnect using the cable that came with the device, into a port on the machine itself rather than a hub.
- Look for a browser permission prompt and approve access to the device if one is waiting.
- Try a current Chromium-based browser, then a different USB port, then a restart.
- If the app mentions a helper service for your browser, install it only from the manufacturer's own site.
- Still stuck? The desktop troubleshooting table covers the same causes from the other side.
Next: the setup walkthrough covers creating a wallet, backing it up and a first transaction that has been verified on the device.