Skip to main content
OfficeIMO Docs Search documentation/

Word Conversion and Rendering

Edit on GitHub

Choose Word-to-HTML, Markdown, PDF, OpenDocument, RTF, Google Docs, or image workflows with explicit fidelity and resource policies.

Word conversion is split into focused adapters so applications do not acquire every renderer and destination model. Start with OfficeIMO.Word, then add the package for the destination you ship.

Routes

DestinationPackageWhat to validate
HTML and MHTMLOfficeIMO.Word.HtmlCSS, images, links, headers/footers, lists, tables, review markup, and external-resource policy
MarkdownOfficeIMO.Word.MarkdownHeading/list semantics, tables, code, images, links, and features with no Markdown equivalent
PDFOfficeIMO.Word.PdfPagination, fonts, shaping, fields, tables, images, headers/footers, links, and renderer diagnostics
OpenDocumentOfficeIMO.Word.OpenDocumentDOCX/ODT model mapping and round-trip expectations
RTFOfficeIMO.Word.RtfRich-text semantics, lists, tables, and bounded legacy-format behavior
Google DocsOfficeIMO.Word.GoogleDocsConversion loss policy, authentication, Drive ownership, and remote update behavior
ImagesOfficeIMO.Word imaging APIsPage size, resolution, fonts, and final-revision view

Use diagnostics as output

A successful method call only proves that an artifact was produced. Treat warnings as part of the conversion result and decide which codes are acceptable. For regulated or high-value output, store the source hash, adapter version, selected options, diagnostics, and destination hash together.

Review-aware conversion

Decide whether the destination should represent the original view, final revision view, visible comments, or a clean approved document. Inspect review state before conversion and fail the job when unresolved comments or unsupported metadata violate policy.

Resource policy

HTML, images, and PDF output can depend on fonts, linked resources, embedded assets, and network access. Prefer explicit local or allow-listed resolvers. Avoid a converter silently reaching arbitrary URLs in a server or build environment.

Use the conversion map for other source families and the generated Word API reference for exact option types.