Where Does the Bluesky App Store Session Data?
The official Bluesky app stores session and cache under one shared ID on Android and iOS, separate from a PDS.
Last updated
The Bluesky client uses xyz.blueskyweb.app on both mobile OSes. That ID covers the Play build, the App Store build and the shared notification group on iOS. Phone files hold persisted interface state plus image cache, while follows and posts stay on the PDS under the handle. A new login pulls the account back without touching server data.
This is distinct from running a Bluesky PDS, which stores repos on a Linux server. Phone storage holds React Native persisted state plus image cache. Sessions expire independently of the app version, so relogin fixes most auth loops. Clear cache from system settings or offload on iOS for bloat. Full storage clear logs out, so use it only when cache clear leaves auth stuck.
Where Bluesky stores this, by platform
/data/data/xyz.blueskyweb.app
Private databases and cache for the verified Bluesky package. Posts stay on your PDS; this folder holds session plus offline UI state.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container plus shared group group.app.bsky for notifications. Bundle xyz.blueskyweb.app. GUID changes per install; quote the bundle ID to support.
Frequently asked questions
Do I lose posts when reinstalling the Bluesky app?
No. Follows, posts and blocks live on your PDS under your handle. The app holds session tokens and UI cache only. Log in on the new phone and everything repopulates.
How do I clear Bluesky cache without losing my account?
Clear cache from system app settings on Android, or offload on iOS. Full storage clear logs you out. This post covers the app; self hosted PDS data lives on your server, not the phone.
Notice an outdated path? Let us know.