What Google Docs does with a Markdown file, and where a web page fits

Google Docs takes Markdown through File, then Import, or a paste with the Markdown option switched on, and that is the door this page is about. The question worth asking is what a web page looks like by the time it arrives, because Google Docs never sees the page itself. It sees whatever the conversion handed over, and nothing else.

Google Docs maps headings onto its own named styles, which is what makes the outline pane work. What comes out of a web page here is the article text as headings and paragraphs, with the links rewritten as Markdown links rather than dropped, so the structure Google Docs is looking for is actually present instead of merely implied. That is the entire trick, and there is nothing clever underneath it.

What survives from a web page into Google Docs

The conversion drops navigation bars, cookie banners, related article rails and the newsletter box before Google Docs ever sees them, because none of it carries meaning into Google Docs and all of it costs something. What it keeps is the part you would otherwise have retyped by hand.

• The real title of the page comes through, not the title the tab was showing, and Google Docs receives it as structure rather than as something to infer.
• The body text arrives in reading order, with its heading levels intact, which is the part Google Docs would otherwise have to reconstruct on its own.
• Links are rewritten as Markdown links instead of being flattened into bare words, so nothing downstream of Google Docs has to guess at it.

What Google Docs never gets back from a web page

Every conversion costs something, and a page listing only the gains is a sales page. Here is what a web page gives up on the way to Google Docs, stated plainly enough that you can decide against it.

• The layout goes, and with it every image that carried no text of its own, and Google Docs will not get it back from anywhere.
• Anything the page draws after the first paint may never be seen at all, so nothing you build in Google Docs should depend on it.
• Whatever sits behind a paywall was never sent to us, so it cannot be recovered, which is a real cost inside Google Docs and not a rounding error.

The URL to Markdown step behind this Google Docs page was measured

our extraction layer does the conversion, and it was proven end to end on 30 August 2026: a live page came back in Markdown carrying its real title, its real text and its converted link, with the cache switched off so nothing was recycled. That is one run on one day and not an average, which is exactly why the date travels with the claim instead of being left out of it. The same output is what Google Docs would have received.

A page that assembles itself in the browser can come back thinner than it looks, and nothing in the output says which part never arrived. Google Docs has no way of telling you any of that from the inside, so it gets said here instead, on the page that sent you there.

Once the page is Markdown, what to do inside Google Docs

With the Markdown in hand, check the outline pane immediately, because a heading that landed as body text is invisible otherwise. That is a Google Docs habit rather than a conversion setting, and it is where most of the value of converting a web page in the first place actually lands.

The constraint worth knowing before you start: once imported the document is no longer Markdown, and the export back out is an approximation. It bites the same way whether the Markdown came out of a web page or out of something else entirely, but it bites hardest on long documents, which is what a web page usually is.

What we will not pretend about URL in Google Docs

• Google Docs will not keep a fenced code block as code, and converting a web page first does not change that in the slightest.
• the paste path and the import path do not produce the same document, which is a Google Docs behaviour rather than anything the page conversion did.
• The conversion costs half a credit and the price is shown before the page is sent, whether the Markdown ends up in Google Docs or nowhere at all.