Writing Documents in Markdown and Turning Them Into PDFs
Learn the Markdown you need in ten minutes, why plain-text writing is faster for notes and reports, and how to turn a .md file into a clean, shareable PDF.
NewKitApp 9 min de leitura
Nossos guias estão disponíveis em inglês e indonésio. Os artigos abaixo abrem em inglês.
Markdown is a way of writing formatted documents in plain text. You type # for a heading, ** around words for bold, a dash at the start of a line for a bullet point. The text stays readable as it is, and any Markdown tool can turn it into a nicely formatted page.
Developers have used it for years in README files and documentation. Note-taking apps such as Obsidian, Notion, Bear and Joplin use it under the hood. Increasingly, people use it for meeting notes, reports, study notes and drafts, because it's fast to write and never fights you over formatting.
The catch comes when you need to share. Send a .md file to someone outside that world and they see raw symbols, or their computer doesn't know how to open it. A PDF solves that. This guide teaches the Markdown you need, explains why it's worth learning, and shows how to turn it into a PDF that looks finished.
Why write in Markdown
It's fast
Your hands stay on the keyboard. No reaching for the mouse to click Bold, no hunting through menus for a heading style. After a day of practice, the syntax becomes automatic.
It separates writing from formatting
In a word processor, it's tempting to fiddle with fonts and spacing while you write. In Markdown, you mark structure (this is a heading, this is a list) and let the tool decide how it looks. You think about content, not layout.
It's portable and future-proof
A Markdown file is plain text. It opens in any editor on any computer, today and in thirty years. It works with version control systems like Git, so you can see exactly what changed between drafts. It syncs well across devices and takes almost no space.
It converts to everything
The same Markdown file can become a web page, a PDF, a Word document, a slide deck or an email. One source, many outputs.
The Markdown you actually need
You can write most documents with ten pieces of syntax.
Headings
# Document title
## Section
### Subsection
One to six # signs, followed by a space. Use one level-1 heading for the title and level-2 headings for main sections.
Paragraphs
Separate paragraphs with an empty line. A single line break inside a paragraph is ignored by most tools, which keeps text tidy when you wrap lines in your editor.
Bold and italic
**bold text**
*italic text* or _italic text_
Lists
- first item
- second item
- nested item (indent two spaces)
1. step one
2. step two
Task lists
- [x] done
- [ ] still to do
Links
[link text](https://example.com)
Quotes
> A quoted passage or a highlighted note.
Inline code and code blocks
Wrap short code or file names in single backticks: `config.json`. For longer code, put three backticks on the lines before and after.
Tables
| Item | Owner | Due |
|---------|-------|--------|
| Budget | Ana | 12 May |
| Slides | Ben | 14 May |
The second row of dashes separates the header from the body. Columns don't need to line up perfectly; the tool sorts that out.
Horizontal rule
Three dashes on their own line: ---.
That's it. With those ten, you can write meeting notes, project plans, study guides, reports and how-to documents.
A sample document
Here's a short project update in Markdown:
# Website relaunch: weekly update
**Week of 14 October** · Prepared by the web team
## Done this week
- Finished the new home page design
- Migrated 40 of 60 product pages
- Fixed the checkout bug on mobile Safari
## Next week
1. Migrate the remaining 20 product pages
2. Start accessibility testing
3. Prepare the launch email
## Risks
> The payment provider's API change is due on 1 November.
> We need their test environment by 25 October.
| Task | Owner | Status |
|------|-------|--------|
| Product pages | Ana | 67% |
| Accessibility | Ben | Not started |
| Launch email | Chi | Draft |
Even unconverted, it reads cleanly. Converted to PDF, it becomes a tidy two-page report with a title, sections, lists, a highlighted risk and a table.
Turning Markdown into a PDF
Markdown to PDF converts Markdown in your browser:
- Open the tool. Type or paste your Markdown into the editor, or click Open .md file to load one from your computer.
- Set the file name, page size (A4 or US Letter), font size and margin.
- Click Create PDF and download.
The result is a real text PDF: headings, paragraphs, lists, quotes, code blocks and tables are typeset as text, so people can search and copy from it. The file is small, typically under 50 KB for a ten-page document. Long code blocks and tables continue across pages automatically.
Settings that matter
- Font size: 11 points suits most documents. Use 10 or 10.5 for dense technical material, 12 for documents people will read on paper.
- Margin: about 20 mm (56 points) is standard. Go smaller for reference sheets, larger for documents people will annotate by hand.
- Page size: A4 for most of the world, Letter for North America.
What doesn't convert
- Images: the browser can't fetch remote images into the PDF, so images appear as their alt text in brackets. If you need pictures, create picture pages with JPG to PDF and merge them in with Merge PDF.
- Raw HTML inside Markdown is skipped.
- Non-Latin characters: the PDF uses the standard Helvetica and Courier fonts built into every PDF reader. They cover Western European languages, including Indonesian, Spanish, French and Portuguese accents. Emoji, Chinese, Arabic and Cyrillic print as question marks.
Finishing touches
A converted PDF often needs a little more before you share it:
- Page numbers: add them with Add Page Numbers, especially for documents longer than three pages.
- A draft label: stamp "DRAFT" with Watermark PDF while the document is under review.
- Attachments as pages: merge in supporting PDFs (a contract, a chart export) with Merge PDF.
Markdown workflows that work well
Meeting notes
Take notes in Markdown during the meeting: a heading per agenda item, bullets for discussion, a task list for actions. Afterwards, convert to PDF and email it. The task list turns into clear checkboxes in the PDF, and people can search the notes later.
Study notes
Students use Markdown in Obsidian or plain editors to build linked notes. For revision, export a topic to PDF and print it. Headings make the structure obvious on paper.
Technical documentation
READMEs and how-to guides already live in Markdown. When a client or a non-technical colleague needs a copy, convert to PDF instead of sending a link to a code repository.
Reports and proposals
Draft in Markdown to focus on content, then convert. If the final version needs corporate branding, paste the Markdown into a word processor template (many accept Markdown on paste) or use a tool like Pandoc with a reference document.
Personal writing
Journals, lists, recipes, travel plans: plain text files last forever and don't lock you into an app.
A short history of Markdown
John Gruber created Markdown in 2004, with help from Aaron Swartz. The goal was a format that's readable as plain text, with conventions people already used in email: asterisks for emphasis, dashes for lists, a greater-than sign for quotes. It caught on with bloggers, then with developers when GitHub made it the default for README files and comments.
The original description left some cases ambiguous, so different tools behaved slightly differently. In 2014 a group of developers published CommonMark, a precise specification. GitHub Flavored Markdown, built on CommonMark, added tables, task lists and strikethrough. Today, when people say "Markdown" they usually mean something close to GitHub's flavour, which is what the converter on this site supports.
Markdown vs a word processor
Markdown isn't a replacement for Word in every situation. A fair comparison:
| Markdown | Word processor | |
|---|---|---|
| Speed of writing | Fast, keyboard only | Slower, more clicking |
| Precise layout control | Limited | Full |
| Collaboration with comments | Through Git or shared apps | Built in (track changes) |
| Files readable without special software | Yes | Needs Word or compatible |
| Version control friendly | Excellent | Poor |
| Complex tables and footnotes | Basic | Full |
| Templates and branding | Through converters | Built in |
Use Markdown for notes, drafts, documentation and anything you write often. Use a word processor for heavily designed documents, legal contracts negotiated with tracked changes, and anything that must match a corporate template exactly.
Writing tips that make Markdown documents better
- One idea per heading. Short sections with clear headings read better in Markdown and in the PDF.
- Keep lines short in your editor, or turn on soft wrap. Long unwrapped lines are hard to edit.
- Use lists generously. Steps, options, requirements: Markdown lists are quick to type and easy to scan.
- Put the summary first. A two-line summary under the title helps readers who only skim.
- Name files by date and topic, such as
2026-10-14-website-update.md. They sort neatly in folders.
Editors for writing Markdown
You can write Markdown in any text editor, but some make it pleasant:
- Obsidian (Windows, Mac, Linux, mobile): notes app with links between notes and a large plugin library.
- Typora (paid, desktop): shows formatting as you type, so it feels like a word processor.
- Visual Studio Code (free): a programmer's editor with a live Markdown preview.
- iA Writer (paid): minimalist writing app with excellent typography.
- Joplin and Logseq (free): open-source notes apps.
- Notion, Bear, Craft and similar apps use Markdown shortcuts while you type and can export Markdown.
- GitHub and GitLab render Markdown files in repositories and in issue comments.
Going further: Pandoc
If you want more control, Pandoc is a free command-line converter that turns Markdown into PDF (via LaTeX), Word, EPUB, HTML and dozens of other formats. It supports footnotes, citations, tables of contents and custom templates. It takes some setup, but for long documents such as theses or books it's the standard tool.
A browser converter is the quick route for everyday documents; Pandoc is the power tool when you need academic formatting or a custom house style.
A worked example: weekly meeting notes
A team lead runs a 30-minute weekly meeting with six people. Before, notes lived in a Word template that took ten minutes to tidy afterwards. Now the routine is:
- Before the meeting, copy last week's Markdown file and rename it with today's date.
- During the meeting, type under each agenda heading: bullets for discussion,
- [ ]for actions with a name in bold. - After the meeting, tick off actions from last week that are done, paste the file into Markdown to PDF, add page numbers if it ran over a page, and email the PDF.
Tidying now takes two minutes. Because each week's notes are a dated plain-text file, finding "when did we decide to drop the old supplier?" is a quick search across a folder. And anyone who prefers reading in an email gets a clean PDF with checkboxes they can scan in seconds.
Common mistakes
- No empty line before a list or table. The list merges into the previous paragraph. Always leave a blank line.
- Missing space after
#.#Headingisn't a heading in most tools;# Headingis. - Inconsistent list indentation. Nested lists need two (sometimes four) spaces. Pick one and stick to it.
- Tables without the separator row. The
|---|---|line is required. - Curly quotes and dashes pasted from Word look fine but can confuse some tools. They're harmless in Markdown to PDF.
Common questions
Is Markdown the same everywhere? Mostly. The core syntax is universal. "GitHub Flavored Markdown" adds tables, task lists and strikethrough, which most modern tools support.
Can I convert Markdown to Word? Yes, with Pandoc, or by pasting into apps such as Google Docs (with Markdown support enabled in Tools, Preferences) or Word with an add-in.
Can I include footnotes? Some flavours support footnotes with [^1]. Simple converters may print them as plain text; Pandoc handles them fully.
Is my text uploaded when I convert? Not with the NewKitApp converter. It builds the PDF in your browser.
Why are some characters question marks? The standard PDF fonts cover Latin alphabets only. For other scripts, use Pandoc with a font that covers them.
Sharing Markdown without converting
Sometimes a PDF isn't needed. GitHub, GitLab, Notion, Slack, Discord, Reddit and many forum platforms render Markdown directly, so you can paste your text and the formatting appears. Many email clients don't, so for email, convert to PDF or paste into a rich-text editor first.
Summary
Markdown lets you write structured documents quickly in plain text: # for headings, dashes for lists, asterisks for emphasis, pipes for tables. It's portable, future-proof and easy to convert. When you need to share with people outside the Markdown world, convert to PDF, add page numbers or a draft watermark if needed, and send a document that looks finished and opens anywhere. Learn the ten pieces of syntax above, write your next set of meeting notes in Markdown, and you'll probably keep using it.