Apps

Google Docs now edits Markdown files natively, no conversion

· Geeknewz Author

Close-up of a code editor file tree showing JavaScript and JSX file names

If you keep notes, READMEs or chatbot output in Markdown, Google Docs just got a lot less fussy about it. Google said on October 5 that Docs can now open, edit and collaborate on .md and .markdown files directly, without turning them into a Google Doc first, and that Drive will show a rendered preview of those files with clickable links and formatted tables. It's rolling out gradually to Workspace customers and personal Google accounts, and Google says it can take up to 15 days to show up.

The key detail is in Google's help page: your file stays an .md file. Before this, opening Markdown in Docs meant importing and converting it, which Google itself admits "often altered formatting, stripped comments, and fragmented files." Now Docs acts as an editor on top of the original file, with sharing, comments and real-time co-editing working as they do on any other Doc.

How it works

According to Google's help center, you upload an .md file to Drive and double-click it. It opens in Docs in what Google calls Markdown Mode, with a small .md tag next to the title. In Drive itself, you can right-click a file, choose Open with Preview, and flip between the raw Markdown and the rendered version at the top of the viewer. Paul Thurrott notes that you can edit either in Docs' usual visual mode or in raw Markdown syntax, so people who like typing asterisks and pound signs aren't forced out of it.

There's no admin control and no user setting, so it simply appears once the rollout reaches your account. That's convenient, though it also means IT teams can't hold it back.

What still gets lost

Markdown is a plain format, and some Docs features don't survive the trip. Google lists three: smart chips turn into plain text or links, web (HTML) formatting becomes plain text, and font colors, highlights and text alignment are removed. If you apply one of those by habit and it disappears, File, then Version history, gets you back to the earlier state. In practice, that means you'll want to keep anything that relies on colored callouts, @-mentions of files or people chips, or carefully centered headings in a regular Google Doc.

How Docs got here

This is the third step in a slow Markdown story at Google, and it helps to see them side by side.

WhenWhat Docs addedWhat it meant for your .md files
March 2022"Automatically detect Markdown" in Tools, Preferences, off by defaultTyping Markdown shortcuts formatted text as you wrote, but nothing read or wrote .md files
July 2024Import and export Markdown, plus optional Paste from Markdown and Copy as MarkdownYou could bring a file in or download one out, but every import became a separate Google Doc
October 2026Native editing in Docs and rendered previews in DriveThe .md file stays an .md file while you and your collaborators edit and comment on it

Google is unusually direct about why it's doing this now. Its announcement describes Markdown as "a standard text format widely used by Large Language Models" and says native editing lets "both users and agents" work on the same file without anyone handling manual conversions. Most AI chatbots answer in Markdown by default, and AI coding tools tend to keep their instructions and notes in .md files, so plenty of those files are already landing in people's Drives.

Who should care

Our take: this is most useful if you write documentation that lives in a code repository, if you keep a Markdown notes folder that syncs to Drive, or if you regularly save chatbot answers and then clean them up with a colleague. Being able to comment on a README with a teammate without breaking it for GitHub is a real quality-of-life fix.

If your documents depend on rich formatting, nothing changes for you, and you should keep them as normal Docs. And if you're a heavy Markdown user with a dedicated editor you love, this probably won't replace it, but it does mean you can finally share a file with someone who only uses Docs and get comments back on the same file instead of a converted copy.

Source: Google Workspace Updates and the Google Docs help page, with reporting from The Verge and Thurrott.com. History: Google's 2022 and 2024 Workspace posts.