A user with a Tangem hardware wallet card discovers they are about to travel through areas with unreliable or nonexistent cellular coverage. They wonder whether they can still access and confirm transactions once they leave connected regions. The question sounds straightforward but contains a subtle contradiction: Tangem operates through a mobile application, yet the card itself stores private keys offline in a secure hardware element. Understanding which operations require active network connectivity and which do not requires separating the card’s capabilities from the mobile app’s dependencies.
The confusion is understandable because Tangem’s architecture differs from traditional hardware wallets like Trezor or Ledger. Those devices use USB cables or Bluetooth and display critical information on their own screens. Tangem cards and rings rely entirely on an NFC connection to a smartphone, which means the device cannot display balance, fees, or receiving addresses without the app. That dependency suggests the wallet cannot function offline at all. In reality, the picture is more granular. Some operations work in airplane mode; others fail silently or appear to work while leaving transactions unsigned.

Where Tangem’s private key storage actually lives
The Tangem card or ring contains a secure element chip, a specialized integrated circuit designed to resist tampering, extraction, and unauthorized access. Private keys are generated and stored entirely within this chip during the wallet’s first setup. Once generated, those keys never leave the secure element. This offline key storage is the core security guarantee: an attacker cannot steal keys through malware on the phone or network interception because the keys exist only in the isolated hardware.
The secure element performs cryptographic operations—signing transactions, deriving public keys, generating addresses—without ever exposing the private key material to the mobile app or the smartphone’s general processor. This is where Tangem differs sharply from a mobile wallet that stores keys in the phone’s encrypted keychain or secure enclave. Even if the mobile app is compromised, the private keys remain unreachable because the signing happens on the card itself.
That security architecture means the card can sign a transaction without network access. The app prepares the transaction data, brings the card close to the phone’s NFC antenna, and the secure element signs it. No internet connection is required for that operation. However, the mobile app must be able to read the card’s public key or derive it from account information stored on the card. If the app crashes, has never been opened before on this device, or lacks cached blockchain data, offline operation becomes impractical even if the signature itself could theoretically be generated without the network.
Initial setup requirements and the first-time setup dependency
Before any offline operation is possible, a Tangem card or ring must be set up using the mobile application. During setup, the app communicates with the card to initialize the secure element, generate private keys, and configure the wallet for one or more blockchains. This setup process requires active network connectivity to verify the card’s authenticity, check firmware status, and in some cases download firmware updates. An offline initial setup is not supported.
Once setup is complete, the card itself contains all necessary data to sign transactions: the private key, the account derivation path, and configuration data for supported blockchains. However, the mobile app still needs certain information to construct valid transactions. It must know the current balance, transaction history, and the nonce or sequence number (for accounts that track transaction order). This information comes from blockchain nodes or indexing services, all of which require internet access.
A critical distinction emerges: the card can sign any transaction data placed before it. The mobile app must provide that data in the correct format. If the app has previously accessed the network and cached the necessary account information—balance, nonce, recent transaction history—it can construct a transaction in airplane mode and bring the card to sign it. If the app has never retrieved this information or was uninstalled and reinstalled, it must reconnect to the network before it can build a valid transaction.
Transaction signing in airplane mode versus transaction broadcasting
Signing and broadcasting are separate steps, and this distinction is often misunderstood. When a user initiates a transaction in the Tangem app and confirms it by holding the card near the phone’s NFC antenna, the secure element signs the transaction using the private key. This signing step produces a digital signature that proves the holder of the private key authorized this specific transaction. The signing step itself requires no network.
Broadcasting is different. Once signed, the transaction must be sent to a blockchain node to be included in the ledger. Broadcasting requires internet connectivity. If the phone is in airplane mode or lacks network access, the signed transaction can be stored temporarily in the app but cannot propagate to the network. When connectivity returns, the app can then broadcast the waiting transaction.
In practice, the Tangem app will present a signed transaction and prompt the user to broadcast it. If no network is available, the app typically displays a message indicating transmission failed. Some versions cache unsigned or signed transaction data to be sent when connectivity returns; others discard it if the user navigates away. Users should verify what their app version does before relying on airplane mode operation for important transactions. Testing with a small amount on testnet is a reasonable precaution.
Address and balance information without network connectivity
One of the most confusing aspects of using Tangem offline is address display. A Tangem card can derive multiple addresses for the same cryptocurrency using standard hierarchical deterministic derivation. However, the addresses must be derived on the card, and the mobile app must have enough information to request or compute the derivation.
If the app has previously connected to the card and cached the extended public key or account information, it can display addresses and check cached balance information in airplane mode. However, that balance is stale; it reflects the state from the last network connection, not the current state of the blockchain. A user relying on this cached data may not notice recent transactions, failed withdrawals, or other account changes.
A more reliable approach is to receive addresses through the NFC connection while in airplane mode. The user can tap the card to the phone and select a blockchain; the app will display the address without requiring network access. However, the app must already know which blockchains the card supports. If the card was set up for Bitcoin, Ethereum, and Solana, the app can display addresses for those three. It cannot add support for a new blockchain without connecting to the internet to download configuration data.
The Tangem Wallet app does cache this configuration locally after first setup, which means offline address display is feasible for blockchains that were configured before the last network disconnection. For a user preparing for extended offline travel, connecting the app to the internet and enabling each blockchain they may need is essential preparation.
Hardware wallet versus network client roles
Understanding Tangem’s offline limitations requires recognizing that the card is a signing device, not a full blockchain client. Traditional hardware wallets like Trezor or Ledger have similar constraints: they can sign but cannot verify blockchain data independently. They rely on a connected computer or app to provide account information.
Tangem adds a layer of complexity because it has no display of its own. A Trezor or Ledger device shows the transaction amount, fee, and recipient address on its own screen, which the user can verify before pressing a physical button to confirm. Tangem must display this information on the smartphone screen. If the phone is compromised or running a modified version of the app, it could display false information to the user while signing a different transaction.
This is not a unique vulnerability—many hardware wallets face this risk—but it means that offline operation does not automatically mean secure operation. A phone running malicious software could show a deposit address to a user in airplane mode, the user could proceed thinking they are in a secure offline environment, but the app could actually broadcast a transaction to a different address once connectivity returns. Airplane mode does not prevent the app from behaving unexpectedly; it only prevents immediate network access.
For security-critical operations, users should connect to trusted networks, verify addresses and amounts carefully, and consider sending test transactions before moving significant amounts. The offline key storage guarantee—that private keys never leave the secure element—is independent of whether the phone’s display can be trusted.
Backup and recovery in offline scenarios
Tangem wallets use backup cards instead of recovery phrases. A user can create backup cards during setup or afterward through the app. These backups are encrypted and tied to the original card’s security configuration. A backup card cannot be used on another phone if the original card is destroyed; the security model is device-bound rather than phrase-based.
Creating a backup requires network connectivity during the initial configuration, but backup cards themselves can be stored offline as physical objects. If the primary card is lost and the user has a backup card, they can pair the backup with any phone running the Tangem app to regain access. This is materially different from a recovery phrase, which remains vulnerable to the person holding it. A backup card is just plastic with data encrypted in its secure element; without the accompanying security configuration from the original card, it is inert.
For users in prolonged offline scenarios, the implication is worth considering: if the phone is lost as well as the card, and no backup card is stored elsewhere, recovery becomes difficult or impossible. Unlike a recovery phrase, which can be reconstructed from memory or a written backup, a Tangem backup card is a specific physical object. Users traveling to areas without reliable connectivity should keep backup cards in a geographically separate location and test the recovery process before relying on it.
Practical recommendations for offline-heavy usage
For a user who expects to spend significant time offline, several practical steps can ease operation. First, establish network connectivity on the phone before disconnecting. Open the Tangem app, tap the card to initialize the connection, and enable all blockchains the user might need. This caches configuration and allows the app to display supported blockchains in airplane mode.
Second, perform recent transactions while online to ensure the app has current account information. Check the balance, review transaction history, and confirm the account is functioning as expected. This cached data will be available offline, though it will become stale over time.
Third, prepare addresses in advance. Use the app to request and verify addresses for anticipated payments, write them down, or save them to a separate device if that is secure in the user’s threat model. This avoids the need to tap the card repeatedly once offline.
Fourth, plan for transaction construction. Offline transaction signing works if the app already knows the account nonce or sequence number. If extended time passes offline, the nonce may have changed due to other transactions. Once connectivity returns, the user must re-check the account state before attempting to sign and broadcast a prepared transaction.
Finally, test the process on a small amount before relying on it. Send a test transaction to a receiving address, enable airplane mode, confirm the transaction can be seen in the app’s history, and verify that tapping the card allows access to address information. This confirms the app’s caching behavior and offline functionality in the actual environment where it will be used.
What offline operation means for Web3 and dApp access
Tangem connects to decentralized applications through standard wallet connection protocols such as WalletConnect rather than browser extensions. This means Web3 applications can request signatures through a connection that is established over the network. If the phone is offline, dApp connections will fail, and the app cannot receive signature requests.
Once connectivity returns, pending signature requests may still be in the dApp’s queue. The user can reconnect, and Tangem can sign and send the transaction. However, dApp access fundamentally requires network connectivity because Web3 operations are initiated by the application, not by the wallet holder checking account information independently.
This represents a meaningful constraint compared to a laptop with a hardware wallet and a browser extension, where the user can access dApps as long as the computer is online, even if the phone is offline. With Tangem, the phone is the primary interface, and offline operation is limited to reviewing cached data and preparing self-initiated transactions.
Frequently asked questions
Can I sign a transaction with a Tangem card while in airplane mode?
Yes. The card’s secure element can sign transaction data through NFC without network access. However, the mobile app must have prepared the transaction with current account information. If the app has cached balance and nonce data from a recent online session, it can construct and sign a transaction in airplane mode. Broadcasting that transaction requires reconnecting to the network afterward.
Do I need to set up a Tangem wallet offline?
No. Initial setup requires active network connectivity to authenticate the card and configure blockchain settings. Once setup is complete, the card can be used offline for signing and address derivation, but the app’s first connection must happen online. Attempting to use an uninitialized card offline will fail.
Will my Tangem app show current balances if I disconnect from the internet?
The app will display cached balance information from the last time it was connected to the network. That information becomes stale immediately and does not reflect recent transactions, deposits, or market changes. Do not rely on offline balance display for decision-making; reconnect periodically to refresh account data.