Google Docs Now Edits Your .md Files — Check What It Rewrites Before You Open Your Notes There

As of October 5, 2026, double-clicking a .md file in Google Drive opens it for editing in Google Docs — and saves changes back to the same .md file.¹ Google documents three classes of rewrites that can occur during an edit session.² Run the pre-flight below before you open any notes file you care about.

The feature is rolling out gradually — Google states "Gradual rollout (up to 15 days for feature visibility) starting on October 5, 2026,"³ so some accounts will see it before others through the end of October. It reaches all Google Workspace customers and users with personal Google accounts, and there is no admin control and no end-user setting to disable it.^{4 5}

"Previously, you needed to import and convert Markdown files into a Doc format, which often altered formatting, stripped comments, and fragmented files," Google wrote in the Workspace Updates announcement.⁶ The new Markdown Mode is designed to solve that — keeping the file in its original format while rendering it inside Docs.¹

Understanding the distinction matters. Rendering Markdown and preserving it are different operations. What follows is what Google has documented about the three changes that happen, what Google has not addressed, and the steps to check your files before you expose them.

What Google says happens to your file

Your .md file stays a .md file — it does not convert to Google Docs format. But three classes of content can be rewritten during an edit session: smart chips become text or links, HTML web formatting becomes plain text, and font colors, highlights, and text alignment are removed. All three are documented by Google.²

The third item — "Web formatting (.HTML) turns into plain text" — may affect more than Docs-native formatting. CommonMark, the specification that formalizes Markdown syntax, defines raw HTML as valid Markdown: "An HTML block is a group of lines that is treated as raw HTML (and will not be escaped in HTML output). There are seven kinds of HTML block."⁷ Whether raw HTML already in your Markdown source file is treated identically to Docs-inserted HTML formatting is not explicitly stated. The safest working assumption is that it might be.

"Text between < and > that looks like an HTML tag is parsed as a raw HTML tag and will be rendered in HTML without escaping," per CommonMark Spec 0.31.2 §6.6.⁸ If your Markdown files contain inline HTML — image tags, <details> blocks, <br>, <mark>, or HTML comments — treat those as at-risk until you can test.

Google also notes: "You can keep your comments and formatting when you reopen your document in Google Docs or in other tools."² The word "comments" in that sentence is ambiguous: standard Markdown has no comment syntax, so what constitutes a "comment" in this context is unclear. Treat this as an open question and verify in your own test.

What Google has not documented

Several Markdown syntax classes common in personal notes have no stated behavior in Google's documentation for this feature. For each one below, the honest answer is: not documented — test it on a copy before opening originals.

Syntax with no documented behavior as of 2026-10-07:

• YAML front matter — a --- delimited block at the top of a file, used by note apps and static-site generators to store metadata. Google's help page makes no mention of it.
• Footnotes — [^1] reference syntax, supported by many Markdown processors. Not addressed.
• WikiLinks — [[note-name]] link syntax, the core cross-reference format in Obsidian-style systems. Not addressed.
• Task lists — - [ ] and - [x] checkboxes from GitHub-Flavored Markdown. Not addressed.
• HTML comments — <!-- comment -->, sometimes used for hidden metadata. Falls near the HTML boundary but is not specifically addressed.

Absence from Google's documentation is not confirmation of safety. It means the behavior is unconfirmed in either direction.

The computer scientist's framing of this problem comes from lens theory, which studies editors that read and write the same data. A re-serialising editor is well-behaved only if it satisfies the GetPut law: "put l (get l s) s = s" — writing back what you read gives you back what you started with.⁹ The 2007 paper that established lens laws also noted that "lenses may have complex side effects when applied to schemas or other structured data."¹⁰ A Markdown file with YAML front matter and wikilinks is structured data by any reasonable definition.

The Pandoc documentation puts the practitioner's version of the same point plainly: you "should not expect perfect conversions between one format and another."¹¹

The pre-flight: grep before you open

Before opening a .md notes file in Google Docs, two minutes of terminal work tells you whether your file contains any of the at-risk syntax classes. Run these commands on your notes folder, make a copy to test, then diff. Do not test on an original you cannot afford to lose.

Step 1 — Find files with at-risk syntax.

# Inline HTML tags (images, details, br, mark, comments, etc.)
grep -rl "<[a-zA-Z/!]" ~/notes --include="*.md"

# YAML front matter (files that open with ---)
grep -rl "^---" ~/notes --include="*.md"

# WikiLinks
grep -rl "\[\[" ~/notes --include="*.md"

# Footnote references
grep -rl "\[\^" ~/notes --include="*.md"

Any file returned is a candidate for testing before you open it in Docs.

Step 2 — Copy and test.

Upload a copy of the file to Drive (or duplicate it inside Drive). Open the copy in Google Docs, make a small edit, save, and then download the file or open it in a plain-text editor. Diff it against your original:

diff original-notes.md downloaded-copy.md

An empty diff means the round-trip preserved your file for that specific content. A non-empty diff shows you exactly what Docs changed — before it happens to your real notes.

Step 3 — Check the three documented classes specifically.

Before editing any file in Docs, confirm whether it contains:

• Smart chips (rare in hand-authored Markdown; possible in a file previously edited in Docs by a collaborator)
• Raw HTML blocks, inline tags, or HTML comments
• Any Docs-specific formatting from a previous Docs session

Step 4 — Keep your own copy.

Whether or not the pre-flight passes, keep a plain-text copy of your notes folder on your own device. A file on your device is diffable at any time, requires no network connection, and cannot be changed by a cloud service without your knowledge.

How to recover if something was rewritten

If you open a .md file in Google Docs and find that content was changed, the Version history path gives you a way back — with two limitations you should know before you rely on it.

To restore: In Google Docs, go to File → Version history → See version history. Select a version from before the edit and restore it.¹²

Limitation 1 — retention for .md files is undocumented. Google Drive Help states that versions of non-Google files are "deleted after 30 days or after 100 newer versions are saved."¹³ That policy applies to non-Google files generally. Whether a .md file under Markdown Mode is treated as a Google file (and potentially subject to longer retention) or as a non-Google file (30 days / 100 versions) is not explicitly documented. If you are working in a heavily-edited file or returning after a month, the version you want may no longer be there.

Limitation 2 — deletion is irreversible. Google's documentation is direct: "Deleting version history is permanent and can't be undone."¹⁴ If a collaborator has cleared version history, or if you are past the retention window, the restore path is closed.

You can name up to 40 versions per document to mark states you want to preserve long-term.¹² Even so, your own local copy — a plain .md file on your device — is the only recovery path that does not depend on Drive's retention policy.

How this looks in a local-first notes setup

An editor that renders Markdown is not the same as an editor that preserves it. The distinction becomes concrete the first time an editor re-serialises a file on save — which Markdown Mode does, by design. "Markdown is a standard text format widely used by Large Language Models (LLMs) to preserve structured content," Google notes in the same announcement,³ and the new mode is framed partly around enabling people and agents to "collaborate without forcing anyone to write raw syntax."⁶

What that framing leaves implicit is the writer's side of the contract: if the tool abstracts syntax away, it must abstract it losslessly for files that contain syntax classes outside its documented scope. The pre-flight above tests that contract on your specific files.

For readers who want data on how note apps handle the inverse scenario — how faithfully they import Markdown files you bring in — MNMNOTE's import-fidelity roundup tests exactly that. For the export direction, the export-fidelity roundup covers what happens when Markdown leaves an app. Both are the complement of this scenario: in-to-app and out-of-app, not in-place editing.

If your notes are plain .md files stored locally on your own device, the diff workflow above is always available. No conversion step occurs unless you choose to open the file in an editor that re-serialises. You can see what changed, and you decide what to keep.

Frequently Asked Questions

Does Google Docs change my Markdown file when I open it?

The file stays a .md file in Drive and does not convert to Google Docs format. However, Google documents three changes that can occur during an edit session: smart chips become text or links, web formatting (HTML) becomes plain text, and font colors, highlights, and text alignment are removed. Open a copy first to test your specific file.²

Is it safe to edit a .md file in Google Docs?

Not without a pre-flight check. Three syntax classes are documented as changed by Google. Several others — YAML front matter, footnotes, wikilinks, task lists, and HTML comments — are not mentioned in Google's documentation, which means their behavior is unconfirmed. Test on a copy, diff the result, and keep your own plain-text backup outside Drive.

What does Google Docs Markdown mode change specifically?

As documented by Google: smart chips become text or links; web formatting (.HTML) becomes plain text; font colors, highlights, and text alignment are removed.² Raw HTML already in your Markdown file falls near the HTML boundary — whether it is treated identically to Docs-inserted HTML formatting is not explicitly stated. Test on a copy before assuming either outcome.

How do I open Obsidian notes in Google Docs?

Double-clicking a .md file in Drive opens it in Markdown Mode in Google Docs. The file remains a .md file.¹ Obsidian-specific syntax — wikilinks ([[note-name]]), YAML front matter, callouts, and %%comment%% blocks — is not addressed in Google's documentation. Treat those as untested and run the pre-flight before opening notes you cannot afford to lose.

How do I restore a Markdown file after Google Docs edited it?

In Google Docs, use File → Version history → See version history to find a save from before the change.¹² Note that version retention for .md files is not explicitly documented — Drive's general policy for non-Google files caps it at 30 days or 100 versions.¹³ Keep your own local backup as your primary safety net.

Can an admin disable Google Docs Markdown editing for a workspace?

No. As of the October 5, 2026 announcement, there is no admin control for this feature, and there is no end-user setting.⁵ All Google Workspace customers and personal account users receive it as part of a rollout that runs for up to 15 days from October 5.³

The only file that cannot be rewritten without your knowledge is one you keep on your own device.

Keep your notes as plain Markdown files, stored locally — no conversion step, no surprises. mnmnote.com