Import and Export Markdown in Google Docs

Original Article ↗ Hacker News Discussion ↗

Google Docs is adding native import and export for Markdown, enabling full round-tripping between rich-text documents and plain-text formats commonly used in code repositories, technical blogs, and LLM workflows. Commenters see this as a major quality-of-life improvement for technical writing and collaboration, especially where teams prefer Docs’ commenting and suggestion tools but need Markdown for publishing, version control, or scientific toolchains like Pandoc. However, some note gaps such as limited code block support, partial rollout, and questions around adherence to CommonMark and advanced features like diagrams or comments in Markdown.

Overall Reception

  • Many commenters are enthusiastic; this removes a big friction point between Google Docs collaboration and Markdown-based workflows (blogs, wikis, static sites, Git repos).
  • Several people say this will significantly improve technical writing workflows, especially where Docs is already the collaboration hub but final artifacts live in Markdown.

Motivations & Use Cases

  • Suspected drivers:
    • LLM workflows: prior copy/paste between Docs and Markdown for prompts or outputs was lossy and annoying.
    • Internal Google workflows: design docs in Docs that later migrate to internal markdown-based wikis.
    • Enterprise demand: large customers needing Markdown import/export for existing processes.
  • Common use cases mentioned:
    • Technical docs stored in GitHub/GitLab but edited collaboratively in Docs.
    • Scientific writing: drafting in Docs then converting via Pandoc/Quarto/Typst/etc.
    • Blog and release notes: draft in Docs, publish via Hugo/Markdown-based blogs.
    • Collaboration with non-technical users who prefer Docs while others prefer Markdown.

Capabilities, Gaps & Ambiguities

  • Announced capabilities:
    • Convert Markdown to Docs on paste.
    • Copy as Markdown.
    • Import and export Docs as Markdown, including via Drive API.
    • Tables and GitHub-flavored extensions reportedly work in internal testing.
    • Export uses CommonMark-compatible output, including reference-style links; images exported as base64 URLs via references.
  • Reported gaps / complaints:
    • Incomplete or still-rolling-out support for code blocks, blockquotes, inline-code behavior, and syntax highlighting.
    • Some code-block features and formatting are only available in certain paid Workspace tiers.
    • No Mermaid diagrams or Slides integration; no markdown-based “edit mode” in Docs.
    • Handling of rich Docs-only features: some are mapped to nearest Markdown equivalent, others dropped.

Rollout & Reliability

  • Feature is still rolling out; many commenters can’t see it yet, leading to confusion with a 2022 “auto-detect markdown while typing” feature.
  • Slow, staged rollout is described as a safety measure, but several people say pre-rollout announcements mean they forget about the feature by the time it appears.

Alternatives & Comparisons

  • People compare Docs unfavorably to Notion and dedicated markdown tools (HackMD, Obsidian, Bookstack, Typst, Slidev, etc.) but see this feature as closing the gap.
  • Some still prefer pure Markdown+git for versioning, while others argue Docs-style comments and suggestions are the main collaborative advantage.