A documentation file can feel straightforward to its author and uninviting to the person asked to review it. Google Docs now lets people edit that same Markdown file visually and add comments without converting it into another document format. Drive also offers a formatted preview.

Google Workspace announced the change on October 5, with a gradual rollout of up to 15 days for Workspace customers and personal accounts. This is an update from earlier this month, rather than a launch today.

Markdown remains the working file

Markdown uses text markers to represent headings, lists and links. It is common in software documentation and material used by AI tools. The change is in the review workflow: Docs acts as the editor, while the file stored in Drive keeps its .md or .markdown extension.

That can remove a familiar source of friction. Consider a team writing a specification in Markdown that needs feedback from someone who does not use a code editor. Converting it into Docs, reviewing it and transferring the content back adds opportunities for copies to diverge. Keeping the format makes it easier to organize collaboration around the same file.

The team still needs to decide which copy is authoritative. If the document also lives in Git, a Drive review does not remove the need to bring changes back into the repository. Collaborative editing and version control solve different problems.

Opening a file and checking formatting

The Google help page explains that users can upload a file to Drive and double-click it to open it in Docs. An .md label beside the title identifies Markdown mode. Drive's preview lets readers switch between Markdown text and the formatted view.

Some Docs-specific formatting changes along the way. Smart chips become text or links; font colors, highlights and alignment are removed; HTML formatting becomes plain text. Version history provides a way to restore the original.

For reviewing requirements or project instructions, that may be a reasonable tradeoff. For a document whose meaning depends on colors or a particular layout, inspect the result before replacing the working copy.

If you regularly send Markdown files to someone for review, start with a representative file containing a table, links and code snippets. Open the output in its eventual destination too. The benefit is a simpler conversation that preserves the content along the way.

Official sources in English. Announcement dated October 5, 2026; documentation checked on October 27, 2026.