diff --git a/apps/docs/content/docs/core/applications/rollbacks.mdx b/apps/docs/content/docs/core/applications/rollbacks.mdx
index ff3f86b..dfb15ec 100644
--- a/apps/docs/content/docs/core/applications/rollbacks.mdx
+++ b/apps/docs/content/docs/core/applications/rollbacks.mdx
@@ -50,4 +50,35 @@ Paste the following code:
 }
 ```
 
+## Rollback to a specific version
 
+The previous steps covered Docker Swarm's automatic rollback feature. Since v0.23.0, Dokploy also supports manual rollbacks to specific deployment points, giving you more control over your application versions.
+
+### Enabling Rollback Feature
+
+To start saving deployment snapshots for rollbacks:
+
+1. Navigate to your application
+2. Go to **Deployments** → **Rollback Settings**
+3. Enable the **Rollback** option
+
+### How it works
+
+- **Automatic snapshots**: Every time you deploy, Dokploy creates a rollback point associated with that deployment
+- **Manual rollback**: Click the **Rollback** button next to any deployment to revert to that specific version
+- **Automatic cleanup**: When old deployments are deleted, their associated rollback snapshots and images are also removed to save space
+
+### Performing a rollback
+
+1. Go to your application's **Deployments** section
+2. Find the deployment version you want to rollback to
+3. Click the **Rollback** button next to that deployment
+4. Confirm the rollback action
+
+<Callout type="info">
+    Having rollbacks enabled will increase storage usage, as it saves previous versions of your application. Consider your storage capacity when enabling this feature.
+</Callout>
+
+<Callout type="warning">
+    **Important**: If you manually clean Docker images using commands like `docker image prune` or `docker system prune`, the rollback snapshots may be lost. Avoid cleaning Docker images if you want to preserve your rollback history.
+</Callout>