That distinction is easy to miss in the launch language. Nextcloud describes the desktop application as central to Hub 26 Summer, and Neowin characterized the release as bringing Euro-Office to the desktop. Yet Nextcloud’s own availability notice separates the shipped Hub 26 Summer server release from the still-pending client download. Independent reporting by Tweakers likewise says the app is due in coming weeks, rather than available now.
For Windows users evaluating alternatives to Microsoft 365, the promise is meaningful: Euro-Office should move document, spreadsheet, and presentation editing out of a browser tab while retaining a connection to a Nextcloud instance. But organizations should treat it as an announced client, not as a completed deployment option, until Nextcloud publishes installers, version numbers, support documentation, and a clear operating model.
A desktop editor changes the practical comparison
Euro-Office arrived as a web-first product. Nextcloud introduced it with Hub 26 Spring in June as an option for Nextcloud Office, allowing organizations to run browser-based editors alongside their own file storage and collaboration platform. The server-side product can edit text documents, spreadsheets, presentations, and PDFs through a Euro-Office Document Server connected to Nextcloud.
That approach has a clear appeal for centrally managed environments: users open documents from a familiar shared repository, administrators retain control of the hosting environment, and collaboration happens inside the same platform used for files, calendars, chat, and access management. It also means the office editor depends on a browser session and a reachable Nextcloud deployment.
A native Windows client addresses a different usage pattern. Many office workers still expect documents to open in a dedicated application with a taskbar presence, separate windows, local file associations, and behavior that does not feel like a web page wrapped around an editor. For IT teams, desktop availability is also a prerequisite for a credible pilot among employees whose workflows depend on Windows PCs rather than browser-only managed devices.
Nextcloud says the client will let people edit locally while keeping files connected to Nextcloud. The company has not yet explained whether “locally” means full offline editing with later synchronization, a desktop shell that still needs the service online, or a mixture of both. That is more than a wording issue. Offline behavior, conflict handling, authentication, local caching, and data residency on endpoint devices determine whether a client fits a regulated or tightly managed Windows environment.
Windows on Arm is included, but the deployment details are absent
Tweakers reports that Euro-Office is planned for Windows on both x64 and Arm64, as well as Linux on x64 and Arm64. macOS support is expected for Arm64 systems. Windows on Arm support would be notable, because it avoids making organizations rely on x64 emulation for a core productivity application on newer Qualcomm-based PCs.
Nextcloud has not yet provided the more operational details that Windows administrators need before they can assess that claim. There is no published installer format, no stated minimum Windows release, no supported Windows Server scenario, no Microsoft Intune or Configuration Manager guidance, and no word on whether the application will support enterprise deployment controls such as per-machine installation, silent installation, managed updates, or policy configuration.
There is also no public statement on document association behavior. A full desktop-office replacement needs to answer basic but consequential questions: Can a user double-click a DOCX, XLSX, or PPTX file in File Explorer? Does the client open local files outside a synchronized Nextcloud folder? Can an organization set Euro-Office as the default handler without breaking Office macros, add-ins, or workflows that rely on Microsoft-specific features?
Those omissions do not mean the capabilities will be absent. They mean there is currently no basis for an IT department to promise them to users. Nextcloud’s existing desktop sync client already operates across Windows, macOS, and Linux, but it is a file synchronization application, not an office editor. The forthcoming Euro-Office app should not be confused with that established client until the company documents their integration and installation path.
The server component remains the administrative center
For organizations already using Euro-Office in Nextcloud, the desktop app is only one part of the stack. Nextcloud’s deployment instructions say the Euro-Office Document Server performs rendering and editing, while a Nextcloud Office connector app links the service to a Nextcloud instance.
The documented self-hosted server setup is substantial enough to matter in capacity planning. Nextcloud lists a minimum of 4GB of RAM, recommends 8GB for multi-user deployments, and calls for HTTPS connectivity between Nextcloud and the Document Server in production. Its Ubuntu and Debian deployment guide also lists PostgreSQL, Redis, RabbitMQ, nginx, and Supervisor among the dependencies, while Docker is presented as an alternative installation method.
In other words, the Windows app will not eliminate the need to operate or subscribe to an office backend. It is expected to make the user endpoint more conventional; it does not turn Euro-Office into a simple standalone replacement for a locally installed copy of Microsoft Office.
That architecture could still be an advantage for organizations seeking control over their document service. An enterprise can host the Nextcloud and Euro-Office components on-premises or through a provider it selects, rather than placing the content in Microsoft’s cloud by default. But it also makes Euro-Office a deployment decision involving identity, reverse proxies, TLS certificates, backup procedures, monitoring, and patch management—not simply a desktop-software swap.
Format compatibility remains the harder migration problem
Euro-Office is based on a fork of OnlyOffice, according to Nextcloud, Tuta, and reporting by Tweakers. The project’s founders have framed the fork as a way to establish European stewardship over a product intended to compete with Microsoft Office and Google Workspace, with contributors including Nextcloud, IONOS, Open-Xchange, Office.eu, Tuta, and others.
The choice gives Euro-Office a foundation built around compatibility with Microsoft Office formats. That can lower migration friction for organizations that exchange DOCX, XLSX, and PPTX files every day. Nextcloud’s initial Euro-Office documentation emphasizes high-fidelity rendering, while Tweakers reported in May that the stable release supported both OpenDocument Format files and standard Microsoft Office formats.
However, Microsoft-format fidelity and digital sovereignty are not identical goals. The Document Foundation, the nonprofit behind LibreOffice, has publicly argued that a sovereignty project should use the OpenDocument Format, or ODF, as its native default rather than Microsoft’s OOXML formats. Its criticism focuses on long-term control over the document format as well as over the servers and source code.
Nextcloud and Euro-Office have not publicly resolved that disagreement by announcing a change in default file format. For a Windows organization, this is a procurement issue rather than an ideological one. Teams that must exchange complex Microsoft Office documents may prioritize compatibility; public bodies building long-lived archives may instead place greater weight on ODF defaults and format governance. A desktop application does not settle that tradeoff.
The earlier fork also drew a public licensing and branding dispute with OnlyOffice. Tweakers reported that the dispute was subsequently resolved, while Nextcloud’s current materials describe Euro-Office as released under open-source licensing and developed through a public process. The relevant point for prospective adopters is that Euro-Office is still a young fork: it has had a stable web release only since June 2026, and the desktop client will be its next major proof point.
What Windows administrators can do before the client ships
Organizations already running Nextcloud can prepare without treating the announcement as a green light for wide deployment.
- Validate Euro-Office document fidelity against the organization’s actual DOCX, XLSX, PPTX, and ODF files, especially templates, tracked changes, formulas, charts, and externally supplied documents.
- Review the Document Server design, including HTTPS exposure, JWT secret management, service monitoring, backups, and the resources needed for concurrent editors.
- Identify groups that genuinely need desktop editing and separate them from users whose work is already well served through a browser and synchronized files.
- Wait for Nextcloud to publish the Windows installer, supported Windows versions, update mechanism, and endpoint-management guidance before adding the client to a software catalog.
Nextcloud has made an important promise for Windows users, particularly those seeking a self-hosted productivity platform that does not start with Microsoft 365. But as of September 17, 2026, the product that matters to them—the Euro-Office desktop app—remains pending. The decisive date will be the actual client release, when IT teams can test how it installs, authenticates, handles local and offline files, and copes with the Microsoft Office documents their users already have.