Render Disks

by render-osse8f889396634MITListed Oct 8, 2026Updated Oct 8, 2026

Attaches and manages persistent disks on Render services—mount paths, sizing, snapshots, file transfers, and single-instance constraints. Use when the user needs persistent storage, file uploads, a custom database on disk, CMS media storage, or needs to understand why their service can't scale horizontally or use zero-downtime deploys. Trigger terms: persistent disk, disk, storage, mount path, sizeGB, SSD, file uploads, snapshots, disk restore, ephemeral filesystem.

Instructions onlyDevOps & Cloud

AI-generated overview

Guides attaching and managing persistent disks on Render services, covering mount paths, sizing, snapshots and constraints.

What it does: This skill provides instructions for attaching and managing persistent SSD disks on Render services, including mount path selection, size configuration, snapshots and file transfers. It documents critical constraints such as single-instance limits, disabled zero-downtime deploys, and runtime-only disk access. It also lists common patterns for CMS media storage, self-managed databases and stateful infrastructure, plus frequent mistakes and their fixes. A reference file covers sizing guidance, snapshot lifecycle and restore procedures.
When to use it: Use it when a user needs persistent storage on Render, such as file uploads, CMS media, or a self-managed database on disk. It also applies when explaining why a service cannot scale horizontally or use zero-downtime deploys, or when restoring data from a disk snapshot.
Requirements: Render paid web services, private services or background workers. No scripts are shipped; it is instructions only, with one reference document. SSH access is needed for SCP file transfers.

Render Persistent Disks

Persistent disks are high-performance SSDs you attach to a Render service to preserve filesystem changes across deploys and restarts. Without a disk, services have an ephemeral filesystem—all local file changes are lost on every deploy.

When to Use

Storing file uploads, CMS media, or user-generated content
Running a self-managed database (MySQL, MongoDB, ClickHouse) on Render
Deploying stateful infrastructure (Elasticsearch, Kafka, RabbitMQ, Mattermost)
Understanding why scaling is blocked or zero-downtime deploys are disabled
Restoring data from an automatic disk snapshot

For managed databases, prefer Render Postgres (render-postgres) or Key Value (render-keyvalue) over self-managed alternatives on disk.

Critical Constraints

These constraints affect architecture decisions. Understand them before attaching a disk:

Constraint	Impact
Single instance only	Cannot scale horizontally (`numInstances` must be 1, autoscaling not available)
No zero-downtime deploys	Old instance stops before new instance starts (brief downtime on each deploy)
Runtime access only	Disk is not available during `buildCommand` or `preDeployCommand` (those run on separate compute)
Not accessible from other services	Only the attached service can read/write the disk
Not available on cron jobs	Attach to a web service, private service, or background worker instead
Not available on one-off jobs	One-off jobs run on separate compute without disk access
Can increase size, cannot decrease	Start small and grow as needed

Setup

Dashboard

Go to your service's Disks page
Set the mount path (absolute path where persistent data is stored)
Choose a size in GB
Click Add disk — triggers a new deploy

Blueprint

yaml

services:  - type: web    name: cms    runtime: node    plan: starter    region: oregon    buildCommand: npm ci && npm run build    startCommand: npm start    disk:      name: cms-data      mountPath: /var/data      sizeGB: 10

services:  - type: web    name: cms    runtime: node    plan: starter    region: oregon    buildCommand: npm ci && npm run build    startCommand: npm start    disk:      name: cms-data      mountPath: /var/data      sizeGB: 10

Mount Path

Only files written under the mount path are preserved. Everything else remains ephemeral.

Runtime	Source code path	Example mount path
Node.js, Python, Ruby, Elixir, Rust	`/opt/render/project/src`	`/opt/render/project/src/uploads`
Go	`/opt/render/project/go/src/github.com/<user>/<repo>`	`.../data`
Docker	Dockerfile's `WORKDIR` (commonly `/app`)	`/app/storage`

Disallowed mount paths

Cannot mount at: /, /opt, /opt/render, /opt/render/project, /opt/render/project/src, /home, /home/render, /etc, /etc/secrets.

Subdirectories of these paths are fine (e.g. /opt/render/project/src/uploads).

Snapshots

Render creates an automatic snapshot every 24 hours
Snapshots are available for at least 7 days
Restore from the service's Disks page in the Dashboard
Full restore only — you cannot restore individual files
Destructive — all changes after the snapshot are lost

Do not restore snapshots for custom database recovery. Use database-native backup tools (mysqldump, mongodump) instead—disk snapshots may capture a corrupted database state.

File Transfers

SCP (via SSH)

bash

# Download from servicescp -s [email protected]_REGION.render.com:/mount/path/file ./local-file
# Upload to servicescp -s ./local-file [email protected]_REGION.render.com:/mount/path/file

# Download from servicescp -s [email protected]_REGION.render.com:/mount/path/file ./local-file
# Upload to servicescp -s ./local-file [email protected]_REGION.render.com:/mount/path/file

Requires SSH access enabled for the service.

Magic-Wormhole

Available on all native runtimes (install manually on Docker):

Common Patterns

Pattern	Service type	Mount path	Notes
WordPress / Ghost / CMS	Web Service	`/var/data` or `/app/content`	Media uploads, SQLite
Self-managed MySQL	Private Service	`/var/lib/mysql`	Use mysqldump for backups, not disk snapshots
File upload API	Web Service	`/opt/render/project/src/uploads`	Single instance constraint
Elasticsearch	Private Service	`/usr/share/elasticsearch/data`	Stateful search infrastructure

Common Mistakes

Mistake	Fix
Expecting horizontal scaling with a disk	Not possible — disk services are single-instance only
Mounting at a disallowed path	Use a subdirectory (e.g. `/opt/render/project/src/uploads` not `/opt/render/project/src`)
Reading disk during build or pre-deploy	These run on separate compute — move logic to the start command
Restoring disk snapshot for a database	Use database-native backups instead
Starting with a large disk size	Start small — you can increase but never decrease

References

Related Skills

render-web-services — Deploy lifecycle, health checks (disk disables zero-downtime)
render-private-services — Internal services with disks (Elasticsearch, MySQL)
render-blueprints — disk field reference in render.yaml
render-postgres — Managed database alternative (no disk management needed)

Source and attribution

Source:render-oss/render-plugin-claude-codeinskills/render-disksat commite8f8893

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from render-oss/render-plugin-claude-code

Render Static Sites

render-oss

Guides deploying and configuring static sites and SPAs on Render's CDN, covering builds, routing, headers and PR previews.

DevOps & CloudOct 8, 2026

Render Scaling

render-oss

Guides scaling of Render web services, private services and background workers, covering instance counts, autoscaling and cost.

DevOps & CloudOct 8, 2026

Render Networking

render-oss

Explains Render private networking: internal DNS, service discovery, ports, and cross-service connectivity.

DevOps & CloudOct 8, 2026

Render Postgres

render-oss

Guides setup, connection, storage, HA, replicas and backups for Render Managed PostgreSQL databases.

DevOps & CloudOct 8, 2026

Render Monitor

render-oss

Monitors Render cloud services in real time: health checks, performance metrics, logs, and database status.

DevOps & CloudOct 8, 2026

Render Domains

render-oss

Configures custom domains and TLS certificates on Render—DNS setup, CNAME records, apex domains, wildcard domains, and certificate troubleshooting. Use when the user needs to add a custom domain, configure DNS, set up HTTPS/TLS, troubleshoot certificate issuance, disable the onrender.com subdomain, or add a wildcard domain. Trigger terms: custom domain, DNS, CNAME, TLS, SSL, HTTPS, certificate, apex domain, wildcard domain, onrender.com, domain verification.

Awaiting classificationOct 8, 2026

Render Disks

Render Persistent Disks

When to Use

Critical Constraints

Setup

Dashboard

Blueprint

Mount Path

Disallowed mount paths

Snapshots

File Transfers

SCP (via SSH)

Magic-Wormhole

Common Patterns

Common Mistakes

References

Related Skills

Source and attribution

More from render-oss/render-plugin-claude-code

Render Static Sites

Render Scaling

Render Networking

Render Postgres

Render Monitor

Render Domains

More in DevOps & Cloud

M5 Onboard

Google Cloud Solution N Tier Serverless Web App

Google Cloud Recipe Onboarding

Customize

Google Cloud Global Frontend Configuration

Google Agents Cli Onboarding