Google Drive and Docs Now Handle Markdown Natively

For years Markdown and Google Docs lived in separate worlds. Developers kept READMEs, documentation and notes as .md files in Git or Obsidian, everyone else wrote in Docs, and moving text between the two meant converting it and fixing whatever broke. In October 2026 Google finally connected them: Google Docs can open and edit .md files directly, and Google Drive shows them rendered.

The key detail is in Google’s help article: the file is not converted to a Docs document. It stays a Markdown file in Drive, and Docs acts only as the editor.

How to use it

There’s nothing to switch on. Upload a .md or .markdown file to Drive and you have two options:

• Preview. Right-click the file and choose Open with → Preview. Drive shows the formatted text with clickable links and tables, and you can toggle between raw Markdown and the rendered view.
• Edit. Double-click the file to open it in Docs. It opens in Markdown Mode, marked with an .md label next to the document title.

In Markdown Mode you get the normal Docs experience: several people editing at once, comments and sharing. When you’re done, the file in Drive is still plain Markdown that any other tool, script or Git repository can read.

What Docs features don’t survive

Markdown is plain text with a little structure, so it can’t store everything a Docs document can. According to Google, these change when you edit a .md file:

• Font colours, highlights and text alignment are removed.
• Smart chips become plain text or links.
• Pasted web formatting turns into plain text.

If an edit breaks something, File → Version history takes you back. In practice this matters only if you try to use a Markdown file like a styled document. For notes, specs and documentation, headings, lists, links and tables are what you need, and those stay.

What was wrong with the old way

Docs has had some Markdown support for a while, such as typing shortcuts and importing or exporting .md files. The problem was that import created a separate Docs copy. You edited that copy, then exported it again, and the round trip regularly changed formatting, dropped comments or left two versions of the same text in different places.

Native editing removes the copy, and with it the question of which version is the current one. That’s the change that makes Markdown in Drive usable for teams, not just for one person converting a file once.

Why Google is doing this now

Markdown used to be a developer thing. Today it’s the default output of practically every AI chatbot, the format of agent instruction files such as AGENTS.md or CLAUDE.md, and the storage format of tools like Obsidian. Google’s Chandu Thota described it, as quoted by 9to5Google, as “the common language between humans and AI agents.”

That’s the real motivation. If a person edits a file in Docs and an AI agent reads and updates the same file, neither side has to convert anything. This site is written in MDX, Markdown with components, so I’m firmly in the group that welcomes it.

Availability

The rollout started on October 5, 2026, and Google says it can take up to 15 days to reach everyone. It covers personal Google accounts and all Workspace editions. 9to5Google notes that it’s on by default even on admin-managed accounts, and according to the Workspace Updates announcement there’s no admin control or user setting to turn it off.

Who benefits

The biggest winners are mixed teams. A developer can keep documentation in Markdown while a product manager or writer comments on it in Docs, without anyone learning Git or converting files. The same goes for Obsidian users who want to share a note, and for anyone preparing texts that end up on a static website.

What’s still missing is support for things Markdown power users rely on, such as front matter or embedded images. If Google adds those, Drive could become a reasonable place to edit content for static sites and documentation portals, not just a place to share it.