Google Docs now edits Markdown files natively, and Drive renders them
Google is letting users open, edit and comment on Markdown files directly in Docs and see rendered previews in Drive, with no admin control or end-user setting.

Google Docs can now open and edit Markdown files without converting them, and Google Drive shows them as rendered previews. Google said the feature covers .md and .markdown files and has no admin control and no end-user setting.
Google announced the change in an Oct. 5, 2026, Workspace Updates blog post. It tagged the post Rapid Release and Scheduled Release.
Docs now opens Markdown files as they are
Google said users can view, edit and collaborate on Markdown files directly in Docs. It described Markdown as “a standard text format widely used by Large Language Models (LLMs) to preserve structured content, like tables, headers, and bulleted lists, without the bulk of heavy file formats.”
Google said users previously had to import and convert Markdown files into a Doc, which “often altered formatting, stripped comments, and fragmented files.” Users can now open, edit and collaborate on the files without changing the file type.
Google said editing Markdown in Docs lets both users and agents collaborate on the same file. It said nobody has to write raw syntax or convert files by hand. Docs’ real-time editing and commenting tools stay available.
Drive displays Markdown as formatted documents
Google said Drive now renders Markdown files as formatted documents. Links are clickable and tables display with their structure.
The rollout is gradual and open to all accounts
Google said the rollout began Oct. 5, 2026, on both Rapid Release and Scheduled Release domains. Google said the feature can take up to 15 days to become visible.
Google said all Google Workspace customers and users with personal Google accounts get the feature. It pointed readers to its Help Center page “View and edit Markdown (.md) files in Google Docs.”
A Markdown file from an agent can be commented on as is
Google’s own description ties the feature to LLM output and to agents sharing files with people. We think the practical effect is that a Markdown file an agent writes can be opened and commented on in Docs without a conversion step.
