Skip to main content

Search OfficeIMO

Enter a topic, API type, or PowerShell command.

Documentation Search all OfficeIMO/

Conversion workflows

Document Conversion Guides for .NET

Choose .NET routes for DOC, DOCX, XLS, XLSX, XLSB, PPT, PPTX, PUB, PDF, and web formats, with documented PSWriteOffice routes called out separately.

Move documents without hiding fidelity decisions

Guide scope
Package
Focused OfficeIMO packages
Runs on
.NET, PowerShell, browser, and CLI
Microsoft Office
Not required
License
MIT

Each route names its supported formats, fidelity boundary, and deployment requirements.

Check the complete format matrix

OfficeIMO conversion is built for .NET applications that need more than a file-extension switch. Each focused package owns a document family, while adapters add PDF, HTML, Markdown, OpenDocument, Google Workspace, and normalized extraction only when the workflow needs them.

Start with the route you need

Input and outputBest starting pointWhat you can inspect
DOC and DOCXOfficeIMO.WordFeature-level compatibility, preservation, and conversion diagnostics
XLS and XLSXOfficeIMO.ExcelWorksheets, formulas, styles, charts, and legacy BIFF decisions
XLSB and XLSXOfficeIMO.ExcelNative binary-workbook parsing and write diagnostics
PPT and PPTXOfficeIMO.PowerPointSlides, shapes, text, media, notes, charts, and fallback decisions
Word to PDFOfficeIMO.Word.PdfPublishing warnings, fonts, images, tables, sections, and output status
Excel to PDFOfficeIMO.Excel.PdfWorksheet selection, pagination, page setup, styles, and export warnings
Publisher to PDFOfficeIMO.Publisher.PdfPage sizes, searchable text, and fidelity diagnostics for Publisher archives
PDF to WordOfficeIMO.Word.PdfEditable reconstruction or rendered-page output with explicit loss diagnostics
PDF tables to ExcelOfficeIMO.Excel.PdfDetected table rows and cells, omitted page content, and import limits
PDF to PowerPointOfficeIMO.PowerPoint.PdfEditable, visual, hybrid, and tables-only projections with warnings
PDF to HTMLOfficeIMO.Html.PdfSemantic or positioned-review HTML with extraction and fidelity diagnostics

For HTML, Markdown, RTF, OpenDocument, Google Docs, Sheets, and Slides, use the focused adapter shown in the package catalog. This keeps dependencies and deployment behavior explicit.

One CLI binary for modern Office-to-PDF routes

Install OfficeIMO.Tool once and use the same officeimo executable for DOCX, XLSX, PPTX, and PUB input:

officeimo convert report.docx
officeimo convert workbook.xlsx --output published/workbook.pdf
officeimo convert deck.pptx --output deck.pdf --force
officeimo convert brochure.pub brochure.pdf

The extension selects the same first-party Word, Excel, PowerPoint, or Publisher PDF adapter used by .NET applications. The source is opened read-only, diagnostics go to standard error, and an existing destination is not replaced unless --force is explicit. The command is intentionally a thin package dispatcher; format-specific fidelity and warning contracts remain in the owning adapters linked above.

PowerShell routes are documented separately

PSWriteOffice includes dedicated DOC/DOCX and XLS/XLSX conversion cmdlets and supports Publisher to PDF through Convert-OfficeDocument. Start with the PSWriteOffice product page, then verify the exact command and parameters in the PowerShell API reference.

Conversion is a policy decision

A document can be readable even when every source feature is not editable in the destination. OfficeIMO distinguishes:

  • Native content represented directly by the destination format.
  • Editable approximation when the closest destination feature is still useful.
  • Visual fallback when appearance matters more than editability.
  • Preserved source when recovery is safer than pretending a conversion was complete.
  • Blocked output when continuing would silently misrepresent the result.

The format compatibility page exposes those states from the same contracts used by the libraries. For governed migrations, analyze first, decide which states your workflow accepts, then write the output.

Browser, server, and desktop choices

The browser playground handles selected conversions on your device, including the Publisher to PDF browser converter. Legacy DOC, XLS, and PPT migration uses the local packages or command-line tools described in the route guides.

Need a broader workflow?

API used on this page

Example source