Athens

Why Substack's Editor Isn't Enough for Serious Writers

- Moritz Wallawitsch

Substack is the best place to publish a newsletter. It is not the best place to write one.

If you use Substack, you already know this. You open the editor. You type a few paragraphs. You want to paste in some markdown notes. It shows up as plain text. You want AI to help you rewrite a clunky paragraph. There is no AI. You want to check what your draft looked like yesterday. There is no version history. You lose your internet connection. You lose your draft.

Substack built one of the best distribution platforms for independent writers. Recommendations, Notes, network effects, paid subscriptions, podcast hosting. The publishing side is excellent. The writing side is not.

This is not a complaint. It is a design choice. Substack is a publishing platform, not a writing tool. The problem is that most writers treat it as both. They draft, edit, and publish inside the same editor. That editor was not built for drafting or editing. It was built for publishing.

The solution is simple: separate your writing tool from your publishing platform. Write somewhere better. Publish on Substack. Best of both worlds.

What Substack's Editor Actually Lacks

Substack's editor is a basic rich-text editor. It handles headings, bold, italic, links, images, blockquotes, and embeds. For a quick update to your subscribers, it is fine. For serious writing, it falls short in seven specific ways.

1. No Markdown Support

Substack does not understand markdown. If you paste markdown into the editor, you get literal asterisks, hash symbols, and dashes. No conversion. No rendering. Just plain text with punctuation where formatting should be.

This matters because every major AI tool outputs markdown. ChatGPT, Claude, Gemini - they all format their responses in markdown. If you use AI to help draft or research your newsletter, you have to manually reformat everything before publishing. We wrote a full guide on the ChatGPT-to-Substack formatting problem because so many writers hit this wall.

It also matters if you write in any markdown-based tool. Obsidian, iA Writer, Notion exports, GitHub readmes - none of them paste cleanly into Substack. You are always reformatting.

2. No AI Editing

Substack has no built-in AI features. No grammar suggestions. No rewriting. No tone adjustments. No "make this paragraph shorter." No "simplify this sentence." Nothing.

This means if you want AI help, you have to leave Substack. Open ChatGPT in another tab. Copy your paragraph. Paste it into the chat. Describe what you want. Copy the response. Paste it back into Substack. Hope the formatting survived. Repeat for every section.

This is the copy-paste workflow that wastes hours every week. It is slow, lossy, and error-prone. You lose formatting on every round trip. You lose context when ChatGPT forgets what your article is about. You cannot see what the AI actually changed without reading both versions side by side.

3. No Version History

Substack saves your draft automatically. But there is no way to see previous versions. No way to compare what you wrote yesterday with what you have today. No way to revert a paragraph you deleted an hour ago.

For a short post, this is fine. For a 3,000-word essay you have been working on for a week, it is a problem. You cut a section on Tuesday because it felt tangential. On Thursday you realize it was the best part. Too late. It is gone.

Google Docs has version history. Notion has version history. Even basic text editors like VS Code have timeline views. Substack has nothing. Your draft is whatever it is right now.

4. No Offline Mode

Substack requires an internet connection to write. If you lose connectivity - on a plane, on a train, in a coffee shop with unreliable wifi - you lose access to your draft. You cannot open it. You cannot edit it. You cannot save it locally.

This is a real problem for writers who travel or who work outside of reliable internet zones. It is also a problem when Substack itself has outages, which happens more often than you would expect for a platform that hosts professional writers.

5. Limited Formatting

Substack covers the basics: headings, bold, italic, links, images, blockquotes, horizontal rules, and embedded content (tweets, YouTube videos, Spotify). For most newsletter posts, that is enough.

But if you need more, you are stuck. No footnotes. No syntax highlighting for code blocks. No tables beyond the most basic grid. No custom callout boxes. No mathematical notation. No collapsible sections. No anchor links within a post.

Technical writers, academics, and long-form essayists regularly need these features. Substack does not offer them and has no plugin system to add them.

6. No Collaboration

Substack has no way to share a draft with a co-author or editor for review. No commenting. No suggesting mode. No tracked changes. If you want someone to review your draft before you publish, you have to copy the text into Google Docs, get feedback there, and then manually apply the edits back in Substack.

This is fine for solo writers who publish without review. It is not fine for writers who work with editors, co-authors, or even just a friend who reads their drafts before they go live.

7. No Import from Google Docs

Many writers draft in Google Docs and want to move the finished piece into Substack. There is no direct import. You copy-paste, and most of the formatting breaks. Headings lose their levels. Tables disappear. Footnotes vanish. Embedded images need to be re-uploaded.

Substack does support importing from a WordPress site or a Mailchimp archive. But importing a single Google Doc with formatting preserved? Not supported. You are left with manual reformatting or third-party conversion tools.

What Substack Gets Right

None of the above means Substack is a bad product. It means Substack is a publishing platform, not a writing tool. And as a publishing platform, it is excellent.

  • Distribution. Substack's recommendation engine puts your work in front of readers who follow similar writers. Notes gives you a social feed to share ideas and attract subscribers. Network effects compound over time.
  • Email delivery. Substack handles email infrastructure. Deliverability rates are high. You do not need to think about SPF records, DKIM, or spam filters.
  • Paid subscriptions. Substack takes 10% of paid subscriptions. In return, you get a full payment infrastructure with Stripe integration, subscriber management, and analytics.
  • Podcast hosting. You can host audio content directly on Substack. It distributes to Apple Podcasts, Spotify, and other platforms automatically.
  • Community. Chat, threads, and discussion sections let you build a community around your writing without a separate Discord or Slack.
  • Simplicity. Substack is intentionally simple. You sign up, you write, you hit publish. There is no theme to configure, no plugin to install, no server to manage. For writers who want zero technical overhead, this is a feature.

These are real strengths. They are why Substack dominates the independent newsletter space. They are also completely separate from the act of writing. Substack is where your writing goes after you write it. It is not where the writing happens.

Why Serious Writers Already Write Elsewhere

If you look at how professional newsletter writers actually work, most of them do not draft inside Substack. They write in Google Docs, Notion, Obsidian, Bear, iA Writer, Ulysses, or a plain text editor. They paste the finished piece into Substack when it is ready to publish.

This is the right instinct. Substack is the distribution layer. The writing tool is something else. The question is which something else.

The most common choice is Google Docs. It has version history, commenting, real-time collaboration, and it works offline with the Chrome extension. But Google Docs has its own problems for newsletter writers. It does not support markdown. Its AI features (Gemini) are shallow - they generate text but do not edit your existing text inline. And pasting from Google Docs into Substack still breaks formatting in unpredictable ways.

Notion is another popular choice. It supports markdown. It has a clean writing interface. But it also has no AI editing (Notion AI generates, it does not edit inline), no version history for individual pages, and exporting to Substack requires going through markdown or HTML first.

Obsidian works well for writers who think in plaintext. It is fast, offline-first, and markdown-native. But it has no built-in AI editing, no collaboration features, and moving content to Substack means converting markdown to rich text manually.

The pattern is clear. Every popular writing tool solves some of Substack's editor gaps but creates new ones. None of them were designed for the specific workflow of "write with AI help, then publish on a newsletter platform."

What the Right Writing Tool Looks Like

If you accept that you should write somewhere else and publish on Substack, the question becomes: what should that somewhere else look like?

Here is the checklist, based on the specific gaps Substack leaves.

  • Markdown support. Write in markdown. See it rendered in real time. Export it as clean HTML that Substack accepts without reformatting.
  • AI editing built in. Select a paragraph. Ask the AI to tighten it, clarify it, or change the tone. See the changes as an inline diff. Accept or reject each one. No copy-pasting to a separate chat window.
  • Version history. See every previous state of your document. Compare versions side by side. Revert to an earlier draft with one click.
  • Offline support. Write without an internet connection. Sync when you are back online.
  • Rich formatting. Footnotes, code blocks with syntax highlighting, tables, callouts. Everything a serious writer might need beyond the basics.
  • Clean export. One-click export to HTML or rich text that pastes into Substack, Ghost, WordPress, or any other publishing platform with formatting intact.

How Athens Fills the Gap

Athens is a writing tool built for exactly this workflow. You write and edit in Athens. You publish on Substack (or Ghost, or WordPress, or wherever your audience lives).

Here is what that looks like in practice.

Writing. Athens is a markdown WYSIWYG editor. You type in markdown and see it rendered in real time. Headings, lists, bold, italic, links, code blocks, footnotes - they all render as you type. No switching between "edit mode" and "preview mode." What you see is what your readers will see.

AI editing. Select any text and ask the AI to edit it. Athens shows you exactly what changed as an inline diff - green for additions, red for deletions. You accept or reject each change individually. The AI edits your document directly. No copying. No pasting. No separate chat window. Your voice stays in the text because you wrote the draft and the AI only touches what you ask it to touch.

Version history. Athens tracks every version of your document. You can scroll through the timeline, compare any two versions, and restore an earlier state. That paragraph you deleted on Tuesday? It is still in the history on Thursday.

Export to Substack. When your post is ready, export it as HTML. Paste it into Substack's editor. The formatting comes through clean. Headings are headings. Lists are lists. Bold is bold. No manual reformatting. No pandoc. No Google Docs intermediary.

The Workflow: Athens + Substack

Here is the step-by-step workflow that serious Substack writers use.

  1. Research and outline. Gather your sources. Write a rough outline in Athens. Use markdown headings to structure your argument.
  2. Draft. Write the first draft. Do not edit as you go. Get the ideas down. Athens saves everything automatically, so you will never lose work.
  3. Edit with AI. Go section by section. Select a paragraph. Ask the AI to make it clearer, shorter, or more direct. Review the diff. Accept what works. Reject what does not. Move to the next paragraph.
  4. Review and polish. Read the full piece from top to bottom. Use version history to compare your final draft with your first draft. Make sure the core argument survived the editing.
  5. Publish. Export from Athens as HTML. Open Substack. Paste. Add your featured image and subtitle. Hit publish.

Total time spent on formatting and reformatting: zero. Total time spent copying text between windows: zero. All of your time goes into the writing itself.

But I Like Substack's Simplicity

Fair point. One of Substack's strengths is that it is simple. Open the editor, write, publish. No plugins. No settings. No complexity.

If you write short updates (under 500 words), if you do not use AI tools, and if you never need to revert to a previous draft, Substack's editor is fine. It does what it needs to do.

But most Substack writers who are reading a blog post titled "Why Substack's Editor Isn't Enough" are not writing short updates. They are writing 2,000-word essays. They are spending hours on each post. They want AI to help them edit. They have lost a paragraph and wished they could get it back. They have fought with formatting after pasting from another tool.

For those writers, adding one tool to the workflow - a proper writing editor - saves more time than it adds. The workflow is still simple: write in Athens, publish on Substack. Two tools instead of one. But the second tool is doing the hard work (distribution) while the first one handles the actual writing.

Substack is Great. Its Editor is Not.

Substack changed independent publishing. It gave writers a direct path to their readers, a way to get paid, and a network that grows with them. That is genuinely valuable.

Its editor is a means of entry, not a writing tool. It is the form you fill out before you publish, not the place where the writing gets done. Treating it as your primary writing environment means accepting limitations that no serious writing tool would impose: no AI, no markdown, no version history, no offline access.

You do not have to accept those limitations. Write in a tool built for writing. Publish on a platform built for publishing. Try Athens for the writing part. Keep Substack for the publishing part. Your writing will be better for it.

For more on the best tools to pair with Substack, see our guide on the best writing apps for Substack. And if you want to understand why AI editing tools are replacing the copy-paste workflow, read the copy-paste era of AI writing is over.