Word (.docx) Compatibility

Word Compatibility in Revise

Our mission with Revise is build the most advanced agentic word processor in the world, and as such we treat Word files (.docx) as a first-class format. Our goal is that a document can pass through Revise on its way between Word users and nothing gets lost. This page is a current map of what survives the round trip today, what is partially supported, and what is still on the roadmap. We update it as coverage grows.

If you find a bug with our .docx format support, please reach out to support@revise.io and let us know!

Fully supported (round-trips both ways)

• Text and formatting - paragraphs, headings, alignment, line spacing, indents, and page breaks; bold, italic, underline, strikethrough, highlights, text colors, font sizes and families, superscript/subscript, and links.
• Tracked changes - insertions, deletions, formatting changes (with revert-to-prior on reject), paragraph split/merge revisions, moved text, and table-row revisions. Author names, dates, and Word revision identity are preserved in both directions, and Word redlines arrive in Revise as reviewable suggestions.
• Footnotes and endnotes - both streams, with correct per-stream numbering.
• Headers and footers - including three-zone layouts, different first-page headers, even-page slots, and PAGE / NUMPAGES fields.
• Comments - anchored ranges, reply threads, and resolved state are preserved through import and export. (Comments don't have an on-screen panel in Revise yet - they pass through untouched.)
• Lists - ordered, unordered, and checklists, with basic nesting.
• Tables - with cell backgrounds, column widths, and header rows.
• Inline images (PNG, JPEG, GIF, BMP), equations (Word math converts to LaTeX and back), and content controls (their content is preserved).
• Page setup - size, orientation, and margins.

Partially supported

These import safely - the text always survives - but some structure or positioning is simplified:

• Text boxes and shapes - the text inside them imports as ordinary paragraphs; the box geometry itself is dropped.
• Merged table cells - the table grid stays aligned, but merged spans import as separate cells.
• Multi-section documents - Revise currently uses one page layout per document, so per-section orientation, margins, and multi-column layouts flatten to a single layout.
• Floating images - the image survives but becomes inline; position and text-wrap settings are lost.
• Named styles - style-based formatting is baked into the text on import, so documents look right but lose the style definitions.
• Custom numbering schemes - exotic list formats, restarts, and deep multi-level schemes simplify to standard lists.
• Fields, bookmarks, and tables of contents - PAGE fields stay live; other fields freeze to their last-cached text, and internal cross-reference anchors don't survive.
• Tab stops - tab characters survive; custom tab-stop positions don't.

Not yet supported

• SmartArt and chart text - currently dropped on import.
• EMF, WMF, and SVG images - Revise imports raster images only.
• Right-to-left text - RTL and bidirectional layout aren't handled yet.
• Some rare run properties - small caps, all caps, double strikethrough, character spacing, and text borders are dropped.
• Paragraph- and table-property revisions - a tracked change that only alters paragraph or table properties imports as the final state rather than a reviewable suggestion. (Text revisions are fully supported - see above.)

Roadmap

Our priority order is simple: anything that could silently lose text gets fixed first (that tier is now clear), then structure (merged cells, sections, floating images), then semantics (styles, numbering definitions, live fields). If a gap on this page matters to your workflow, tell us - real documents from real users are how we prioritize.