Help · Deployment

Supported operating systems

OfficeAPI runs on 6 operating systems — Windows, Linux, macOS, Android, iOS, and HarmonyOS — on local devices and in cloud environments you manage, with zero dependencies.

Definition. A supported operating system is a platform on which the OfficeAPI engine ships and runs with its full documented capability: the same 42 conversion pairs, 32 preview extensions, and both integration paths.

Which operating systems does OfficeAPI support?

OfficeAPI supports 6 mainstream desktop, mobile, and server operating systems, so one integration can cover every platform your product ships to.

Platform Class Typical deployment
Windows Desktop / server Desktop applications, Windows servers
Linux Server / desktop Servers, containers, desktop applications
macOS Desktop Desktop applications
Android Mobile Mobile applications
iOS Mobile Mobile applications
HarmonyOS Mobile / device Mobile and device applications

Is the behaviour the same on every platform?

Yes. Format coverage, offline operation, and the two integration paths are identical across the 6 systems. The dynamic library is available on all of them; process invocation works wherever your platform allows starting a process.

Local device or cloud?

Because OfficeAPI is fully offline, the same engine can run:

  • on the device — inside a desktop or mobile application, so documents never leave the user's machine;
  • in your cloud — on servers you operate, as a library inside your service or as a process you start.

There is no OfficeAPI-hosted service in either case.

On the device In your cloud
Platforms Windows, macOS, Linux, Android, iOS, HarmonyOS Linux, Windows servers
Data location User's device Your infrastructure
Network needed No No (internal only)

How do you plan a multi-platform rollout?

  1. List the platforms your product ships to and confirm each is one of the 6 above.
  2. Pick one integration path per platform (library where a supported language is available, process otherwise).
  3. Package the zero-dependency engine with each build; no office suite or rendering service is installed alongside it.
  4. Verify your input and output formats once; they do not vary by platform.

Frequently asked questions

Does OfficeAPI need an office suite installed on the machine?

No. OfficeAPI ships without runtime dependencies on any of the 6 platforms.

Can the same build serve desktop and mobile?

You ship a build per platform, but the engine, formats, and behaviour are the same across all of them.

Is there a hosted or browser-based version?

No. OfficeAPI runs on the device or on servers you manage.

References

Ready to integrate

Bring the engine into your product.

Compare integration paths