How to Save a Substack Post as Markdown (Paywall-Aware, No Cross-Promo)

Substack doesn’t want you to leave with the content. There’s no native export, no “download this post” button, no public API for paid subscribers to back up the essays they’ve paid for. Every post you open is wrapped in subscribe-modal overlays, cross-promotion blocks from other newsletters in the network, and a footer that begs for an email address. If you’ve ever tried to drop a Substack essay into Claude or Obsidian, you know the problem --- copying from the page drags the noise along with it.

This guide covers every method to convert a Substack post to clean Markdown --- from a single essay to a paywalled long-read with embedded audio.

Why Save Substack Posts as Markdown?

Markdown is the format that works wherever a newsletter needs to go:

• Archive your favorite essays --- writers leave Substack, posts get hidden behind paywalls, accounts get suspended. Your notes shouldn’t depend on a platform’s uptime
• Build a research library --- one folder of clean .md files is searchable in seconds across hundreds of newsletters
• Feed it to an LLM --- Claude, ChatGPT, Gemini, and local models all read Markdown natively as context
• Escape platform lock-in --- a paid subscription buys you access, not ownership. Markdown gives you the copy you already paid for
• Quote a specific passage --- finding “that paragraph about compounding” in a 5,000-word essay is one search away
• Translate a foreign-language post --- once it’s text, any translation tool works on it

The use case driving most Substack-to-Markdown traffic in 2026 is the first two: people want a permanent, portable copy of the essays they care about, decoupled from the platform.

Method 1: Minibase (Fastest, One Click)

Minibase is a Chrome extension that turns any Substack post into a Markdown file with one click. It reads the post body directly from the DOM, strips every subscribe-modal and cross-promo block, and produces something that reads like the original essay, not a scraped page.

How it works:

1. Open the Substack post in Chrome
2. Click the Minibase extension icon in your toolbar
3. A .md file downloads instantly (or lands in your Minibase Vault if connected)

What you get:

• Post title and subtitle as Markdown headings
• Author name, publish date, and newsletter name in frontmatter
• Full body with all headings, pull-quotes, and inline images preserved
• Block quotes kept as > Markdown quotes, not rendered as page styles
• Embedded podcast episodes as Markdown audio references with the original URL
• Footnotes inlined where they belong
• Frontmatter with title, author, newsletter, publish date, and canonical URL

What gets removed:

• Subscribe-modal overlays that pop up mid-scroll
• “From X’s Substack” cross-promotion blocks at the top and bottom of the post
• “Share this post” / “Pledge your support” / “Restack” call-to-action banners
• Footer signup forms and recommendation grids
• Substack nav chrome and the floating reading-progress bar

Best for: Researchers, writers, anyone with paid subscriptions they want to actually own, AI users feeding context to Claude or ChatGPT. If you need a clean essay that you’ll paste into an LLM or read in Obsidian, this is the cleanest path.

Example Output

Saving a Packy McCormick essay produces:

---
title: "The Substack Renaissance"
subtitle: "How creator-led media is rebuilding the internet from the bottom up"
author: Packy McCormick
newsletter: Not Boring
url: https://www.notboring.co/p/the-substack-renaissance
date: 2026-02-14
---

# The Substack Renaissance

## How creator-led media is rebuilding the internet from the bottom up

Five years ago, the idea that a single writer could sustain a six-figure
business from a newsletter sounded absurd. Today there are hundreds of
them, and the model is starting to eat traditional media from the edges.

> "The best journalism of the next decade won't come from newsrooms.
> It'll come from one person, a Substack, and a community of 20,000
> readers who actually care."

## Why Now

Three things converged...

That file is one paste away from being usable Claude context, one keystroke away from being a permanent Obsidian note.

Method 2: Email + Manual Reformat

Every Substack post is also delivered as an email. You can save the email and convert it to Markdown by hand.

Steps:

1. Open the post in your Gmail or Apple Mail
2. View source or “Show original”, copy the HTML
3. Run it through an HTML-to-Markdown converter (pandoc, turndown, html2md)
4. Strip the header banner, the footer signup form, and the cross-promo blocks manually

Problems with this approach:

• Substack emails are wrapped in heavy table-based HTML that converts to ugly Markdown
• The cross-promo blocks (“Subscribe to X who also writes on Substack”) are deeply nested and hard to strip with a single regex
• Embedded podcasts come through as inline audio players that don’t translate to Markdown
• Footnotes get duplicated between the body and the email footer
• Images are referenced by tracking URLs that expire
• Paywalled posts arrive as truncated previews in email, so the full essay isn’t even there

Workable for a single short post. Falls apart on anything long or on paid content.

Method 3: RSS Feed + Script

Every public Substack has an RSS feed at <newsletter>.substack.com/feed. You can poll it and convert each item to Markdown.

curl https://newsletter.substack.com/feed | \
  pandoc -f html -t markdown -o post.md

Best for: Engineering teams archiving newsletters at scale, or anyone building an automated reading pipeline. Requires a scripting environment and a cron job.

Problems with this approach:

• RSS only exposes free posts. Paywalled essays don’t appear in the feed
• The feed returns the email-formatted HTML, so you inherit all the cross-promo and signup-form noise
• No author metadata beyond the channel name --- guest posts get attributed to the newsletter, not the writer
• Embedded podcasts are stripped from the RSS payload
• Pull-quotes lose their styling and merge into the body text
• Cleanup pass (removing subscribe blocks, fixing image URLs) is a separate step

This is the right method if you’re building a pipeline for a public newsletter you have rights to. It’s overkill for one post, and it can’t reach the paid content most readers actually want to archive.

Method 4: Browser Minibase As (PDF) + OCR

Chrome’s “Save as PDF” works on any page, including paywalled Substack posts you’re logged into.

Steps:

1. Open the post in Chrome
2. Cmd+P, choose “Save as PDF”
3. Run the PDF through an OCR tool (Adobe Acrobat, Tesseract, or pdftotext)
4. Clean up the output into Markdown

Problems for the Markdown use case:

• Output is page-formatted, not document-formatted --- headings lose their hierarchy, paragraphs break across page boundaries
• Subscribe-modal overlays often render into the PDF, so the noise comes with you
• Pull-quotes, block quotes, and code samples all lose their structure
• Images are baked into the page as pixels, not referenced --- no way to recover the originals
• OCR introduces typos on serif-heavy newsletter typography
• Embedded podcasts and links don’t survive the PDF round-trip

Last-resort method when nothing else can reach the content. Not a primary workflow.

Which Method Should You Use?

Scenario	Best Method
Paste a Substack essay into Claude or ChatGPT	Minibase --- one click, structured output
Archive your paid subscriptions	Minibase --- works on paywalled posts you’re logged into
Build a personal newsletter research library	Minibase --- consistent frontmatter, easy to search
Auto-archive a free newsletter at scale	RSS + script --- programmatic, but free posts only
Email-only flow with manual triage	Email + reformat --- works if you only save 1-2 essays a week
Last-resort capture of an unreadable page	Save as PDF + OCR --- noisy but always works

For most people --- especially anyone with paid subscriptions or using Substack as research input --- Minibase is the answer. It produces the cleanest Markdown with zero setup, and it handles paywalled essays the same way it handles free posts: from whatever the logged-in browser can see.

Edge Cases Minibase Handles

• Paywalled posts. Minibase sees what your logged-in browser sees. If you’re a paid subscriber, you get the full essay. If you’re not, you get the public preview, exactly as it appears on the page. No cracking, no scraping --- just a clean copy of what you already have access to.
• Cross-promotional blocks. Substack injects “From X’s Substack” recommendation blocks at the top and bottom of most posts. Minibase strips them automatically. The exported Markdown only contains the essay itself, attributed to the actual author.
• Embedded podcast episodes. Substack posts increasingly include audio. Minibase captures the episode as a Markdown audio reference with the original URL, so you can re-listen or pipe it to a transcription tool later.
• Comment sections. Top-level comments are captured with the commenter name and date. Deep nested threads get summarized rather than dumped raw, so a 400-comment discussion doesn’t bloat the file.
• Threads (Substack’s Twitter-like feature). Saved as a chronological Markdown list with author and timestamp, the same shape as a Twitter thread export.
• Notes. Substack’s micro-posts work too. The Markdown is shorter but has the same frontmatter shape, so they sit alongside long-form posts in the same folder.
• Multiple newsletters from the same author. Each post gets its newsletter name in frontmatter, so a writer who publishes on three different Substacks ends up in three searchable buckets without manual tagging.
• Custom domains. Plenty of Substacks run on their own domain (stratechery.com, notboring.co, noahpinion.blog). Minibase detects the Substack-powered backend regardless of the URL and applies the same clean export.
• Posts with heavy images. Images stay referenced by their original URLs, with the alt text and captions preserved. The file stays small and portable.

Pair It With Your Workflow

The Markdown output works wherever you need it:

• Claude / ChatGPT / Gemini --- paste the file in, ask follow-up questions about the essay
• Obsidian --- drop it in your vault, link it to related notes, search across all your saved newsletters
• Notion --- paste directly, headings and quotes render correctly
• Apple Notes --- clean import via the Markdown share extension
• Readwise / Reader --- the Markdown imports cleanly without the cross-promo and signup noise that comes from a raw URL save
• Minibase Vault --- if you’ve connected one, every Substack save lands there automatically with backlinks and tags

FAQ

Does Minibase work on paywalled Substack posts? Yes, on the posts your account has access to. Minibase reads what your logged-in browser can see. If you’re a paid subscriber, you get the full essay. If you’re not, you get the public preview, exactly as Substack shows it to you.

Does Minibase work on custom-domain Substacks? Yes. Substacks that run on their own domain (Stratechery, Not Boring, Noahpinion) export the same way as *.substack.com sites. The extension detects the Substack-powered backend.

Can I save Substack Notes and Threads? Yes. Notes export as short Markdown files. Threads export as chronological Markdown lists with author and timestamp on each entry.

What about the comment section? Top-level comments are captured with the commenter’s name and date. Deeply nested threads are summarized to keep the file readable. If you want every comment verbatim, that’s a one-line option in the extension settings.

Does Minibase strip the “Subscribe now” modals and cross-promo blocks? Yes. Subscribe-modal overlays, “From X’s Substack” cross-promotion blocks, “Pledge your support” banners, and footer signup forms are all removed. The exported Markdown only contains the post itself.

Does it preserve images and pull-quotes? Yes. Images are referenced by their original URLs with alt text and captions intact. Pull-quotes export as Markdown block quotes (>).

What about embedded podcast episodes? Captured as a Markdown audio reference with the original episode URL. If you want a transcript, send the URL to your transcription tool of choice afterwards.

Does saving a Substack post share my account with anyone? No. The extension runs locally in your browser. It reads the post the same way your browser does and writes the Markdown to your machine. No login data leaves your computer.

How much does it cost? Minibase has a free tier so you can try it on a few posts. After that, a small subscription covers ongoing use.

Related Minibase Guides

• Save Medium Articles as Markdown --- the paywalled post you opened in incognito, captured cleanly
• Save YouTube Videos as Markdown --- transcript, summary, timestamps, all in one file
• Save Twitter / X Threads as Markdown --- every tweet, in order, with attribution
• Save Notion Pages as Markdown --- toggles expanded, databases as tables