Marble vs WordPress

WordPress is open-source website software with blogging built in. You choose a host, which can include managed services. WordPress.com is a separate managed hosting service with its own plans. This comparison covers the open-source software. Marble hosts an editor and API for posts on a frontend you build. WordPress can serve a themed website or a custom frontend through its REST API. Choose based on whether you need a post service or a broader website system.

Start for freeSee the comparison

The short answer

Choose Marble when

  • You already have a site in Next.js, Astro, or another framework and want a hosted editor and post API.
  • Your content fits posts with authors, one category, tags, and typed custom fields.
  • You want HTML or Markdown for your frontend without maintaining a WordPress installation or choosing a WordPress host.
  • The hosted Free, $5/month Hobby, or $20/month Pro workspace plan fits your usage, and you host your frontend separately.

Choose WordPress when

  • You want a website built with themes, or you depend on WordPress plugins and built-in comments.
  • Your writers need scheduled publishing, revision restore, or the core Editor, Author, and Contributor permissions.
  • You need custom post types and taxonomies beyond a blog's post model.
  • You want control of your WordPress installation, or a managed WordPress host that handles operations for you.

Marble and WordPress, side by side

The differences that change which product fits. Plan and product details link to WordPress's own documentation. Last checked October 2026.

TopicMarbleWordPress
Built forBlog posts, articles, and changelogs on a site you build.Blogs and broader websites, with posts, pages, themes, and plugins. An ordinary blog does not need plugins.WordPress: Features
Website and frontendYou build and host the frontend. Marble is not a theme or site builder.Use a WordPress theme for the public site, or build a separate frontend that reads the built-in REST API.WordPress: FeaturesWordPress docs: Posts REST API
Editor and content outputA rich text editor with post bodies delivered as HTML or Markdown.The block editor stores HTML with block delimiter comments. Dynamic blocks render on the server. REST responses can include rendered HTML.WordPress docs: Block markupWordPress docs: Posts REST API
Blog post fieldsPosts already have authors, one category, tags, a cover image, a slug, and a description.Posts already have an author, categories, tags, a featured image, a slug, and an excerpt. No custom post type is needed for a blog.WordPress docs: Post settingsWordPress docs: Posts REST API
Custom content typesA fixed post model with typed custom fields. No arbitrary content types or custom taxonomies.Register custom post types and taxonomies in code or through plugins. Set show_in_rest to expose them through the REST API.WordPress docs: Custom content types and the REST API
Custom fieldsAdd typed custom post fields in the dashboard.Register post meta and expose it through the REST API with show_in_rest. Custom fields do not inherently require a paid plugin.Learn WordPress: Custom fields and the REST API
Headless deliveryA hosted REST API and TypeScript SDK. Your frontend renders the returned HTML or Markdown.Fetch posts at /wp-json/wp/v2/posts and render the returned HTML. Theme styling and plugin behavior may need separate frontend work.WordPress docs: Posts REST APIWordPress docs: Block markup
CMS hostingCMS hosting and the media library are included within your plan's limits. Frontend hosting is separate.Choose hosting for the open-source software. Managed WordPress hosts can handle operations. WordPress.com packages hosting in its own service plans.WordPress.com: WordPress.com vs WordPress.org
MaintenanceMarble operates the hosted CMS. You maintain your frontend and its integrations.Plan for updates and backups. WordPress supports background updates, and managed hosts can handle maintenance. Responsibilities depend on your host and installed plugins.WordPress docs: Updating WordPressWordPress.com: WordPress.com vs WordPress.org
Drafts and revisionsDraft and published posts, with draft sharing on Hobby and Pro. No built-in revision restore UI.Core drafts, pending review, and autosaves. Compare revisions and restore earlier content without a paid add-on.WordPress docs: Post settingsWordPress docs: Revisions
Scheduled publishingNo built-in scheduled publishing.Schedule posts in core with a future publication date. Default WP-Cron runs on page loads, so low traffic can delay tasks. A host or system scheduler can address this.WordPress docs: Post settingsWordPress docs: WP-Cron
Team permissionsOwner, Admin, and Member roles. Plans allow 1 team member on Free, 5 on Hobby, and 10 on Pro.Core Administrator, Editor, Author, Contributor, and Subscriber roles, with capabilities you can customize through code or plugins.WordPress docs: Roles and capabilities
Themes, plugins, and commentsNo WordPress-style theme or plugin system, built-in comments, or commerce backend. Add those services to your frontend separately.Themes control the website's presentation, plugins extend its behavior, and comments are built in. Check how any plugin works with a headless frontend.WordPress: FeaturesWordPress docs: Posts REST API
Software and pricingHosted Free plan at $0, Hobby at $5/month, and Pro at $20/month per workspace on monthly billing. Frontend hosting is separate.Free GPL software. Budget for hosting and any paid themes, plugins, or services you choose. WordPress.com has separate hosting plans.WordPress: FeaturesWordPress.com: WordPress.com vs WordPress.org

What publishing a post looks like

With Marble

  1. 1Create a workspace. The editor, media library, and post model are ready.
  2. 2Write a post and set its authors, category, tags, and metadata.
  3. 3Publish, then fetch the post through the SDK or REST API and render its HTML or Markdown.
  4. 4Configure a webhook to revalidate or rebuild your frontend when posts change.

With WordPress

  1. 1Choose a WordPress host or install WordPress on your infrastructure. Agree who handles updates and backups.
  2. 2Use a theme for your site, or connect your custom frontend to the built-in REST API. Basic blogging does not require plugins.
  3. 3Write in the block editor, set the post's author and taxonomy, and publish or schedule it. Use revisions when you need to restore earlier content.
  4. 4For a themed site, WordPress renders the post. For a custom frontend, fetch the rendered HTML and account for any theme styles or plugin behavior your content needs.

Moving blog posts from WordPress to Marble

  1. Export your posts with Tools > Export as WordPress XML, also called WXR, or fetch them through the REST API. Follow every page of REST results, not just the first response. Marble cannot directly import WXR or raw REST JSON.
  2. Resolve author, featured media, category, and tag IDs into the values you need. The REST API supports embedded or linked resources. Choose one category per post for Marble, and keep a record of each post's old public URL.
  3. Convert each post body into a Markdown file. Review block content, shortcodes, and interactive embeds. Replace anything that depends on WordPress or plugin code with content your new frontend can display. Move images or verify their URLs before removing the old media host.
  4. Add title, slug, description, date, category, and tags as supported frontmatter. In Settings > Data, upload the .md files individually or in ZIP batches. The import limits are 4 MB per upload, 100 Markdown files per ZIP, and 20 MB of extracted content.
  5. Review the imported drafts before publishing. Posts initially use the importing user's author profile, so reassign authors where needed. Set cover images and custom fields manually, and check dates, taxonomy, links, and converted content. The importer does not rehost images automatically.
  6. Keep the old public URLs or add redirects in your frontend. Audit titles, descriptions, canonical URLs, and publication dates after publishing. Matching a slug alone does not preserve a dated or category-based WordPress URL.
  7. Move only posts that fit Marble's model. Themes, plugins, comments, forms, users, roles, and custom content types do not transfer. Keep any needed website or application functionality running elsewhere before retiring WordPress.

Frequently asked questions

Common questions about choosing between Marble and WordPress.

Is Marble a good WordPress alternative for a blog?

Yes, if you build your own frontend and want a hosted editor and API for posts. Choose WordPress when you want a themed website, depend on its plugins, or need built-in comments, scheduling, and revision restore. Both already have a blog post model, so neither requires you to design one from scratch.

Is WordPress free, and how does its pricing compare?

The open-source WordPress software is free. You pay for hosting and any optional paid plugins, themes, or services. WordPress.com is a separate managed hosting service with its own plans. Marble includes CMS hosting on Free at $0, Hobby at $5/month, and Pro at $20/month per workspace on monthly billing. You still host your frontend. Compare the services and maintenance your project needs, rather than treating a WordPress.com starting price as the cost of every WordPress setup.

Can I use WordPress headlessly with Next.js or Astro?

Yes. WordPress has a built-in REST API for posts that custom frontends can fetch. Ordinary post content can arrive as rendered HTML, so a custom block renderer is not required for that HTML. You still need to reproduce any theme styles or plugin behavior your frontend depends on. Marble also supports custom frontends, with HTML or Markdown post bodies.

Do WordPress custom fields require a paid plugin?

No. You can register post meta in code and expose it through the REST API with show_in_rest. The official custom fields tutorial explains this setup. Plugins can provide other field interfaces and workflows. Marble lets you add typed fields to posts in its dashboard, while WordPress also supports custom post types and taxonomies.

Can I import my entire WordPress site into Marble?

No. Marble has no direct WordPress WXR or REST JSON importer. Convert blog posts into Markdown files with supported frontmatter, then use the file importer to create drafts. Review authors, covers, custom fields, image URLs, and redirects. Themes, plugins, comments, users, and custom content types need a separate plan.

More resources

Try Marble with your own site.

Create a free workspace, publish a post, and fetch it from your frontend in a few minutes.

Start for freeView pricing