How to Enable Markdown in Google Docs (and Fix It When It Doesn't Work)
You read that Google Docs supports Markdown, but you type ## Heading and nothing happens, or you paste a block of Markdown and it lands as raw text with the symbols still showing. The feature exists, but it is off by default and split across three separate paths that each behave differently. Here is exactly how to enable it, what each path covers, and how to fix the cases where it still does not work.
How to enable Markdown in Google Docs
Markdown handling is a per-account setting, not a per-document one, and it is disabled until you turn it on:
- Open any Google Doc.
- Click Tools, then Preferences.
- Check Enable Markdown.
- Click OK.
That is the whole setup. Once it is on, it applies to every document under that Google account, on that account only. If you use more than one Google account, you have to enable it for each.
What "Enable Markdown" actually turns on
Turning the setting on enables three different behaviors, and knowing which one you are using explains most of the confusion:
- Autocorrect as you type. Typing
#,*, or-and a space converts to headings, emphasis, and list items live while you write. - Paste from Markdown. Copy Markdown text, right-click where you want it, and choose Paste from Markdown. A plain
Ctrl+VorCmd+Vdoes not do the conversion, which is the single most common reason people think the feature is broken. - Import and export. Open a
.mdfile with File, then Open, and download a doc as Markdown with File, then Download, then Markdown (.md). Google added this native import and export path in July 2024.
"I enabled it and Markdown still isn't working"
Almost every "not working" report traces back to one of a handful of specific causes. Match your symptom to the fix:
| Symptom | Cause | Fix |
|---|---|---|
Paste shows literal # and * | Used Ctrl+V, not the special paste | Right-click and choose Paste from Markdown |
| Nothing converts as you type | Setting is off, or off on this account | Re-check Tools, Preferences, Enable Markdown on the correct account |
| Tables paste as a row of pipes | Native paste does not build table structure | Convert first with a tool, see below |
| Code block keeps its backticks | Fenced code is not a supported target | Convert first, or format the block manually |
| Works on desktop, not on phone | The mobile apps do not offer the same Markdown handling | Use the desktop web app |
| Download as Markdown looks wrong | Tables and some structure do not round-trip cleanly | See Google Doc to Markdown |
What still will not work, even when enabled
Enabling the setting fixes the basics, but some content has no reliable native path regardless:
- Tables usually stay as literal pipe characters on paste.
- Fenced code blocks keep their backticks instead of becoming a formatted block.
- Images referenced by URL do not render.
- Comments are never carried across import or export.
The reason is structural: a Google Doc is a document model with real table and list elements, not a text renderer, so a line of pipes has nothing to map to unless a converter builds the table first. The simple inline styles have an obvious mapping and survive; the structural ones do not. For a fuller breakdown, see what works and what breaks in Google Docs Markdown.
Two quick fixes for the content that breaks:
- To turn Markdown into rich text that survives the paste, including tables, use Markdown to Google Docs.
- To clean up messy or mixed AI output before pasting, run it through paste to Markdown. This comes up constantly because AI assistants output Markdown by default.
When enabling the setting is not enough
The setting is built for one-time conversion. It does nothing for the case where the source keeps changing:
- Your source of truth is a Markdown file in a repo, and teammates edit the Google Doc.
- An agent regenerates the Markdown on every run.
- You want comments and edits from the Doc reflected back into your local file.
In all three cases you end up pasting in one direction, then the other, by hand. The conversion was never the hard part; keeping two copies in agreement over time is. That is the gap md2gd closes: it keeps a local Markdown file and a real Google Doc in sync both ways, so the Doc stays a native, commentable document and the Markdown stays your source of truth.
FAQ
Where is the Enable Markdown setting in Google Docs? Open Tools, then Preferences, and check Enable Markdown. It is a per-account setting and applies to all your documents on that account once enabled.
Why is Markdown not working after I enabled it?
The most common reason is using a normal paste. Markdown text has to be inserted with the right-click Paste from Markdown option, not Ctrl+V. Tables and code blocks also do not convert even with the setting on.
Does Markdown work in the Google Docs mobile app? The Markdown paste and import behavior is a desktop web feature. Use Google Docs in a browser for reliable Markdown handling.
How do I paste a Markdown table into Google Docs? Native paste does not build the table. Convert the Markdown to rich text first with Markdown to Google Docs, which preserves tables, then paste the result.
The short version
Enabling Markdown in Google Docs takes four clicks under Tools, then Preferences. That gets you live formatting, a right-click paste, and .md import and export. It will not give you tables, code blocks, or a document that stays current after the source changes. For the parts the native feature drops, start with the free tools, and reach for two-way sync when the copy-paste loop becomes the bottleneck.