Every “Substack alternatives” article recommends the same thing: Ghost, Beehiiv, ConvertKit, Buttondown. Sometimes WordPress. Sometimes Medium, which is hilarious if you left Medium for Substack three years ago.

They’re all fine. They’re also all the same shape. You sign up, you get a dashboard, you write inside their editor, your content lives in their database. If you leave, you export a zip file and hope the formatting survives.

That’s not an alternative. That’s a lateral move.

#Why People Actually Leave Substack

The reasons I hear aren’t usually about price. Substack takes 10% of paid subscriptions, which stings, but that’s not what pushes people out.

It’s the creeping realization that your writing doesn’t live where you think it does.

Your posts are in Substack’s database. Your subscriber list is accessible through an export, but the relationship runs through Substack’s infrastructure. Your URLs are either on a Substack subdomain (which you’ll lose if you leave) or a custom domain (which requires careful DNS work to migrate). Your formatting is whatever Substack’s editor produces — not a format you chose.

The export is a zip of HTML and CSV files — and it leaves your images behind, still hosted on Substack’s servers. It’s better than nothing. But if you’ve published 200 posts, converting that export into something another platform can import cleanly is a weekend project you’ll never finish.

#The Question Behind the Question

When someone searches “Substack alternative,” they usually mean one of two things:

“I want a better version of Substack.” More features, lower fees, better design tools, bigger network. Ghost, Beehiiv, and Buttondown are good answers here. They’re real platforms with real advantages over Substack.

“I want to stop renting.” I want my writing in a format I control, on a domain I own, in files I can open ten years from now without depending on any company still being around.

If you’re in the second camp, the standard alternatives don’t solve your problem. They just change your landlord.

#What Owning Your Blog Actually Looks Like

Imagine your blog is a folder on your computer. Inside it are markdown files — one per post. The filename is the URL. The first heading is the title. A line of frontmatter at the top handles the meta description.

my-blog/
  posts/
    substack-alternative-for-writers.md
    why-i-write-in-public.md
    drafts/
      half-finished-idea.draft.md

You write in whatever text editor you like. You save. The post is live.

You want to edit? Open the file, change it, save. You want to unpublish? Move the file to the drafts folder. You want to back up your entire blog? Copy the folder. You want to switch platforms? The files are markdown. Everything reads markdown.

There’s no database to export. No formatting to convert. No account to close. The blog is the folder.

#How This Works in Practice

FolderPress does exactly this. You connect a Dropbox folder, and every markdown file in it becomes a post on your site, on your custom domain.

The workflow is:

1. Write a markdown file in any editor — Obsidian, iA Writer, VS Code, whatever you already use.
2. Save it to your Dropbox blog folder.
3. It’s published.

No CMS login. No paste-into-editor step. No “configure the SEO fields” screen. The file metadata handles it.

Drafts stay in a drafts subfolder. They don’t publish until you move them out. The entire publishing model is file operations — create, rename, move, delete. Things every operating system has understood since the 1970s.

#What You Give Up

This isn’t a trick. There are real tradeoffs.

No built-in newsletter. Substack’s biggest advantage is the newsletter integration — write a post, it emails your list. FolderPress doesn’t do that. If you need email, you’d pair it with Buttondown, MailerLite, or any email service that can send to a list. Your blog handles the web side. Your newsletter tool handles the email side. They’re separate concerns — which is arguably how it should be, but it’s more setup than Substack’s one-click publish-and-email.

No network effects. Substack has a recommendation engine, a social feed, a discovery layer. A file-based blog has none of that. Your traffic comes from search, social, and word of mouth. You’re trading distribution for independence. That’s a real cost for new writers still building an audience.

No visual editor. You’re writing markdown. If you’ve never used markdown, there’s a learning curve. It’s not steep — headers, links, bold, lists cover 90% of blogging — but it’s there. Substack’s rich text editor is genuinely easier for people who just want to type and format visually.

No comments section. If reader discussion matters to you, you’d embed a third-party solution or link to a discussion thread elsewhere.

#What You Get

Actual file ownership. Not “you can export your data” ownership. Your blog is already files on your filesystem. There’s nothing to export because there’s nothing locked in.

Editor freedom. Write in the app that makes you write more. Obsidian if you like backlinks. iA Writer if you like focus mode. VS Code if you’re a developer. Typora if you want live preview. Vim if you’re that person. The editor is your choice because the format is open.

Portability that isn’t theoretical. Every static site generator, every markdown-based platform, every CMS with a markdown importer can read your posts. If FolderPress shuts down, you lose nothing. Your files haven’t moved. You just point a different tool at the same folder.

Dropbox as version control. Every save creates a version in Dropbox’s history. You can roll back any post to any previous state. No Git required. No “undo” anxiety. Just save and write.

Speed. The time between finishing a post and it being live on your site is measured in seconds. There’s no deploy, no build, no queue. Dropbox syncs, FolderPress reads, the post is up.

#Who This Is Actually For

I’ll be specific, because this isn’t for everyone.

This works well if you’re a writer who already thinks in terms of files and folders. If you organize your notes in Obsidian or Bear or a plain folder structure. If you already know markdown or are willing to learn it. If you have Dropbox or are willing to use it. If you want a personal blog or professional blog and don’t need a membership platform.

This doesn’t work if you need built-in paid subscriptions. If your primary goal is email newsletter growth. If you want your platform to handle discovery and recommendations. If you’re running a media business with multiple contributors and editorial workflow. Substack, Ghost, or Beehiiv are better tools for those problems.

The honest answer to “what’s the best Substack alternative” depends entirely on what you actually wanted from Substack. If you wanted the platform features but cheaper or better — switch to Ghost. If you wanted your writing to exist as durable, portable, yours-forever files that happen to also be a blog — that’s a different category entirely.

#The File Is the Exit Strategy

The deepest problem with platform-hopping is that every migration loses something. Formatting breaks. URLs change. SEO rankings evaporate. Images need re-uploading. It’s friction that compounds every time you move.

Writing in markdown files on your own filesystem means the migration already happened. You already left. Your writing lives in the most portable format that exists, in a location you control, backed up by a sync service with version history.

The next time a platform changes its terms, raises its prices, or makes a decision you disagree with — you don’t need an exit strategy.

You never needed one. The files were always yours.