Where Does Jami Store Accounts and Data?
Jami stores dring.yml plus account files in Local jami on Windows, Application Support on Mac, and XDG folders on Linux.
Last updated
Jami keeps identity on the device, not on servers. Global options live in dring.yml while accounts, certificates, and history live in per account files beside it. Cache and sent media branch into their own folders.
Every platform follows the same split with different roots. Linux uses XDG config plus local share, Windows uses Local jami trees, Mac uses Application Support. Mobile builds sandbox the same files beyond file manager reach. Export plus database copy covers full moves.
Sent recordings and images sit in a sent_data folder inside local data. That folder is the easy win when disk runs low, though trimming it orphans old media references in history.
Where Jami stores this, by platform
%APPDATA%\Local\jami
Global dring.yml plus per account files here. Cache sits in %USERPROFILE%\.cache\jami. Export .jac archives before copying raw folders.
~/.local/share/jami
Same account plus config split under the XDG homes. Database copies go with the .jac exports. Quit Jami before touching either tree.
~/Library/Application Support/Jami
Full config tree for direct downloads. App Store builds sandbox under Containers instead. Check both when the first path looks empty.
Frequently asked questions
How do I move Jami to a new computer?
Export each account from Settings to a .jac archive first, then copy the account data folders with Jami quit. Import the archives on the new device before replacing the database copy. The archive restores contacts while the database restores history.
Can I back up a Jami account?
Yes through the export flow, which is the only supported path. Copying raw key folders without the archive strands contacts. An account removed from every linked device without a backup cannot be retrieved at all.
Notice an outdated path? Let us know.