What Can and Can’t You Do with Markdown Formatting?
Updated
Markdown lets you control the structure and display of text—such as making words bold, creating headers, and organizing lists—but it does not let you control visual styling like font size, color, or typeface. If your goal is clean, portable, structured writing, Markdown is a good fit. If you need precise visual design, you’ll need more than Markdown.
What Markdown Can Do
Markdown is a way to write content for the web using “plaintext”—the regular alphabet plus a few familiar symbols like asterisks (*) and backticks (`). According to Markdown Tutorial, formatting text in Markdown has a very gentle learning curve, and the site estimates that if you have ten minutes, you can learn Markdown.
Its core capabilities focus on text display and organization:
- Emphasis and bold — highlight words with simple symbols
- Headers — create a hierarchy of section titles
- Lists — organize items into ordered or unordered groups
- Readable source — the raw text stays understandable even before rendering
Because Markdown is plaintext, text written in it “can be easily shared between computers, mobile phones, and people.” This portability is a key advantage: the same file works across devices and platforms without a heavy word processor.
What Markdown Can’t Do
Markdown Tutorial is explicit about the limits: it “doesn’t do anything fancy like change the font size, color, or type.” In other words:
- No font size control — you can mark something as a header, but you can’t set an exact point size
- No color control — text color is determined by the renderer, not your Markdown
- No typeface selection — you can’t choose fonts like Arial or Times New Roman
- No fine visual layout — precise positioning, spacing, and design are outside its scope
This makes Markdown a poor choice for tasks like designing a poster, a branded brochure, or a pixel-perfect layout. It is a writing format, not a design tool.
Where Markdown Fits Well
Markdown is “quickly becoming the writing standard for academics, scientists, writers, and many more,” and sites like GitHub and reddit use it to style comments. That context tells you where it shines:
| Use case | Good fit? | Why |
|---|---|---|
| Notes, documentation, README files | Yes | Structure matters more than styling |
| Comments on GitHub or reddit | Yes | These platforms render Markdown natively |
| Sharing text across devices | Yes | Plaintext is portable |
| Precise visual design | No | No control over fonts, colors, sizes |
How to Decide
Choose Markdown when you want structured, portable, easy-to-write text and are happy to let the platform handle appearance. Avoid relying on it when the visual result—exact fonts, colors, and layout—is the point. A practical test: if you can describe your goal as “make this a header” or “bold this word,” Markdown works; if you need “make this 18pt blue Helvetica,” it doesn’t.
Markdown Tutorial structures its lessons around a single concept at a time, followed by exercises, which suits beginners who want to confirm these boundaries hands-on within a short session.