> ## Content Index
> Fetch the complete content index at: https://blog.harshkohli.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Google Docs Can Now Edit Markdown Files Natively
- URL: https://blog.harshkohli.com/google-docs-markdown-files-native-editing/
- Published: 2026-10-27T09:02:28.000Z
- Updated: 2026-10-27T09:02:28.000Z
- Description: Google Docs now opens .md files without converting them, with comments, live editing and rendered previews in Drive. Here is how it works.
- Author: Harsh Kohli
- Tags: Tech News, Software

I've lost count of how many times I've pasted a README into Google Docs and watched it turn into a mess of stray asterisks and broken tables. Google has finally fixed that. Docs can now open and edit Markdown files as Markdown, and the rollout should be reaching most accounts this week.

## What happened

Google first [announced the feature on its Workspace Updates blog](https://workspaceupdates.googleblog.com/2026/10/preview-edit-and-collaborate-on-Markdown-files-natively-across-Drive-and-Docs.html?ref=blog.harshkohli.com) on October 5, with a gradual rollout of up to 15 days. On October 26 it followed up with a longer [post on the Google Developers Blog](https://developers.googleblog.com/preview-edit-and-collaborate-on-markdown-md-files-natively-in-google-docs-and-drive/?ref=blog.harshkohli.com) saying anyone with a Google or Workspace account can now try it.

Here's how it works. Upload a .md or .markdown file to Drive and double-click it. It opens in Docs in a Markdown mode, with a small .md badge next to the title. You edit the formatted text the normal way, and the file stays a Markdown file in Drive, so nothing gets converted to a Google Doc. Comments, sharing and live co-editing all work. Drive also gets a rendered preview with clickable links and proper tables, plus a toggle to see the raw text.

The [Google Docs help page](https://support.google.com/docs/answer/18289341?hl=en&ref=blog.harshkohli.com) lists a few catches. Smart chips turn into plain text or links, and font colours, highlights and text alignment get removed, because Markdown can't store them. If something breaks, Version history gets the old copy back.

## Why it matters

Markdown is everywhere now. Project docs on GitHub use it, and most AI chatbots and coding agents write their answers in it. Until now, getting those files into Docs meant a lossy import, and getting them back out meant cleaning up by hand. Google is openly pitching this as a way for people and AI agents to work on the same file, which tells you where it thinks documents are heading.

For me the bigger win is the boring part: a teammate who has never typed a pound sign for a heading can now review and comment on a README without me sending them a PDF.

## What to do

- Drop any .md file into Drive and double-click it. If it still opens as plain text, the rollout probably hasn't reached your account yet.
- Don't add colours or smart chips to files that also live in a code repo. They'll be stripped when the file saves.
- If you run AI models locally and save their answers as Markdown, you can now share them straight from Drive. My [LM Studio guide](https://blog.harshkohli.com/run-deepseek-llama-locally-lm-studio-windows/) shows how to set that up.

There's no admin switch or user setting for this. It just shows up once your account gets it.