Why Every Newsletter Writer Should Draft in Markdown

You write your newsletter in Google Docs. Or Notion. Or Apple Notes. You get the draft where you want it. Then you copy it into Substack. Headings lose their levels. Bold disappears. Links break. You spend twenty minutes reformatting something that was already formatted.

Next week you decide to move from Substack to Ghost. Now you have 50 posts trapped in Substack's editor. Exporting them produces messy HTML. You spend an entire weekend cleaning up formatting that should have been clean from the start.

This problem has a name: format lock-in. And it has a solution that has existed since 2004.

Markdown.

What Markdown Actually Is

Markdown is a plain text format with simple syntax for formatting. A "#" becomes a heading. Two asterisks become bold. A bracket-parenthesis pair becomes a link. That is the entire concept.

The file itself is just text. You can open it in any text editor on any operating system. It will still be readable in fifty years. Try saying that about a Google Doc or a Notion page.

But the real power of Markdown is not the syntax. It is what happens when you need to move your writing somewhere else. Markdown converts cleanly to HTML, PDF, Word, LaTeX, and every other format that matters. One source file, infinite outputs. Write once, publish anywhere.

Newsletter writers face a unique problem. You are not just writing a document that lives in one place. You are writing content that needs to travel. It goes from your drafting tool to your publishing platform. It might also go to your blog. Or to a client review. Or to social media as a thread.

Every time your content moves between tools, you lose something. Formatting breaks. Styles shift. Links vanish. The more proprietary your source format, the worse the damage.

Markdown eliminates this entirely. Here is why it matters for each part of your newsletter workflow.

1. Portability: One File, Every Platform

The same Markdown file works with Ghost, WordPress, Hugo, Jekyll, Astro, and any other publishing platform built in the last decade. Most of them accept Markdown natively. The ones that do not (like Substack and Beehiiv) accept HTML, and Markdown converts to clean HTML in one step.

This means you are never locked in. If Ghost doubles its pricing, you move to WordPress. If Substack changes its terms, you switch to Beehiiv. Your content comes with you, perfectly formatted, every time. No weekend-long migration projects. No hiring a freelancer to reformat 200 posts.

Compare this to writing in Google Docs. Copying from Google Docs into Substack produces invisible styling artifacts. Heading levels get wrong. Line spacing shifts. Bullet points nest incorrectly. You fix it manually, post by post, week after week.

Compare this to writing in Notion. Notion's export produces Markdown, technically. But it adds Notion-specific syntax, breaks images, and handles tables inconsistently. The "Markdown" you get from Notion often needs cleanup before it is usable anywhere else.

Writing in Markdown from the start means your content is clean from the start. No cleanup. No reformatting. No platform-specific quirks to work around.

2. AI-Native: LLMs Think in Markdown

This is the reason that did not exist five years ago and now matters more than anything else.

Large language models - GPT-4, Claude, Gemini, all of them - read and write Markdown natively. When you paste a Google Doc into ChatGPT, the AI receives stripped text with no formatting information. It cannot see your headings, your bold text, your structure. When it writes back, it outputs Markdown that you then have to manually reformat into your document.

When your draft is already in Markdown, the AI sees exactly what you see. Headings, emphasis, links, lists - all preserved. When the AI edits your text, the result is Markdown that slots directly back into your document with no conversion step.

This is not a minor convenience. For newsletter writers using AI to edit, brainstorm, or rewrite sections, the format match between your draft and your AI tools eliminates an entire category of friction. No lossy round-trips. No reformatting. The AI and your editor speak the same language.

For a deeper look at why Markdown and AI are such a natural fit, see why Markdown is AI-native.

3. Version Control: Track Every Change

Markdown files are plain text. Plain text works with Git. Git tracks every change you have ever made to a file, who made it, and when.

For solo newsletter writers, this means you never lose a draft. You can see exactly what your post looked like three revisions ago. You can recover a paragraph you deleted last Tuesday. You can compare this week's draft to last week's and see precisely what changed.

For teams, Git is even more powerful. Multiple people can edit the same document. Changes merge automatically when they do not conflict. When they do conflict, Git shows you exactly where the disagreement is so you can resolve it. No more "Final_v3_REAL_FINAL.doc" files. No more emailing attachments back and forth.

Google Docs has version history, sure. But try exporting a Google Doc's full revision history. You cannot. It is locked inside Google's ecosystem. Markdown files in Git give you complete ownership of your revision history, forever.

4. Future-Proof: Readable Forever

Proprietary formats die. Microsoft Word 97 files are painful to open today. Google could shut down Docs tomorrow (they have shut down plenty of products ). Notion could change its export format. Substack could fold.

A Markdown file written in 2004 opens perfectly today. A Markdown file written today will open perfectly in 2050. It is plain text. Any computer with a text editor can read it. No software required. No account required. No internet required.

For newsletter writers building an archive of work, this matters. Your posts are your portfolio. They represent years of thinking and writing. Store them in a format that does not depend on any company staying in business.

5. Speed: Just Type

Making text bold in Google Docs: select text, move mouse to toolbar, click B. Or memorize Ctrl+B.

Making text bold in Markdown: type ** before and after the word. Your hands never leave the keyboard.

This sounds trivial. It is not. Newsletter writers produce content on a schedule. Weekly, sometimes daily. Every small friction point compounds. Reaching for the mouse to click a formatting button breaks your flow. Keyboard-native formatting does not.

Heading levels, links, blockquotes, lists - all typeable inline without touching a toolbar. Once you internalize the syntax (which takes about a day), you write faster because formatting happens as part of typing instead of as an interruption to it.

The Objection: "Markdown Is Ugly"

The most common objection to Markdown is that it looks like code. Hashtags for headings. Asterisks for bold. Brackets for links. Writers are not programmers. They do not want to look at syntax while they write.

Fair. And completely solved.

Modern WYSIWYG editors render Markdown as formatted text in real time. You type a "#" and it becomes a heading. You wrap a word in asterisks and it becomes bold immediately. You never see the raw syntax unless you want to.

The experience is identical to writing in Google Docs or Notion. The difference is under the hood. Your file is Markdown, not a proprietary format. So you get all the portability, AI-compatibility, and version control benefits without giving up visual formatting.

Athens is built this way. You write in a clean, visual editor. The underlying format is Markdown. When you need to export, copy, or move your content, it travels cleanly because the source is a universal format, not a proprietary blob.

For a detailed comparison of the Markdown writing experience versus Google Docs, see Markdown vs. Google Docs for writers.

Here is how Markdown works with each major newsletter platform. The workflow is slightly different for each, but the core idea is the same: write in Markdown, publish anywhere.

Ghost: Native Markdown Support

Ghost speaks Markdown natively. Its editor accepts Markdown input. You can paste Markdown directly into the Ghost editor and it renders correctly. Headings, bold, italic, links, images, code blocks - all preserved.

The workflow is simple. Write your newsletter in a Markdown editor. Copy. Paste into Ghost. Publish. No conversion. No reformatting. No cleanup.

Ghost also supports importing Markdown files directly. If you keep your newsletter archive as Markdown files (which you should), you can import your entire backlog in minutes.

Substack: Convert to HTML, Then Paste

Substack does not support Markdown natively. Its editor expects rich text or HTML. This is one of Substack's biggest frustrations for writers coming from Markdown workflows.

The solution: convert your Markdown to HTML, then paste the HTML into Substack's editor. Athens handles this automatically. Export as HTML and Substack receives clean, properly formatted content. Headings, links, bold, lists - all intact.

The alternative - copying from Google Docs into Substack - introduces invisible styling that causes unpredictable formatting issues. HTML converted from Markdown is clean. No hidden styles. No mysterious spacing. What you see is what your readers get.

For more on the Substack formatting problem and how to solve it, see the best writing apps for Substack.

WordPress: Markdown Blocks or Paste HTML

WordPress supports Markdown in multiple ways. The block editor has a native Markdown block. Paste your Markdown in and it converts to formatted blocks automatically. Plugins like WP-Markdown and Jetpack add broader Markdown support across the editor.

You can also paste HTML converted from Markdown, just like with Substack. WordPress handles clean HTML well. The result is properly formatted posts without manual adjustment.

For writers running a self-hosted WordPress newsletter, Markdown is especially powerful. You can automate publishing with scripts that convert Markdown files to WordPress posts via the REST API. Your entire publishing workflow can be file-based.

Beehiiv: HTML Paste

Beehiiv, like Substack, does not support raw Markdown. But it handles pasted HTML well. Convert your Markdown to HTML, paste it into the Beehiiv editor, and your formatting comes through clean. Same workflow as Substack.

The pattern is consistent across platforms. Even when a platform does not support Markdown directly, Markdown converts to clean HTML that every platform understands. The source format is universal even when the destination is not.

Here is what the actual workflow looks like when you draft in Markdown.

Draft in a Markdown WYSIWYG editor. You see formatted text. The file underneath is Markdown.
Edit with AI. Because your draft is Markdown, AI tools can read and edit it without losing formatting. Edits apply inline, directly in your document.
Export to your platform. Ghost gets Markdown directly. Substack, Beehiiv, and WordPress get HTML. One click, clean output.
Archive the Markdown file. Save it in a folder. Commit it to Git. Back it up however you like. It is a plain text file. It will outlast every platform you publish on.

Compare this to the Google Docs workflow: draft in Docs, copy into your platform, fix broken formatting, publish, then realize you have no clean archive because the definitive version is split between Docs and Substack.

Or the Notion workflow: draft in Notion, export (get messy Markdown with Notion quirks), clean up the export, paste into your platform, fix formatting again. Two cleanup steps instead of zero.

What You Lose by Not Using Markdown

Let me be specific about the costs of drafting in proprietary formats.

Time. Ten to twenty minutes per post fixing formatting after pasting into your newsletter platform. Over a year of weekly publishing, that is eight to seventeen hours spent reformatting.
Portability. When you want to switch platforms, you are facing a manual migration. Every post needs to be reformatted individually.
AI effectiveness. AI tools lose your formatting when you paste from proprietary editors. They give back Markdown that you have to manually convert. Every AI interaction has a tax.
Archive quality. Your definitive copy is stuck in someone else's server. If that service changes, shuts down, or breaks, your archive degrades.
Repurposing. Turning a newsletter into a blog post, a book chapter, or a social thread means reformatting again. Markdown converts to anything. Google Docs converts to a mess.

Getting Started

You do not need to change your entire workflow at once. Start with your next newsletter.

Pick a Markdown WYSIWYG editor. Athens gives you visual editing with Markdown underneath, plus AI editing that works natively with the format. Write your draft. Export it to your platform. Notice how much cleaner the formatting comes through.

Then do it again the next week. Within a month, you will have a clean archive of Markdown files. You will have cut the formatting tax from your workflow entirely. And when you inevitably switch platforms or add a blog or repurpose your content, your files will be ready.

Markdown is not exciting. It is not flashy. It is a forty-year-old idea (plain text with minimal syntax) applied to a twenty-year-old format. But it is the most practical decision a newsletter writer can make. Write in the format that works everywhere, and everywhere will work for you.

For more on why Markdown and AI are a natural fit, read why Markdown is AI-native. For a broader comparison of drafting tools, see Markdown vs. Google Docs for writers.