New: Get 2 months free on any annual plan. Claim offer →

Can You Host WordPress on Vercel? The Honest 2026 Answer

Short answer: no, you cannot host WordPress on Vercel the way you host it on a normal web host. Vercel does not run PHP and does not offer a MySQL database or a persistent filesystem, which are the three things a standard WordPress install needs. What you can do is run WordPress somewhere else as a headless CMS and deploy a Next.js front end to Vercel, or export your site to static files and serve those.

That distinction matters more than most tutorials admit. Below is what each approach actually involves, what it costs, and the cases where it is genuinely worth the trouble.

Why Vercel Cannot Run WordPress Directly

WordPress is a PHP application backed by a MySQL or MariaDB database. The official WordPress requirements list PHP 7.4 or greater and MySQL 8.0 or MariaDB 10.5 or greater, plus HTTPS support. Vercel’s runtimes cover Node.js, Python, Ruby and Go functions, not PHP with a long-lived database connection.

There are three hard blockers, and none of them have a clean workaround:

  • No PHP runtime. Community PHP builds for serverless exist, but they are unofficial and painful to maintain for something as plugin-heavy as WordPress.
  • No persistent filesystem. Vercel functions are ephemeral. Media uploads, plugin installs and cache files written to wp-content would vanish between invocations.
  • No bundled database. You would still pay a separate provider for MySQL, plus the latency of connecting to it from a cold serverless function.

This is also the consensus you will find in the Reddit threads people search for on this topic. The people who tried it usually stopped, not because it is impossible in a lab sense, but because the maintenance never pays for itself.

Approach One: Headless WordPress With a Next.js Front End

This is the setup Vercel’s own documentation promotes, and it is legitimate. You keep WordPress running on real WordPress hosting, expose the content through the REST API or WPGraphQL, then build a Next.js front end that fetches that content and deploys to Vercel.

The editor experience stays familiar. Writers still log into wp-admin, still use the block editor, still schedule posts. Visitors never touch the WordPress server directly, which is a real security benefit because the admin surface sits behind a separate domain.

A typical stack looks like this:

  • WordPress backend on a managed host, often at a subdomain like cms.yoursite.com
  • WPGraphQL or the REST API as the content layer
  • Next.js using incremental static regeneration so pages rebuild on a schedule or on publish
  • Vercel for the edge network, previews and Git-based deploys

If Git-driven deployment is the part you actually want, note that you can get it without rewriting your site. Our WordPress hosting with Git gives you version-controlled deploys and staging while the site stays plain PHP WordPress.

What Headless Actually Breaks

This is the part the tutorials skim. Going headless means the theme layer disappears, and a surprising amount of WordPress lives in that layer:

We cover this topic in more depth in Can Squarespace Host WordPress? The Straight Answer for 2026.

Related reading: Can Netlify Host WordPress? The Straight Answer for 2026.

  • Page builders stop working. Elementor, Divi and Beaver Builder output PHP-rendered HTML and CSS that a Next.js front end will not receive.
  • Forms need rebuilding. Contact Form 7 and Gravity Forms submissions have to be re-plumbed through API routes.
  • SEO plugins need bridging. Yoast and Rank Math meta has to be queried and re-rendered manually in your head tags.
  • Previews get fragile. Draft previews require extra token handling and often break after a plugin update.
  • WooCommerce is a project, not a plugin. Cart, checkout and session state all need custom work.

Read our take on plugin compatibility before committing, because the plugin ecosystem is the single biggest reason people use WordPress in the first place.

Approach Two: Static Export to Vercel

The lighter option is to keep WordPress running locally or on a cheap host, then generate flat HTML with a plugin like Simply Static or WP2Static and push those files to Vercel. Vercel serves static output well, and the free Hobby tier covers small personal projects.

This works for brochure sites, documentation and portfolios where content changes a few times a month. It falls apart the moment you need comments, search, member logins, dynamic pricing or anything that writes to a database at runtime. The same logic applies to hosting WordPress on Netlify, which has the identical PHP limitation.

One caveat people miss: every content edit triggers a full or partial rebuild. On a 2,000-page site, that turns a two-minute typo fix into a ten-minute publish cycle.

The Cost Math Nobody Shows You

People chase this setup expecting free hosting. Here is what the headless route usually adds up to in 2026:

  • WordPress backend host: $10 to $40 per month, because you still need somewhere to run PHP and MySQL
  • Vercel Pro: $20 per user per month once you outgrow Hobby, plus usage-based bandwidth and function charges
  • Developer time: 40 to 120 hours to build a front end that matches what a theme gave you for free
  • Ongoing maintenance: two codebases, two dependency trees, two things that can break at 2am

Compare that with a single managed plan around $20 to $30 per month that includes caching, a global CDN, SSL and backups. Our breakdown of managed WordPress hosting costs in 2026 puts the numbers side by side.

When Vercel Is Actually the Right Call

We are not anti-headless. There are real cases where it wins:

  • You already have a React or Next.js team and the front end is the product
  • You publish to a website, a mobile app and a kiosk from one content source
  • Traffic is genuinely spiky and you want edge rendering by default
  • The marketing site is mostly static and the interactive parts live in JavaScript anyway

If none of those describe you, the honest answer is that a well-tuned WordPress host beats a headless rebuild on speed-to-launch and total cost. Sites that lean on plugins, such as course platforms or membership sites, are the worst candidates for going headless.

The Simpler Path Most Sites Should Take

Most of the performance people want from Vercel comes from caching and a CDN, not from the framework. Server-level caching plus 35 or more edge locations puts a normal WordPress site in the 0.5 to 1.2 second range for first paint on typical marketing pages.

For a growing company site, business WordPress hosting with staging, daily backups and 24/7 support solves the same problems without a rewrite. If your current host is the actual bottleneck, our guide on the signs it is time to migrate to managed hosting is a better starting point than a headless project. And if you are still scoping what the platform can do, see 14 real WordPress use cases for 2026.

Frequently Asked Questions

What is the cheapest way to host a WordPress site?

Shared hosting starts around $3 to $6 per month in the first year, though renewal prices commonly double. For anything earning revenue, a managed plan in the $20 to $30 range usually costs less overall once you account for downtime, security cleanups and developer hours.

Is Vercel good for website hosting?

Vercel is excellent for JavaScript front ends built with Next.js, Nuxt, SvelteKit and similar frameworks, and its Hobby tier is free for personal projects. It is not a general-purpose web host, since it does not support PHP applications, MySQL databases or persistent file storage.

What is the best hosting for a WordPress website?

The best fit for most sites is managed WordPress hosting with server-level caching, a global CDN, free SSL, automated daily backups and staging. Check whether the plan covers your real monthly visitor count, because overage fees are where cheap plans get expensive.

Can I host WordPress for free?

You can publish free on WordPress.com’s free tier, but you get a subdomain, ads and no plugin uploads. Self-hosted WordPress software is free under the GPL, as explained on WordPress.org, though you still pay for a server and a domain, typically $60 to $300 per year combined.

Want a Straight Answer About Your Setup?

Tell us what your site does and what is slow about it, and we will say plainly whether headless is worth it or whether better WordPress hosting fixes it in an afternoon. Free migration is included, and the 14-day trial does not need a card.

← Previous How to Host WordPress on Cloudflare: The Honest 2026 Guide

Leave a Comment

Your email address will not be published. Required fields are marked *