Where Does SchildChat Store Sessions?
Where SchildChat keeps sessions on desktop and mobile, fork of Element layout. Full paths are listed below.
Last updated
SchildChat is Element fork for Matrix with local sessions. Your rooms live on the homeserver. Each device holds session files, cache, and encryption keys.
Same Matrix ID plus homeserver means same rooms. Exact session file names shift with Element versus SchildChat builds. Keep cross signing set up before moves. If rooms show undecrypted, verify the new session from an old device rather than resetting keys. When in doubt, verify paths inside the app before trusting a remembered folder. Screenshots of settings help when support asks for reproduction steps later.
Where SchildChat Matrix stores this, by platform
%appdata%\SchildChat (sessions, rooms on homeserver)
Rooms follow your Matrix ID on its homeserver. Sessions live locally with E2EE keys. Export megolm keys before wiping. Verify new sessions after moves.
~/.config/SchildChat (sessions, rooms on homeserver)
Same session model on Linux under the app config path. Keys need cross signing anew. Homeserver holds the room truth, not device files.
Frequently asked questions
How do I move SchildChat to a new device?
Sign in on the new device with the same Matrix ID and rooms return from the homeserver. Devices hold login plus message cache. Keys need cross signing verification anew. Check the homeserver URL before wiping, since a second account shows empty.
Does SchildChat back up E2EE keys?
No. SchildChat reads rooms from your Matrix homeserver without a separate backup. The app holds session files plus E2EE keys. Reinstalls restore rooms after sign in while keys need verification. Export megolm keys from settings for keeps.
Notice an outdated path? Let us know.