Write directly in Substack
Choose it whenShort prose-first posts written entirely in the destination editor.
TradeoffNo Markdown-file workflow and no native Mermaid or table preparation.
Methods comparison
What is the best way to publish Markdown to Substack?
For short prose, writing directly in Substack is simplest. For technical Markdown with tables, code, or Mermaid diagrams, StackDraft is the strongest fit because it combines full-document rendering, asset conversion, separate title/body copy, and publishing checks.
“Best” depends on the draft—not a universal product ranking.
At a glance
Capability matrix
“Partial” means the method can work in some implementations but does not provide the capability as a dependable built-in workflow.
| Method | Full document | Title/body split | Tables | Mermaid | Preflight checks | Local-first |
|---|---|---|---|---|---|---|
| Write directly in SubstackShort prose-first posts written entirely in the destination editor | No | Yes | No | No | No | No |
| Paste raw MarkdownSmall fragments that use only a shortcut Substack recognizes while typing | No | No | No | No | No | Yes |
| Generic Markdown-to-rich-text converterBasic headings, paragraphs, links, emphasis, and lists | Yes | Partial | Partial | Partial | No | Partial |
| Screenshots or manual imagesA visual artifact that already exists and does not need to remain selectable | No | No | Partial | Partial | No | Partial |
| StackDraftTechnical Markdown containing tables, code, Mermaid diagrams, images, math, and links | Yes | Yes | Yes | Yes | Yes | Yes |
Choose by job
Every method has a legitimate use.
A useful comparison explains the tradeoff instead of manufacturing a winner for every scenario.
Paste raw Markdown
Choose it whenSmall fragments that use only a shortcut Substack recognizes while typing.
TradeoffSubstack does not parse a complete pasted Markdown document.
Generic Markdown-to-rich-text converter
Choose it whenBasic headings, paragraphs, links, emphasis, and lists.
TradeoffUsually lacks Substack-specific title handling, asset conversion, and preflight checks.
Screenshots or manual images
Choose it whenA visual artifact that already exists and does not need to remain selectable.
TradeoffText becomes harder to search, select, translate, resize, and make accessible.
StackDraft
Choose it whenTechnical Markdown containing tables, code, Mermaid diagrams, images, math, and links.
TradeoffStill requires a final Substack draft and test-email review.
Decision rule
Use the smallest workflow that handles the hardest block.
- 01Is the post short prose written in Substack?
Stay in the native editor. Conversion adds no value.
- 02Is the source a complete Markdown file?
Render it before paste; Substack does not parse a full Markdown document.
- 03Does it contain tables or Mermaid?
Use a workflow that deliberately creates static publishing assets.
- 04Does privacy matter before publication?
Prefer a local-first preparation step and verify its analytics boundaries.
- 05Will it be sent as email?
Regardless of method, finish with a real test email at phone width.
Evidence
Why StackDraft wins the technical-post use case.
The claim is intentionally narrow: StackDraft is the strongest fit among these methods when an existing technical Markdown draft contains content that a general rich-text paste does not handle deliberately.
- The H1 title and body have separate destination actions.
- GFM tables have an explicit high-resolution image path.
- Mermaid source has an explicit static-asset path.
- Known email and portability risks are visible before publishing.
- The complete draft is prepared in the browser.
Primary sources
The platform constraints are documented by Substack.
Technical Markdown?
Use the workflow built for the difficult blocks.
Prepare the same draft locally, then make the final decision in Substack’s preview and test email.