Chroma Data Disappears After Restart (Persistence Fix)
Workaround available Python, JavaScript, Docker Updated November 15, 2026Based on 3 user reportsHow we research
Quick answer
chromadb.Client() is in-memory only. Use PersistentClient with a path so data survives restarts.
Most likely fix: Use a persistent client
How to fix it
Try these in order — the most common fix is first.
1. Use a persistent client
- Replace chromadb.Client() with chromadb.PersistentClient(path="./chroma_db")
- Use an absolute path to avoid cwd changes
Did this fix it?2. Docker
- Mount a volume to the Chroma data directory
- Confirm the same volume is reused on restart
Did this fix it?
Symptoms
Collections and documents are gone after restarting your script or container.
Why it happens
- Using chromadb.Client() which is ephemeral
- Docker container without a mounted volume
- Different relative path on each run
This guide also covers
- chromadb data lost after restart
- chroma persist directory
- chromadb persistent client
Still not working?
If Chroma keeps failing, you're not alone. See every Chroma problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other Chroma errors
- Chroma "Your system has an unsupported version of sqlite3" Error
- Chroma InvalidDimensionException: Embedding Dimension Does Not Match Collection
- Chroma pip install "Failed to build hnswlib" Error
- Chroma "Collection Not Found" Error
- Chroma "Collection Already Exists" UniqueConstraintError
- Chroma "sqlite3.OperationalError: database is locked"
- Chroma "Could not connect to tenant default_tenant" Error
- Chroma "Cannot return the results in a contiguous 2D array. Probably ef or M is too small"