Frequently Asked Questions

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.

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.

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.

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.

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.

PSWriteOffice is a PowerShell module that wraps the OfficeIMO .NET libraries. It provides 150+ cmdlets and DSL aliases for creating Office documents from PowerShell scripts without writing C#. Install it with Install-Module PSWriteOffice.

Yes. All core libraries (Word, Excel, PowerPoint) support both creating new documents and loading/editing existing ones. The OfficeIMO.Reader package provides a unified extraction API across all formats for AI ingestion and search indexing.

It depends on the package. OfficeIMO.CSV and OfficeIMO.Markdown are the strongest current fits for AOT- and trimming-sensitive workloads. The Open XML-based packages should be tested against your exact publish profile and deployment target before you rely on NativeAOT in production.

The core Office document packages are built on DocumentFormat.OpenXml, while image- and converter-oriented packages also use components such as SixLabors.ImageSharp, AngleSharp, and QuestPDF depending on the feature area. The Markdown and CSV core packages stay dependency-light. See the Third-Party Dependencies page for the package-by-package breakdown and upstream license notes.

Yes. The OfficeIMO.Word.Pdf converter package supports Word-to-PDF conversion without Office. There are also converters for Word-to-HTML and Word-to-Markdown.

OfficeIMO.Excel supports parallel execution for bulk operations like AutoFit and bulk writes. Each document instance is independent and can be used on separate threads. Concurrent access to a single document instance is not supported.