Plain text, rich text or Markdown? How to choose the right format

When you open a notes app you rarely think about formats. You type, maybe press a bold button, and move on. But the format underneath matters more than it seems. It decides whether your note survives being pasted into an email, whether a colleague on another device can open it, and whether it can be searched, versioned or converted later.

There are three formats most people meet every day: plain text, rich text and Markdown. Each one makes a different trade-off between simplicity, appearance and portability.

Plain text: just the characters

Plain text is the simplest possible format. A plain text file stores the characters you typed and nothing else — no fonts, no colors, no bold, no images. The classic example is a .txt file opened in Notepad on Windows or TextEdit in plain mode on a Mac.

Where it shines:

• Portability. Every operating system, phone, programming language and text editor can read plain text. Files written in the 1970s still open perfectly today.
• Copy and paste. Plain text never drags hidden formatting into the place you paste it.
• Code and data. Configuration files, scripts, logs and command snippets must be plain text; hidden formatting would break them.
• Speed. There is nothing to style, so writing is completely distraction-free.

Where it falls short: there is no way to show emphasis, headings or links visually. Long plain-text documents can feel like a wall of words unless you structure them carefully with blank lines and simple conventions such as dashes for lists.

Rich text: what you see is what you get

Rich text stores formatting alongside the words: bold and italic, headings, lists, links, sometimes colors, images and tables. Word processors, email composers and most "notes" apps use rich text. Under the hood it may be HTML, RTF, a .docx file or an app's own internal format.

Where it shines:

• Readability. Headings, bold key terms and real bullet points make long notes easy to scan.
• No syntax to learn. Toolbar buttons and keyboard shortcuts such as Ctrl+B or Cmd+B are familiar to everyone.
• Mixed content. Images, links and quotes sit naturally inside the text.

Where it falls short:

• Messy pasting. Copying rich text from a web page often brings fonts, sizes and colors along. When you paste into another document, the styles clash.
• Lock-in. Some rich-text formats only open properly in the app that created them. Exporting can lose formatting.
• Hidden structure. It is hard to see why a paragraph behaves strangely, because the formatting codes are invisible.

Tip: most programs support "paste as plain text" with Ctrl+Shift+V (Windows, Linux and many browsers) or Cmd+Shift+Option+V on Mac. It strips the formatting and saves cleanup time.

Markdown: plain text that knows how to look good

Markdown sits between the two. You write plain text, but you use a few simple characters to describe formatting: # Heading, **bold**, - list item, [link](https://example.com). A Markdown viewer turns those marks into nicely formatted output, while the file itself stays readable as plain text.

Where it shines:

• Portable and formatted. You get headings and lists without giving up plain-text durability.
• Keyboard-first. Once you know the syntax, you never reach for the mouse to format.
• Developer-friendly. README files, documentation, wikis, issue trackers and many chat apps use Markdown.
• Easy to convert. Tools can turn Markdown into HTML, PDF, slides or Word documents.

Where it falls short: there is a small learning curve, different apps support slightly different flavors, and complex layouts — multi-column pages, precise image placement, colored text — are outside what Markdown is designed for.

Side-by-side comparison

Which one should you use? A practical guide

Choose plain text for

• Quick capture: phone numbers, addresses, reminders, one-line ideas.
• Anything you will paste somewhere else: a form, a terminal, a chat, a code editor.
• Code snippets, commands, configuration and log excerpts.
• Notes you want to keep for decades with zero risk.

Choose rich text for

• Meeting notes and summaries you will share with non-technical people.
• Documents that need images, highlighted key terms or quotes.
• Drafts you plan to export to Word or print.

Choose Markdown for

• Documentation, README files, wiki pages and technical notes.
• Long notes that benefit from headings but must stay portable.
• Writing for the web: blog drafts, newsletter content, forum posts.
• Study notes and outlines you want to restructure often.

Converting between formats

Moving between formats is usually one-way friendly. Plain text becomes Markdown just by adding a few symbols. Markdown becomes rich text by rendering it — copy the formatted preview and paste it into an email or document. Rich text back to plain text is easy, but you lose the formatting; rich text to Markdown requires a converter or some manual cleanup.

A good habit: write in the simplest format that does the job, and convert only when you need to. Starting in plain text or Markdown keeps every option open; starting in a proprietary rich-text format can close some doors.

How this works in Notepad Free

Notepad Free offers all three as separate note types. The Plain text tab is a clean editor for raw text. The Rich text tab has a formatting toolbar with bold, italic, underline, headings, lists, quotes, links and images, and it sanitizes pasted HTML so stray styles from websites do not come along. The Markdown tab shows your source and a live preview side by side. You can download any note as a text file, and rich text can also be exported as a Word document or printed to PDF.

The bottom line

There is no single best format — only the best format for a given note. Plain text is the most durable, rich text is the most familiar, and Markdown gives you a bit of both. Knowing the trade-offs means you will pick the right one in seconds, and your notes will look right wherever they end up.