Documented steps

Auth: api-key header for all snapshot endpoints (create/list/download/recover/upload) when auth is enabled.
Create a snapshot: curl -X POST 'http://localhost:6333/collections/{collection_name}/snapshots' -H 'api-key: <API_KEY>' — builds a tar archive under the configured snapshot path
List snapshots: curl 'http://localhost:6333/collections/{collection_name}/snapshots' -H 'api-key: <API_KEY>'
Download: curl 'http://localhost:6333/collections/{collection_name}/snapshots/{snapshot_name}' -H 'api-key: <API_KEY>' --output backup.snapshot
Recover from URL or server-local path: curl -X PUT 'http://localhost:6333/collections/{collection_name}/snapshots/recover' -H 'api-key: <API_KEY>' -H 'Content-Type: application/json' -d '{"location": "http://qdrant-node-1:6333/collections/{collection_name}/snapshots/snapshot-2022-10-10.snapshot", "priority": "snapshot"}' — creates the target collection if it does not exist
Recover from a locally uploaded file: curl -X POST 'http://localhost:6333/collections/{collection_name}/snapshots/upload?priority=snapshot' -H 'api-key: <API_KEY>' -F 'snapshot=@/path/to/backup.snapshot'
Single-node only: recover at startup with ./qdrant --snapshot /path/to/snapshot:target_collection_name
Official docs: https://qdrant.tech/documentation/snapshots/

Known gotchas

In a distributed deployment snapshots are per-node — trigger and manage them on each node, not once per collection
Restore priority defaults to replica (prefers existing cluster data over the snapshot) — restoring into a fresh collection almost always needs priority: snapshot or incoming data is ignored
Snapshots only restore into the same minor version or the next minor version — large version gaps are unsupported
PUT .../snapshots/recover (URL/path source) and POST .../snapshots/upload (multipart file) are distinct — wrong method/path for your source fails
The no_sync priority is for specialized manual shard management only — never for routine restores

qdrant.tech/documentation · 6 steps · unrated

Create, download, and restore Qdrant snapshots (collection, shard, and full-storage) for backup and migration

qdrant.tech/documentation · 12 steps · unrated

Create a Qdrant collection with a given vector size and distance metric via PUT /collections/{collection_name}

qdrant.tech · 7 steps · unrated

Give your agent this knowledge — and 17,800+ more routes

One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Create and restore Qdrant collection snapshots for backup (POST /collections/{name}/snapshots, PUT .../snapshots/recover)

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 17,800+ more routes

Need this verified for your stack — or a route we don't have yet?