Convert DOCX to Markdown

1. 1

   Add your Word document

   Drag and drop a DOCX file onto the upload area, or click Browse to pick one. Only Word .docx files are accepted, and anything else is refused straight away with a message telling you what to do instead. Conversion starts on its own — there is no button to press first.

2. 2

   Choose how the Markdown should look

   Pick a Markdown flavour: GitHub Flavored Markdown for repositories and most static sites, CommonMark for strict parsers, or Pandoc if you are feeding the output into a Pandoc pipeline. Then decide what happens to embedded images, whether to add YAML front matter, whether to demote the headings, and whether to wrap long lines.

3. 3

   Check it in the preview

   Switch between Source and Rendered. Source shows the exact Markdown you are about to take away; Rendered shows how it will look once a Markdown renderer has read it, so you can confirm the tables, lists and links came through before you commit to the result.

4. 4

   Copy or download

   Use Copy to put the Markdown on your clipboard, or Download to save a .md file. If the document contained images, download the ZIP instead — it holds the .md file and an images folder whose files match the paths in the Markdown. Everything runs on your device and no document is ever uploaded.

Every part of a Word document that has a Markdown equivalent is carried across, and the parts that do not are written as HTML rather than quietly dropped.

• Real tables: Word tables become pipe tables, with the column alignment read from the document rather than guessed.
• Footnotes and endnotes: Both become [^1] references with their definitions collected at the end of the file.
• Full inline formatting: Bold, italic, strikethrough, underline, highlight, superscript, subscript, inline code and links all survive.
• Image extraction: Embedded pictures are written into an images folder and delivered with the Markdown as one ZIP.
• YAML front matter: The title, author, subject, keywords and dates stored in the document become a front matter block.
• Three Markdown flavours: GitHub Flavored Markdown, CommonMark and Pandoc, each with the syntax that flavour actually supports.
• Rendered preview: Switch between the Markdown source and how it will look, before you copy or download anything.
• Batch with one archive: Convert many documents and take them away as a single ZIP instead of one save prompt each.

Structure is the part of a Word document that is easiest to lose and hardest to notice losing. A converter that flattens a table into loose paragraphs produces output that looks fine at a glance and is wrong in a way you only discover after pasting it somewhere. This tool treats structure as the thing being converted.

How a Word Table Becomes Markdown

• Header rows: A row Word marks as a repeating header becomes the table header. If no row is marked, the first row is used, because that is what a Word table's first row almost always is.
• Column alignment: Left, centre and right are read from the document's own paragraph alignment and written as ---, :---: and ---:.
• Pipes inside cells: A cell containing a pipe character is escaped so it does not split the column in two.
• Multi-paragraph cells: Two paragraphs in one cell are joined with a line break, which keeps the pipe table intact instead of forcing the whole table to HTML.
• Merged cells: Markdown has no way to express a merged cell, so tables that use one are written as HTML — accepted by every Markdown renderer, and lossless.
• Nested lists: List nesting is preserved to any depth, indented so the content lines up the way CommonMark requires.

The word Markdown covers several dialects that genuinely differ, and picking the wrong one produces a file full of stray punctuation instead of formatting. The flavour setting changes the syntax that is emitted, not just a label.

Which One Should You Pick?

• GitHub Flavored Markdown: The default, and the right answer for GitHub, GitLab, wikis and most static site generators. Pipe tables, ~~strikethrough~~ and [^1] footnotes are all available.
• CommonMark: The strict baseline. It has no table, strikethrough or footnote syntax at all, so those constructs are written as HTML, which renders correctly everywhere rather than showing literal tildes and pipes.
• Pandoc: Adds Pandoc's own ^superscript^ and ~subscript~ syntax. Pick it when the Markdown is going into a Pandoc pipeline that will read those.

A Word document usually carries more than text. Where those extras go is a decision that depends on what you are doing with the Markdown, so it is a setting rather than an assumption.

Three Ways to Handle Embedded Images

• Extract to a folder: Each picture is written to images/image-1.png and referenced by that relative path. The download becomes a ZIP holding the .md file and the folder, ready to commit to a repository.
• Embed inline: Each picture becomes a data URI inside the Markdown itself. The file is self-contained and much larger, which suits pasting a short snippet somewhere that cannot host files.
• Leave them out: No image references at all, for a migration where the pictures are already hosted somewhere and only the text needs moving.

What Goes Into the Front Matter

• Title, author and subject, taken from the document properties Word stores rather than guessed from the text.
• Keywords, split into a YAML list when the document has more than one.
• Created and modified dates, in the ISO form static site generators expect.
• Every value is quoted where it needs to be, so a title containing a colon cannot break the site build that reads it.

Converting Word to Markdown enables version control, creates developer-friendly content, facilitates documentation, allows GitHub publishing, and converts documents for technical writing.

Benefits of Markdown Format

• Version Control: Markdown is plain text, so a diff shows what actually changed instead of a binary blob.
• Developer-Friendly: It lives beside the code it documents and needs no special editor.
• GitHub Publishing: README and wiki content renders natively on GitHub and GitLab.
• Technical Writing: Docs-as-code toolchains take Markdown as their input format.
• Simple Formatting: The syntax is small enough to read as plain text and write without a toolbar.

Conversion happens in two stages, and knowing which is which explains why changing a setting is instant while the first conversion takes a moment.

Conversion Process

• Read the document: The .docx is opened on your device and its structure, styles, images and properties are read out. This is the part that costs time, and it happens once per file.
• Write the Markdown: The structure is turned into Markdown according to the flavour and the other settings. This is pure text work, so it is effectively instant.
• Change a setting: Only the second stage runs again. That is why the preview updates the moment you touch a control, even on a very long document.
• Batch: Each document is read and written independently, and every result can be copied, downloaded on its own, or collected into one archive.

Understanding these facts helps you make better conversion decisions.

Key Statistics

• A 25,000-word document containing 50 tables is read in about 22 milliseconds and re-rendered in under one millisecond when a setting changes.
• Only .docx is accepted. The older binary .doc format is refused with an explanation, because it is a different format that Word can convert for you.
• Free covers one document at a time, up to 50 MB, with every conversion feature included; Pro covers batches of up to 50.
• Escaping is kept to a minimum: characters that could start Markdown are escaped, and characters that could not are left exactly as they were.
• Headings, lists, links, emphasis, tables, footnotes and images are all preserved.

Converts a 25,000-word document with 50 tables in well under a second, on your device.

Follow these guidelines for optimal Word to Markdown conversion results.

Quality Considerations

• Use Word's built-in Heading styles rather than manually enlarged bold text — a converter can only recognise a heading that is marked as one.
• Check the Rendered tab before downloading, especially for documents with tables, to confirm the structure came through as you expect.
• If the Markdown is going under an existing title, demote the headings by one so the document has a single top-level heading.
• Choose CommonMark only when a strict parser requires it; the HTML fallbacks it produces are correct but more verbose.
• Test the .md file in its destination — GitHub, a static site, a wiki — after downloading.

Common Use Cases

• Documentation: Move an existing Word manual into a docs-as-code repository without retyping it.
• GitHub Publishing: Turn a specification or a proposal into a README or a wiki page.
• Technical Writing: Bring drafts written in Word into a Markdown toolchain for review and version control.
• Blog Posts: Convert a written draft into a post for a static site generator, front matter included.
• Developer Content: Extract tables and code-like content from a Word spec into a form that can be diffed.

• Word to PDF
• Word to HTML
• Word viewer
• Word to Text
• Compress Word
• CSV to Markdown