Where Does Letta Store Agent Data?
Letta keeps server state and agent data in a letta directory under your home folder. The server reads an env file beside it.
Last updated
Letta runs agents as a local server with persistent memory, and that memory lives on disk in a letta folder in your home directory. SQLite state, uploaded files, tool definitions, and per agent data sit underneath it. Server settings arrive through environment variables or an env file, not through the data folder.
Self hosted agent frameworks blur config and data more than most tools, so keep the two straight during moves. Copy the data directory for memory and the env file for behavior. Version upgrades migrate the embedded schema automatically, but snapshots beforehand remain cheap insurance.
Where Letta stores this, by platform
C:\Users\[Username]\.letta
SQLite state, agent files, and tool data under one home directory. Back it up with the server stopped plus the env file. Postgres mode moves conversation state out.
~/.letta
Same home directory layout as other platforms. The server creates it on first run if missing.
~/.letta
Identical to macOS. Docker deployments mount this path as a volume to persist memory across container recreations.
Frequently asked questions
How do I back up a Letta server?
Back up the whole directory with the server stopped, plus the env file holding API keys and model endpoints. Agents reference files and tools by paths that only make sense with both halves together.
Can state live in Postgres instead?
Point the server at a Postgres connection string instead of the default embedded database. The directory still holds configs and local files, while conversation state moves to the database.
Notice an outdated path? Let us know.