WordPress on Render
Render publishes its own guide for deploying WordPress.
PHP content management system that requires a database and persistent filesystem for uploads and plugins.
What WordPress needs.
Every host claims to run WordPress, so the claim on its own decides nothing. These are the things WordPress actually requires from the platform underneath it, and what Render publishes about each. Render documents 4 of the 4.
Persistent storage
Supported
Uploads, themes and plugins are written to disk while the site is running. A host that resets the filesystem on every deploy loses them.
Sources (1) →Sources ↓
- Persistent Disks – Render Docs ↗
“You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts.”
Read 2026-09-05 · official docs
Managed databases
Supported
Every post, option and user lives in MySQL. Without a managed database you are running, patching and backing one up yourself.
Sources (1) →Sources ↓
- Render Postgres ↗
“Deploy fully managed, enterprise-grade databases that scale to any workload.”
Read 2026-09-05 · official docs
Storage (entry plan)
No persistent disk is included on any instance type, including the entry `0.5c-512mb` plan; services run on an ephemeral filesystem unless a persistent disk is attached separately
A media library grows steadily and is almost never pruned. Disk is the cap a WordPress site reaches first.
Sources (1) →Sources ↓
- Persistent Disks – Render Docs ↗
“By default, Render services have an ephemeral filesystem.”
Read 2026-09-05 · official docs
Monthly visits cap
No request-count cap is published; traffic is capped by outbound bandwidth, 5 GB/month included on Hobby and 25 GB on Pro.
Managed WordPress plans meter traffic rather than CPU, so the visit ceiling is the real size of the plan you are buying.
Sources (1) →Sources ↓
- Outbound bandwidth — Render Docs ↗
“Each workspace receives a monthly included amount of outbound bandwidth based on its plan: Workspace plan Included bandwidth Hobby 5 GB Pro 25 GB Scale 1 TB Enterprise Custom”
Read 2026-09-14 · official docs
What Render documents.
Render publishes its own guide for deploying WordPress.
This guide shows how to deploy a WordPress instance on Render in just a few minutes.
Sources (1) →Sources ↓
- Deploy WordPress – Render Docs ↗
“This guide shows how to deploy a WordPress instance on Render in just a few minutes.”
Read 2026-09-05 · official docs
WordPress features on Render
Capabilities Render documents specifically for WordPress, with the constraint it documents alongside each.
managed_mysql
Not supported
Render offers managed Postgres databases, along with Key Value instances that are compatible with virtually all Redis clients. You can also run your own custom database instance (MariaDB, MongoDB, etc.) backed by a persistent disk. [...] You can also use a persistent disk to run a custom database instance instead of Render Postgres, such as MySQL.
automated_backups
Limited
Relying on a disk snapshot to restore a database is not recommended. Restoring a disk snapshot will likely result in corrupted or lost database data. [...] you can easily add additional security and backups using the official Jetpack plugin
Sources (2) →Sources ↓
- Render FAQ – Render Docs ↗
“Render offers managed Postgres databases, along with Key Value instances that are compatible with virtually all Redis clients. You can also run your own custom database instance (MariaDB, MongoDB, etc.) backed by a persistent disk. [...] You can also use a persistent disk to run a custom database instance instead of Render Postgres, such as MySQL.”
Read 2026-09-13 · official docs
- Deploy WordPress – Render Docs ↗
“Relying on a disk snapshot to restore a database is not recommended. Restoring a disk snapshot will likely result in corrupted or lost database data. [...] you can easily add additional security and backups using the official Jetpack plugin”
Read 2026-09-13 · official docs
What it costs to run there.
- Pricing model
- The Hobby plan does not have a monthly fee, so you only pay for usage.
- When you exceed a cap
- Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is reached Render stops running pipeline tasks, builds included.
- Regions
- Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (3) →Sources ↓
- Platform Features by Plan – Render Docs ↗
“The Hobby plan does not have a monthly fee, so you only pay for usage.”
Read 2026-09-05 · official docs
- Build pipeline — Render Docs ↗
“Running out of minutes If you run out of pipeline minutes during a given month, you automatically purchase a supplementary amount of minutes for your current tier, unless: You've reached your monthly spend limit, or You haven't added a payment method.”
Read 2026-09-14 · official docs
- Regions — Render Docs ↗
“You can deploy Render services to any of the following regions to minimize latency for your users: Oregon, USA Ohio, USA Virginia, USA Frankfurt, Germany Singapore”
Read 2026-09-14 · official docs
Whether it suits you.
Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.
Consider something else if…
Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.
Visit Render documentation