Office file conversion SDK

Convert Office files inside your product.

Convert DOCX to PDF and PDF back to DOCX, plus XLSX and PPTX to PDF. Run the binary where the file lives, or use the SDK libraries to create, edit, read, and convert Office files.

An agent reads a weekly report from email, OfficeAPI creates a DOCX report, converts it to PNG for a work group, and keeps the DOCX for later editing.

conversion workflow

Supported formats

Read and write Office formats.

Each family shows the formats OfficeAPI can read and the formats it can produce.

01

Word

Input formats

10
Office new
  • DOCX
  • DOTX
  • DOCM
  • DOTM
Office legacy
  • DOC
  • DOT
WPS
  • WPS
  • WPT
OpenDocument
  • ODT
Text
  • RTF

Output formats

8
Office new
  • DOCX
Layout
  • PDF
Images
  • JPEG
  • PNG
  • BMP
  • SVG
  • TIFF
  • EMF
02

Excel

Input formats

10
Office new
  • XLSX
  • XLSM
  • XLTX
  • XLTM
Office legacy
  • XLS
  • XLT
WPS
  • ET
  • ETT
Text
  • CSV
OpenDocument
  • ODS

Output formats

9
Office new
  • XLSX
Text
  • CSV
Layout
  • PDF
Images
  • JPEG
  • PNG
  • BMP
  • SVG
  • TIFF
  • EMF
03

PowerPoint

Input formats

10
Office new
  • PPTX
  • PPTM
  • POTX
  • POTM
Office legacy
  • PPT
  • POT
WPS
  • DPS
  • DPT
OpenDocument
  • ODP
Layout
  • PDF

Output formats

2
Office new
  • PPTX
Layout
  • PDF

AI workflows

AI workflows still need a file step.

OfficeAPI is not an AI model. It gives agents and pipelines a way to create, convert, read, and deliver Word, Excel, PowerPoint, and PDF files.

Weekly report

Create the report and send a preview image.

Send a preview image. Keep the editable Word file.

OfficeAPI creates the DOCX, converts it to PNG for the work group, and keeps the DOCX available for the next edit.

Knowledge ingestion

Prepare our Office files for search.

Convert files before indexing.

Convert Word, Excel, and PowerPoint files into the format your pipeline reads before chunking, embedding, or retrieval.

Operations automation

Send the weekly pack.

Deliver spreadsheets and decks as PDF.

When a workflow generates a workbook or presentation, convert it to PDF before sending it to customers or teammates.

SDK

Run conversion as a binary. Embed file operations as libraries.

Run the conversion binary on a server or client where the file already lives. Or use Rust, Go, Java, and C++ libraries to create, edit, read, and convert Office files in your product.

Conversion binary

Run conversion on the server or client.

Use the binary on a mainstream operating system and convert the file where it already lives.

Office libraries

Create and edit Office files in code.

Use Rust, Go, Java, or C++ libraries to create, edit, read, and convert Office files inside your product.

  • Rust
  • Go
  • Java
  • C++

Create

Build Word, Excel, and PowerPoint files from application data.

Edit

Update an existing Office file in code.

Read

Open an Office file and extract the content your product needs.

Convert

Convert between supported formats, including DOCX to PDF and PDF to DOCX.

How it works

Convert a file in three steps.

Choose the file you have, choose the format you need next, and return the result to your product, user, or agent.

$office.convert(input, output)
  1. 01

    Choose the source

    Start with the Office file you already have: Word, Excel, PowerPoint, or PDF.

  2. 02

    Choose the target

    Select the output format the product, user, or agent needs next.

  3. 03

    Use the result

    Return the converted file to the user, to storage, or to the next workflow step.

Why OfficeAPI

A practical file layer for products and agents.

01

Supported conversions

Convert the formats your workflow needs.

DOCX to PDF and PDF to DOCX, plus XLSX to PDF and PPTX to PDF.

02

Product-ready delivery

Choose a binary or a library.

Run conversion on a server or client, or call Rust, Go, Java, and C++ libraries from your own code.

03

Agent-ready files

Give AI workflows a reliable file step.

Agents and pipelines still need files they can create, convert, read, and send. OfficeAPI handles that step.

FAQ

Common OfficeAPI questions.

A quick overview of supported conversions, delivery options, and how OfficeAPI fits into AI workflows.

What is OfficeAPI?

OfficeAPI is an Office file conversion SDK. It provides a conversion binary plus Rust, Go, Java, and C++ libraries for working with Office files. Supported examples include DOCX to PDF, PDF to DOCX, XLSX to PDF, and PPTX to PDF.

Can it convert Word to PDF and PDF to Word?

Yes. DOCX can be converted to PDF, and PDF can be converted back to DOCX when the next step needs an editable Word file.

Does it convert Excel to PDF and PowerPoint to PDF?

Yes. OfficeAPI supports XLSX to PDF and PPTX to PDF for sharing workbooks and presentations as PDF.

Is OfficeAPI a binary or a library?

Both. The conversion binary runs on a server or client on mainstream operating systems. Rust, Go, Java, and C++ libraries let your product create, edit, read, and convert Office files in code.

Does OfficeAPI include an AI model?

No. OfficeAPI provides file operations for AI workflows; it does not provide an AI model. Agents and pipelines can use it to create, convert, read, and send Office files.

Start with the SDK

Add Office file conversion to your product.

Explore the SDK