Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Docx-to-Markdown

layout-aware Word to Markdown converter

Details

External ID
49728477
Source
HN
Company
—
Product
Docx-to-Markdown
Website domain
docx-editor.dev
Launched
Sept. 16, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.12998405103668262
Tags
—
Fetched at
Sept. 20, 2026, 5:44 p.m.
Updated at
Sept. 20, 2026, 5:44 p.m.

Description

Hey HN, I’m the author of the https://github.com/eigenpal/docx-editor, it’s an SDK that implements Word-compatible layout engine in Typescript.Today, we are releasing Word to markdown converter library. It’s open source and published under Apache 2.0 license. It uses our layout engine, so it can return accurate, per-page markdown blocks (with headers, footers, and image references). We also handle fonts (Google fonts as fallback) or let you pass your font files upfront for accurate content measurement.To our surprise, Word to per-page Markdown conversion is not a solved problem even in 2026! We initially faced this friction when preprocessing Word documents for agentic workflows. For our use case, it was important to represent per-page content in markdown. Initially, we ended up using LibreOffice sidecar to convert to PDF and then using .pdf -> .md library. This was not ideal given that LibreOffice sidecar that was sitting idle most of the time.This issue is addressed with docx-to-markdown library. it can be used directly in your Typescript ingestion pipeline. Try with your docs at https://www.docx-editor.dev/solutions/word-to-markdown.(if you catch any bugs please let us know in the comments / or file gh issues)

Enrichment

Theme
markdown editors and writing tools
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
layout-aware docx to markdown converter for developers
Manually corrected
False

Could you build this?

No Building a layout-aware Word-to-Markdown converter requires writing a full Word-compatible layout and pagination engine in TypeScript, which entails deep reverse engineering of Microsoft Word's proprietary rendering, line-breaking, and pagination rules.

What it would actually take: The engine requires parsing OpenXML (DOCX), extracting font metrics, constructing a layout tree, computing exact line-breaks, margins, tables, headers/footers, and page breaks identical to Word's rendering engine. A real version requires implementing font measurement pipelines (Canvas/FreeType/HarfBuzz in WASM), handling bidirectional text and complex script layout, and managing complex table pagination algorithms. This level of specification compliance and rendering fidelity demands specialized document engineering expertise.

Discussion

5 comments analyzed.

Competitors mentioned: Microsoft Office, Google Workspace

Concerns raised: Docx to markdown is a lossy conversion losing formatting details

Feature requests: Convert markdown back to docx, Sync markdown edits back to docx

Competitors

Other products that read as similar to this one — 247 launches clear the similarity bar, closest 8 shown.

Attention rank: #226 of 248 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 320 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.