Published: Last updated:

LibreOffice

Local office suite

LibreOffice is a free, open-source office suite for documents, spreadsheets and presentations, stewarded by the non-profit Document Foundation. It is built natively on the open OpenDocument Format, runs locally on the organisation's own infrastructure, and positions itself as a sovereign alternative to Microsoft 365.

LibreOffice began in 2010 as a fork of OpenOffice.org and has been developed since by a community of volunteers and companies. Unlike a hosted productivity cloud, LibreOffice is a desktop suite that works with no account, no subscription and no data flowing into a foreign cloud. This page sets out what LibreOffice is technically, how it relates to the OpenDocument Format, where its compatibility with the Microsoft formats reaches its limits, and why it is a recurring reference point in the question of digital sovereignty.

What the suite contains

LibreOffice bundles six applications under a shared interface. They cover the same scope a typical office environment expects from an office suite:

  • Writer. Word processing from quick notes to full-length books.
  • Calc. Spreadsheets for analysis, calculations and charts.
  • Impress. Presentations with slides and multimedia.
  • Draw. Drawings, diagrams and simple illustrations.
  • Base. A database front end for tables, forms and queries.
  • Math. An editor for mathematical formulas.

The suite runs on Windows, macOS and Linux and is available in many languages. It is installed on the endpoint in the classic way; a server-side variant for browser-based editing exists separately as LibreOffice Online and in products built on it, but that is not the core of this desktop suite.

Licence and stewardship

LibreOffice is made available under the Mozilla Public License v2.0 (MPL 2.0); contributions are historically dual-licensed under MPL 2.0 and LGPLv3+. The source code is open to inspection and modification. The project is stewarded by The Document Foundation, a charitable foundation under German law (a Stiftung) based in Berlin, announced in 2010 and formally registered as a foundation in 2012. This construction matters for the sovereignty question: behind LibreOffice there is no single commercial vendor whose ownership or jurisdiction could change, but a foundation with an open membership base. That makes LibreOffice independent of any single corporation's business strategy, while at the same time placing maintenance and support more firmly in the hands of the using organisation or specialised service providers.

ODF native, OOXML as an import path

The technical core of LibreOffice is the OpenDocument Format (ODF) with the extensions ODT, ODS and ODP. ODF is an open XML standard maintained at OASIS and standardised as an ISO/IEC norm; it is the default format in which LibreOffice saves. This is exactly where it differs from suites that carry OOXML as their core and support ODF only as an addition, such as the European suite Euro-Office derived from ONLYOFFICE.

LibreOffice can open and save the Microsoft formats DOCX, XLSX and PPTX, but that support runs through import and export filters, not through a native data model. In practice that means: simple documents move losslessly, yet with complex layouts, embedded macros (VBA), pivot tables or conditional formatting, deviations can occur. Anyone who exchanges documents regularly with a pure Microsoft environment should test filter fidelity against their own files instead of assuming lossless compatibility. This qualification is not a detail but the decisive point of any migration decision.

The format decision

Which format forms the core shapes the sovereignty of an office environment more than the choice of tool. The following view shows what LibreOffice is built for and where the reconciliation with the Microsoft world begins:

flowchart TD
    A["Document in LibreOffice"] --> B{"Target environment?"}
    B -->|"own corpus"| C["save as ODF<br/>ODT, ODS, ODP"]
    B -->|"exchange with Microsoft"| D["OOXML via filter<br/>DOCX, XLSX, PPTX"]
    C --> E["open ISO standard<br/>readable long term"]
    D --> F["test filter fidelity<br/>layout, macros, pivot"]

The path to the left is the safe one: ODF is an open standard that decouples the long-term readability of documents from any single vendor. The path to the right is the reality check: as long as counterparts work in OOXML, the filter path stays necessary, and its fidelity needs testing.

Documents stay on the organisation's own machines

LibreOffice is a concrete example of what digital sovereignty looks like in everyday office work. Anyone editing documents in Microsoft 365 potentially hands content and telemetry into a foreign jurisdiction; where the US Cloud Act applies, a US provider can be compelled to disclose data, even when it is held in Europe. A locally installed, open-source suite keeps documents and editing within the organisation's own control perimeter and eases compliance with the revised Swiss Data Protection Act (revFADP). That this lever is real is shown by the German state of Schleswig-Holstein, which is moving around 30,000 workstations from Microsoft Office to LibreOffice and Linux, expressly citing independence from a single vendor.

For Swiss organisations, LibreOffice remains a building-block decision, not a turnkey offering. The sober weighing against the established Microsoft world, including migration effort, training and compatibility limits, should be tested against the organisation's own files before any switch. As a younger, OOXML-strong and European-stewarded alternative, Euro-Office stands alongside it, taking a different technical path.

Where the limits are

  • Compatibility is filter work. The Microsoft formats are supported through filters, not natively. With complex documents, VBA macros or pivot tables, deviations can occur that should be tested against the organisation's own files before a switch.
  • Desktop, not cloud. LibreOffice is at its core a desktop suite. Real-time browser collaboration, as known from productivity clouds, requires separate, server-side components.
  • Maintenance sits with the organisation. Without a vendor contract there is no bundled support. Updates, training and operation are the responsibility of the using organisation or a specialised service provider.
  • End-user familiarity. The interaction model and feature details differ in places from the familiar Microsoft interface. The switch is not purely a licensing question but also one of onboarding.

References

Related topics

Ask AI

These links open external AI services, the conversation and its content are sent to their providers.