VS Code Markdown to Word: Extensions, Setup & Export Guide

Visual Studio Code is not just a code editor — it is one of the most capable Markdown authoring environments available today. With over 15 million monthly active users and a marketplace containing thousands of extensions, VS Code offers a uniquely powerful platform for writing, previewing, and exporting Markdown documents. Unlike dedicated Markdown editors such as Typora or Obsidian, VS Code gives developers the ability to stay within a single tool for both code and documentation.

The built-in Markdown preview (Ctrl+Shift+V) renders your document in real time, letting you see exactly how headings, lists, tables, code blocks, and images will look before exporting. Side-by-side editing (Ctrl+K V) lets you write and preview simultaneously, making it easy to catch formatting issues early.

Beyond preview, VS Code offers intelligent syntax highlighting for Markdown, auto-completion for common patterns, integrated spell checking through extensions, and deep Git integration so you can version-control your documents alongside your code. When it comes time to export to Word, the extension ecosystem bridges the gap seamlessly — either through one-click GUI commands or through Pandoc integration in the integrated terminal.

Markdown All in One by Yu Zhang is the most widely installed Markdown extension for VS Code, with over 8 million downloads. While it does not directly export to DOCX, it supercharges your Markdown editing experience with keyboard shortcuts, auto-preview, table of contents generation, list editing helpers, and math equation support via KaTeX. It is the ideal companion extension to pair with a dedicated export tool like vscode-pandoc.

Pandoc Citer by notZaki brings academic citation support directly into VS Code. If you write research papers, technical reports, or any document that requires bibliographic references, this extension provides auto-completion for citation keys from your BibTeX or BibLaTeX files. When combined with Pandoc for export, your @citation-key references are automatically resolved into properly formatted citations in the output Word document, complete with a bibliography section.

Markdown PDF by yzane is one of the most versatile export extensions, primarily designed for PDF output but also capable of producing DOCX files when Pandoc is installed on your system. It leverages Chromium under the hood for PDF generation and can be configured to call Pandoc for Word output. With over 3 million downloads, it is a mature and reliable choice. The extension adds right-click context menu options and command palette commands for quick export.

vscode-pandoc by Doug Finke is the most direct bridge between VS Code and Pandoc. This extension wraps Pandoc commands into VS Code’s command palette, allowing you to convert Markdown to DOCX, PDF, or HTML with a single keystroke. It reads your Pandoc configuration from VS Code settings, so you can specify custom reference documents, table of contents generation, citation processing, and any other Pandoc flag without touching the terminal. This is the top recommendation for developers who want reliable, high-quality Word output.

The Docs Authoring Pack by Microsoft is an extension bundle originally designed for contributors to Microsoft Learn documentation. It includes several individual extensions: Docs Markdown (custom Markdown shortcuts and snippets for docs.microsoft.com), Docs Preview (custom rendering that matches Microsoft Learn styles), Docs YAML, and Docs Article Templates. While it does not export directly to DOCX, it provides a professional Markdown authoring environment with validation, link checking, and template insertion that pairs well with a Pandoc-based export workflow.

Before installing any VS Code extension, you need Pandoc on your machine. Open a terminal and install using your package manager:

# Windows (via Chocolatey)
choco install pandoc

# macOS (via Homebrew)
brew install pandoc

# Ubuntu / Debian
sudo apt-get install pandoc

Verify with pandoc --version. You should see version 3.x or later for best DOCX support.

Open VS Code and press Ctrl+Shift+X to open the Extensions sidebar. Search for "vscode-pandoc" by Doug Finke. Click Install. Alternatively, install from the terminal:

code --install-extension DougFinke.vscode-pandoc

Open VS Code settings (Ctrl+,) and search for "pandoc". Alternatively, edit your settings.json directly with the following configuration:

{
    // Path to Pandoc executable (if not in PATH)
    "pandoc.executable": "pandoc",

    // DOCX-specific options
    "pandoc.docxOptString": "--reference-doc=custom-template.docx --toc --number-sections",

    // PDF options (optional)
    "pandoc.pdfOptString": "--pdf-engine=xelatex --toc",

    // HTML options (optional)
    "pandoc.htmlOptString": "--standalone --self-contained"
}

The pandoc.docxOptString field is where you pass all Pandoc flags for Word output. You can include any valid Pandoc option here.

Create or open a .md file in VS Code. Use the built-in side-by-side preview to verify formatting as you write:

• Press Ctrl+K V to open side-by-side Markdown preview
• Press Ctrl+Shift+V to open preview in a new tab
• Use Ctrl+B for bold and Ctrl+I for italic (with Markdown All in One installed)

The preview gives you a reasonable approximation of the final output, though the actual Word document styling will depend on your reference template.

With your Markdown file open and active, press Ctrl+Shift+P to open the command palette. Type "Pandoc Render" and select "Pandoc Render: docx". The extension will invoke Pandoc with your configured options and generate a DOCX file in the same directory as your Markdown source.

The output file will have the same name as your Markdown file but with a .docx extension. For example, report.md becomes report.docx.

Basic Conversion

# Convert the currently open file to Word
pandoc document.md -o document.docx

With Table of Contents and Numbered Sections

pandoc document.md -o document.docx \
    --toc \
    --toc-depth=3 \
    --number-sections

With Custom Template and Citations

pandoc document.md -o document.docx \
    --reference-doc=my-template.docx \
    --citeproc \
    --bibliography=references.bib \
    --csl=apa.csl \
    --metadata title="My Report"

This command applies a custom Word template, processes citations from a BibTeX file, formats them in APA style, and sets the document title metadata.

Step 1: Generate a Default Reference Document

First, generate Pandoc’s default reference document so you have a starting point to customize:

pandoc -o custom-reference.docx --print-default-data-file reference.docx

Step 2: Customize Styles in Word

Open custom-reference.docx in Microsoft Word. Go to the Styles pane and modify the styles that Pandoc uses. The key styles to customize include:

• Normal — Body text font, size, and line spacing
• Heading 1 through Heading 6 — Section heading formatting
• Source Code — Inline code font and background
• Verbatim Char — Code block character styling
• Block Text — Blockquote formatting
• Table — Table borders, shading, and cell padding
• Header / Footer — Page headers and footers

Save the file after making changes. Do not add any content — Pandoc only reads the styles, not the text.

Custom Keybindings for Export

[
    {
        "key": "ctrl+shift+d",
        "command": "pandoc.render",
        "args": "docx",
        "when": "editorLangId == markdown"
    },
    {
        "key": "ctrl+shift+p ctrl+shift+p",
        "command": "pandoc.render",
        "args": "pdf",
        "when": "editorLangId == markdown"
    },
    {
        "key": "ctrl+shift+h",
        "command": "pandoc.render",
        "args": "html",
        "when": "editorLangId == markdown"
    }
]

With this configuration, pressing Ctrl+Shift+D while editing a Markdown file will instantly generate a Word document.