# WordPress on Render

Canonical: https://inetgeek.com/stacks/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 requires from the platform underneath it, and what Render publishes about each. Render documents 4 of the 4.

| Requirement | Render | Why it matters |
| --- | --- | --- |
| 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. |
| Managed databases | Supported | Every post, option and user lives in MySQL. Without a managed database you are running, patching and backing one up yourself. |
| 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. |
| 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. |

- Persistent storage source: https://render.com/docs/disks
- Managed databases source: https://render.com/docs/postgresql
- Storage (entry plan) source: https://render.com/docs/disks
- Monthly visits cap source: https://render.com/docs/outbound-bandwidth

## What Render documents

> This guide shows how to deploy a WordPress instance on Render in just a few minutes.

Source: https://render.com/docs/deploy-wordpress

### WordPress features on Render

- **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. ([source](https://render.com/docs/faq))
- **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 ([source](https://render.com/docs/deploy-wordpress))

## What it costs to run there

|  | Render |
| --- | --- |
| 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 |

- Pricing model source: https://render.com/docs/new-workspace-plans
- When you exceed a cap source: https://render.com/docs/build-pipeline
- Regions source: https://render.com/docs/regions

## 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.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for WordPress: https://inetgeek.com/stacks/wordpress/
- Render: https://inetgeek.com/hosting/render/