Markdown: the language you use to talk to ChatGPT and Claude

Good tools don't ask you to notice them: they just sit where they're needed and do their job quietly, without begging for a five-star review. Markdown is exactly that kind of tool. It's been quietly hanging around all these years, in software documentation and on forums. You just never stopped to think about what it was for or how it worked. Well, now's the time to find out.

Why you never noticed it before

You never paid attention to Markdown for a pretty understandable reason: it was designed to be invisible from the start.

It's a format that hides behind its own output. You've definitely seen that output — you've read well-structured documentation on GitHub or neatly formatted posts on Reddit. You just never guessed what was going on underneath. To actually dissect Markdown, you need to switch sides and start writing.

AI models brought Markdown to most people’s attention for the first time: it’s the format Claude or ChatGPT uses for replies.

On screen you see normal text, but the moment you copy it into a plain text editor, out pop strange asterisks and hash signs.

Why AI models will love you

Knowing Markdown is the key to a healthy relationship with artificial intelligence. A huge chunk of the material modern language models were trained on (GitHub repositories, technical documentation, Stack Overflow, and millions of Obsidian notes) was written in Markdown. It's LLMs’ native language. When you ask an AI to "format the answer with a level-two heading and a code block," it picks up on that instantly, because that's exactly how it learned to read.

Feed a model a Markdown document, and it'll "digest" it far more accurately than it will a bulky PDF or DOCX. The reason is simple: there's no hidden formatting, no junk metadata, no conversion artifacts inside — just clean, predictable text. You start talking to the machine on its own turf, and it's always nicer dealing with someone who speaks your language.

Why it beats a plain .txt

How is Markdown better than a plain text file? After all, you can open a .txt file anywhere too. The difference is that a text file is bare text with no internal structure. While Markdown doesn’t include Word’s burden of hidden styles, it does give the renderer silent instructions:

"here's a heading, and here's a list." It just also keeps the file readable even with no rendering at all. The word **important** surrounded by asterisks looks a bit unusual, but its meaning registers instantly.

All the syntax you'll ever need

The idea behind Markdown is very simple: we agree that certain characters mean a certain kind of formatting. If you want to bold a word in Word, you select it with your mouse and hunt for the "B" button on the toolbar, or blindly and casually mash "Cmd/Ctrl B". In Markdown you just put two asterisks before and two after (though any Markdown editor will also easily take "Cmd/Ctrl B").

This agreement boils down to a surprisingly short list of rules.

• Headings — hash signs. One # for a big heading, two ## for slightly smaller, three ### for very modest. It’s the same logic as H1/H2/H3 in Word, just without the mouse and clicking around in menu buttons.

• Bold and italic — asterisks. Two **like this** give you bold, one *like this* gives you italic. Three asterisks ***like this*** give you both at once, for those times when you don't feel like holding back.

• Lists — dashes or numbers followed by periods. Use one of these at the start of a line, and a pile of chaos instantly turns into a tidy list.

• Code — backticks: `like this`. Type one on each side for an inline snippet, three for a standalone block. It's the only way to drop in code without turning the whole text into unreadable mush.

• Links — square brackets for the visible text, and right after them, no space, parentheses for the actual address. Write [click here](https://example.com), and you get a neat link.

• Quotes — an angle bracket > at the start of a line. And you get a quote, which everyone formats differently. A vertical line running down the whole paragraph is the canonical look in newer editors, but unfortunately both Word and Google Docs treat it as just an indented line. That’s why exporting Markdown quotes from Google Docs is a huge headache: that indent isn't Markdown anymore, and it usually just gets dropped in the transfer.

There you have the six core building blocks. Everything else — tables, footnotes, checklists — is just extensions that can behave differently depending on the program.

A brief history of the format that was right under your nose

The late programmer and activist Aaron Swartz and the blogger and essayist John Gruber invented Markdown in 2004. Gruber wanted to write for the web without getting bogged down in HTML tags, so he and Swartz came up with an elementary idea: let the text look formatted even in its raw state, the way people already wrote informally. Asterisks around a word already hint at emphasis. A hash sign at the start of a line already looks like a heading. Gruber simply codified what people were doing intuitively and wrote a program to convert it to HTML.

The format spread quietly, without any fanfare. When GitHub adopted it in 2008, Markdown went from a blogger's toy to the infrastructural backbone of the internet. Millions of README files, issues, and pull requests all came through in Markdown. Then Notion, Obsidian, Reddit, and Stack Overflow, along with various messaging apps, jumped on board. By the early 2020s, the language was pretty much everywhere.

The dirty little secret

Here honesty demands we pause and admit something a bit awkward.

Markdown, conceived as a single universal format, has splintered over time into a whole bunch of dialects. GitHub Flavored Markdown understands tables, but most other implementations don't. CommonMark tries to be a strict standard, and mostly pulls it off, but not everywhere. MultiMarkdown adds footnotes. Obsidian has bolted on its own extensions on top of all that.

In practice, this means a table that looks perfect on GitHub might render as unreadable garbage in a different editor. A format meant to spare the world a compatibility headache went and spawned its own compatibility headache.

One thing's comforting: our six simple building blocks work everywhere, all the time.

How this will change the rest of your life

Markdown won't turn your world upside down. But it will give you a quiet little thrill when, years from now, you open an old file on a completely different computer, running an unfamiliar operating system, in a new editor — and find you can still read it and edit it just fine. You get used to that pleasure fast, kind of like using a good knife in the kitchen.

This is one of those rare cases where a bare-bones tool turns out to be genuinely built to last. Complex word-processor formats have changed over and over in the last twenty years, while Markdown from 2004 looks and reads exactly like Markdown from 2024. In a world where software goes obsolete faster than your subscription fee gets charged, that alone is a remarkable achievement.

To wrap up

Every great system, in the end, comes down to something very simple. For Markdown, it's this:

# Here's a heading

Here's something in bold, **important**, and in italics, *slightly less important*

• here's a to-do item you'll get around to someday

[here's a link](https://example.com)

`here's some code`

> here's a quote

Six lines. Dreamed up in 2004. Understood by robots and humans alike. Even Google Docs gets it (with some caveats about the blockquote). One last disclaimer: trying to open a Markdown file in MS Word in the summer of 2026 can still leave Word thoroughly confused. Sad, but then again, what other bad news about Microsoft were you missing? It's not all doom and gloom here, either: MS Word handles copy-pasted Markdown just fine. It has no choice.

If you want to dig deeper

Where it all started

Daring Fireball: Markdown — John Gruber's original page from 2004. The spec is written in the spirit of the format itself: simple, with no unnecessary complications. It’s literally a historical document.

How it's officially structured

CommonMark — a large-scale attempt to bring order to things, launched in 2014, once it became clear that dozens of Markdown implementations had stopped understanding each other. There's also an interactive editor here where you can try out the syntax right in your browser.

GitHub Flavored Markdown — the spec for the dialect you'll run into most often. Tables, task lists, strikethrough text — it's all here. You don't have to read the whole thing, but it's interesting to see how seriously people took a format that was dreamed up over a weekend.

For practice

Markdown Tutorial — an interactive tutorial, no installation required. Twenty minutes, and there's nothing left to google.