Where Does Qdrant Store Vectors and Snapshots?
Qdrant persists vectors and indexes under /qdrant/storage in Docker, with snapshots and config mounted alongside it.
Last updated
Qdrant separates code from state with three container paths. Storage holds vectors, payloads, and the write ahead log. Snapshots holds collection backups. Config holds the production YAML.
The storage mount is the one you cannot skip. Without it, stopping the container drops the collections. Snapshots are optional but worth mounting, since restores read from there. Config only matters when you override ports, auth, or cluster settings.
Where Qdrant stores this, by platform
/qdrant/storage
Main vector store. Mount a persistent volume here in compose or run commands. Default ports are 6333 for REST and 6334 for gRPC.
/qdrant/snapshots
Collection snapshot output. Mount it when you schedule backups so archives survive container replacement.
Frequently asked questions
Which volumes should I mount for Qdrant in Docker?
Mount a volume to /qdrant/storage and keep it. Add /qdrant/snapshots for collection backups and /qdrant/config/production.yaml for custom settings.
Why does Qdrant warn about the filesystem on Windows?
Use a named Docker volume rather than a Windows bind mount. Shared Windows mounts lack full POSIX semantics and can corrupt the index.
Can cluster nodes share one storage folder?
Give each node its own storage mount. Cluster nodes must not share one directory, since each keeps its own shards, WAL, and snapshots.
Notice an outdated path? Let us know.