2026-10-21 Google Docs now edits Markdown files natively

Canonical version: 2026-10-21 Google Docs now edits Markdown files natively.

Google Docs can now open, edit and share Markdown files without turning them into Google Docs. You double-click a .md file in Google Drive, it opens in Docs, and it stays a .md file. Drive also gets a rendered preview for Markdown files.

I spotted it in a thread on r/ObsidianMD, then went to Google's own announcement and Help Center article for the details. This matters to me because I keep my knowledge in Markdown files in Obsidian, and sharing those notes with people who don't use Obsidian has always meant converting them first.

What changed

Google announced it on the Workspace Updates blog on 5 October 2026: you can "view, edit, and collaborate on Markdown (.md or .markdown) files directly in Google Docs, as well as view rendered previews in Google Drive."

According to the Help Center, here's how it works:

• Preview in Drive. Right-click a .md file, then Open with > Preview. The viewer lets you switch between the raw Markdown and the rendered preview, with clickable links and formatted tables.
• Edit in Docs. Double-click the file and it opens in "Markdown Mode", with an .md tag next to the title. Google is explicit about it: "Your file does not convert to a Google Docs file. It stays an .md file, kept in Drive."
• Collaborate. Sharing, comments and real-time co-editing work on the .md file. Google says you keep "your comments and formatting when you reopen your document in Google Docs or in other tools."

There's no admin control and no user setting (it's simply on). The rollout started on 5 October 2026 for both Rapid Release and Scheduled Release domains, with up to 15 days for the feature to show up. It's available to all Google Workspace customers and to personal Google accounts, so by now most people should have it.

Google justifies the feature with AI: Markdown "is a standard text format widely used by Large Language Models (LLMs)", and the feature lets "both users and agents" collaborate on the same file. Before this, you had to import and convert Markdown into a Doc, which (Google's words) "often altered formatting, stripped comments, and fragmented files."

What gets lost

The Help Center lists a few Google Docs features that don't survive in a Markdown file:

• Smart chips become plain text or links
• Web (HTML) formatting becomes plain text
• Font colors, highlights and text alignment are removed

If an edit breaks something, File > Version history gets you back to the previous version.

Google lists nothing else. It doesn't say which Markdown flavor Docs reads and writes (CommonMark? GitHub Flavored Markdown (GFM)?), and it doesn't mention code blocks, task lists, footnotes or YAML frontmatter at all. Tables are the only extended feature it names, in the Drive preview. I haven't found anything on mobile support either.

How it relates to the older Markdown features

Docs has had some Markdown support for a while, and it's easy to mix things up:

• 2022: Markdown autocorrect. Since March 2022, Tools > Preferences > Automatically detect Markdown turns # headings, bold, italic, strikethrough and links into formatting as you type. Bullets and checkboxes already worked that way before.
• 2024: conversion in and out. Since July 2024, you can paste from Markdown, copy as Markdown, export a Doc via File > Download > Markdown (.md), and import a .md file as a Doc. Import and export are on by default; copy and paste need Enable Markdown in the preferences.

All of those convert. You start from Markdown and end up with a Google Doc (or the other way around), and every round trip goes through a conversion. The new Markdown Mode is the first time the .md file itself is what you edit and share.

Why I care

I strongly believe in the File over app principle: the files you create matter more than the tools you use to create them. Markdown is the format that makes this work in practice, because almost every tool can read it. My notes live in Obsidian today, but they're plain .md files, and I could open them with anything tomorrow.

The weak spot has always been collaboration. Most people I'd ask to review a note or co-write a document don't use Obsidian, and a lot of people do their writing in Google Docs. Until now, the options were to send a PDF, convert to a Doc and copy the changes back by hand, or ask them to edit raw Markdown. Picking files over apps meant trading real-time collaboration for durability and Data Ownership.

With this change, the file can stay the same file. You put a .md note in Drive, share it, your collaborators comment and edit in a familiar interface, and you get a .md file back. Each person works in the app they prefer, and nobody has to convert anything.

It also confirms something I've been saying for a while: Markdown has become the shared format between humans and AI. Google now justifies a Docs feature by pointing to LLMs and agents, and a few years ago Markdown was mostly a format for developers and note-taking nerds.

What to check before sharing your vault notes

Obsidian notes aren't pure CommonMark. They use Obsidian Flavored Markdown, and Google's documentation says nothing about those extensions. So treat the following as open questions and test them on a copy before you share anything important:

• Wikilinks. **Note** links only make sense inside the vault. In Docs, I'd expect them to show up as plain text at best. See Obsidian Wikilinks.
• Embeds and callouts. `` embeds and > [!note] Obsidian Callouts aren't mentioned either. My guess is that they come through as plain text or a quote block, and that embeds don't show the embedded content.
• Properties. Google doesn't mention YAML frontmatter. Check whether Obsidian Properties survive an edit as they were.
• What Docs writes back. Even when a feature survives, Docs may rewrite the syntax when it saves (list markers, emphasis style, escaping, line breaks, table formatting). Compare the file before and after an edit with git diff or any diff tool.
• Comments. Google says comments are kept, but not where they're stored. Check whether they end up in the file or only in Drive.

My advice: start with a simple note (headings, lists, links, a table) and do one full round trip. Upload it, edit it in Docs, download it and diff it. If your vault syncs through Google Drive, be even more careful: whatever Docs saves lands directly in your vault.

Each tool that reads and writes .md files natively makes plain-text notes more useful, and Google Docs is one of the most widely used editors out there.

That's it for today! ✨

References

• Google Workspace Updates, "Preview, edit and collaborate on Markdown (.md) files natively across Drive and Docs" (2026-10-05): https://workspaceupdates.googleblog.com/2026/10/preview-edit-and-collaborate-on-Markdown-files-natively-across-Drive-and-Docs.html
• Google Docs Help, "View and edit Markdown (.md) files in Google Docs": https://support.google.com/docs/answer/18289341
• Google Docs Help, "Use Markdown in Google Docs, Slides, & Drawings": https://support.google.com/docs/answer/12014036
• Google Workspace Updates, "Import and export Markdown in Google Docs" (2024-07-16): https://workspaceupdates.googleblog.com/2024/07/import-and-export-markdown-in-google-docs.html
• Google Workspace Updates, "Compose with Markdown in Google Docs on web" (2022-03-29): https://workspaceupdates.googleblog.com/2022/03/compose-with-markdown-in-google-docs-on.html
• r/ObsidianMD thread where I spotted the news: https://www.reddit.com/r/ObsidianMD/comments/1wyw49q/google_docs_now_natively_supports_md_files/

Related

• Markdown
• Obsidian Flavored Markdown
• File over app principle
• Obsidian
• Obsidian Wikilinks
• Obsidian Callouts
• Obsidian Properties
• Data Ownership
• CommonMark
• GitHub Flavored Markdown (GFM)

About Sébastien

Ready to get to the next level?