OfficeAPI · Rust document engine for products and on-device AI

Convert and preview office files inside your own product.

OfficeAPI is a document engine written in Rust. Embed it as a library or run it as a process, and it converts and previews Word, Excel, and PowerPoint files entirely offline — for your users and for the models running beside them.

Fully offline · Zero dependencies · Runs on six operating systems

receive · file handed to the engine
Word documentreport.docx
OfficeAPIRust core
Converted filereport.pdf
PreviewPage 1 of 12

The file never leaves the device — not for users, not for local models.

The demo cycles through receiving a Word document, processing it, and delivering a PDF and a preview. It rests on the final stage when reduced motion is enabled.

34input formats
15output formats
32preview extensions
6operating systems

How it works

Three steps. None of them leave your product.

  1. 01

    Hand over the file

    Your product passes an office file to OfficeAPI through a library call or a process.

  2. 02

    The engine does the work

    OfficeAPI reads the document and converts it or renders a preview, offline.

  3. 03

    Take the result back

    A converted file or a preview comes back to the surface your users are already on.

Two surfaces, one core

Conversion and preview from the same engine.

Both surfaces read the same documents, so a file you can convert is a file you can also show.

01

Conversion

Read and write Word, Excel, and PowerPoint formats, from Office Open XML and 97–2003 files to WPS, OpenDocument, PDF, images, and text.

Browse conversion formats
02

Preview

Render documents, spreadsheets, and presentations for display inside your product, with no separate viewer service.

Browse preview formats

Why Rust matters here

Built for the places a hosted service cannot go.

Cross-platform, simple to integrate

One engine runs on desktop, mobile, and server operating systems and plugs in through a library or a process.

Memory-safe and fast

Written in Rust, OfficeAPI combines memory safety with native performance on every platform it runs on.

Broad format coverage

Word, Excel, and PowerPoint families, including WPS and OpenDocument, with strong compatibility across versions.

Fully offline

Deploy on a local device or in a cloud environment you manage. No file is sent to a hosted service.

Zero dependencies

Ship OfficeAPI on its own, with nothing else to install or keep up to date alongside it.

Where it runs

Desktop, mobile, and server. Same engine.

OfficeAPI ships to the operating systems your product already targets, so the document step travels with the file instead of routing through a server.

See integration paths
  • 01Windows
  • 02Linux
  • 03macOS
  • 04Android
  • 05iOS
  • 06HarmonyOS

Two ways in

Call it as a library or run it as a process.

Pick the boundary that fits your architecture. Both paths run offline and speak to the same Rust core.

Compare integration paths

In-process, lowest overhead

Dynamic library

Link OfficeAPI directly into your application. Bindings are provided for Rust, Go, Java, C++, Python, and other popular languages.

Isolated, language-agnostic

Process invocation

Run OfficeAPI as a separate process and talk to it across a clear boundary, independent of your application's language or runtime.

RustGoJavaC++Pythonand more

Questions

The short answers.

What is OfficeAPI?
OfficeAPI is a Rust-based document engine for converting and previewing office files inside your own product.
Can OfficeAPI run offline?
Yes. OfficeAPI is designed for offline execution, with deployment on a local device or in a cloud environment you manage.
How do I integrate OfficeAPI?
Use the dynamic library from Rust, Go, Java, C++, Python, or another supported language, or invoke OfficeAPI as a process.
Which platforms does OfficeAPI support?
OfficeAPI runs on Windows, Linux, macOS, Android, iOS, and HarmonyOS.

Start with the formats

See what OfficeAPI can do with the files you already have.

Browse supported formats