{
"schema_version": 2,
"id": "commands/save",
"title": "SAVE",
"url": "https://redis.io/docs/latest/commands/save/",
"summary": "Synchronously saves the database(s) to disk.",
"since": "1.0.0",
"tags": [
"docs",
"develop",
"stack",
"oss",
"rs",
"rc",
"oss",
"kubernetes",
"clients"
],
"last_updated": "2026-09-18T09:48:09+01:00",
"page_type": "content",
"content_hash": "e2c8b65b67c4bd1eefcf4b6e9b93d03c34a42effe5db4af34b3b4c8c1187a00a",
"sections": [
{
"id": "overview",
"title": "Overview",
"role": "overview",
"text": "The `SAVE` commands performs a **synchronous** save of the dataset producing a\n_point in time_ snapshot of all the data inside the Redis instance, in the form\nof an RDB file.\n\nYou almost never want to call `SAVE` in production environments where it will\nblock all the other clients.\nInstead usually [`BGSAVE`](https://redis.io/docs/latest/commands/bgsave) is used.\nHowever in case of issues preventing Redis to create the background saving child\n(for instance errors in the fork(2) system call), the `SAVE` command can be a\ngood last resort to perform the dump of the latest dataset.\n\nSee the [persistence documentation](https://redis.io/docs/latest/operate/oss_and_stack/management/persistence) for detailed information."
},
{
"id": "redis-software-and-redis-cloud-compatibility",
"title": "Redis Software and Redis Cloud compatibility",
"role": "content",
"text": "| Redis
Software | Redis
Cloud | Notes |\n|:----------------------|:-----------------|:------|\n| ❌ Standard
❌ Active-Active | ❌ Standard
❌ Active-Active | |"
},
{
"id": "return-information",
"title": "Return information",
"role": "returns",
"text": "**RESP2:**\n\n[Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK`.\n\n**RESP3:**\n\n[Simple string reply](../../develop/reference/protocol-spec#simple-strings): `OK`."
}
],
"examples": []
}