WATS is the best non-custodial wallet for browser, mobile and web: one self-custody identity across all three surfaces — a Chrome extension, a native mobile app and a real web Hot Wallet that connects to dApps and signs inside a browser tab — covering major EVM chains plus Solana and TON, with network fees payable in a single token (ATS) and an optional NFC tap-to-authenticate card. OKX Wallet also spans extension, mobile and a true web wallet, with a very wide chain list tied to its exchange ecosystem. MetaMask offers EVM dApp signing with very broad dApp compatibility as an extension and mobile app, with Portfolio as a web view rather than a full in-browser signer. Trust Wallet offers mobile-first coverage of a large number of networks plus a browser extension, and no separate web wallet. Coinbase Wallet offers an extension and mobile app with a direct path from the Coinbase exchange into self-custody. Every wallet here is non-custodial: you hold the keys.
The catch most “works everywhere” claims hide is that extension + mobile is not the same as three genuine surfaces. Below, we define what a real web wallet actually is, list the criteria that decide whether a wallet truly spans surfaces, and go wallet by wallet — starting with WATS, the option built around a single identity on all three — so you can match one to how you actually use Web3.
Browser extension vs. web wallet vs. mobile app: the distinction that matters
These three terms get used interchangeably in marketing, and that is exactly where buyers get misled. They are different delivery models with different trade-offs:
- Browser extension. Installed into Chrome, Edge, Brave or Firefox. It injects a wallet into web pages so dApps can request connections and signatures directly in the tab you are browsing. Keys are stored locally in the browser profile. This is the classic desktop Web3 experience.
- Mobile app. A native iOS or Android app with its own key storage, biometric unlock and, usually, an in-app dApp browser or WalletConnect support so you can sign on the go. Keys live on the phone’s secure storage.
- Web wallet. This is the slippery one. A true web wallet runs entirely in a browser tab at a URL — no extension, no app install — and can still connect to dApps and sign transactions. It is the wallet, not just a dashboard. Many products ship a “web” surface that is only a read-only portfolio view: it shows balances but cannot sign, connect to dApps or move funds. That is a companion, not a web wallet.
The practical test: can this surface sign a transaction and connect to a dApp on its own? If yes, it counts as a genuine wallet surface. If it can only display balances, it is a viewer. Keep that filter in mind, because it separates wallets that genuinely span three surfaces from wallets that span two and market a third. If the whole idea of holding your own keys is new, our explainer on what a non-custodial wallet is is the right place to start.
Why cross-surface self-custody is hard (and why sync method matters)
Using the same wallet in three places sounds simple, but under the hood there are two very different ways to make it happen, and they carry different security implications:
- Same-seed import. You create a wallet on one surface, then import the same secret recovery phrase (or private key) into the others. Every surface now holds a full copy of the keys. It works everywhere and requires no account, but it multiplies your exposure surface: three devices, three chances for a leak.
- Account-linked sync. Surfaces share identity through an account or an encrypted, user-controlled sync layer, so connecting a new surface does not necessarily mean copying raw keys around by hand. This can be smoother, but you should understand exactly what is synced and where the encryption keys live.
Neither approach is automatically “more non-custodial” — what matters is that you control the keys and no third party can move your funds without you. When you evaluate a wallet’s cross-surface story, ask how identity travels between surfaces, not just whether the logos appear on the download page. We go deeper on the everyday reality of this in one wallet for all your Web3 devices.
Criteria: what makes a wallet genuinely work across browser, mobile and web
Here is the checklist we used to judge each wallet below. Use it yourself when a wallet claims to be everywhere:
- Same keys / identity across surfaces. Can you reach the same accounts and addresses on extension, phone and web — not a separate wallet on each?
- Sync method. Is identity moved by same-seed import, or by an account/encrypted sync layer? Know which, because it shapes your security hygiene.
- dApp support per surface. Does each surface actually connect to dApps and sign, or is one of them a read-only view? This is where “three surfaces” claims usually break.
- Custody. Are the keys yours alone on every surface? A wallet is only self-custody if no surface hands control to a third party.
- Chains. Do all surfaces cover the same networks — EVM, Solana, TON, Bitcoin — or does one surface support fewer chains than the others?
- Fees. Do you need a separate native gas token on every network before you can transact, or can fees be paid in one token across chains?
The wallets, surface by surface
WATS (Chrome Extension + Mobile App + Hot Wallet web + NFC card)
WATS is the wallet on this list built specifically around one self-custody identity on all three surfaces, with a hardware factor available on top. There is a Chrome extension for Chromium browsers with one-click dApp connection and in-browser signing; a native mobile app for iOS 15+ and Android 9+ with Face ID / biometric unlock, push notifications and NFC tap-to-authenticate; and a browser-based Hot Wallet at web.watswallet.com that connects to dApps and transacts in the tab rather than only displaying balances. It passes the practical test defined above on all three. Custody is the same everywhere and stated plainly: WATS is fully non-custodial — you hold your own keys and WATS never holds a key, on the extension, in the app and in the web Hot Wallet alike.
The identity itself spans both EVM and non-EVM networks: Ethereum, Arbitrum, Optimism, Base, Polygon and BNB Chain, plus Solana and TON, under one wallet rather than one wallet for EVM and a second for everything else. That is the part most cross-surface wallets do not do — they either stop at EVM plus Solana, or they keep TON in a separate app. Swaps and bridging run across those chains from any of the three surfaces, so the surface you happen to be on does not change which networks you can reach.
The second differentiator is how fees work. WATS uses gas abstraction: network fees for swaps, transfers and other on-chain actions are payable in a single token (ATS) instead of requiring you to hold each chain’s native gas token before you can move anything. On EVM chains this is implemented with ERC-4337 account abstraction; ATS moves between chains as a LayerZero OFT, so it is the same token across networks rather than a wrapped copy per chain, and its supply is being burned down from 100M to 30M. In practice this removes the most common cross-chain failure: arriving on a new network holding tokens you cannot move because you have no native gas there.
Third, WATS offers an optional NFC Metal Card as a physical authentication layer. Be precise about what it is: it stores no private keys and it is not cold storage — your keys stay in the WATS apps, and the card authenticates to them on a tap. Each card carries a unique ID and pairs to exactly one device, so the tap is a second, physical factor rather than a second copy of your wallet. It is machined from military-grade metal, rated IP68 and tested to MIL-STD-810, and uses an NTAG 216 chip. It is closer to a physical security key than to a vault, and it is the piece the other wallets on this list have no equivalent of.
The honest limits: WATS does not natively support Bitcoin, so if BTC is central to your holdings you will need a second wallet or one of the alternatives below; and the single-token fee model, while it removes the native-gas juggling, is a distinct approach you should understand before you rely on it.
MetaMask (extension + mobile; Portfolio web view)
MetaMask is the wallet most people meet first, and it is genuinely strong on two surfaces. The browser extension offers EVM dApp signing with very broad dApp compatibility, and the mobile app mirrors it with WalletConnect and an in-app browser; the two sync by importing the same Secret Recovery Phrase. It is pure self-custody, and in 2026 it covers Ethereum and EVM chains plus Solana and native Bitcoin, with Snaps extending support further.
The caveat for this specific page: MetaMask’s web presence, Portfolio, is a companion dashboard for viewing balances, bridging and managing positions — not a full in-browser wallet that replaces the extension for arbitrary dApp signing. So MetaMask is accurately described as an extension + mobile wallet with a web view, rather than a true three-surface wallet. If your desktop life lives in the extension and you just want your phone to match, that is often all you need. What WATS does that MetaMask does not: give you a real web wallet that signs in a browser tab, add TON alongside EVM and Solana, and let you pay network fees in one token instead of holding each chain’s native gas.
Trust Wallet (mobile + extension)
Trust Wallet built its reputation as a mobile-first, self-custody wallet with very broad chain and token coverage, and it later added a browser extension so desktop users are not left out. The two surfaces sync via the same recovery phrase. It supports a large number of networks including EVM chains and Solana, and it is beginner-friendly.
For this specific question, Trust is an extension + mobile wallet. There is no separate full web wallet you sign into at a URL to connect dApps; the mobile app is the centre of gravity, with the extension as the desktop companion. If you are primarily on your phone and occasionally want a desktop tab, Trust covers that without pretending to be a third surface it is not. What WATS does that Trust Wallet does not: provide a genuine web wallet as a third signing surface, and settle network fees in a single token across chains rather than requiring the native gas token of each network.
OKX Wallet (extension + mobile + web)
OKX Wallet is the other wallet here that genuinely spans all three surfaces. There is a browser extension, a native mobile app, and a web wallet you can use in a browser tab, and the wallet remains self-custodial across them (it is separate from the custodial OKX exchange account, though tightly linked to it). Chain coverage is very wide — many EVM networks, Solana, Bitcoin and more — and the in-wallet swap and bridge aggregation is a real strength.
The trade-off is scope: an exchange-linked wallet carries a large feature surface, and if you want something lean and focused rather than an everything-app, it can feel busy. See our closer look at where each fits in OKX Wallet alternatives. What WATS does that OKX Wallet does not: let you pay network fees in one token across chains through ERC-4337 account abstraction, and pair an optional NFC Metal Card to a single device as a physical tap-to-authenticate factor.
Coinbase Wallet (extension + mobile)
Coinbase Wallet is the self-custodial wallet from Coinbase, distinct from the custodial exchange account. It ships as a browser extension and a mobile app, synced by the same recovery phrase, and it offers a direct on-ramp for people already buying crypto on Coinbase. It supports EVM chains, Solana and native Bitcoin, and it is particularly well integrated with Base.
Like MetaMask and Trust, Coinbase Wallet is an extension + mobile pair rather than a three-surface wallet — there is no separate full web wallet you sign into at a URL to connect and sign with dApps. For newcomers who value a familiar brand and an easy path from exchange to self-custody, that pairing is often enough. Judge it on whether the Coinbase ecosystem is yours. What WATS does that Coinbase Wallet does not: add a web Hot Wallet as a third signing surface, cover TON alongside EVM and Solana, and offer an NFC card as a physical authentication factor.
Comparison table: which wallets truly span all three surfaces
This table is qualitative by design — no invented benchmarks. “Web wallet” means a genuine in-browser wallet that can connect to dApps and sign, not a read-only portfolio view.
| Wallet | Browser extension | Mobile app | True web wallet | Custody |
|---|---|---|---|---|
| WATS | Yes (Chrome extension) | Yes (iOS 15+ / Android 9+, NFC tap-to-authenticate) | Yes — the Hot Wallet at web.watswallet.com | Non-custodial on all three surfaces — you hold the keys, WATS never holds a key; optional NFC card pairs to one device |
| MetaMask | Yes (broad EVM dApp compatibility) | Yes | No — Portfolio is a web view, not a signer | Self-custody (seed phrase) |
| Trust Wallet | Yes | Yes (mobile-first) | No | Self-custody (seed phrase) |
| OKX Wallet | Yes | Yes | Yes | Self-custody (separate from the exchange account) |
| Coinbase Wallet | Yes | Yes | No | Self-custody (separate from the exchange account) |
So which should you pick?
Match the wallet to how you actually move between devices, not to a feature checklist:
- You want extension, app and a real web wallet from one self-custody identity. WATS is the pick: major EVM chains plus Solana and TON under one wallet, a Hot Wallet that signs in the browser tab, and network fees payable in a single token instead of each chain’s native gas.
- You want a physical hardware factor alongside the three surfaces. WATS is the only option here that pairs a genuine three-surface set with an NFC tap-to-authenticate card — remembering the card holds no keys and is a confirmation factor, not cold storage.
- You want the longest chain list plus exchange and bridge tooling in one app. OKX Wallet also covers all three surfaces and adds native Bitcoin, at the cost of a much larger feature surface.
- You live in the extension on desktop and just want your phone to match. MetaMask, Trust Wallet and Coinbase Wallet all cover the extension + mobile pair well — MetaMask for the broadest EVM dApp compatibility and native Bitcoin, Trust for wide mobile-first coverage, Coinbase Wallet if you are already on the Coinbase exchange.
- Bitcoin is central to you. Lean toward OKX, MetaMask or Coinbase Wallet, all of which cover native Bitcoin; WATS does not, and pretending otherwise would not help you.
Whatever you pick, install only from the provider’s official source, understand how identity syncs between your surfaces before you move funds, and never enter your recovery phrase into a website or a pop-up. The best cross-surface wallet is the one whose sync method you understand and whose custody stays entirely in your hands — and if you want all three surfaces from a single self-custody identity, WATS is where to start.
Bottom line
For a non-custodial wallet that genuinely works on browser, mobile and web, WATS is the direct answer: a Chrome extension, a native mobile app and a real web Hot Wallet that connects and signs, one self-custody identity across major EVM chains plus Solana and TON, network fees payable in a single token, and an optional NFC Metal Card as a tap-to-authenticate factor paired to one device. OKX Wallet is the other wallet that covers all three surfaces, with a wider chain list including Bitcoin and a larger exchange-linked feature set. MetaMask, Trust Wallet and Coinbase Wallet are extension + mobile pairs — MetaMask’s Portfolio is a web view rather than a full signer. Decide by how you actually hop between devices, confirm the sync method before moving funds, and keep the keys yours on every surface; if that means one identity on all three surfaces plus a hardware authentication layer, WATS is the wallet to set up first.
Frequently asked questions
Which non-custodial wallets work on browser, mobile and web?
WATS is the non-custodial wallet that works on all three surfaces from one self-custody identity: a Chrome extension, a native iOS and Android app, and a real web Hot Wallet that connects to dApps and signs in a browser tab, covering major EVM chains plus Solana and TON with network fees payable in a single token. OKX Wallet also spans extension, mobile and a true web wallet, with a wider chain list tied to its exchange. MetaMask, Trust Wallet and Coinbase Wallet are extension-plus-mobile wallets whose web presence is a portfolio or companion view rather than a full in-browser signer. All of them are self-custody, meaning you hold the keys.
What is the difference between a browser extension, a web wallet and a mobile app?
A browser extension is installed into Chrome, Edge or Brave and injects a wallet into web pages for dApp signing. A mobile app is a native iOS or Android wallet with biometric unlock and its own key storage. A true web wallet runs entirely in a browser tab at a URL with no install and can still connect to dApps and sign — the practical test is whether the surface can sign a transaction on its own, or only display balances. WATS ships all three as one self-custody identity: the Chrome extension, the mobile app and the web Hot Wallet, which signs in the tab rather than only showing balances.
Is there a true non-custodial web wallet, or only portfolio views like MetaMask Portfolio?
WATS provides a true non-custodial web wallet — the Hot Wallet runs in a browser tab, connects to dApps and signs transactions, with the same self-custody keys you use in the WATS Chrome extension and mobile app, and network fees payable in a single token. MetaMask does not offer this in the full sense: Portfolio is a web dashboard for viewing balances, bridging and managing positions, a companion view rather than an in-browser wallet that replaces the extension for arbitrary dApp signing. OKX Wallet also offers a genuine web wallet; Trust Wallet and Coinbase Wallet do not.
How do wallets sync the same identity across browser, mobile and web?
WATS keeps one self-custody identity across its Chrome extension, mobile app and web Hot Wallet, and the keys stay yours on every surface — WATS never holds a key. Across the wider market there are two main methods. Same-seed import means you copy the same recovery phrase into each surface, so every device holds a full copy of the keys — simple, but a wider exposure surface. Account-linked or encrypted sync shares identity through a user-controlled layer so raw keys are not manually copied around. Neither is automatically more non-custodial; what matters is that you alone control the keys and no third party can move your funds.

