EmDash vs WordPress: where it wins and where it doesn't
An honest EmDash vs WordPress comparison from someone running both: where EmDash genuinely wins, the drawbacks that don't get talked about, the real adoption numbers, and who should stay put.
I ran WordPress for years and I still think it earned its 40-something percent of the web. I also run this site on EmDash, a CMS that is six months old. So this is not a fanboy listicle - it is the comparison I wish someone had written before I moved: where EmDash genuinely beats WordPress, the drawbacks that get glossed over, and the adoption numbers as they actually stand.
One disclosure up front: I build plugins for EmDash, so I am not neutral. That is exactly why the drawbacks section below is longer than the wins section.
The shape of the fight
- WordPress
- Powers roughly 43% of the web, 20+ years of ecosystem, around 60,000 free plugins
- EmDash
- Public since April 2026; 184,179 npm downloads in the last 30 days
- EmDash registry
- 65 plugins - three orders of magnitude smaller, no pretending otherwise
- Sites on EmDash
- 628 and counting, by the project's own tracker
- Stack
- WordPress: PHP plus MySQL on a host you babysit. EmDash: Astro on Cloudflare Workers or a Node VPS
- The admin
- Both are real CMSs - collections, block editor, drafts, revisions. EmDash is not a static generator in a costume
Where EmDash genuinely wins
Speed you do not have to buy plugins for
Every page on this site is server-rendered HTML behind the Cloudflare edge cache. Warm responses come back in about 20 to 35 milliseconds, and there is no PHP worker assembling the page per request. On WordPress the equivalent took a caching plugin, a CDN, object-cache config and usually a performance plugin fighting the page builder for last place.
A smaller attack surface
There is no wp-login.php to brute-force - sign-in is passkeys with a magic-link fallback. Sandboxed plugins run in a separate isolate with declared capabilities, not PHP executing inside your request on every page load. The admin sits under /_emdash/ and the public site does not ship it. WordPress security is a discipline; here most of it is the architecture.
Maintenance that stops being a chore
Deploy is one command - it builds, checks production migrations, uploads the Worker and warms the cache, as documented in the Cloudflare Workers deploy tutorial. There is no weekly round of plugin updates hoping none of them conflicts, and no PHP version bump breaking the site on a Friday. The content model lives in seed.json and migrations in the repo, so what is in production is what is in git.
Cost
A WordPress site worth visiting costs real hosting money - ten to thirty a month for anything managed. This site runs on the Workers Paid plan at five dollars a month, and the free tier works if you skip sandboxed registry plugins. The Docker path on a cheap VPS lands in the same range.
WordPress asks you to keep a machine patched forever. EmDash asks you to write a theme once and deploy with a command. Which chore you prefer is the real question.
The drawbacks, honestly
This is the section most comparison posts skip, and the reason the article is worth reading. These are real and current, not hypothetical:
What WordPress still does better
- The plugin gap: 65 registry plugins versus ~60,000. If your site runs on a niche WordPress plugin, its EmDash counterpart probably does not exist yet
- Themes are code, not click-install: an EmDash theme is Astro components and CSS tokens in a repository. There is no theme directory where a non-developer clicks Activate
- No commerce, membership or LMS story: WooCommerce, LearnDash and MemberPress have no counterparts. If money changes hands on your site, WordPress wins today
- The sandbox costs money on Cloudflare: registry plugins need Workers Paid at $5 a month. Free-tier Workers sites can still run plugins in-process from source, but that is a code workflow
- Migration is manual: there is no importer. Content moves by scripting the REST API, which is a project, not a click
- The community is small: when you hit an odd bug the answer might be reading the source rather than a forum thread with a green checkmark
- It is a 1.0.x project: solid enough for this site, but the APIs are six months old and the long tail of edge cases is still being found
Adoption: where it actually stands
The numbers worth quoting, all current: 184,179 npm downloads in the last 30 days, 65 plugins in the registry, 628-plus sites tracked by the project, and a GitHub repo past 13,500 stars that was created in April 2026.
Honest caveats on those numbers: npm downloads count CI runs and bots too, so the sites counter is the better signal - and 628 sites against WordPress's hundreds of millions is a rounding error. The trajectory is real; the scale is not there yet. Six months ago this project did not exist, so what you are measuring is slope, not mass.
If you want the longer production story rather than numbers, the six-month EmDash review on bitdoze.com covers who it is and is not for after running it daily.
Who should switch
EmDash is a good home if
- The site is content - a blog, docs, a marketing site, a content hub - and WordPress feels like overkill
- You or your team are comfortable in a code editor; themes and schema are files you own
- You want edge-speed pages without a caching plugin stack
- A fixed $5-a-month hosting bill beats a variable managed-hosting one
- Plugin security alerts in your inbox every week finally wore you down
Stay on WordPress if
- Commerce, memberships or courses are core to the site
- Editors build pages visually and nobody wants to own Astro code
- You need a niche plugin that has no EmDash equivalent - check the registry first
- The site works, is maintained, and the migration budget does not exist
Try it this weekend
A low-risk test drive
Scaffold locally
npm create emdash@latest gives you a working CMS on SQLite - no Cloudflare account needed. Poke the admin, create a collection, write a post. This is the fifteen-minute version of the decision.
Pick a hosting path
Cloudflare Workers for the managed route, Docker on a VPS for the boring-reliable one, or Coolify if you want a self-hosted PaaS. All three are documented in the tutorials below.
Move one real page
Port your about page or one post, theme and all. That exercise tells you more than any comparison article - including this one.
The tutorials to start with
- Deploy EmDash on Cloudflare Workers
Workers, D1, R2 and the free tier, step by step
- Deploy EmDash with Docker
Self-host on a VPS with benchmarks to size it
- Coolify on a VPS
A self-hosted PaaS for the Docker route, with free SSL
- Build a custom EmDash theme
Tokens, blocks and seed schema on a real site
- EmDash CMS tutorial
From npm create to a running admin
- Migrate from WordPress
The full move, step by step, if you decide to go
Common questions
FAQ
Is EmDash just Astro with extra steps?
Astro is the rendering layer - the same reason sites built on it are fast. On top sits the real CMS: collections, the block editor, users and roles, media, revisions, a REST API and a plugin system. You would not call WordPress just PHP.
Can a non-developer run an EmDash site?
Once it is set up, yes - the admin is a normal CMS admin and editors never see code. The setup and the theme are the developer-shaped part, and those are one-time jobs.
What does it cost compared to WordPress?
This site: $5 a month on Workers Paid, and free-tier works without registry plugins. A comparable cared-for WordPress install on managed hosting is typically $10 to $30 a month before the plugin licenses.
Will my WordPress content import?
Not by clicking a button. Content moves through the REST API - paste by hand for small sites, script it for archives. The migration guide covers the route that works.
Is it too young to trust?
For a commerce site or a client's livelihood, maybe. For a content site you control, the risk profile is reasonable: the data sits in D1 or SQLite you can dump, and the theme is your code either way.
The fair summary: WordPress is the safer default and EmDash is the better tool for the job it aims at. If your site is content and you can own an Astro codebase, the six-month-old contender already beats the incumbent on speed, cost and the week you get back every month. If your site sells things or your editors build pages visually, the incumbent still earns its install base.