Where Does Trainline Store Tickets and Bookings?
Trainline keeps bookings in your account with tickets cached in a private sandbox and Wallet passes for gates.
Last updated
Trainline bookings live server-side. The app holds session, cached tickets, and recent searches in its sandbox. Gates accept the Wallet pass or the in-app code, both rendered from the same booking.
Booking fees and Railcards apply at purchase and store against the account, not the device. A new phone with the same login sees the same discounts immediately. Season tickets and saved routes reappear alongside regular bookings.
Where Trainline stores this, by platform
/data/data/com.thetrainline
Private sandbox for cached tickets and session. Bookings and Railcards are account-side. Add Wallet passes for reliable offline gates.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same account archive. Apple Wallet passes duplicate tickets outside the app. Confirmation emails carry PDF fallback.
Frequently asked questions
Do Trainline tickets work offline?
Tickets cache in the app after first open, and Wallet passes work fully offline. Open each ticket on Wi-Fi before heading underground. E-ticket PDFs in email serve as backup.
How do I move Trainline to a new phone?
Log in and bookings return. Railcards and saved passengers sync from the account. The sandbox only held cached copies that rebuild on first view.
Notice an outdated path? Let us know.