DOCX workflow guide

How to convert DOCX to Markdown and keep images

Move a Word document into Obsidian, GitHub, or an AI workflow without separating the Markdown from its image files.

Prepare the Word document

Use the modern .docx format. Old .doc files, macro-enabled files, encrypted packages, and damaged documents are not accepted by the current converter.

Save as .docx

Open older Word files in Word or a compatible editor and save a clean .docx copy first.

Keep standard images

PNG, JPEG, and GIF images can be copied as real files instead of flattened placeholders.

Simplify unusual objects

Convert essential SmartArt, charts, equations, or legacy drawing objects to images if exact appearance matters.

Retain the original

The generated Markdown is a working copy. Keep the source DOCX as the authoritative record.

Create one portable Markdown package

Choose the DOCX and run the browser-local converter. The same workflow extracts document structure, copies supported image bytes, creates relative paths, and writes the coverage report.

Parse the document

Headings, paragraphs, emphasis, links, lists, and simple tables are rebuilt as Markdown.

Extract the assets

Supported images are copied into assets/ with stable names such as image-001.png.

Build the ZIP

The Markdown, optional assets folder, and conversion-report.json are downloaded together.

Check what moved and what still needs review

DOCX can contain several XML parts and embedded object types. The report separates tested output from content that needs a manual comparison.

AreaStatusWhat the evidence shows
Headings, paragraphs, lists, linksConvertedCore structure is covered by integration fixtures and deterministic output checks.
PNG, JPEG, and GIFCopied as assetsOriginal raster bytes retain source order and use portable relative paths.
Simple tablesConvertedA basic two-column, two-row fixture preserves its row and column relationship.
Equations, VML, charts, SmartArtReview requiredDetected unsupported objects are listed as warnings instead of being silently treated as complete.
Old, encrypted, macro, or damaged filesNot acceptedThe converter stops before creating a misleading partial package.

Use the package without breaking image paths

Extract the ZIP into one folder and keep its internal structure. Most Markdown tools can resolve assets/image-001.png when the Markdown file and assets folder remain siblings.

Obsidian

Copy the extracted folder into the vault, then confirm that attachment paths render as expected.

GitHub

Commit the Markdown and assets directory together so relative image links remain valid.

AI knowledge workflow

Review warnings and decide how the destination system should handle image files before ingestion.

Continue with the right next step.

Compare the workflow guide with the evidence behind its limits.