Writing in Markdown on iPad: A Practical Workflow

Writing in Markdown on an iPad comes down to four moves: open an editor that saves real plain-text .md files, learn a small set of syntax, set up your keyboard and Split View so typing and research sit side by side, and keep every draft portable. Markdown was designed to read naturally as plain text and convert cleanly to HTML, which is exactly why it travels so well between an iPad, a Mac, and the web.

Quick answer

Pick a native editor that stores plain .md files in the Files app or iCloud Drive. Learn roughly eight constructs — headings, emphasis, lists, links, inline code, fenced code blocks, task lists, and tables. Connect a keyboard (or use the on-screen one), open your reference material in Split View, and write. Because the file stays plain text, you can move it anywhere later without conversion.

Step-by-step

1. Choose an editor that saves plain .md files

Format matters more than features here. Choose an editor that writes standard Markdown to a real file you can see in the Files app, rather than locking your words inside a proprietary database. Plain text is the reason your notes will still open in ten years, a point worth keeping in mind as you compare options — see why plain text outlasts proprietary formats.

2. Learn the core syntax

You can write most documents with a handful of constructs. Headings use leading hash characters, lists use a hyphen, and links wrap the text in brackets followed by the URL in parentheses:

# Title
## Section

- First item
- Second item

A [link](https://example.com) and some **bold** text.

For anything technical, fenced code blocks keep your samples intact. Open and close with three backticks, and name the language after the opening fence so the editor can highlight it:

let greeting = "Hello, iPad" print(greeting)

Two extensions from GitHub Flavored Markdown earn their keep for writers. Task lists turn list items into checkboxes, which is handy for tracking steps inside a note:

- [x] Draft the intro
- [ ] Add code examples
- [ ] Proofread

Tables use pipes and a separator row. If you only remember the constructs above, keep the CommonMark reference one tap away; for the deeper history and rationale, John Gruber's original Markdown description is still the clearest source. If you are unsure which dialect to target, our guide to CommonMark vs GitHub Flavored Markdown breaks down the differences.

3. Set up your keyboard and shortcuts

Because Markdown is mostly symbols, a hardware keyboard speeds things up. Connect one and tune its behavior in Settings > General > Keyboard > Hardware Keyboard, where you can adjust auto-correction, auto-capitalization, and modifier keys; Apple documents the full set of options for using an external keyboard with iPad. Turn off smart punctuation if you write code, so your straight quotes and dashes stay literal.

4. Keep sources beside your draft with Split View

Most writing is really just reading and typing in turns. Put your research on one side and your editor on the other using Split View on iPad: tap the multitasking control at the top of a window, choose Split View, and pick the second app. Drag the divider to give the editor more room when you shift from reading to drafting.

5. Organize, export, and reuse

Because the output is plain text, organizing is just file management: group drafts into folders or projects, tag them so search stays fast, and sync through iCloud Drive so the same files open on your Mac. When you need HTML, a PDF, or a Word file, convert from the Markdown source rather than maintaining two copies.

Common problems and fixes

Smart punctuation trips people up most often: curly quotes and em dashes can break code samples and link syntax. Disable it in keyboard settings before writing anything technical. If a table or task list renders as raw text, your target only supports plain CommonMark — switch to a tool or preview that understands GitHub Flavored Markdown, since tables and task lists are extensions. If your words feel trapped, that is a format problem, not a writing problem: export or copy them into a .md file and keep the original plain text from then on. And if the on-screen shortcut row or your hardware shortcuts disappear, check that the keyboard is still paired and that Full Keyboard Access settings have not overridden the app's own shortcuts.

Doing this with Carets

Carets is a fast, native notes and code editor for iPhone, iPad, and Mac — Markdown, plain text, and code with syntax highlighting, organized into files, projects, and tags. It fits this workflow for three concrete reasons. First, it is native and built for iOS and Mac rather than a web wrapper, so typing and scrolling stay responsive on iPad. Second, it handles Markdown, plain text, and code in one place, with syntax highlighting when you drop in a fenced code block — so a writer with the occasional snippet and a developer editing a README use the same editor. Third, your work lives in plain-text files organized by projects and tags, which keeps everything portable and easy to find later. Carets is available on the App Store for iPhone, iPad, and Mac.

FAQ

Do I need an external keyboard to write Markdown on iPad?

No. The on-screen keyboard works fine, and Markdown's symbols are all reachable. A hardware keyboard mainly speeds up symbol-heavy syntax and unlocks keyboard shortcuts, so it is a comfort upgrade rather than a requirement.

CommonMark or GitHub Flavored Markdown — which should I use?

Write to CommonMark for portable prose; reach for GitHub Flavored Markdown when you need tables, task lists, or strikethrough. GFM is a superset of CommonMark, so plain documents render the same in both.

How do I keep my Markdown files portable?

Save real .md files to the Files app or iCloud Drive instead of a closed database, and avoid app-specific syntax extensions. Plain text opens anywhere, which is the whole point of writing in Markdown.

Can I write code snippets in the same editor?

Yes. Fenced code blocks with a language name keep snippets readable, and an editor with syntax highlighting makes them easier to scan — useful for scratch files, config edits, and README authoring alongside your prose.