Documents stay on the device
OfficeAPI runs fully offline inside your desktop or mobile app. The file the model works on is never uploaded to a conversion service.
OfficeAPI for on-device AI
Give local models the documents they need, without leaving the device.
On-device AI works on the files people already have: contracts, spreadsheets, decks. OfficeAPI converts those Office files into PDF, images, and CSV right on the device, renders previews for the user, and never uploads anything.
The loop
From a file on the device to a model, and back to the user.
Every step runs where your app runs. The document is converted, read, and previewed on the same device.
- 01On the devicecontract.docx
- 02OfficeAPIconvert · render
- 03Local modelcontract.pdf / pages.png / table.csv
- 04Back to the userin-app preview
Why on the device
Three things OfficeAPI does for an on-device AI feature.
Formats a local model can consume
Convert Word, Excel, and PowerPoint files to PDF, JPEG/PNG/BMP images, or CSV on the device, then hand the result to whatever model runs beside your app.
Preview closes the loop
Render the original or the generated document in your own UI so the user can see what the model saw and approve what it produced.
What the model receives
Output formats a local pipeline can read.
Pick the representation your model or pipeline consumes. Every pair below is documented in the conversion matrix.
Open the conversion matrix- PDFvector or image-onlyWord · Excel · PowerPoint
- JPEG · PNG · BMPpage bitmapsWord · Excel
- SVG · TIFF · EMFvector pagesWord · Excel
- CSVtabular dataExcel
Where it ships
The same engine on every device your model runs on.
OfficeAPI has zero dependencies, so it travels inside your app to desktop and mobile alike. Link it as a dynamic library or run it as a process.
RustGoJavaC++Pythonand more
- 01Windows
- 02Linux
- 03macOS
- 04Android
- 05iOS
- 06HarmonyOS
- Does OfficeAPI send documents to a server for AI processing?
- No. OfficeAPI is designed for offline execution and runs on the device or in a cloud environment you manage. It converts and previews files locally; it does not upload them.
- Which output formats are useful for a local model?
- OfficeAPI writes PDF (vector and image-only), bitmap images (JPEG, PNG, BMP), vector images (SVG, TIFF, EMF) for Word and Excel, and CSV for Excel. Pick the one your model or pipeline reads best.
- Which platforms can run OfficeAPI next to an on-device model?
- Windows, Linux, macOS, Android, iOS, and HarmonyOS. OfficeAPI has zero dependencies, so it ships inside your app without an office suite or rendering service.
- How does my app call OfficeAPI?
- Link it as a dynamic library from Rust, Go, Java, C++, Python, or another supported language, or invoke it as a process. Both paths run offline.
Start building