Google Docs Markdown: Enable, Paste, Import, and Export Markdown

Google Docs Markdown support comes in four parts: autoformat as you type, Paste from Markdown, importing a .md file, and exporting one. Autoformat and the paste and copy commands are off until you tick Enable Markdown under Tools, then Preferences. Import and export work without any setting. This guide covers all four paths, what Google documents for each, and what to check on each one.

How Do I Enable Markdown in Google Docs?

Open any document on the web, go to Tools, choose Preferences, and tick Enable Markdown on the General tab. Google's help page documents the path, and the July 2024 Workspace update confirms that the copy and paste commands ship disabled while import and export are on by default. The setting lives in your preferences rather than in the document, so a shared Doc doesn't carry it to other editors.

With the box unticked, Docs may still convert a typed # Heading and show a "Previewing Markdown formatting" prompt with an Enable Markdown button. That is a one-off nudge to switch the feature on; bold and italic markers stay as literal text until you do.

The right-click menu has no Markdown entries while the box is unticked. Paste from Markdown and Copy as Markdown only appear once the preference is on.

Three things the setting doesn't cover. List autoformat (- or 1. at the start of a line) is a separate box in the same dialog, Automatically detect lists. Link detection is another separate box. And the help page describes every step with "on your computer". We couldn't find the preference in the mobile instructions, so treat markdown in Google Docs as a desktop-browser feature.

Which Markdown Syntax Does Google Docs Autoformat?

With the preference on, Docs converts these patterns as you type them, according to the help page:

# Heading 1 through ###### Heading 6
*italic* or _italic_
**bold** or __bold__
***bold italic*** or ___bold italic___
~strikethrough~
[link text](https://example.com)

Note the single tilde for strikethrough; GitHub uses two. The conversion fires when you type the closing marker, so pasting a block of syntax as plain text with Ctrl+V doesn't trigger it.

Tables, fenced code blocks, images, footnotes, blockquotes, and task lists aren't on the list. For those you need one of the other three paths, or a different tool. If you need a literal asterisk, pressing Ctrl+Z (Cmd+Z on a Mac) straight after an autoformat reverts it, as with Docs' other autocorrections.

How Do You Paste Markdown Into Google Docs?

How to paste Markdown into Google Docs: copy the source from wherever you wrote it, right-click in the document, and choose Paste from Markdown. Docs converts the whole clipboard in one pass, which handles multi-paragraph content that autoformat can't.

The reverse command, Copy as Markdown, sits in the same right-click menu: select formatted content, copy it as Markdown, and paste it into a README or a chat window. Both commands need Enable Markdown ticked; they don't appear in the menu at all until it is.

This is the path we prefer for drafts written elsewhere. Write and preview in a Markdown editor, then paste into Docs when you need comments from people who don't want to see syntax. Copy back as Markdown when the review is done. The Notion Markdown guide covers the equivalent workflow for Notion, which handles paste a little differently.

Google Docs Markdown Support Matrix

Google doc Markdown support is documented precisely for autoformat, but Google says nothing about which elements the paste, import, and export converters handle. That gap is where most "google docs import markdown" frustration comes from. The table below separates what the help page guarantees from what you need to test with the sample document further down.

The pattern is simple: anything Docs has a native object for (headings, emphasis, links, lists, tables) is safe, and anything it represents with styling alone (code, quotes) is where the converter may lose information. Google also updates the converters without a changelog, so a round trip that worked last quarter may behave differently today. Our Markdown table guide and code block guide show the syntax the converter expects on the way in, which removes one variable when something fails.

Test Document: Try It in the Editor, Then Paste It Into Docs

Edit the sample below, copy the left pane, and use Paste from Markdown in a Doc to see the conversion for yourself. It contains one of every element from the matrix, so anything Docs drops is obvious.

print('Check whether the fence survives')

Import and Export: .md Files In and Out of Google Docs

Two routes import Markdown to Google Docs from a file. In Docs, choose File, Open, Upload, pick the .md file, and it converts and opens as a new document. In Drive, upload the file, right-click it, and choose Open with, then Google Docs. Both keep the original file untouched and create a separate Doc.

Export is the reverse: File, Download, Markdown (.md). The option sits in the same download list as PDF and EPUB, and it's available without touching Preferences.

The export is the most useful of the four paths for people who live in Markdown. It's the only supported way to get a colleague's Doc into a repository without a third-party tool. Its main weakness is anything Docs represents with styling alone, code above all. Check any technical document after export and re-fence code blocks by hand where the backticks didn't survive.

When the native import loses too much, convert Markdown to Google Docs by way of Word instead. Turn your Markdown into a .docx with the Markdown to DOCX converter, then open that file in Docs. Word import is the older, more mature path, and it carries tables and images through Docs' native objects. The Markdown to Word guide walks through that conversion.

Why Isn't Markdown Working in Google Docs?

Work through these in order (they cover the enable markdown google docs questions we see most):

1. The preference is off. Tools, Preferences, Enable Markdown. It's off by default and stored with your preferences, so a colleague's document doesn't carry the setting with it.
2. You pasted instead of typing. Autoformat only fires as you type the closing marker. For pasted text, use right-click, Paste from Markdown.
3. The syntax isn't supported. Tables, code fences, and images never autoformat. Use paste or import.
4. A space is missing. #Heading doesn't convert; # Heading does. Same for list markers.
5. You're on mobile. The Docs apps don't expose the preference in the help page's instructions; open the document in a desktop browser.
6. You're looking for the add-on's menu. The third-party Docs to Markdown add-on runs in its own sidebar under Extensions. It predates the native support and is a separate feature; the native commands live in the right-click menu and File menu instead.

To turn Markdown off again, untick the same box. Existing formatting stays; only future typing stops converting.

Google Docs Markdown FAQ

Google Docs Markdown is now good enough for the common case: headings, emphasis, links, lists, and tables have native equivalents and move in and out of Docs with the four native paths. Code blocks, images, and footnotes need a manual check or the .docx route. Draft in the editor where you can see the rendered result, paste into Docs for review, and export back to .md when the comments are resolved.