Markdown vs rich text

Use Markdown when text must stay portable, live in version control or end up on the web. Use rich text when page layout matters or your collaborators expect a word processor.

The difference

Markdown is plain text with a few symbols for formatting. You type **bold** and a preview shows bold; the file itself stays readable in any text editor.

Rich text (Word, Google Docs, most email and note apps) stores formatting in the document format. You select text and click B; what you see is what you get, but the file needs an app that understands its format.

# Meeting notes

- **Decision:** ship on Friday
- Owner: [Sam](mailto:sam@example.com)

Comparison

MarkdownRich text
PortabilityA .md file opens anywhere and converts to HTML, PDF or Word.Tied to a format (.docx, Google Docs); copying between apps can lose formatting.
Version controlLine-by-line diffs in Git; easy to review and merge.Binary or app-specific; relies on the app's own history.
Formatting controlStructure only: headings, lists, tables, code. No fonts, colours or page layout.Full control over fonts, colours, spacing and page layout.
CollaborationThrough Git and pull requests, or by sharing files and links.Real-time co-editing, comments and suggestions built in.
Learning curveA dozen symbols; the basics take minutes, with a cheat sheet at hand.None for basic use; everyone knows the toolbar.

Choose Markdown for

Choose rich text for

Using both

You don't have to choose once. Pandoc converts in both directions:

pandoc notes.md -o notes.docx     # Markdown to Word
pandoc report.docx -o report.md   # Word to Markdown

Without tools, copy the rendered preview from a Markdown editor and paste it into Word or Google Docs: headings, lists, links and tables keep their formatting. To share a finished Markdown document, export it to PDF.

Try it in Hashlite: open the free editor and see the result as you type.