Articles
Published · August 25, 2026

Markdown Keyboard Shortcuts for Faster Writing on Mac

Command+B, Command+I, Command+K, and Command+E map to Markdown bold, italic, link, and code on Mac. Here's how each shortcut works and when it's worth using.

Quick answer

On Mac, Command+B inserts Markdown bold (**text**), Command+I inserts italic (*text*), Command+K wraps a selection as a link ([text](url)), and Command+E wraps it as inline code (` code `). None of this is a Markdown invention — they're the same bindings Apple documents as system-wide Mac text-formatting shortcuts, which is why GitHub's own editor maps them the same way. Press the shortcut, and instead of applying rich-text formatting, a Markdown-aware editor inserts the raw syntax characters around your selection. The file stays plain text; only the rendered preview looks bold or linked. For the full range of emphasis syntax — including strikethrough and combining bold with italic — see Markdown bold, italic, and strikethrough.

Step-by-step

Bold and italic without lifting your hands off the keyboard

Select a word or phrase and press Command+B. A Markdown-aware editor wraps it in double asterisks — **like this** — rather than turning the text visually bold in the editor itself. Command+I does the same with single asterisks for italic (*like this*). CommonMark's spec treats underscores as an equivalent delimiter (__text__, _text_), but asterisks are the more common default, since underscores can misfire inside_words_with_underscores. Stack both shortcuts on the same selection and you get triple asterisks for bold-italic combined (***text***).

Inline code and fenced code blocks

Command+E is the one worth memorizing if you reference commands, filenames, or variables inline — it wraps a selection in single backticks (` npm install `) without breaking your sentence. That's a different job from a fenced code block, which needs triple backticks on their own lines and is meant for something you'd actually copy and run, not a word inside a sentence. There's no universal shortcut for inserting a fence, since it's a block-level structure rather than a text-wrap operation. Most editors handle it with a slash command, a toolbar button, or you just type the three backticks yourself. See inline code vs. code blocks for the fuller breakdown of when each one is the right call.

Links, fast

Command+K saves the most typing of the bunch. Select your link text, press Command+K, and the editor wraps it as [text]( ) with your cursor already inside the parentheses — paste a URL and you're done, no manual bracket-matching. Some editors go a step further: paste a URL directly onto selected text and it auto-converts to a Markdown link, while Command+Shift+V replaces the selection with the pasted link entirely instead of wrapping it. Choosing between an inline link and one you define once and reference by label elsewhere? Inline vs. reference-style links covers that trade-off.

Headings and structure while drafting

Headings don't get a dedicated Mac-wide shortcut, and that's fine — typing ## before a line is already about as fast as any keybinding would be. It's a prefix, not a wrap-a-selection operation. One to six # characters map to heading levels one through six.

Common problems and fixes

The shortcut does nothing, or inserts a literal character. This usually means the field you're typing in isn't Markdown-aware — a plain text box has no idea what Command+E means, so it either ignores the keypress or falls through to whatever else claims that binding. Check the specific app's shortcut list rather than assuming every text field understands Markdown shortcuts the same way.

Command+B or Command+I applies real formatting instead of inserting asterisks. That's expected in a word processor, where Command+B triggers true bold text. Only editors that treat the file as Markdown source will interpret the same shortcut as "insert the syntax characters" — the two are different jobs that happen to share a keybinding.

Command+K doesn't grab the clipboard. Some apps expect a URL already copied before you hit the shortcut; others pop open a separate field to paste or type into. Neither is wrong. It's app-specific behavior, so if the link shortcut seems to do less than you expected, check whether the app wants the URL pre-copied first.

A shortcut seems to get swallowed entirely. Command+K in particular gets reused by a lot of apps for search or "clear," and a system-wide remap can shadow it before your editor ever sees the keypress. If a Markdown shortcut stops responding, check System Settings > Keyboard > Shortcuts for a conflicting global binding before assuming the editor is broken.

Once formatting shortcuts are second nature, the next friction point is usually screen space — flipping between a reference tab and your draft, or referencing one document while writing another. Writing on iPad? Split View and multitasking shortcuts for writers covers that half of the workflow.

Frequently Asked Questions

Is there a universal keyboard shortcut for Markdown bold and italic on Mac?

Command+B and Command+I are the de facto standard across Mac apps and Markdown editors, including GitHub's web editor — pressing them wraps your selection in ** or * rather than applying rich-text formatting. The visual result in a Markdown editor is the raw syntax characters, not bolded or italicized text, until the file renders.

What's the keyboard shortcut to insert a Markdown link?

Command+K is the most common binding. In GitHub's editor and most Markdown-aware apps, it wraps your selection as link text and drops your cursor into the parentheses to paste or type the URL — faster than typing [ ]( ) by hand.

Do these shortcuts work the same in every Markdown editor?

The syntax they insert (**, *, ` `, text`) is standardized by CommonMark and GFM, so the output is portable. The key bindings themselves are app-specific conventions, not a Markdown standard — most editors follow the Command+B/I/K/E pattern because it matches system-wide Mac shortcuts, but always check an unfamiliar app's shortcut list before assuming.

Is it faster to use shortcuts or just type the Markdown characters?

For single words or short phrases, typing ** or ` `` directly is often just as fast as reaching for a modifier key. Shortcuts pay off most when wrapping a longer selection, inserting a link (which has two parts to manage), or when you're mid-flow and don't want to break typing rhythm to hit shift and a symbol key repeatedly.

Doing this with Carets

Carets ships native Command+B, Command+I, Command+K, and Command+E bindings that insert real Markdown syntax — not rich-text formatting — because the file underneath is always plain text, on iPhone, iPad, and Mac alike. That's the difference between a Markdown-aware editor and a word processor with a Markdown export button: the shortcuts do the same job as any other Mac app's, but what they write to disk stays portable.

Carets is native and fast, built for iOS and Mac rather than a web wrapper, and it keeps Markdown, plain text, and code in one editor — so the same shortcuts that format a note also work when you're editing a code snippet or a README. Files stay organized into files, projects, and tags, and syntax highlighting kicks in automatically for code.

Download Carets for iPhone, iPad, and Mac on the App Store.