Each guide covers the source draft, conversion, destination check, and actual email preview.
Publish technical Markdown without fighting the editor.
Practical, tested workflows for moving tables, code, diagrams, Obsidian notes, and VS Code drafts into Substack’s web and email formats.
How to Add a Table in a Substack Post (Without a Blurry Screenshot)
Learn how to add a table to a Substack post with Markdown, convert it into a crisp image, check mobile readability, and add useful alt text.
Tables, code, Mermaid, images, links, and Markdown edge cases get first-class treatment.
Guidance follows StackDraft’s current behavior and links to official platform documentation.
The reproducible compatibility report classifies 20 Markdown cases and publishes the complete results as JSON.
Every StackDraft guide
Start with your source editor or the format that is hardest to move.
Add a table to a Substack post
Learn how to add a table to a Substack post with Markdown, convert it into a crisp image, check mobile readability, and add useful alt text.
Markdown to Substack
Convert Markdown to Substack-ready rich text while preserving headings, links, lists, code, tables, and technical diagrams.
Obsidian to Substack
Publish an Obsidian Markdown note on Substack without losing headings, links, code, tables, diagrams, or local images along the way.
Substack formatting guide
Format Substack posts for the web and email with a clean heading structure, readable code, accessible images, lists, quotes, and links.
Code blocks in Substack
Add readable code blocks to Substack from Markdown, preserve syntax structure, and keep long lines usable in web posts and email.
Mermaid diagrams in Substack
Turn Mermaid flowcharts and sequence diagrams into readable PNG assets for Substack posts and emails, with a reliable Markdown workflow.
VS Code Markdown to Substack
Move a Markdown article from VS Code to Substack with clean rich text, working links, readable code, converted tables, and email-safe diagrams.
Write where you think. Verify where readers will read.
Keep the source in Markdown, prepare it as rich text, then treat Substack’s web preview and test email as the final renderers.
- 01Draft
Obsidian, VS Code, Cursor, or a local file
- 02Prepare
Preview, convert, and resolve publishing checks
- 03Verify
Paste into Substack and send a test email