Where Does Element X Store Sessions?
Element X keeps sessions in app-private SQLite stores via the Matrix Rust SDK. No file-manager path exists; logout wipes them.
Last updated
Element X stores everything in its app-private sandbox: Matrix Rust SDK SQLite databases for room state, event cache, media, and crypto, plus caches beside them. Android and iOS expose no file-manager path into that sandbox. Session keys live in the OS keystore (Keystore/Keychain), separate from the databases.
That design answers the location question with a negative: there is no user-serviceable file. Backups happen through Matrix itself (server-side history plus Secure Backup for E2EE keys), never file copies. Clearing app data or uninstalling wipes sessions by design, which surprises users migrating phones who expect a transferable file.
Where Element X stores this, by platform
(app-private sandbox, no file path)
Rust SDK SQLite stores plus caches, all inside the private sandbox. No browsable path. Migrate via login plus verification, never file copy. Clearing data wipes sessions by design.
(app-private sandbox, no file path)
Same sandboxed SQLite layout in the app container. Keys in Keychain. Re-login refetches rooms; E2EE history requires Secure Backup or a verified sibling device.
Frequently asked questions
where is the element x database file
Nowhere reachable. Element X stores Rust SDK SQLite databases inside its private sandbox on both OSes. Migration means verifying the new login with the old device (QR or emoji check), not copying files.
why did clearing app data log me out of everything
Expected. The SDK encrypts stores with keys held in the OS keystore, and uninstalling or clearing data drops both halves. Re-login refetches joined rooms from the homeserver; E2EE history needs a verified backup or another logged-in device.
Notice an outdated path? Let us know.