ONLYOFFICE Desktop Editors: an offline OOXML suite built from a server core
Open-source office suite pack that comprises all the tools you need to work with documents, spreadsheets, presentations, PDFs, and PDF forms on Windows, Linux, and macOS
At a glance
- What is it?
- The repository is a pack of six submodules rather than a single application, and that structure explains both its format fidelity and its install story. A look at what it does offline, what the AGPL covers, and which questions to settle before rolling it out.
- Who is it for?
- Adopt it if you need offline editing of Office Open XML files with PDF form support and you are willing to install from deb, rpm, exe, dmg, Snap, Flatpak or AppImage packages. Do not adopt it if your requirement is a fully self-hosted stack where every component is auditable from this repository alone, because the interface and SDK layers live in separate repositories, and do not treat the AGPL-3.0 licence as settled until your own counsel has read the LICENSE file.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 131 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on September 29, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What ONLYOFFICE Desktop Editors actually solves, and for whom
The problem is narrow and specific: editing .docx, .xlsx and .pptx files on a desktop without a network connection, while keeping enough format fidelity that the file still opens correctly in Microsoft Office afterwards. The README states the application allows creating, viewing and editing documents stored on a Windows, Linux or macOS machine without an Internet connection, and that it is fully compatible with Office Open XML formats.
The audience follows from that. Anyone who receives OOXML attachments and cannot send them to a cloud service: people working under data handling rules, people on air-gapped machines, people who simply do not want a browser tab between them and a spreadsheet. PDF forms matter here too. The suite includes a Form Creator and a PDF Editor, so filling a PDF form is an in-application task rather than a separate download.
What it is not is a Word clone with a plugin ecosystem bolted on. The README frames plugins as a way for developers to add features not directly related to the OOXML format, which is an honest description of the boundary: the core is a format engine, and everything else is an extension.
Six submodules: the architecture behind the desktop app
The repository is not a monolith. The top level contains core, desktop-apps, desktop-sdk, sdkjs, web-apps and dictionaries, and the README describes each one. desktop-apps is the frontend used to build the program interface for the chosen operating system. desktop-sdk is the SDK described as a core part of the editors. sdkjs is the JavaScript SDK containing the client-side API. web-apps is the frontend that lets a user create, edit, save and export text, spreadsheet and presentation documents through a common document editor interface. core holds server core components for ONLYOFFICE Document Server, and the README says it is the part used to enable conversion between popular office formats, listing DOC, DOCX, ODT, RTF, TXT, PDF, HTML, EPUB, XPS, DjVu, XLS, XLSX, ODS, CSV, PPT, PPTX and ODP. dictionaries supplies spellchecking dictionaries.
That layout is the single most useful fact for a technical evaluator, because it tells you where a bug or a patch belongs. A rendering problem in the editor surface is a web-apps or sdkjs concern. A file that converts badly is a core concern. A packaging problem on Linux is a desktop-apps concern. The practical consequence is that a fix for your issue may land in a repository that is not the one you are reading, and the CHANGELOG.md here will not necessarily mention it.
It also means the desktop application carries a component named for a server. The README is explicit that core is server core components for Document Server and that it is a part of the desktop editors, so the conversion pipeline is shared rather than reimplemented for the desktop build.
Installing ONLYOFFICE Desktop Editors and opening a first file
The README points to deb, rpm, exe and dmg packages from the official website, and lists Snap, Flatpak and AppImage as alternatives. The commands below are the distribution-channel ones, because those are the ones a Linux user can reproduce from a terminal. Run them only if your system is set up for that channel.
For Snap, the README directs you to snapcraft.io:
snap install onlyoffice-desktopeditorsFor Flatpak, the README directs you to flathub.org under the application ID org.onlyoffice.desktopeditors:
flatpak install flathub org.onlyoffice.desktopeditors
flatpak run org.onlyoffice.desktopeditorsThe first command installs the application from Flathub. The second launches it; if the install succeeded you should see the suite's start screen rather than a missing-runtime error. On Windows and macOS the README gives no command line path at all, only the exe and dmg packages from the download page, so there is nothing to paste into a terminal there.
Once the application is open, the first real use is to create a document locally: the README says the application allows creating, viewing and editing documents stored on your PC or Mac without an Internet connection. Opening an existing .docx from local storage is the honest test of the format claim, because it exercises the conversion path described for core. If you want to use the cloud connectors, the README lists ONLYOFFICE, Moodle, Box, Dropbox, ownCloud, Nextcloud, Seafile, Liferay and kDrive as supported targets; the connection is configured from inside the application, and the README does not document the exact dialog steps.
Where the desktop build stops being the right tool
The most concrete limitation is the one the repository structure creates: the desktop application is assembled from submodules, and the README sends anyone who wants to build it to build_tools rather than giving instructions here. If your organisation needs a reproducible in-house build with a pinned toolchain, this repository alone does not provide that recipe. You are following a link to another repository and inheriting whatever state it is in.
The second limitation is scope creep in the other direction. The README's plugin section is clear that plugins exist for features not directly related to the OOXML format. If your workflow depends on a specific macro or plugin, that is an extension surface, not a core guarantee, and the API documentation lives at api.onlyoffice.com rather than in this repository.
The third is a licensing boundary that is easy to misread. The suite is licensed under AGPL-3.0, and the README's LICENSE link points at a docspace.onlyoffice.com share rather than a file in the tree. That is unusual for an AGPL project and worth noting: the licence text you are expected to read is hosted off-repository. Whether that matters to you depends on whether you are merely using the desktop application or planning to distribute a modified build, and the second case is where AGPL-3.0 obligations become a question for your own legal review rather than for a README.
Finally, if your actual requirement is browser-based collaborative editing with server-side storage, the desktop application is the wrong entry point. The README repeatedly references ONLYOFFICE Document Server as the thing that core, sdkjs and web-apps belong to; the desktop build packages those pieces for local use.
How it compares with LibreOffice on the same desktop
LibreOffice is the obvious alternative for the same job, and the difference is architectural rather than cosmetic. LibreOffice is a native office suite with its own document model and its own file format lineage, importing OOXML through filters. ONLYOFFICE Desktop Editors, by the README's own description, is built around OOXML compatibility as the primary target and reuses a server core for conversion between a long list of formats.
That distinction shows up in day-to-day behaviour more than in feature checklists. A suite whose native model is OOXML tends to round-trip .docx and .xlsx with fewer surprises in layout-sensitive documents, because the internal representation is closer to the file on disk. A suite with a different native model can be more predictable for its own formats and more variable when importing someone else's.
The second difference is the collaboration story. The README lists connectors to ONLYOFFICE, Moodle, Box, Dropbox, ownCloud, Nextcloud, Seafile, Liferay and kDrive for real-time collaboration. LibreOffice's comparable path runs through its own document foundation infrastructure rather than those specific services. If your files already live in Nextcloud or ownCloud, the connector list is the deciding fact, not the editor's feature set.
The third is extensibility. LibreOffice macros are a long-established surface. Here the extension surface is a JavaScript plugin API documented at api.onlyoffice.com, with a marketplace of existing plugins. Neither is better in the abstract; they are different skills to hire for.
Release cadence, upgrade cost and what the licence asks of you
The release history is steady. v9.3.0 arrived on 2026-02-25, v9.3.1 on 2026-03-03, and v9.4.0 on 2026-05-19, with the last push to the repository on 2026-05-21. That is a maintenance cadence measured in weeks, not years, and the patch release three weeks after a minor suggests fixes ship between feature drops.
Upgrade cost depends entirely on which channel you chose. Snap and Flatpak users get updates through their package manager, which is the low-effort path. Users who installed a deb, rpm, exe or dmg from the download page are responsible for fetching the next package themselves; the README does not describe an in-application updater or a self-update mechanism, so plan for a manual download at each release unless your platform's package tooling covers it. AppImage users replace a file.
The licence is AGPL-3.0. For an individual or a company installing the desktop application to edit its own documents, the practical question is simply whether the terms are acceptable. For anyone modifying the code and making it available over a network, AGPL-3.0 carries obligations that differ from permissive licences, and the README's licence link points outside the repository. Read the actual LICENSE file before you build on this in a distributed product. That is a boundary to check, not a conclusion anyone else can draw for you.
Editorial conclusion
Adopt it if you need offline editing of Office Open XML files with PDF form support and you are willing to install from deb, rpm, exe, dmg, Snap, Flatpak or AppImage packages. Do not adopt it if your requirement is a fully self-hosted stack where every component is auditable from this repository alone, because the interface and SDK layers live in separate repositories, and do not treat the AGPL-3.0 licence as settled until your own counsel has read the LICENSE file. Verify three things first: that the package you download matches the platform you actually run, that your collaboration targets appear in the documented connector list (ONLYOFFICE, Moodle, Box, Dropbox, ownCloud, Nextcloud, Seafile, Liferay, kDrive), and that you have read the build_tools instructions before promising anyone an in-house build.
Frequently asked questions
Is ONLYOFFICE Desktop Editors free?
The repository is licensed under the GNU Affero Public License, version 3.0, and the README describes the suite as a free office suite. The AGPL-3.0 terms still apply to the code, so free to use is not the same as free of licence conditions.
Is ONLYOFFICE a legitimate and reliable service?
The repository describes ONLYOFFICE Desktop Editors as an AGPL-3.0 licensed application with packages published through the official website, Snapcraft, Flathub and AppImageHub, with source repositories for each. Judgements about the company behind it are not something these files establish.
Is ONLYOFFICE a Russian company?
Nothing in the repository, README or release information addresses the company's corporate jurisdiction, so this question cannot be answered here. The README documents the software, its licence and its installation channels, not corporate ownership.
What is the best document editor for PC?
That depends on the format you receive. ONLYOFFICE Desktop Editors targets Office Open XML compatibility for .docx, .xlsx and .pptx and works offline on Windows, Linux and macOS, which suits people who exchange Office files and cannot use a cloud service.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/onlyoffice-desktopeditors)