Home Developer Tools Word to Markdown Converter
📄
Developer Tools

Word to Markdown Converter

Convert Microsoft Word documents (.docx) to clean Markdown — paste Word content or upload a .docx file to extract headings, bold, italic, lists, links and tables as Markdown.

📄 Paste or upload .docx🔄 Converts formatting⚡ Instant output📋 Copy Markdown
Switch: 📋 HTML Table Generator 🌐 HTML Viewer / Preview 📝 Markdown Editor / Preview ⚙️ Markdown Table Generator ✏️ SVG Path Optimizer 📄 Word to Markdown Converter
Word / Rich Text Input
Markdown Output

📖How to Use the Word to Markdown Converter

  1. 1
    Paste your Word content

    Copy text from a Microsoft Word document and paste it into the input area. Formatting such as headings, bold, italic, lists and links is detected automatically.

  2. 2
    Review the Markdown output

    The converter maps Word formatting to Markdown syntax: headings become # H1, ## H2; bold becomes **bold**; italic becomes *italic*; lists become - or 1. items.

  3. 3
    Copy or download

    Click Copy Markdown to grab the output, or Download .md to save as a Markdown file. The output is compatible with GitHub, GitLab, Notion, Obsidian and any Markdown editor.

💡Common Use Cases

SituationWhy It Helps
README migration Convert Word docs to MD
CMS publishing Export Word to Markdown CMS
Documentation Migrate Word specs to Git

Frequently Asked Questions

What Word formatting is converted to Markdown?

The converter maps the most common Word formatting to Markdown equivalents: Heading 1/2/3/4/5/6 styles → # / ## / ### etc., Bold → **text**, Italic → *text*, Bold+Italic → ***text***, Underline → *text* (closest Markdown equivalent), Strikethrough → ~~text~~, Hyperlinks → [link text](url), Bullet lists → - item, Numbered lists → 1. item, Blockquotes → > text, Inline code → `code`, Tables → pipe-format Markdown tables, Horizontal rules → ---.

Can I upload a .docx file or only paste content?

Both options are supported. For pasting: copy content from a Word document (Ctrl+A, Ctrl+C) and paste it into the input area — formatting metadata is passed through the clipboard. For uploading: click Upload .docx and select a Word document. The .docx file is parsed locally in your browser using a JavaScript library (mammoth.js) to extract text and formatting without any server upload. Both methods produce equivalent results.

Does it convert Word tables to Markdown tables?

Yes — tables in Word documents are converted to pipe-formatted Markdown tables. The first row is treated as the header row. Cell content including inline formatting (bold, italic, links) is preserved within the Markdown table cells. Complex table features like merged cells (colspan/rowspan) cannot be represented in Markdown pipe tables — they are simplified to a flat grid with content preserved but merge structure removed.

What happens to images in the Word document?

Embedded images in the Word document are not directly convertible to Markdown (Markdown image syntax requires a URL or file path, not raw image data). Images are replaced with a placeholder comment in the Markdown output: <!-- Image: [image dimensions and position note] -->. To include images, export them from Word separately and host them, then update the placeholder with the correct Markdown image syntax: ![alt text](image-url.png).

Does it handle footnotes and endnotes?

Footnotes and endnotes from Word documents are converted to Markdown footnote syntax where supported: the footnote marker becomes [^1] in the text and the footnote content becomes [^1]: footnote text at the bottom of the document. Standard Markdown does not include footnote syntax, but GitHub, Pandoc, and many extended Markdown parsers (MultiMarkdown, kramdown) support this format. In plain CommonMark, footnotes appear at the bottom as numbered references.

What is the best way to convert a long Word document?

For long documents (50+ pages), convert section by section rather than the whole document at once. This makes it easier to review and correct the output, handle complex tables individually, and deal with special characters or symbols that may not convert cleanly. After converting, read through the Markdown in the preview panel to catch any formatting issues before copying the final output. The word count in the status bar helps you track how much content has been converted.

Does it preserve heading hierarchy for document structure?

Yes — the converter detects Word's Heading 1 through Heading 6 paragraph styles and maps them to the corresponding Markdown heading levels (# through ######). This preserves the full document hierarchy. Normal paragraph text becomes plain Markdown paragraphs. The heading structure is also reflected in the live preview which shows a formatted document with the correct visual hierarchy, making it easy to verify the structure is correct before exporting.

What special characters can cause issues in conversion?

Some special characters and symbols used in Word documents do not have direct Markdown equivalents: em dashes (—) become -- or --- depending on context, smart quotes (" ") are converted to straight quotes (" "), ellipsis (…) becomes ..., non-breaking spaces become regular spaces, and various mathematical or typographic symbols may be converted to their Unicode representation or HTML entity. Review the output for any characters that need manual correction.

Can I convert Google Docs to Markdown?

Yes — Google Docs can be exported in two ways: (1) Copy and paste directly from Google Docs into the input area (formatting is passed through the clipboard similar to Word); (2) Download from Google Docs as .docx (File → Download → Microsoft Word) and then upload the .docx file here. Option 2 typically produces more accurate results as the full formatting information is captured in the Word file rather than just what the clipboard transfers.

Is the conversion private — is my document uploaded to a server?

Yes, completely private. The entire conversion process runs locally in your browser using JavaScript. For pasted content, no data leaves your browser at all. For .docx file uploads, the file is read and processed entirely in browser memory using the mammoth.js library — it is never transmitted to any server. This makes the tool safe for confidential business documents, legal files, HR materials and sensitive content.