Markdown to Google Docs

Why pasting Markdown into a Google Doc does nothing

Google Docs has never had a Markdown import worth the name. Paste a document you wrote in Markdown and Docs treats it as what it literally is — a wall of plain characters. The hashes stay hashes, the asterisks stay asterisks, and the table you were rather proud of arrives as a row of pipes.

Before — what a plain paste gives you
## Quarterly review
The **median** sync time fell to 385 ms.
| Metric | Q2 | Q3 |

After — what a rich-text paste gives you
Quarterly review          ← styled as Heading 2
The median sync time fell to 385 ms.   ← median in bold
Metric  Q2  Q3            ← a real 3-column table

The fix is not to fight Docs but to hand it something it already understands. There are exactly two routes that work reliably, and this tool does both.

Route one: paste as rich text

A clipboard can carry the same content in several flavours at once. When you copy from a web page, the browser puts both a text/plain version and a text/html version on it; the app you paste into picks whichever it prefers. Google Docs prefers the HTML, and maps it onto its own styles.

That is all the Copy for Google Docs button above does. It renders your Markdown to HTML, writes that HTML to the clipboard alongside the original text, and lets Docs do the rest. Paste with ⌘V or Ctrl+V and the formatting is simply there. The one thing to avoid is Paste without formatting — that menu item, and ⌘⇧V, deliberately take the plain flavour and throw the other one away.

Route two: import a .docx

For a long document, a file is steadier than a clipboard. Press Download .docx and you get a real Word document with styled headings, lists, tables and code blocks. In Docs, use File → Open → Upload; or drag the file into Drive, right-click it and choose Open with → Google Docs. Docs converts it on the way in, and you end up with a native document rather than a pasted block.

The same file works in Word, Pages and LibreOffice, which is why the Markdown to Word converter is the same machinery pointed at a different destination.

What about Google Docs’ own Markdown support?

It exists, and it is worth knowing what it covers before you decide you do not need a converter. Under Tools → Preferences there is an Automatically detect Markdown checkbox. With it on, Docs converts a handful of patterns as you type them: # plus a space becomes a heading, * plus a space starts a bullet, **bold** and *italic* resolve when you close them, and [text](url) becomes a link.

Two limits matter. It is a typing feature, so it does very little for text that arrives by paste; and it has no notion of tables, blockquotes or fenced code blocks. Recent versions of Docs have also gained a paste handler that recognises some Markdown, and an export path at File → Download → Markdown that is genuinely good — useful if you want to go the other way. But for moving a finished document into Docs, none of it is dependable enough to plan around, particularly the moment a table is involved.

What survives, and what does not

Headings are the important one. They do not merely come across bigger and bolder — they land as Docs’ own Heading 1 through Heading 6 styles, which is what makes the document outline in the left sidebar populate and what an inserted table of contents reads from. Along with them: bold, italic, strikethrough, links, ordered and unordered lists including nested ones, blockquotes, tables with their header row, and inline and fenced code in a monospace face.

Four things do not. Images written as ![alt](https://…) are not fetched — Docs will not pull a remote file in on your behalf, so add those by hand. Footnotes, which are not standard Markdown anyway, arrive as plain text. Maths in $…$ or $$…$$ stays as typed. And syntax highlighting inside code blocks is lost, because Docs has no concept of a code block to highlight — you get monospace text on a light background, which is usually enough.

Which route to pick

Pasting is right for a section: a set of release notes into a running document, a table into a report, an outline into a brief someone else started. It is instant, it drops in at the cursor, and it leaves the rest of the document alone.

The .docx import is right for a whole document, and it is the one to reach for when there are several tables, deeply nested lists, or a colleague on a browser whose clipboard behaves oddly. It costs you one extra step and gives you a cleaner result. If you are coming from the other direction — a Word file or a web page you want as Markdown — Word to Markdown and HTML to Markdown do the reverse trip.

Or start in Markdown and stay there

Converters exist because the notes and the document live in different formats. Bulguritto removes that gap for the notes half: every note is a plain .md file on disk, synced between iPhone, iPad and Mac, edited with real headings and real tables rather than raw syntax. It is free, and when something does need to become a Google Doc, the copy button above is still one press away.