Skip to main content
Open Source • MIT License • Builders, Extraction, and PowerShell Automation

Office Documents Without Office

Create, read, and edit Word, Excel, PowerPoint, Markdown, and more from .NET and PowerShell. Zero COM dependencies, cross-platform, AOT-ready.

.NET dotnet add package OfficeIMO.Word
PowerShell Install-Module PSWriteOffice
No COM
No Office Required
Cross-Platform
AOT-Ready
MIT License
10+ Packages
5 Target Frameworks
0 COM Dependencies
3 Platforms

Get Started in Three Steps

Install the Package

Add the NuGet package for the document format you need, or install the PSWriteOffice PowerShell module. Targets .NET 8+, .NET Standard 2.0, and .NET Framework 4.7.2.

Write Fluent Code

Use the intuitive, object-oriented API to create, read, or edit documents. Available in C# with fluent builders and PowerShell with DSL aliases.

Get Perfect Documents

Output standards-compliant Office documents that open flawlessly in Microsoft Office, LibreOffice, and Google Docs. No manual XML wrangling required.

A Library for Every Format

Start with the document builder you need today, then layer in Reader for ingestion and PSWriteOffice for scripting and automation.

Core Builders

Generate Word, Excel, PowerPoint, Markdown, CSV, and Visio output directly from .NET.

OfficeIMO.Word Most Popular

Create and edit .docx documents with a friendly object model

Paragraphs Tables Converters
dotnet add package OfficeIMO.Word

Automation and Ingestion

Use Reader for extraction and chunking, then PSWriteOffice when your workflow needs PowerShell-first automation.

PSWriteOffice PowerShell

PowerShell module for creating Office documents with DSL aliases

PowerShell DSL Automation
Install-Module PSWriteOffice
Code Examples

Multiple Ways to Build Documents

The same site should support hand-written .NET code, higher-level builders, and PowerShell automation without looking like separate products.

using var doc = WordDocument.Create("report.docx");
    
    var paragraph = doc.AddParagraph("Quarterly Sales Report");
    paragraph.Style = WordParagraphStyle.Heading1;
    
    doc.AddParagraph("Generated automatically with OfficeIMO.Word.");
    
    var table = doc.AddTable(4, 3);
    table.Rows[0].Cells[0].Paragraphs[0].Text = "Region";
    table.Rows[0].Cells[1].Paragraphs[0].Text = "Revenue";
    table.Rows[0].Cells[2].Paragraphs[0].Text = "Growth";
    table.Rows[0].IsHeader = true;
    
    table.Rows[1].Cells[0].Paragraphs[0].Text = "North America";
    table.Rows[1].Cells[1].Paragraphs[0].Text = "$1,250,000";
    table.Rows[1].Cells[2].Paragraphs[0].Text = "+12%";
    
    doc.Save();
Comparison

Choose the Right Fit

Compare OfficeIMO against the typical trade-offs of commercial document suites without freezing the page around vendor snapshots that drift over time.

Decision pointOfficeIMOTypical commercial suiteWhat to validate
Licensing and source accessMIT license with source availablePaid license or subscription with closed-source implementationProcurement rules, redistribution terms, and whether source inspection matters to your team
Primary workflow.NET packages plus first-party PowerShell automation through PSWriteOfficeUsually strong .NET APIs, with PowerShell often handled through custom wrappersWhether the team needs native scripting, CI automation, or admin-friendly document jobs
Format and workload focusStrongest around Open XML packages, Markdown, CSV, and document-reader workflows in this repoOften broader across rendering, conversion, and additional file-format familiesThe exact formats, conversions, and rendering scenarios your product must support
Deployment modelCOM-free and friendly to server, container, and automation environmentsOften server-safe as well, but packaging and runtime dependencies still varyTarget OS, hosting model, native dependencies, and whether your builds need to stay lightweight
AOT and trimming realityPackage-specific, with the cleanest story today in lighter packages such as Markdown and CSVVaries by vendor, package, and feature setReal publish profiles, linker settings, and the exact package mix you plan to ship
Support modelGitHub issues, source inspection, and community-driven troubleshootingVendor-maintained docs, support channels, and commercial escalation pathsResponse expectations, SLA requirements, and who owns production support
Debugging and customizationYou can inspect behavior directly, patch locally, and understand how documents are producedYou usually depend on vendor fixes, support guidance, and extension pointsHow often you need deep debugging, custom behavior, or internal platform ownership
Total cost profileNo license fee, but your team still owns evaluation, testing, and operational confidenceLicense cost in exchange for support, broader coverage, and procurement-friendly packagingWhether engineering time or commercial support is the scarcer resource for your organization

What You Can Build

See real-world documents generated with OfficeIMO and PSWriteOffice.

Automated Sales Report

Complete Word document with formatted tables, charts, headers, footers, and table of contents generated from database queries.

Word Tables Charts TOC

Financial Dashboard

Excel workbook with multiple sheets, pivot tables, conditional formatting, sparklines, and interactive charts.

Excel Charts Pivot Tables Formatting

Quarterly Presentation

PowerPoint deck with branded slides, data-driven charts, shape layouts, and speaker notes auto-generated from templates.

PowerPoint Slides Charts Shapes

Documentation Pipeline

Markdown documents built with the fluent API, parsed into typed ASTs, and rendered to HTML for blog posts and release notes.

Markdown HTML Blog CI/CD

Frequently Asked Questions

Does OfficeIMO require Microsoft Office to be installed?

No. OfficeIMO works entirely with Open XML standards and does not require Microsoft Office, COM automation, or any Office interop assemblies. It runs on any platform where .NET is available.

What .NET versions are supported?

OfficeIMO targets .NET 8.0, .NET 10.0, .NET Standard 2.0, and .NET Framework 4.7.2. This means it works with .NET Core, .NET 5+, and legacy .NET Framework projects.

Is OfficeIMO free for commercial use?

Yes. The OfficeIMO packages themselves are published under the MIT License. However, some optional package families build on third-party dependencies with their own upstream terms, so commercial teams should also review our Third-Party Dependencies page during OSS approval.

How does OfficeIMO compare to Aspose or GemBox?

OfficeIMO is an open-source MIT-licensed option focused on COM-free Open XML workflows, while products like Aspose or GemBox are commercial suites with broader vendor support and different format coverage. Pricing, editions, and support terms change over time, so verify current details with each vendor directly. Our comparison page focuses on trade-offs rather than fixed price claims.

Can I use OfficeIMO in a Docker container or CI/CD pipeline?

Yes. Because OfficeIMO is COM-free and runs on .NET, it fits well in Linux containers, GitHub Actions, Azure DevOps, and other CI/CD environments. For rendering-heavy scenarios such as PDF output, validate the fonts and native dependencies you plan to ship with your container image.

View All FAQs

Start Building Office Documents Today

Free, open source, and MIT licensed. Install in seconds.

.NET dotnet add package OfficeIMO.Word
PowerShell Install-Module PSWriteOffice
Get Started