Headless WordPress vs a traditional theme, and which to choose
Compare headless WordPress with a traditional theme: who renders pages, plugins, forms and security trade-offs and when each approach is the better choice.
Last updated October 28, 2026
A traditional WordPress theme and a headless setup both show your content to visitors, but they do it in different places. This article explains the difference, the trade-offs of each, and how to decide which suits your site.
How a traditional theme works
With a normal theme, WordPress does everything. When a visitor opens a page, your server runs PHP, reads the post from the database, applies the theme templates and sends back finished HTML. Plugins can change that output directly through hooks, shortcodes and widgets. Caching plugins and CDNs are often added to avoid rebuilding every page for every visit.
How a headless setup works
“Headless” means the part visitors see and the part you write in are separate. WordPress keeps your posts, pages, menus and settings, and shares them over an API such as the WordPress REST API. A separate frontend, built with a framework such as Astro, reads that data and renders the pages visitors see.
In Hatch Connect, that frontend is a small Astro site that runs as a Cloudflare Worker in your own Cloudflare account. You keep writing in the normal block editor; WordPress stays your back office. See how headless WordPress with Astro works in Hatch.
Side-by-side comparison
| Topic | Traditional theme | Headless (for example with Hatch) |
|---|---|---|
| Who renders pages | Your WordPress server, on each request or from cache | A separate frontend; with Hatch, a Worker on Cloudflare |
| Editing | Block editor or page builder, with live theme preview | Block editor as usual; WordPress stays the back office |
| Plugins that change page output | Work directly | Work only if the frontend reads their data. Hatch reads specific SEO, forms, shop and custom field plugins |
| Forms and comments | Handled by WordPress in the theme | Sent from the frontend back to WordPress; Hatch stores form entries and passes comments to normal moderation |
| Public attack surface | The whole WordPress site is what visitors hit | Visitors hit the frontend; WordPress can be locked down more tightly |
| Moving parts | One system | Two systems that must stay in step |
When a traditional theme is the better choice
- You depend on a page builder or plugins that inject output into the theme and have no headless support.
- You want one system with no API in between.
- Your site is private, on a local network or not reachable over https. A deployed frontend on Cloudflare must be able to reach WordPress over https.
When headless is worth it
- You want visitors served from Cloudflare’s network instead of your WordPress server.
- You want to separate the public site from wp-admin and switch on stricter protections for WordPress.
- You are a developer who wants a stable REST API to build your own frontend against.
Headless is not automatically faster or better. Results depend on your content, plugins, hosting and how the frontend is built, so measure your own site before and after.
What Hatch does and does not change
Hatch does not install, bundle, switch or remove any theme. After a successful deploy, visitors who open the raw WordPress address are redirected to the same path on your frontend, while wp-admin, wp-login, the REST API, feeds, sitemaps and previews are never redirected. Disconnect turns the redirect off again.
FAQ
Do I lose my theme if I go headless with Hatch?
No. Hatch never switches or removes your theme. A signed-in user still sees the site’s own theme on the bare home URL.
Do I need to learn a new editor?
No. You write with the standard block editor, and Hatch reads what you write over REST. No custom blocks are needed.
Can I go back to a normal theme?
Yes. Open Hatch, Connection, and press Disconnect. The redirect stops. The Worker stays in Cloudflare until you delete it under Workers & Pages.