Substack vs WordPress: Which Should Writers Use?

The problem

Writers choosing a platform are really choosing what they can and can't do later. Two who left Substack, or partly left it, named what they missed:

"No API, no webhooks, no Zapier integration, no SSO" (LinkedIn, 2025-09-03)

"There is still no API for writers. There is still no support for Markdown." (X, 2026-09-05)

The other side deserves a hearing too. Substack itself says, "You can always export the email addresses of both your free and paid subscribers" (@Substack, 2026-10-15). In our October 2026 review of public forum threads, lock-in and backup came up in 19 of the 65 writer sources. Several Hacker News commenters, though, argued that lock-in is low because the list exports in one click (see the Substack export help).

So the honest question is not "which is better?" It is "which trade-offs fit how you write and grow?" Both platforms are good at different things. Below is a fair comparison as of October 2026, with every price and fee linked to its source.

How do Substack and WordPress compare at a glance?

	Substack	WordPress.com (hosted)	WordPress.org (self-hosted)
Cost to start	Free to publish (Substack)	Free plan; paid plans from US$4/mo billed yearly (WordPress.com)	Software is open source under GPLv2 (WordPress.org); you pay for hosting
Fee on paid subscriptions	10% plus Stripe	10% (Free) down to 0% (Commerce), plus Stripe	None from WordPress; your payment plugin and Stripe
Email newsletter built in	Yes	Yes: "Email every post to unlimited subscribers" on every plan	Needs a plugin or email service
Custom domain	One-time $50 (Substack)	"Free domain for one year with annual plans"	Yours by default
Custom design / code	No custom CSS or HTML (Substack)	Themes; plugins on every paid plan	Full control
Public API	No general writer API	REST API	REST API (WordPress)
Reader network / discovery	Substack app, Notes, recommendations	The WordPress.com Reader	None built in
Export	Zip of posts, list and stats	WXR export	WXR export plus full database

How much will I pay in fees on each platform?

For paid newsletters, fees matter more than plan prices. Substack's pricing article lists:

Fee	Substack
Substack fee	10% of each subscription payment
Stripe card processing	2.9% + $0.30 per payment for US cards
Stripe Billing (recurring)	0.7%
Custom domain	One-time $50

WordPress.com's pricing page lists a "Fee on paid subscriptions and payments" by plan, with Stripe's processing fee charged separately:

WordPress.com plan	Price, billed yearly (monthly billing)	Fee on paid subscriptions
Free	US$0	10%
Personal	US$4/mo (US$9)	8%
Premium	US$8/mo (US$18)	4%
Business	US$25/mo (US$40)	2%
Commerce	US$45/mo (US$70)	0%

The rough rule: on Substack the platform fee grows with your revenue. On WordPress.com you can trade a higher plan price for a lower percentage. On self-hosted WordPress you pay fixed costs (hosting, an email service, maybe a membership plugin) and keep more of each payment, but you do more of the work yourself. Prices on WordPress.com's page can change with promotions, so check them on the day you decide.

Which is better for SEO and owning my audience?

Ownership. On both platforms you own your words and your list. Substack's Terms of Use say you own what you create, "That includes publications, subscriber lists", and the export gives you "posts, subscriber list, and related statistics" (Substack Help). WordPress goes further: self-hosted, the database and server are yours.

Custom domain. Substack charges a one-time $50, needs a subdomain such as www, and "Emails are still sent from [yoursubdomain]@substack.com" (Substack Help). On WordPress the domain and sending setup are entirely yours.

SEO. Substack says it does "a number of things behind the scenes" for indexing, but "Some SEO features, such as sitemaps and Google Search Console verification, become available as your publication grows" (Substack Help). WordPress gives you control over sitemaps, schema, internal linking, page speed and templates from day one, through themes and plugins. If organic search is your main growth channel, that control is WordPress's strongest argument.

Discovery. Substack's advantage is its network. One writer who loads a monthly export into a database reported that, over twelve months, "recommendations from other writers brought me about 15,000 free signups" (r/Substack, 2026-10-11). That is one self-reported case, not a typical result, but WordPress has no built-in equivalent.

Can I extend or automate each platform?

This is the biggest practical gap.

Need	Substack (as of October 2026)	WordPress
Read your posts as data	RSS feed; no general posts API	REST API, JSON
Custom HTML or embeds in posts	Not supported: "you can't paste raw code" (Substack)	Full HTML blocks
Plugins	None	Large plugin directory; on WordPress.com, "every paid plan" (WordPress.com)
Automations (Zapier, Make)	Via RSS; no native app	Via the REST API or plugins
AI assistants	Official MCP for some publications (see Substack MCP server)	Via the REST API

If you want Substack's network and payments but need data out, the newsletterapi Posts API and MCP server give you read-only access to your own publication. For what Substack itself offers, see does Substack have an API?.

How do I move from Substack to WordPress?

1. Export from Substack: Settings → Exports → "Create new export" (Substack Help). Also export your subscriber CSV (see exporting Substack subscribers).
2. Import posts. WordPress.com has a Substack importer for "posts, images, podcasts, and public comments", plus a separate guide to "import free and paid subscribers" (WordPress.com Support). On self-hosted WordPress, the Substack Importer plugin imports "Posts and images", podcasts, comments on public posts and author information from your export file. It needs the WordPress Importer plugin installed first.
3. Expect timeouts on big archives. The plugin's FAQ says "timeouts can occur" with many posts and images; you may need to "run the import several times until all content has been imported" (WordPress.org).
4. Move subscribers separately. The plugin lists "Mailing lists" only as a future plan, so import your CSV into your email tool, for opted-in readers only.
5. Redirect. If you used a custom domain on Substack, point it at WordPress and set up redirects for your old /p/post-slug URLs.

How do I move from WordPress to Substack?

1. Import posts by URL (full walkthrough: importing posts to Substack). Substack's importer supports WordPress: "Just paste in your blog or newsletter URL" from Settings → Import/Export → "Import posts" (Substack Help).
2. Check the archive came across. Imports that rely on RSS may only include recent posts. Substack warns that some platforms include only "the latest 20 posts" in their feeds. Re-import with "Update existing posts" if needed.
3. Keep a WordPress backup. Tools → Export creates a WXR file with "posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users" (WordPress.org).
4. Import your list. Upload a CSV of opted-in subscribers. Substack may flag lists for review, and "Collections of contacts, leads, or other sources where all participants did not opt in are likely to be denied" (Substack Help).

Converting formats by hand is tedious. The newsletterapi import converter turns a WordPress WXR or other exports into clean, Substack-ready posts.

So which should I choose?

If you…	Lean towards
Want to start writing today with zero setup and built-in payments	Substack
Grow mainly through other writers' recommendations and the app	Substack
Grow mainly through Google search and need full SEO control	WordPress
Need custom design, plugins, a shop or integrations	WordPress
Earn a lot from subscriptions and want a lower platform fee	WordPress.com higher plans, or self-hosted
Want both	WordPress as your home site, Substack for the newsletter, linked by the signup embed and RSS (see embedding Substack on your website)

Whichever you choose, keep regular exports. Our Substack backup guide shows how in five minutes a month.