Skip to main content
Agency Program 50% cashback. Exclusive discounts. Priority support. Built for growing agencies. 50% cashback. Exclusive discounts. Priority support. Built for growing agencies. Speak to the team Join free

EmDash vs WordPress (EmDash 1.0 Tested, 2026)

We installed EmDash 1.3.1, counted its plugin registry and moved a real WordPress site into it. Here is how the two CMSs compare in October 2026.

NS
Neha Sharma
Content, InstaWP
Updated Oct 22, 2026 29 min read

EmDash vs WordPress comes down to one trade. Cloudflare’s EmDash 1.0 is the better-engineered CMS for developers starting a new content site on Astro, with sandboxed plugins and a built-in MCP server. WordPress is still the practical choice for anything that needs mature plugins, a visual builder, a full store, or clients who edit their own site.

We tested that claim instead of repeating it. In October 2026 we scaffolded EmDash 1.3.1, counted its plugin registry, and moved a real WordPress site into it twice, once with a WXR file and once with the official EmDash Exporter. This guide compares both platforms across ten areas, shows what survived the move (and what did not), and explains where managed WordPress hosting on InstaWP closes the gaps EmDash points at, without leaving WordPress.

Key takeaways
  • EmDash is no longer a beta. Cloudflare shipped EmDash 1.0 on 28 September 2026, and the current release is 1.3.1. It is MIT-licensed, built on Astro and runs on Cloudflare Workers or Node.js.
  • The plugin ecosystem is real but small. On 21 October 2026 the EmDash registry listed 98 plugins from 52 publishers, including Stripe Checkout and two commerce plugins. WordPress.org lists more than 72,000.
  • The sandbox is opt-in. Registry plugins always run isolated, but a new project ships with no sandbox runner, and on Cloudflare it needs the Workers Paid plan. Plugins added in code run in the main process.
  • Migration works for content, not for business logic. In our test, posts, pages, images, tables and ACF values came across. Shortcodes, a quote block’s text, WooCommerce prices and SKUs did not.
  • Staying on WordPress? InstaWP’s managed WordPress hosting gives you a live HTTPS site in about 40 seconds, InstaMCP for AI agents on every plan, and staging, scanning and WAF protection that cover most of what EmDash promises.
Try WordPress the fast waySpin up a free WordPress sandbox on InstaWP and compare it with EmDash yourself.
Create a free sandbox →
EmDash vs WordPress side-by-side comparison illustration

EmDash vs WordPress: What Is the Difference at a Glance?

EmDash is a TypeScript CMS built on Astro that treats security isolation and AI agents as core features. WordPress is a PHP CMS whose strength is its ecosystem: plugins, themes, page builders, hosts and people. The table below compares the current versions as of October 2026.

AreaEmDash 1.xWordPress 7.x
Language and stackTypeScript, AstroPHP, MySQL or MariaDB
Runs onCloudflare Workers (D1, R2) or Node.js (SQLite, libSQL)Any PHP host, from shared hosting to managed clouds
Plugin modelSandboxed isolates with admin-approved permissions (when a sandbox runner is configured)PHP in the same process as core, full access
Plugin catalogue98 registry plugins, 52 publishers (21 Oct 2026)72,000+ on WordPress.org plus premium marketplaces
Visual page builderNoneBlock editor, Site Editor, Elementor, Bricks, Divi
E-commerceStripe Checkout and early commerce pluginsWooCommerce and its ecosystem
AI and MCPBuilt-in MCP server with OAuth 2.1 and fine-grained scopesAbilities API and MCP Adapter; built in on InstaWP via InstaMCP
LicenceMIT, any licence for pluginsGPL v2
SetupCLI scaffold, then a passkey-based adminFive-minute install, or about 40 seconds on InstaWP
Migration inWXR upload or EmDash Exporter pluginMature tools between hundreds of hosts

What Is EmDash, and What Changed in EmDash 1.0?

EmDash is a free, open-source content management system from Cloudflare, announced on 1 April 2026 as “the spiritual successor to WordPress” and declared stable with EmDash 1.0 on 28 September 2026. It keeps a WordPress-like admin (posts, pages, media, menus, comments) but rebuilds everything underneath in TypeScript on EmDash‘s Astro foundation.

EmDash 1.3.1 admin dashboard with posts, pages, media and the sidebar menu
The EmDash 1.3.1 admin we installed on 21 October 2026. The sidebar mirrors WordPress concepts: posts, pages, media, comments, menus, widgets.

Version 1.0 changed the comparison in four ways that the April coverage, including our own first version of this article, could not account for:

  • A plugin registry now exists. It runs on the AT Protocol, so publishers keep ownership of their identity and releases. Site owners browse it at plugins.emdashcms.com or from the admin, and see each plugin’s permissions before they install it.
  • Sandboxing works on Node.js too. On Cloudflare each plugin runs as a Dynamic Worker. On Node.js EmDash starts workerd, the open-source Workers runtime, as a child process.
  • More database options. D1 on Cloudflare, SQLite or libSQL on Node.js, and a Hyperdrive adapter for an existing PostgreSQL database.
  • Real adoption signals. Cloudflare reports more than 175 contributors, more than 1,800 commits and 25 languages, and says it moved its own blog to EmDash in August.
The sandbox is not on by default. When we scaffolded a site with npm create emdash@latest (version 1.3.1, Node.js template), the generated config had no sandbox runner, and the Plugins screen showed “No plugins configured”. EmDash’s own plugin sandbox docs confirm that the Cloudflare templates leave the binding commented out, and that the Cloudflare sandbox needs the Workers Paid plan. Plugins listed in code under plugins: [] run in the EmDash server process with no isolation.

Why Is EmDash Being Called a “WordPress Killer”?

EmDash is called a WordPress killer because a large infrastructure company built it to fix WordPress’s best-known weaknesses from a clean slate. Four things made the launch louder than a typical new CMS.

  • Cloudflare is not a startup. It is a publicly traded company whose network carries a large share of web traffic, so its CMS arrives with real resources and distribution.
  • The “two Matts” story. EmDash was built by Matt “TK” Taylor and Matt Kane at Cloudflare. WordPress was co-founded by Matt Mullenweg. The coincidence gave the story an easy headline.
  • AI agents helped build it. Cloudflare says it used AI agents to build the first version in roughly two months.
  • It targets WordPress’s pain points directly. Plugin security, serverless hosting, GPL licensing and AI-native design are the problems EmDash says cannot be fixed inside WordPress’s architecture.

Matt Taylor put it bluntly in an interview with Computerworld: “There is a whole new generation of developers, and WordPress is old news to them. If you are starting today, there is no way you are picking WordPress.” That is the claim this comparison tests. Watch our video take first:

For the longer developer opinion piece, read Is EmDash Really a WordPress Alternative? A Developer’s Honest Look at the Hype. And if you are wondering whether WordPress itself is fading, our take on is WordPress dead covers the numbers.

EmDash vs WordPress: Is EmDash Really a WordPress Alternative?

EmDash is a real WordPress alternative for developer-built content sites, and not yet an alternative for most business sites. It wins on architecture, licensing and AI design, and loses wherever an ecosystem matters. Here is the detailed EmDash vs WordPress comparison, area by area, using EmDash 1.3.1 and WordPress 7.0 and later.

1. Which Is More Secure, EmDash or WordPress?

EmDash has the stronger plugin security model, because each registry plugin runs in its own isolate with only the permissions an admin approves. WordPress plugins run with full access, so WordPress security depends on how well the site is managed. Cloudflare led its launch with security for a reason: plugins are the biggest attack surface in any CMS.

In EmDash, a plugin that emails you after a post is saved declares two capabilities, such as read:content and email:send. It cannot touch the database, the filesystem or any network host it did not declare. Before install, EmDash checks the bundle’s checksum, name, version and permissions, and an update that adds permissions waits for your approval again.

A WordPress plugin is PHP that hooks straight into core. It can read the database, write files and call any host. WordPress manages that risk around the plugin instead: directory review and release scanning, reputation, updates, and the hosting layer. That is where the WordPress plugins ecosystem, WordPress plugin security best practices and managed hosting do the work.

WordPress plugin
One PHP process
Core + every plugin + theme share it
DatabaseFilesNetworkOther plugins
Full access by default. Risk is managed around the plugin: updates, scanning, WAF, virtual patching.
EmDash registry plugin
Its own isolate
Dynamic Worker (Cloudflare) or workerd (Node.js)
read:contentemail:senddeclared hosts only
Starts with no access. An admin approves each permission. Needs a sandbox runner configured, which new projects leave off.
AspectEmDashWordPress
Plugin executionSandboxed isolate per registry pluginShared PHP process with core
Permission systemDeclared in a manifest, approved by an adminNone (full access by default)
Network accessDeclared hostnames onlyUnrestricted
Database accessOnly through declared capabilitiesFull direct access
Blast radius of a bad pluginIts own sandboxThe whole site
CatchSandbox needs a runner; Workers Paid on Cloudflare; not available on Hyperdrive deploymentsMitigated by updates, scanning, WAF and virtual patching
Track recordToo new to measureMost reported vulnerabilities come from plugins, not core

Verdict: EmDash wins on architecture. In practice, WordPress plugin risk is manageable: use reputable plugins, keep them updated, and run on managed hosting platforms with vulnerability scanning, a WAF and virtual patching. All-in-one-cloud platforms like InstaWP add a vulnerability scanner and managed updates from the Plus plan, and InstaShield WAF on every production plan.

2. How Do EmDash and WordPress Differ in Architecture and Hosting?

EmDash is serverless-first: on Cloudflare Workers it scales to zero when idle and you pay for compute time. WordPress is a classic server application that runs PHP, a web server and MySQL all the time. That difference shapes cost, speed and how many places you can host each one.

On Cloudflare, EmDash stores content in D1 (distributed SQLite) and media in R2. On Node.js it uses SQLite on a persistent disk or a remote libSQL database, and the docs warn that SQLite will not work on hosts with ephemeral storage. WordPress needs Apache or Nginx, PHP and MySQL, and its speed comes from layers: page cache, object caching, a CDN and tuned PHP. Performance optimization in WordPress is a deep, well-documented craft.

Modern WordPress hosting platforms have removed most of that work. On InstaWP each site runs isolated, with its own Linux user, database and PHP-FPM pool, plus InstaCDN, InstaShield and daily backups from the Plus plan, an object cache from Plus, and five server regions.

AspectEmDashWordPress
RuntimeV8 isolates on Workers, or Node.jsPHP on Apache or Nginx
DatabaseD1, SQLite, libSQL, or PostgreSQL via HyperdriveMySQL or MariaDB
Scale to zeroYes, on CloudflareNo, the server stays on
Idle costNone on Workers (plan fees aside)Server cost regardless of traffic
CDNCloudflare networkConfigured, or included on managed hosts
Self-hostingNode.js plus a persistent disk for SQLitePHP plus MySQL, documented everywhere
Hosting choiceCloudflare (best supported) or any Node.js hostHundreds of hosts worldwide

Verdict: EmDash is attractive for spiky or low-traffic content sites on Cloudflare. WordPress wins for heavy, dynamic sites (WooCommerce, memberships, LMS) because its hosting ecosystem is far more mature and battle-tested.

3. Which Is Better for AI Agents and MCP?

EmDash was designed for AI agents from day one, with an MCP server built into every site. WordPress added the pieces in core (the Abilities API in 6.9 and the AI Client in 7.0), and InstaWP ships a full MCP server, InstaMCP, on every site it hosts. So both can be operated by an agent today; they differ in governance and in what the agent can reach.

EmDash’s MCP server lives at /_emdash/api/mcp and accepts OAuth 2.1 with PKCE, personal access tokens or a device flow. Its scopes are fine-grained: content read and write, media, schema, taxonomies, menus, settings, plugin tools, and whole-site export and import. Agents also get an EmDash CLI and Agent Skills.

EmDash Create New Token screen with scopes for content, media, schema and admin access
EmDash personal access tokens choose scopes per token (captured in April 2026).

On the WordPress side, WordPress 7.0 shipped on 20 May 2026 with the AI Client, building on the Abilities API, and WordPress 7.1 followed. The official WordPress MCP Adapter turns abilities into MCP tools, but on a bare install it exposes very little.

InstaMCP: governed MCP on every InstaWP site. You do not need to wait for core. InstaWP’s MCP integration for WordPress turns on with one toggle in the site’s MCP panel and gives agents 43 typed tools for posts, pages, media, users, plugins, themes, templates and settings. WordPress roles map to four OAuth scopes, Safe Mode blocks deletes, and raw PHP, SQL and file tools stay off until an admin enables them. Every PHP write is linted before it reaches disk. The InstaWP docs include setup guides for 14 clients, including Claude, ChatGPT, Cursor and VS Code.
InstaWP site dashboard with the MCP panel and the Enable MCP toggle highlighted
InstaMCP is one toggle in the InstaWP site dashboard.

Watch how an agent hardens a WordPress site through InstaWP’s MCP integration:

AspectEmDashWordPress (with InstaWP)
MCP serverBuilt in on every siteInstaMCP built in on InstaWP; MCP Adapter elsewhere
Auth and scopesOAuth 2.1, PATs, device flow; fine-grained scopesFour OAuth scopes mapped to WordPress roles
Code and file accessPlugin and theme codeTheme, plugin and PHP tools, off until an admin enables them
CLIEmDash CLIWP-CLI (mature) and the InstaWP CLI
Site export and import over MCPYesContent and settings tools; migrations through InstaWP
Maturity1.x, weeks oldWordPress ecosystem plus production InstaMCP

Verdict: EmDash wins on design purity and on scope granularity. WordPress with InstaMCP closes the practical gap today, on a platform with years of CLI tooling. Read is MCP on WordPress safe and our best WordPress MCP plugins test for the governance details.

4. How Do Custom Content Types Compare?

EmDash creates custom content types in the admin with no code and gives each one its own database table. WordPress needs code or a plugin such as ACF for the same result, and stores everything in shared tables. EmDash is cleaner; WordPress is more familiar and has the larger tool chain.

EmDash Content Types screen listing the Pages and Posts collections and their features
EmDash 1.3.1 Content Types: each collection lists the features it supports, such as drafts, revisions, scheduling, search and SEO.

In EmDash a content type is a “collection”. You add fields (text, number, boolean, image, JSON and more), set validation, and EmDash creates a dedicated table. Content is stored as Portable Text, a structured JSON format, rather than HTML. A short walkthrough of the April build is in the create content type animation (a large GIF, about 59 MB).

WordPress keeps posts in wp_posts and fields in wp_postmeta. Registering custom post types takes register_post_type or a plugin such as ACF, Pods or Meta Box. It works, it has worked for over 20 years, and almost every developer knows it.

AspectEmDashWordPress
Create a typeAdmin UI, no codeCode or a plugin (ACF, Pods)
StorageA table per collectionShared wp_posts and wp_postmeta
ValidationBuilt inVia plugins
Content formatPortable Text (JSON)HTML and block markup
ToolingNewACF, Meta Box, Pods and thousands of add-ons

Verdict: EmDash wins on data design. WordPress wins on tooling, and its HTML is easier to move anywhere.

5. Can Non-Developers Build an EmDash Site?

Not yet. EmDash themes are Astro projects written in code, and EmDash has no visual page builder. WordPress has the block editor, the Site Editor and page builders such as Elementor, Bricks and Divi, so people who never open a code editor can build complete sites.

EmDash themes cannot touch the database, which removes a whole class of theme vulnerabilities. The theme catalogue is growing: Cloudflare highlights Lexington Themes, with 44 Astro themes that have EmDash variants, and an alpha AI site builder called EmDash Build. WordPress.org lists 8,769 free themes in its theme directory (21 October 2026), plus a large premium market.

AspectEmDashWordPress
Theme frameworkAstro components, TypeScriptBlock themes, theme.json, PHP templates
Visual builderNoneBlock editor, Site Editor, Elementor, Bricks, Divi
Non-developer themingNot practical todayStrong
Theme securityNo database accessFull execution access via functions.php
Theme catalogueEarly (for example 44 Lexington themes)8,769 free on WordPress.org, plus premium

Verdict: WordPress wins decisively for anyone who is not a frontend developer. Until EmDash gets a visual builder, it is a developer tool.

6. How Big Is Each Plugin Ecosystem?

WordPress.org listed 72,276 free plugins on 21 October 2026; the EmDash registry listed 98. EmDash’s ecosystem went from zero in April to a working registry with SEO, forms, email, analytics, reviews and payments, but it is more than 700 times smaller than WordPress’s.

EmDash Plugins screen showing No plugins configured
April 2026: the EmDash Plugins screen with no plugins. A fresh 1.3.1 Node.js scaffold still shows this until you configure a sandbox runner.

We queried the registry’s public discovery API: 98 packages from 52 publishers. Most are at version 0.x. The list includes a Stripe Checkout plugin (v0.9.0, MIT, five permissions), DinkusKit Commerce, a DashCommerce setup listing, Freeform forms, SEO and schema, Umami analytics and a CrowdSec integration. Paid plugins are on the roadmap, not live.

Stripe Checkout for EmDash listing in the EmDash plugin registry showing version, MIT license and 5 permissions
Each registry listing shows the version, licence and the number of permissions the plugin asks for.
AspectEmDashWordPress
Plugins available98 (52 publishers), 21 Oct 202672,276 free on WordPress.org, plus premium
MarketplaceAT Protocol registry, free plugins onlyWordPress.org plus premium marketplaces
E-commerceStripe Checkout, early commerce pluginsWooCommerce
Forms, SEO, analyticsEarly options for eachMature options for each
LMS, membership, bookingNot found in the registryLearnDash, MemberPress and many more
Plugin licensingAny licenceGPL for WordPress.org distribution
Trust signalsDeclared permissions, signed releasesRatings, reviews, install counts

Verdict: WordPress wins overwhelmingly. EmDash has a better plugin architecture with far fewer plugins in it. For any production site that needs more than publishing, WordPress is still the safe choice.

7. Which Is Easier to Set Up and Use?

WordPress is easier for almost everyone. EmDash setup is a developer task: a terminal command, a config file, a deploy, then a passkey-based admin. On InstaWP a WordPress site is live on HTTPS in about 40 seconds with no terminal at all.

We timed both on 21 October 2026. npm create emdash@latest (create-emdash 1.3.1, Node.js blog template, dependencies installed) finished in 34.4 seconds on our machine. That gives you a local project, not a live site. Creating a WordPress 7.1.3 site with the InstaWP CLI took 39.7 seconds from request to a responding HTTPS URL.

Terminal running the EmDash create project prompt asking for a project name
EmDash starts in the terminal.
EmDash setup wizard asking the admin to create a passkey instead of a password
EmDash 1.3.1 setup asks the first admin to create a passkey rather than a password.

The EmDash admin is familiar once you are in. It looks like a cleaner classic WordPress admin, and its editor is a rich text editor with a publish panel rather than a block editor.

EmDash playground dashboard with content counts and recent activity
The EmDash playground dashboard (April 2026).
EmDash post editor with title, featured image, rich text toolbar and publish panel
The EmDash 1.3.1 post editor: one rich text field stored as Portable Text, with slug, bylines and taxonomies in the side panel.

One Reddit user in the r/WordPress EmDash vs WordPress thread summed up the gap: most people who run WordPress sites have never used a VPS or a terminal. On InstaWP you pick a WordPress and PHP version, a region and a name, and the site is ready.

InstaWP new site wizard with WordPress version, PHP version, server location and site name
Creating a WordPress site on InstaWP takes a few fields and no terminal.
AspectEmDashWordPress
Setup for non-developersNot practical without helpAbout 40 seconds on InstaWP (measured)
Setup for developers34.4 s scaffold (measured), then config and deployFive-minute install, or instant on a managed host
Admin loginPasskey firstPassword, with 2FA plugins
EditorRich text, Portable TextBlock editor plus classic
Learning resourcesDocs and a Discord of 800+ membersHuge: courses, YouTube, WordCamps

Verdict: WordPress wins decisively. For agencies whose clients edit their own sites, it remains the practical recommendation.

8. How Do the Licences Differ?

EmDash uses the MIT licence and lets plugins and themes use any licence, including proprietary ones. WordPress uses GPL v2, and anything distributed on WordPress.org must be GPL too. For commercial plugin authors, this is EmDash’s strongest argument after security.

AspectEmDashWordPress
Core licenceMITGPL v2
Plugin and theme licenceDeveloper’s choiceGPL for WordPress.org
Licence contagionNone (sandboxed, no shared code)Debated for code that uses WordPress APIs
OpennessFull source (MIT)Full source (GPL v2)

Verdict: EmDash wins for commercial flexibility. GPL has kept the WordPress ecosystem open for two decades, which is part of why it is so large.

9. Can You Sell Content or Products on EmDash?

Partly. EmDash has built-in support for x402, an open standard that lets AI agents pay per request for content, and its registry now has Stripe Checkout. WordPress has no native payments, but WooCommerce, MemberPress, Easy Digital Downloads and paywall plugins cover almost every model.

AspectEmDashWordPress
Built-in monetizationx402 pay-per-requestNone (plugins)
Agent paymentsBuilt inNo established solution
StoreStripe Checkout, early commerce pluginsWooCommerce
Memberships and coursesNot found in the registryMemberPress, LearnDash and more
Payment gatewaysStripe, wallets (x402)Stripe, PayPal, Square and more

Verdict: A split. EmDash is early on agent payments; WordPress wins on every kind of selling people do today.

10. How Hard Is It to Move Between WordPress and EmDash?

Moving content from WordPress to EmDash is possible in minutes; moving a whole site is not. EmDash imports WordPress content through a WXR file or the EmDash Exporter plugin, but PHP themes, plugins and shortcodes do not carry over. WordPress itself moves between hosts easily.

EmDash Import from WordPress screen with site URL check and WXR upload
The EmDash WordPress importer (April 2026). Version 1.3.1 adds a migration-key option for the Exporter plugin.

WordPress portability is one of its most underrated strengths. InstaWP offers one-click migration from other hosts, staging and production on the same dashboard, 2-way sync between environments, and push and pull between local and cloud. See how to import a WordPress site for every method.

AspectEmDashWordPress
Import from WordPressWXR or EmDash Exporter (tested below)Not applicable
ExportWhole-site package, also over MCPWXR, database and file exports
Theme and plugin migrationRebuild requiredPortable across all WordPress hosts
Host portabilityCloudflare or Node.js hostsHundreds of hosts
Staging and syncNot built inBuilt in on InstaWP (staging, clone, 2-way sync)

Verdict: WordPress wins on portability. The EmDash importer is good for content, as our test shows next.

Already on WordPress? Keep your plugins and get the speed.Move your site to InstaWP managed hosting with free migrations on every plan.
Start a free migration →

We Moved a Real WordPress Site to EmDash: What Survived?

Posts, pages, images, tables, categories and ACF values survived our move to EmDash 1.3.1. Shortcodes, dynamic blocks, a quote block’s text and WooCommerce prices and SKUs did not. The importer itself was fast: three or four screens and about a minute of work, with a clear summary at the end.

Method (21 October 2026). We built a WordPress 7.1.3 test site on InstaWP with six posts, eight pages, one WooCommerce product, a Contact Form 7 form, an ACF field group with six fields, three media files and a comment. One post used every common block: heading, list, quote, image with caption, table, columns with a button, code, a YouTube embed and a gallery. We then imported it into a fresh EmDash 1.3.1 site twice: once by uploading a WXR export, and once with the EmDash Exporter plugin (v1.2.0, installed from GitHub, since it is not on WordPress.org). We followed the official migrate from WordPress guide.

EmDash importer review step mapping ACF fields such as client name, budget and industry to new EmDash fields
With the Exporter plugin, the review step offers to create EmDash fields for each ACF field.
Came across
Posts, pages, drafts and the scheduled post (kept as scheduled)
Headings, bold, italic and links
Lists, tables, code blocks
Images with captions, gallery, cover block
Columns and buttons (as structured data)
Categories and tags
ACF text, number, true/false and select values (Exporter only)
Comments, product categories, site title and logo (Exporter only)
Converted with caveats
ACF relationship and image fields: kept as WordPress IDs, not EmDash entries
YouTube embed: stored as an embed object; check it renders in your theme
WooCommerce product: title, description and image only
Contact Form 7 form: imported as its own content collection (WXR only)
Lost or broken
Quote block text: only the citation survived, in both runs
Shortcodes: left as plain text, such as [contact-form-7 …]
Latest Posts dynamic block: imported as an empty HTML block
WooCommerce price and SKU
ACF values and comments (WXR only)
WXR only: every category and tag created twice
What we checkedWXR uploadEmDash Exporter 1.2.0
Content items imported15 of 16 (the contact form failed)15 of 15, no errors
Media files3 of 3, URLs rewritten3 of 3, URLs rewritten
ACF field valuesNot importedImported into new fields
CommentsNot imported2 imported
Categories and tagsDuplicated (en and en_US copies)Imported once
Custom taxonomy (product categories)SkippedCreated
Quote block textLostLost
ShortcodesPlain textPlain text
WooCommerce price and SKULostLost
EmDash WordPress importer result after a WXR upload: 15 items imported with 1 content error
The WXR run finished with one error (“Invalid locale code: en_US” on the contact form) and created a collection for the form.

Two problems surprised us. First, the quote block’s text disappeared in both runs while its citation stayed, so a blog full of pull quotes would lose them silently. Second, the WXR run created every category and tag twice, once with the locale en and once with en_US (our WordPress site’s language), and the default blog theme listed both. The Exporter run did neither of those duplications.

EmDash import complete through the EmDash Exporter plugin with comments, taxonomies and site identity imported
The Exporter run: 15 items, 3 media files, 2 comments, a custom taxonomy and the site identity, with no errors.
If you try a WordPress to EmDash migration: use the EmDash Exporter rather than WXR, keep the WordPress site online until media has downloaded, and search the result for [ to find shortcodes. Rebuild quotes, forms, stores and dynamic blocks by hand. Our test was one small site on one day, so treat it as a checklist, not a guarantee.

How to Migrate WordPress Content to EmDash

  1. Back up WordPress, including the database and wp-content/uploads, and note your permalinks, menus and custom post types.
  2. Install the EmDash Exporter from the wp-emdash GitHub releases on the WordPress site and generate a migration key under Tools, EmDash Migration.
  3. Open Import in the EmDash admin, paste the key, and review how each post type maps to a collection, including the suggested ACF fields.
  4. Map authors to EmDash users, or leave them as guest bylines.
  5. Run the media step so EmDash downloads images and rewrites their URLs.
  6. Verify before cutover: compare counts, open complex posts, search for shortcodes, and set up redirects for any changed URLs.

Which Should You Choose, EmDash or WordPress?

Choose EmDash for a new, developer-maintained content site on Astro or Cloudflare where you value isolation and an MIT licence. Choose WordPress for client sites, stores, memberships, anything a non-developer must edit, and any site that depends on specific plugins.

A developer’s own blog or docs site on AstroEmDashEmDash fits: code-first themes, Portable Text, scale to zero on Workers.
A marketing site on Cloudflare with a small team of developersEitherEither works. EmDash if the team writes TypeScript; WordPress if marketers need a visual builder.
Agency client sites the client editsWordPressWordPress: page builders, training material and a familiar editor.
A WooCommerce storeWordPressWordPress: price, SKU and order data do not migrate, and EmDash commerce is early.
A membership, course or booking siteWordPressWordPress: we found no LMS, membership or booking plugins in the EmDash registry.
A site AI agents operate every dayEitherEither: EmDash’s MCP is built in; on WordPress use InstaMCP on InstaWP.
A high-traffic publisher with editorial workflowsWordPressWordPress today, with an eye on EmDash: Cloudflare runs its own blog on it.

Staying on WordPress: How Does InstaWP Compare to Running EmDash on Cloudflare?

Most of what draws developers to EmDash is available on WordPress through InstaWP. InstaWP is a managed WordPress hosting provider where a site is live in about 40 seconds, protected by InstaShield WAF, and ready for AI agents through InstaMCP, while you keep every plugin and theme you already use.

What you need EmDash on Cloudflare WordPress on InstaWP
Live site Scaffold, configure, deploy Live HTTPS site in ~40 s (measured)
Plugin safety Sandbox, if a runner is configured InstaShield WAF, scanner and virtual patching
AI agents Built-in MCP server InstaMCP: 43 tools, scopes, Safe Mode
Plugins 98 registry plugins 72,000+ WordPress plugins
Visual building None Block editor, Elementor, Bricks, Divi
Staging Not built in Built-in staging from Pro
Migration Content import, rebuild the rest Free migrations on every plan
Billing Workers usage and plan Per site per day, from $5/mo

Step 1: Create a WordPress site

Click New Site, choose From Scratch, Snapshot or Store, then pick the WordPress and PHP versions, server location and a name. Start on a free sandbox or choose a plan.

InstaWP plan picker with Free, Sandbox, Starter, Plus, Pro and Turbo plans and daily prices
Choose a sandbox to test, or a production plan.

Step 2: Open the site and log in

The site is ready with its URL, credentials, a database editor, a code editor and Magic Login, so you can get into wp-admin in one click.

InstaWP Your new WordPress website is ready screen with URL, Magic Login, Code Editor and DB Editor
A ready WordPress site with Magic Login and developer tools.

Step 3: Turn on InstaMCP for your AI agent

Open the site’s MCP panel, switch on Enable MCP and copy the connection URL into Claude, ChatGPT, Cursor or VS Code.

InstaWP MCP panel with the Enable MCP toggle
Enable MCP is one switch per site.

Step 4: Test changes on staging

On Pro and above, branch a staging copy of the live site, test updates there, then push to production.

InstaWP staging panel with a production site, its staging copy and Pull to staging and Push to production buttons
Built-in staging with pull and push.

Step 5: Watch security and updates from Manage

Manage shows uptime, performance and vulnerabilities, with scanners and activity logs, and managed updates from the Plus plan.

InstaWP Manage dashboard with uptime, performance and vulnerability summaries and scanners
One dashboard for uptime, performance and vulnerabilities.
JobPickWhy
Learn EmDash or prototype on AstroEmDashMIT, code-first, free
Client site with plugins and a builderWordPress on InstaWPEcosystem plus managed hosting
Store, membership or LMSWordPress on InstaWPWooCommerce and mature plugins
Agent-operated WordPress siteWordPress on InstaWPInstaMCP on every plan
Test EmDash next to WordPressBothKeep production on WordPress while you evaluate
Test your next client site on InstaWPCreate a WordPress site in about 40 seconds and turn on InstaMCP with one switch.
Create a WordPress site →

Can You Host Your WordPress Site on InstaWP?

Yes. InstaWP is a managed WordPress hosting provider that hosts production sites on its own infrastructure, billed per site per day from $5 a month. A sandbox becomes a production site with one click, on the same URL with the same data, so you build, test and launch without a migration.

InstaWP hosting page showing the Sandbox to Production toggle with InstaCDN, InstaShield and daily backups
Sandbox to production on the same URL.

Each site runs isolated with its own Linux user, database and PHP-FPM pool, in one of five regions (US, UK, Germany, Singapore, Australia). Security comes from InstaShield, delivery from InstaCDN, and recovery from automatic backups. Developers get SSH, WP-CLI, Git and SFTP on every plan through the developer tools. In August 2026 a test site on InstaWP’s new-generation servers scored 9.8 out of 10 in WP Benchmark, against 7.3 on the previous generation; the method is in our WordPress hosting benchmark.

FeatureStarterPlusPro and above
Free SSLYesYesYes
InstaCDNBasic edgePremiumPremium
InstaShield WAFBasicAdvancedAdvanced
Bot and DDoS protectionNoYesYes
BackupsWeeklyDailyDaily
Object cache (Valkey)NoYesYes
Managed updates and uptime monitoringNoYesYes
Vulnerability scannerNoYesYes
Built-in stagingNoNoYes
Image optimizationNoNoYes
InstaMCP, SSH, WP-CLI, Git, SFTP, free migrationsYesYesYes
PlanPrice per monthBest for
Sandbox$2Testing and demos
Starter$5Small production sites
Plus$9Business sites that need daily backups and scanning
Pro$15Sites that need staging and image optimization
Turbo$25Busier sites
Elite$45High-traffic sites

Every account gets $25 in free credits, a 14-day money-back guarantee on production plans and no annual contract. Current prices are on the InstaWP pricing page.

Launch your site on InstaWP managed hostingProduction WordPress hosting from $5/mo per site, with $25 in free credits.
See hosting plans →

The Overall Verdict: Is EmDash Better Than WordPress?

EmDash is better engineered; WordPress is better for shipping real sites today. EmDash wins the areas that depend on architecture, and WordPress wins the areas that depend on an ecosystem, which are the ones most projects are judged on.

AreaWinnerMargin
Plugin securityEmDashModerate (when the sandbox is configured)
Architecture and hostingEmDashNarrow (managed WordPress hosting closes it)
AI and agentsEmDashNarrow (InstaMCP closes it on WordPress)
Content modelingEmDashModerate
LicensingEmDashModerate
Theming and visual buildingWordPressDecisive
Plugin ecosystemWordPressOverwhelming
Setup and editingWordPressDecisive
Monetization todayWordPressLarge (EmDash leads only on agent payments)
Migration and portabilityWordPressDecisive

Sanchit Vir Gogia of Greyhound Research framed it best: this is “operating model versus operating model,” not product versus product. Incumbents have inertia; insurgents have architectural purity. EmDash has grown quickly since April, but from a much smaller base.

The short version

Pick EmDash for a new developer-run content site on Astro. Pick WordPress for client work, commerce and anything that depends on plugins, and run it on managed WordPress hosting like InstaWP for the isolation, edge delivery and agent access that EmDash advertises.

What Should You Actually Do?

Most teams should stay on WordPress, move it to a modern hosting platform, and evaluate EmDash on a side project. That captures most of the benefit with none of the migration risk.

  • Stay and modernise. Run WordPress on InstaWP for vulnerability scanning, InstaShield, staging and InstaMCP. Use InstaWP to start with a free sandbox.
  • Pilot EmDash where it fits. Try it on a new Astro content site, or in the EmDash playground, before any client work.
  • Watch three signals. Paid plugins in the registry, a visual builder, and a production-ready store. When those land, re-run this comparison. Meanwhile, use the AI features that arrived with WordPress 7.0.

If you want the Astro frontend without leaving WordPress, our guide to headless WordPress with Astro is the middle path, and the free WordPress staging guide covers safe testing.

EmDash vs WordPress FAQs

Is EmDash free?

Yes. EmDash is free and open source under the MIT licence. You pay only for hosting: Cloudflare Workers usage, or any Node.js host. Sandboxed plugins on Cloudflare need the Workers Paid plan.

Does EmDash only run on Cloudflare?

No. EmDash runs on Cloudflare Workers with D1 and R2, or on Node.js with SQLite or libSQL. A Hyperdrive adapter connects Workers to an existing PostgreSQL database. Cloudflare is the best-supported platform.

Can I migrate my WordPress site to EmDash?

You can migrate the content. EmDash imports posts, pages, media, taxonomies and, with the EmDash Exporter plugin, ACF values and comments. In our October 2026 test, shortcodes, a quote block’s text, dynamic blocks and WooCommerce prices and SKUs did not survive, and themes and plugins must be rebuilt.

Does EmDash have plugins or a WooCommerce equivalent?

EmDash has a plugin registry with 98 plugins from 52 publishers as of 21 October 2026, including Stripe Checkout and early commerce plugins. There is no WooCommerce equivalent yet, and paid plugins are not live.

Does EmDash have a page builder?

No. EmDash themes are Astro projects written in code, and the editor is a rich text editor. WordPress has the block editor, the Site Editor and builders such as Elementor, Bricks and Divi.

Is EmDash 1.0 ready for production sites?

For developer-run content sites, yes: Cloudflare runs its own blog on EmDash. For sites that need plugins, a store, memberships or non-technical editors, WordPress is the safer production choice today.

Is EmDash more secure than WordPress?

EmDash’s plugin model is more secure by design, because registry plugins run isolated with approved permissions. New projects leave the sandbox off, though, and plugins added in code run without isolation. A well-managed WordPress site with a WAF, scanning and updates is secure in practice.

Can I host my WordPress site on InstaWP?

Yes. InstaWP is a managed WordPress hosting provider with plans from $5 a month per site, free migrations, InstaShield WAF, InstaCDN, backups and InstaMCP on every plan. Plus adds daily backups, the object cache and the vulnerability scanner, and Pro adds built-in staging.

Move your client sites to InstaWPManaged WordPress hosting with staging, scanning and InstaMCP. $25 in free credits to start.
Get started free →
NS
Neha Sharma
Content, InstaWP

Neha writes practical WordPress tutorials and agency playbooks, with a focus on dev workflows and AI building.