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 the Hobby workspace plan (Pro 25 GB, Scale 1 TB)
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 ↗
“Hobby | 5 GB”
Read 2026-09-05 · 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
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 hit, Render stops all pipeline tasks including service builds for the rest of the month (platform-wide, all plans)
- 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 ↗
“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. In the above cases, Render stops running pipeline tasks (including service builds!) for the remainder of the current month.”
Read 2026-09-05 · official docs
- Regions ↗
“Oregon, USA / Ohio, USA / Virginia, USA / Frankfurt, Germany / Singapore”
Read 2026-09-05 · 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