Using Ledger Offline | Network Role, Screen Confirmation, and Record Boundary

Using Ledger offline is best understood by separating roles. The app view may need a network connection for account display or a prepared request, while the device screen is where the user reviews and confirms the local device step.

Direct Answer: The Device and the App Have Different Network Roles

The device does not become a web account simply because the app view uses network data. Treat the app as the display and coordination layer, and treat the Ledger device screen as the place where the local confirmation state is read.

What the App View Needs

The app view may need access to show balances, account labels, or prepared request details. For a related boundary, see Ledger network requirement check, which separates app entry, screen state, and local record.

What the Device Screen Confirms

The device screen confirms the local prompt. For the same idea in another FAQ context, offline signing protects keys explains why screen review and local confirmation should stay distinct from app display.

Record the Offline Boundary Clearly

Write down whether the app view was online, whether the device screen showed a clear prompt, and what local step was completed. If the question is about viewing accounts, compare it with offline account view FAQ before changing the setup.

Do not record recovery phrase words or PIN digits. A useful offline-use note contains only the entry path, screen prompt, local confirmation state, and the date of the check.