render-disks

Attach and manage persistent disks for Render services with mount paths and sizes.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/renderinc/render-codex-plugin --skill render-disks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-disks
Source: https://github.com/renderinc/render-codex-plugin/tree/main/skills/render-disks
Command: npx skills add https://github.com/renderinc/render-codex-plugin --skill render-disks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Persistent disks provide durable storage for Render services, allowing filesystem changes to persist across deploys and restarts. Without a disk, services run on an ephemeral filesystem where data is lost on each deploy.

Core Features & Use Cases

  • Attach a high-performance SSD disk to a service to persist data and support stateful workloads (e.g., CMS media, file uploads, self-managed databases).
  • Configure disk properties via mountPath and sizeGB, with constraints like single-instance operation and controlled restore behavior.
  • Use disk snapshots to restore a previous state and understand when not to rely on disk for certain workloads (e.g., ephemeral builds).

Quick Start

Add a disk to your service via the Disks page by specifying a mountPath and sizeGB, then deploy.

Frequently Asked Questions about render-disks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach persistent disks to Render services?

To attach persistent disks to Render services, navigate to the Disks page, specify a mountPath and sizeGB, then deploy your service to apply the durable storage configuration.

Why does my Render service lose filesystem data on every deploy?

Render services lose filesystem data on deploys because they run on an ephemeral filesystem by default. Attaching a persistent disk preserves your filesystem changes across deploys and restarts.

How do disk snapshots work for restoring Render service data?

Disk snapshots capture a previous state of your persistent storage, allowing you to restore Render service data to that point. Use snapshots for safe restoration of durable disk contents.

Can I use persistent storage with background worker services on Render?

Yes, persistent storage applies to web, private, and background worker services on Render. You can attach disks to support stateful workloads requiring durable storage across these service types.

What are the limitations of using persistent disks on Render?

Persistent disks on Render require single-instance operation and have controlled restore behavior. Avoid relying on disks for ephemeral builds or workloads that do not need durable filesystem storage.

When do I need persistent storage for my Render service?

You need persistent storage when running stateful workloads like CMS media storage, file uploads, or self-managed databases. Persistent disks preserve this data across service deploys and restarts.