Skip to main content

Why do people not like Substack?

A fair look at why writers, readers and developers dislike Substack: fees, lock-in, app push, moderation, and which gripes are overblown.

Updated 21 min readMarkdown

People dislike Substack for several separate reasons, and they don't weigh the same. The complaints that survive a fact-check are structural: it keeps 10% of paid subscriptions on top of Stripe's fees, it has no publishing API or webhooks that I could find documented, every email goes out from a substack.com address you can't change, you can't add custom CSS or HTML, and its app, Notes and recommendations steer readers toward the platform instead of toward your own site. A second group is about values, mostly how Substack has handled extremist publications, and that's a judgement call rather than a bug. A third group is overblown, because Substack is free to start on, lets you export your list, and does more for technical writers than its reputation suggests.

Last verified: 2026-11-19. Fees, limits and help-centre wording below were read from each vendor's own pages that day, in USD. Substack's help pages block scripted HTML requests, so I read them through the help centre's public JSON endpoint, which returns the same article text. Vendors change these pages often, so check again before you pay anyone.

Who is complaining, and about what?

Three different audiences use the word "dislike", and mixing them up is why most arguments about Substack go nowhere.

Writers who sell subscriptions mostly talk about money and lock-in: the percentage, the sender address, and a growing set of features that tie readers to Substack's app. Developers talk about what they can't do: write to the platform from code, inject markup, keep content in a repo, control URLs. Readers complain about the other end of the pipe: an account they didn't ask for, marketing email from Substack itself, push notifications, and paywall prompts. And a separate group, loud since late 2023, objects to what Substack does and doesn't remove from its platform.

I'll go through them in that order, and for each one I'll say what I could verify and where the complaint runs ahead of the facts. Substack also has real strengths, and I'll get to those before the alternatives. One disclosure up front: VeloCMS is my own project, and it shows up near the end as one option among six.

Is the 10% cut the real problem?

It's the most repeated complaint and it's real, but the arithmetic is more interesting than the slogan. Substack's cost page says publishing is free at any list size, and that once you turn on paid subscriptions Substack keeps 10% of each payment. Stripe's processing comes out separately: 2.9% + $0.30 for US cards and 0.7% for Stripe Billing on recurring payments, plus a one-time $50 if you want a custom domain. The page also says Substack adds no fee to web payments, though subscriptions bought in its iOS app may cost readers more to cover Apple's cut, and that the 10% on in-app purchases is calculated on your web price.

Here's my own arithmetic with those listed rates for a US card, ignoring tax. A reader paying $5 a month leaves you $4.02: Substack takes $0.50, Stripe's card fee is $0.445 and Billing is $0.035, so about 19.6% disappears. At $80 a year the same stack takes $11.18, roughly 14%. Notice what that says. At $5, Stripe alone takes nearly as much as Substack does (48 cents against 50), because the fixed 30 cents hurts small prices. Any platform that charges 0% still leaves you the Stripe part. beehiiv's pricing page says so in as many words: 0% of paid subscription revenue, with Stripe's standard fee on top.

So the honest version of the complaint isn't "Substack is expensive", it's "the 10% scales with your success while a flat fee doesn't." That's a fair point once you're earning real money. Take Ghost: its pricing page lists Publisher at $29 a month billed yearly for 1,000 members, with paid subscriptions and a 0% transaction fee. Ten percent of $290 a month is $29, so above roughly that much monthly subscription income the flat fee wins on this one line item. I only priced the 1,000-member tier, and hosting plans usually climb with list size, so run your own numbers.

Where the complaint is overblown: a writer with a free list pays Substack nothing to publish, at any list size (the optional $50 custom domain aside). The about page pitches the platform as "free to start and free to leave", and nothing I read contradicted the first half. Flat-fee tools such as Ghost bill you whether or not anyone pays you.

One more wrinkle from the migration docs: the 10% doesn't disappear when you leave. Ghost's Substack migration guide says Substack will continue to take its 10% on existing paid subscriptions, and gives a Ghost concierge address for help getting those fees removed. Buttondown's guide says the same and suggests asking Substack's support to disconnect Stripe and remove the 10% application fee without cancelling or refunding existing subscriptions. That brings us to the next complaint.

Is Substack a closed box for developers?

Mostly yes, with a couple of useful exceptions. This is the complaint I'd weigh most if you build things for a living.

Start with what exists. Substack publishes a Developer API Terms of Use, last updated 8 January 2026. It describes an API that can return public creator and publication data: name, profile and publication URLs, total subscriber count, bestseller status, leaderboard recognitions. It says use is subject to rate limits "as determined by Substack in its sole discretion", that Substack may revoke the licence at any time, and that you may not use it to replicate or materially compete with core Substack features. Nothing in it mentions creating or editing posts, managing subscribers, or sending email. One caveat: the last clause of the Terms points to a support article with technical documentation for generating an API key and using the API. I couldn't read it. It isn't in the help centre's public article list (I paged through the whole public list via the JSON endpoint), and its page sits behind a bot challenge. So what I can report is the scope the Terms themselves describe, which is public data.

Substack also documents an MCP server for AI assistants. It's read-only (dashboard metrics, traffic, settings), it "cannot publish posts, send Notes, or modify your account", and it requires an admin on a Bestseller publication. Useful if you qualify, but it's an analytics window, not a publishing pipeline.

On webhooks and automation platforms, I searched the help centre for "webhook", "Zapier" and "developer" on the day I wrote this and got no results for any of them. That's absence from the documentation, not proof nothing exists, so test before you build on an assumption. What does exist is an RSS feed at your.substack.com/feed (I fetched the feed of Substack's own publication and it came back as RSS 2.0), embed codes, and an RTMP key for live video.

Now the fairness check, because the "no code" reputation is a bit stale. The editor has a code block with syntax highlighting, automatic language detection and a copy button, LaTeX equations, and a GA4 connection where you paste a measurement ID. A tutorial blog works. What you can't do is touch the markup: the help centre says custom CSS or HTML aren't supported in the post editor, down to raw iframe embeds, and only approved embed types go through.

Can you actually get your data out?

Yes, with some homework. Substack's export page says you go to Settings, then Exports, then "Create new export", and get a zip with your posts, subscriber list and related statistics, with an email when it's ready. The subscriber list also has its own CSV export from the Subscribers page, and that page states plainly that it's "not currently possible to export a file with subscriber names". You get emails and subscription metadata, not first and last names.

Two things the export pages don't settle, and I'd check them before deleting anything. First, images. Substack doesn't say whether they travel in the zip, while Buttondown's migration guide says it replaces images hosted on Substack's CDN and tells you to verify them before closing your account. Second, formatting on arrival. beehiiv's import notes say code blocks arrive as plain text and need recreating, and comments, category structures and paywall placements aren't carried over. If your archive is tutorial-heavy, budget an afternoon.

Then there's Stripe, where two official-sounding paths do opposite things. Buttondown's guide warns, in a warning callout, not to disconnect Stripe from the Substack dashboard because that cancels and refunds all paid subscriptions. Ghost's guide says to reuse the same Stripe account, and Substack's own page on turning off paid subscriptions describes the "Disconnect Stripe" button as refunding and cancelling everyone. Pick your destination first, then ask Substack support for help with a clean handover.

Substack's counter, which is fair: it says you'll always own your readers' email addresses and can export them at any time, including readers who arrived from the app. Plain followers are a different story. Followers are the lighter relationship from the Notes side, and per Substack's help page they don't get your posts by email. The same page asks whether you can get your follower list if you leave Substack, and the answer it gives is a flat "No." So the list you can take with you is your subscribers, not everyone who follows you.

Does Substack let you control your site, your emails and your URLs?

Less than people expect from a tool at this price point, though it's catching up.

On design, a new website editor lets you pick a theme and set blocks, header, footer, colours and fonts across the home, welcome, post and section pages. That's real theming, as far as it goes, but it's a settings panel and not a stylesheet.

On email, the sender page is blunt: you can change the sender name but not the address, and every email goes from [subdomain]@substack.com. For anyone who has thought about SPF, DKIM and sender reputation, that has two sides. You inherit Substack's established sending reputation, which is a gift to a new writer, and you can never build your own domain's reputation or switch providers without changing the address your readers see.

On domains, setup costs a one-time $50, needs you to already own the domain, uses a CNAME to target.substack-custom-domains.com, and can take up to 36 hours to verify. Substack recommends a www or other subdomain and offers root-domain redirects through an A record. Registrars that only allow CNAMEs on subdomains, the root-domain page notes, force a subdomain. Changing your plain Substack subdomain breaks all your links unless you pick the redirecting option, which can only be used once.

On URLs and search, you can edit a post's slug on a draft, within 2 to 48 characters of lowercase letters, numbers and dashes. The SEO guide is the part that raised my eyebrows: it says some SEO features, "such as sitemaps and Google Search Console verification, become available as your publication grows", and ties that to publishing regularly, growing your list and enabling paid subscriptions. I don't know where that threshold sits, and I won't pretend to know how it affects ranking. For a developer used to dropping a sitemap into a repo, though, having it gated is a surprise.

Is Substack pushing writers toward its app and Notes?

Yes, and Substack says so itself, though it frames it as growth rather than capture. The help centre's follow page says following was built to help maximize subscriptions, not to replace them. Its recommendations page says new subscribers may see up to three recommended publications right after signing up. And the about page claims more than half of new subscribers and 30%+ of paid subscriptions come from inside Substack's own network. I can't verify those figures, and Substack doesn't say how they were measured.

The friction people describe is partly about defaults. A help article explains that readers who install the app may be on "Smart notifications": they primarily get push alerts about new posts, with email only for posts they've missed if they haven't opened the app in a while. That's a setting a reader can flip back to "Prefer email", but it means a subscriber who installs the app may stop getting your email the way you assume they do. If your whole workflow assumes inbox delivery, that's worth knowing. Notes work similarly: per another help page, new notes don't email subscribers, but the app may send a one-time push when you publish your first note and occasional pushes after that.

The sharpest version of the critique is lock-in. David Farrier, one of the New Zealand writers who left in 2025, is reported by The Spinoff as saying that features like podcasts, live video, Notes and comments can make writers feel reliant on the app, and that he worried about lock-in: the longer he stayed, the harder it might be to leave. A writer who has staked their growth on recommendations will find those don't follow them to a new platform. That isn't a trick, it's what a network is. But it's the reason "free to leave" and "easy to leave" aren't the same sentence.

Why do some people object to Substack's moderation?

This is the section where I'll stick to what's documented and leave the verdict to you, because reasonable people land in different places.

The sequence, from reporting and Substack's own statements. In November 2023, Jonathan M. Katz wrote an article for The Atlantic headlined "Substack Has a Nazi Problem"; as Platformer summarises it, the piece identified newsletters with overt Nazi symbols alongside others devoted to far-right extremism. In December, 247 Substack writers signed an open letter asking the company to clarify its policies. On 21 December co-founder Hamish McKenzie replied for the founders. TheWrap quotes him as writing "We don't like Nazis either". The core of his position was that censorship, including demonetising publications, doesn't make the problem go away. The founders' stated position was that open discourse works better than banning. Platformer wrote that the statement seemed to be at odds with Substack's own published content guidelines.

On 8 January 2024, after Casey Newton's Platformer flagged six publications, Substack's founders said five of the six violated existing content guidelines, and the company removed them. It said it had not changed its policy and would not proactively remove neo-Nazi or far-right extremist content, per Platformer's account of the statement. Three days later Platformer announced it was leaving for Ghost, having grown from 24,000 to more than 170,000 free subscribers on Substack, according to TheWrap. Not everyone accepts how Platformer framed it: Jesse Singal published a rebuttal whose headline calls Platformer's reporting on the subject "shoddy and misleading".

The next flashpoint was in late July 2025, when Substack sent a push alert promoting a newsletter that described itself as National Socialist. Substack told Gizmodo that it had "discovered an error that caused some people to receive push notifications they should never have received." The number of recipients wasn't disclosed. That incident matters to the app-and-recommendations debate in the previous section, because it's an automated system promoting content, which is a different thing from merely hosting it.

For the current rule text, Substack's Content Guidelines (last updated 29 September 2026) say the platform can't be used to publish content or fund initiatives that "incite violence based on protected classes", list credible threats of physical harm, and state that Substack has "the exclusive right to interpret and enforce these guidelines." Whether that line is too permissive, too strict or about right depends on your values. For a business owner the practical takeaway is narrower: your publication sits on a platform whose policies you can't change, and some writers decided they didn't want their revenue share to support that arrangement.

What do readers dislike?

Reader-side complaints are the easiest to verify, because Substack documents the settings.

When you subscribe to any publication, Substack creates an account for you automatically using the email you entered. Then, according to its page on stopping Substack emails, you may get occasional marketing mail about new features, reading suggestions, and activity digests about replies and mentions, with push toggles beside each. Creators' recommendations also feed a digest email to their subscribers. Every one of these can be switched off, but an account and marketing mail you never asked for is the part I'd expect readers to mind most, though I found no survey data on it.

On the paywall side, Substack has leaned into conversion tools. Its freewall asks readers to subscribe for free before reading the rest of a post, and metering gives free subscribers a set number of paid posts a month (the default is 3, adjustable from 1 to 50). Those are writer-controlled options, so the real nuisance is writers using them aggressively, not a platform rule. Email clipping can look like a Substack fault but is mostly Gmail's behaviour: Substack's editor warning explains that Gmail clips messages above about 102KB, which hits long image-heavy posts on any email platform.

What does Substack do well, and which complaints are overblown?

A short list, because a fair critique includes this part.

Starting costs nothing and needs no setup. Discovery tools exist that a self-hosted blog simply doesn't have, and writers who credit them aren't imagining it, even if the percentages are Substack's own. The export is a documented feature rather than a support ticket, RSS is complete enough to read from, and the post editor now handles code and equations. Substack's help pages are updated constantly (the cost page I quoted was edited the morning I wrote this), which is a decent sign the product is alive and maintained.

The overblown ones, in my reading: "Substack locks your list" (it doesn't, the CSV export is documented), "you can't write about code" (you can), and "10% is a scam" (it's a trade for hosting, payments plumbing and discovery that some writers value and others don't). The complaints that I'd weigh most are the ones with no workaround inside the product: no write API or webhooks that I could find documented, a fixed sender address, no custom CSS or HTML, and a network whose benefits stay behind when you leave.

What do people move to instead?

If you want out, six options come up most often. I've kept this short on purpose, since other articles on this publication compare alternatives in depth. Prices are the ones each vendor's page showed on 2026-11-19.

  • Ghost. Open source under the MIT licence, self-hostable or managed. Publisher is listed at $29 a month billed yearly for 1,000 members with paid subscriptions and 0% transaction fee; the Starter plan's comparison table says no paid subscriptions. Weakness: I only read the prices at 1,000 members (the page has a member slider that I left alone), so price your own list size, and self-hosting means you run it.
  • beehiiv. Free plan for up to 2,500 subscribers, with API access listed (excluding the Send API) but no paid subscriptions; Lite is $49 a month on yearly billing at the 1,000-subscriber price point and adds paid subscriptions. The page lists webhooks as a paid-plan feature. Takes 0% of paid revenue per its FAQ. Weakness: cost scales with list size.
  • Kit. A free plan up to 10,000 subscribers that includes selling digital products and subscriptions. Weakness: the page lists a 3.5% + 30 cent transaction fee on sales (it says that includes card processing), so compare that against Substack's 10% plus Stripe on your own prices.
  • Buttondown. Free for the first 100 subscribers, custom-domain sending in the base plan, and paid subscriptions as a $9 a month add-on. Weakness: add-ons stack, and archives on a custom domain are a separate $29 a month add-on.
  • WordPress. Software under the GPLv2 or later, so you pick the host and plugins. Weakness: on self-hosted WordPress, newsletters mean a plugin or separate service, and updates, backups and security are your job.
  • VeloCMS. My own project, a young hosted CMS covering blog, newsletter and memberships. Pricing lists Pro at $9 a month, Business at $29 and Agency at $69, with a 0% platform fee on Stripe sales and a custom domain on every plan. There's no free plan: every plan starts with a 14-day trial, a card is required unless you have a cardless trial code, and the first charge comes on day 15. The REST API is available from Pro with Bearer keys and HMAC-signed webhooks, but its members endpoint is read-only with masked emails. Custom sender domains are listed from Business up. Weaknesses: small community, an ecosystem nowhere near WordPress's, no built-in reader network like Substack's, and it's sold as a hosted service, so if self-hosting is a hard requirement pick Ghost or WordPress.

No option beats Substack on discovery and zero setup, and none of them hands you an audience. What they buy you is control over the pieces I flagged above.

Which complaint should change your decision?

If you're a writer with a small list and no plans to build around the site, probably none of them. Stay, enjoy the network, and revisit when the 10% starts to feel big.

If you need to write to your publication from code, send from your own domain, run your own markup, or keep a clean exit path, the structural complaints are the ones that matter, and the checklist from the sections above is short: confirm what the export gives you, know how Stripe moves, and decide whether the network benefits are worth the portability you give up. If moderation policy is the deciding factor, no technical comparison will settle it for you.

FAQ

Does Substack take a cut of paid subscriptions?

Yes. The cost page says Substack keeps 10% of subscription revenue when you turn paid subscriptions on, and Stripe charges its own processing fees separately. Publishing on a free list costs nothing.

Does Substack have an API or webhooks?

I found no documented publishing API or webhooks. The API terms describe access to public creator and publication data, and the MCP server is read-only and limited to Bestseller publications. The Terms also point to a technical-documentation article for API keys that I couldn't open, so treat "no publishing API" as unconfirmed rather than proven. Searching the help centre for "webhook" returned nothing on the day I checked.

Can I take my subscribers if I leave?

You can export the list as a CSV, though without subscriber names, per the export help article. Moving paid subscribers depends on the destination, so don't use Substack's "Disconnect Stripe" button until you've read that platform's migration guide.

Can I send newsletters from my own email address on Substack?

Not as far as the help centre says. You can change the sender name but not the sender address, which is always a substack.com address built from your subdomain.

Is Substack bad for SEO?

I can't give you a ranking verdict. What I can verify is that you can edit post slugs and connect GA4, while sitemaps and Google Search Console verification are described as features that unlock as a publication grows.

Sources

Everything below was read on 2026-11-19, except where the text says otherwise.

About the author

  • Building VeloCMS.org , A fast multilingual CMS for blogs and online stores. I write about headless CMS, Next.js, SEO and moving off WordPress and Shopify.

No comments yet. Be the first to comment.