Skip to main content
Get Started
OfficeIMO Docs Search documentation/
API ReferencePackagesGitHub

Browser Converter

Edit on GitHub

Run supported OfficeIMO conversions locally through the WebAssembly app on OfficeIMO.com. Includes examples and API links.

The browser converter is a static Blazor WebAssembly application. Supported conversions execute inside the current tab; selected files are not uploaded to OfficeIMO.

Supported browser routes

SourceOutputEngine
DOCXPDFOfficeIMO.Word.Pdf
XLSXPDFOfficeIMO.Excel.Pdf
PPTXPDFOfficeIMO.PowerPoint.Pdf
HTMLPDFOfficeIMO.Html.Pdf
MarkdownHTML preview and downloadOfficeIMO.MarkdownRenderer
HTMLMarkdownOfficeIMO.Markdown.Html
MarkdownDOCXOfficeIMO.Word.Markdown

The app includes sample inputs for every route. Files are limited to 25 MiB. Before a DOCX, XLSX, or PPTX file is parsed, the app also rejects packages with more than 5,000 parts, an individual expanded part over 32 MiB, more than 128 MiB expanded in total, or a part compression ratio over 200:1.

Excel workbooks that pass those package checks are converted in full while every sheet's used range stays within 50,000 cells. If a sheet exceeds that budget, the app automatically generates a preview of up to 250 rows per sheet. Conversion warnings stay visible with the result instead of being hidden behind a successful download.

Privacy and hosting

Browser-local processing is the strongest privacy default for a public demo because document bytes do not cross a server boundary. It is not the right execution model for every production workload.

Host OfficeIMO in your own service when you need larger inputs, authentication, queues, storage, audit logs, or formats that are not suitable for WebAssembly. In that model, your organization owns the transport, access, logging, and retention policy.

Publishing contract

The website pipeline builds the converter from its project source and mounts the published wwwroot output under /apps/officeimo-converter/. This keeps the deployed WebAssembly assets and integrity metadata aligned with the source in the same build.

The production-shaped publish relinks the converter's native WebAssembly assets, including HarfBuzz. Install the matching SDK's wasm-tools workload once before running it:

dotnet workload install wasm-tools
pwsh -NoProfile -File .\Website\build.ps1 -PowerForgeRoot C:\path\to\PSPublishModule

Use dotnet workload list to verify the workload on an existing build machine. Use -Dev for a faster content/API build. The converter project itself can be checked directly with:

dotnet build .\Website\Apps\OfficeIMO.Web.Converter\OfficeIMO.Web.Converter.csproj -c Release