LibreOffice for Education: Regaining Digital Sovereignty

Every year, millions of students open a laptop and log into Microsoft 365 or Google Workspace, surrendering their digital sovereignty to US Big Tech in the process. Teachers use cloud-based editors to assign homework. School administrators manage documents in proprietary formats. This ecosystem runs smoothly and seemingly without friction, but almost no one questions the cost of this normalisation.

Unfortunately, the cost is quite high.

An invisible resume

Schools don’t just teach maths and history; they also teach mental processes, such as how to do research, think critically and interact with tools and institutions. Software is part of this invisible curriculum. A student who has spent years using Microsoft Word or Google Docs as the archetype of “word processing” or “collaboration” respectively has not developed neutral, transferable skills, but has become a future customer.

This is not a conspiracy, but rather the way markets work. Microsoft and Google both offer heavily discounted or even free licences to educational institutions, knowing that brand loyalty formed in childhood tends to persist into adulthood and the working world. The licence discount is, in commercial terms, the cost of acquiring a new customer, which schools effectively pay on behalf of the seller.

LibreOffice offers an alternative to this approach, teaching students to develop a different type of relationship with their tools.

Privacy and data security

LibreOffice is a free office suite for Windows, macOS and Linux, managed by the non-profit organisation The Document Foundation and developed by a global community of contributors. It offers programs for word processing, spreadsheets, presentations, databases, drawings and mathematical formulas — in other words, all the functions required in a school environment.

Unlike Microsoft 365 or Google Workspace, LibreOffice does not require a subscription or an internet connection. It also does not require the creation of accounts for minors or send data to remote servers. It installs and works locally, so data stays where the user puts it.

For schools operating in areas with poor connectivity — a more widespread reality than one might think — this is not a minor issue, but the difference between a functioning lesson and a frozen loading screen.

For schools concerned about student privacy, the difference is even more significant. Microsoft 365 and Google Workspace collect behavioural and usage data, and the terms of service governing the management, storage and use of this data are opaque, complex and subject to change.

LibreOffice does not collect any data, either user or operational, as no account is required to use it and there is no default telemetry. Therefore, there is no data to lose in the event of a malfunction or system breach.

The lesson of open standards

LibreOffice is based on the Open Document Format (ODF), an ISO standard file format that no company owns or controls. Documents created in ODF today will be readable by any ODF-compatible software, even in 20 or 50 years’ time. This is not because the vendor has decided to maintain backward compatibility, but because the standard is public, documented and independent of any commercial interests.

This is extremely important for schools, which are public services funded by citizens and accountable to communities, not private businesses. The documents they produce, such as curricula, assessments, student records and administrative correspondence, belong to the public sphere to a certain extent. Locking these documents into a proprietary format controlled by a single US company creates a form of digital dependency that is incompatible with the commitment of educational institutions to autonomy and critical thinking.

Teaching students to create and share documents in an open format shows them that technology can be responsible and transparent, and that the tools they use do not have to be ‘black boxes’ owned by a company.

The potential lesson of Linux

LibreOffice is the default office suite in most Linux distributions. A school that adopts LibreOffice is a school that has opened the door to using Linux on its personal computers. This is important for budgetary reasons — Linux significantly extends the useful life of older PCs — but also from an educational perspective.

This is demonstrated by the experience of Italian schools in the province of Bolzano, Italy, which use the Linux distribution FUSS (Free Upgrade for a Digitally Sustainable School). On 20 April 2026, it will celebrate its 20th anniversary with a public event where I will talk about the topics covered in this article.

Linux powers the internet, large research centres such as CERN, the world’s top 50 supercomputers, most smartphones and a large proportion of corporate infrastructure with which students will work when they leave school or university.

Students who have grown up using only Windows or Chromebooks have no practical knowledge of how operating systems work, how software is installed and managed, or how IT infrastructure is structured. However, a student who has used a Linux-based system, even in a school setting, will have at least a basic understanding of the fundamentals of modern computing.

This is not an ideological commitment to open source. It is about training graduates who understand the technological world they are entering and the digital tools they will use throughout their lives.

The pitfalls of proprietary software

A student who uses proprietary software throughout their education may unknowingly absorb a series of misconceptions and misinformation:

  • That documents reside in the cloud or on someone else’s server as if this were normal and natural.
  • Collaboration means sharing access within a supplier’s system.
  • That software is a subscription service which is paid for monthly and whose features or price may change at any time.
  • That the interface of a tool is defined by what a company has decided to build and not by what users need.
  • Lock-in of proprietary formats is an integral part of the system because that’s just how things are.

All of this information is biased and teaches dependency. It serves the long-term commercial interests of suppliers rather than the long-term autonomy of students.

In contrast, LibreOffice lessons teach that software can be free as in freedom, not just free as in price; that file formats can be public standards; that the user community, rather than profit, can be the basis for software development; and that the tools we use can be transparent, modifiable and independent of a single company’s commercial strategies.

An analysis of the counterarguments

Students must learn the tools they will use in the workplace. In theory, this argument has some merit, but in reality, it is inconsistent because the conceptual skills developed with Microsoft 365 — document structuring, formatting, use of styles and spreadsheet formula management — can be transferred to LibreOffice and vice versa. According to the logic of this argument, skills learned on a platform that later changes its interface or mode of delivery from desktop to cloud are not transferable. Microsoft has modified its products several times over the last ten years. The enduring lesson is to learn the concepts, not the menus.

Google Docs facilitates collaboration. This is true within the Google ecosystem. LibreOffice, together with Nextcloud or a similar solution, offers comparable collaboration features without exposing data. However, the problem in this case is the lack of expertise in schools to configure it, which highlights the need for better IT support in education rather than permanent structural dependence on Google.

LibreOffice is more difficult to use. For users who have never used either, the learning curves are comparable, and the perception that Microsoft Office is “easier” largely stems from prior exposure, which itself stems from schools having already made the choice we are questioning.

A concrete proposal

The transition, of course, must not be abrupt or absolute, since this could trigger resistance to change, especially among parents, who in most cases have been victims of the pitfalls of proprietary software.

Schools could start with a few small steps:

  • Adopt ODF as the standard format for all documents, regardless of the software used to create them. This would break the format lock-in without requiring an immediate change in software.
  • Introduce LibreOffice alongside proprietary tools, allowing all students to work with both and understand the differences in approach between proprietary software and FOSS.
  • Migrate administrative workflows to LibreOffice to reduce licensing costs and create institutional familiarity before introducing it in classrooms.
  • Collaborating with local FOSS communities for technical support and training would be a form of civic engagement that would benefit both schools and businesses in the area.

None of these small steps represents a radical choice. Many school systems in Europe have adopted these measures, either fully or partially, and experience shows that the transition can be managed and that the benefits are real.

Conclusion

The dominance of Microsoft 365 and Google Workspace in schools is not the result of these tools being proven to be superior for educational purposes. Rather, it is the result of effective commercial strategies, network effects and institutional inertia. Schools have largely accepted this situation without considering the long-term costs in terms of student data, public budgets, digital sovereignty and the type of digital citizens that schools and universities should be educating.

LibreOffice offers an alternative approach based on open standards, public accountability and independence from commercial platforms. While not perfect, it is a tool that schools can truly own and control.

This is worth much more than a discounted or seemingly free subscription.

UPDATED Request to the European Commission to adhere to its own guidances

The European Commission has accepted our request, and starting from today – Friday March 6 – has added the Open Document Format ODS version of the spreadsheet to be used to provide the feedback. We are grateful to the people working at DG CONNECT, the Commission’s Directorate-General for Communications Networks, Content and Technology, for responding to our request within 24 hours. At this point, the rest of this message is no longer relevant, and the call for action is no longer necessary.

ARCHIVED MESSAGE

The European Commission has spent years advocating for open standards, vendor neutrality, and digital sovereignty. The European Interoperability Framework explicitly recommends open formats for public sector digital services. The EU’s own Open Source Software Strategy calls for reducing dependency on proprietary technologies, and the Cyber Resilience Act itself is designed to address systemic risks from unaccountable technology dependencies.

On March 3rd, 2026, the European Commission published a request for feedback on to the guidances to be provided in relation to the CRA, which must be provided through the linked spreadsheet in .xlsx format, a proprietary format that makes interoperability extremely difficult due to its ever changing and undocumented features.

This is not a minor procedural oversight. It is a structural bias built into the process which sends out a clear message: full participation in EU policymaking requires a Microsoft licence.
We ask the European Commission to lead by example by following its own guidances in relation to interoperability and at to least provide, alongside the proprietary format generated by the proprietary software and services they use, also an Open Document Format (ODF) file which is an actual interoperable and internationally recognised standard.

While the Commission evaluates plans to upgrade its infrastructure and services to Open Source solutions, with the aim of improving resiliency and reduce risky dependencies, it should implement in its standard procedures the release of documents in ODF format to allow all citizens, organisations and institutions to participate in the democratic processes.

#CyberResilienceAct   #OpenStandards   #DigitalSovereignty   #OpenSource   #LibreOffice   #ODF

CALL FOR ACTION

Dear Commission representatives,

We are writing to provide feedback on a procedural matter that, while perhaps appearing minor at first glance, carries significant implications for the principles underpinning EU digital policy — in particular the commitments to open standards, interoperability, and vendor neutrality that the Commission itself has championed in multiple legislative and strategic contexts.
The stakeholder feedback template for the Cyber Resilience Act Guidance document has been made available exclusively in Microsoft Excel format (.xlsx). This choice is, respectfully, difficult to reconcile with the Commission’s own stated commitments.

The .xlsx format is a proprietary format defined and controlled by Microsoft Corporation, a private entity incorporated in the United States. In fact, although OOXML (ISO/IEC 29500) has been approved as a standard, its implementation has never complied with the specifications of the standard itself, as widely documented in the literature on interoperability. Requiring participants to use this format as the sole vehicle for structured data entry effectively conditions participation in a public consultation on the availability or willingness to use software produced by a single supplier.

This stands in direct contradiction to several principles the EU has advanced:

• The European Interoperability Framework (EIF), which recommends the use of open standards in public sector digital services and the avoidance of lock-in to proprietary technologies.
• The Open Source Software Strategy 2020–2023 and its successor, which promote the use of open source and open standards across EU institutions.
• The spirit, and arguably the letter, of the very Cyber Resilience Act itself, which seeks to reduce systemic risk arising from dependency on unaccountable or opaque technology components.

A consultation process that requires respondents to use a proprietary format produces a structural bias: it disadvantages individuals, organisations, and public administrations that have made the entirely legitimate and EU-endorsed choice to operate on open source software and open formats. A citizen or small organisation using LibreOffice, for instance, may encounter compatibility issues when working with the provided .xlsx template. A government body that has migrated to ODF-based workflows faces an unnecessary obstacle.

The remedy is straightforward. Feedback templates of this kind should be provided in at minimum two formats: one open format (ODF spreadsheet, .ods, being the obvious choice, as it is a true ISO-standardised format with no proprietary ownership) and one widely-used proprietary format for those whose environments require it. Ideally, a plain-text or web-based form would supplement both, removing the spreadsheet dependency entirely for respondents who prefer it.

The Commission’s credibility on digital sovereignty, open standards, and vendor-independent infrastructure is undermined — symbolically but meaningfully — each time its own processes rely exclusively on proprietary formats from non-European technology vendors. The CRA is precisely the kind of legislation where procedural consistency with stated principles matters most.

We respectfully urge the Commission to review its template distribution practices and to adopt a format-neutral approach to stakeholder consultation as standard policy going forward.

Yours faithfully,

Board of Directors
The Document Foundation
Berlin, March 5, 2026

 

Further Update about Font Replacement

I have already covered the topic of font replacement in LibreOffice in 2020 and in 2025.

Unfortunately, the vast majority of personal computer users are unaware of this issue and believe that the fonts installed on their PC are the only fonts available. None of them realise that personal computer fonts are actually software, and as such can be installed on a PC like any other programme, provided that a licence is purchased (in the case of proprietary fonts, supplied by companies such as Adobe and Microsoft) or that the licence is open and free.

Font management is one of the main problems that users encounter when using LibreOffice to manage a document created with a proprietary office suite, because the absence of the original proprietary font (for example, Arial and Times Roman in the case of the older generation, Calibri and Cambria in the case of the intermediate generation, and Aptos in the case of the latest generation) causes the text to flow differently – because the fonts used for replacement are not metrically compatible – and this leads the user to think that LibreOffice is not working.

LibreOffice is the only office suite to provide an input and output font conversion feature which, when used correctly, significantly reduces or even eliminates the problem.
This is because LibreOffice thinks about its users, although it obviously needs curious users who do not stop at a small problem – because a different scrolling on the screen of the same document is a small problem – and instead of immediately thinking that the software is not working, they seek information to find a solution.

In the following slides, which I used for a workshop during the last SFScon in Bolzano, and which I have already published, there is a summary of the problem and its solution. As soon as possible, I will return to the subject with more information, hoping that repetition will help users who do not seek information and who, for this reason, are completely defenceless against the strategies of companies that provide proprietary office suites.

SFScon Font Management 2025

 

ODF is just the first of the advantages of LibreOffice

Comments continue to be posted on articles that refer to blog posts on OOXML and related topics, from users who claim to support FOSS but in fact choose proprietary software, for reasons that have nothing to do with the support they claim to offer.

These users share a preference for the proprietary OOXML document format and the Microsoft 365 ribbon interface, demonstrating on the one hand incompetence regarding formats and on the other hand subservience to proprietary marketing. Some of them even use the definition of “standard” for the ribbon interface, which in reality is neither a standard nor a good example of ergonomics.

In reality, if ODF is LibreOffice’s first advantage from an open source perspective, the flexibility of the user interface is probably the second. Let’s start with an in-depth analysis of these two important advantages.

Native support for the ODF format

LibreOffice uses ODF as its native format rather than as a second choice, handled in an approximate manner with the aim of disqualifying ODF in the eyes of users, as Microsoft, OnlyOffice and WPS Office do.

This means that documents are transferred perfectly without the risk of silent data loss, formatting corruption or schema compromise. Users working in environments that require ODF compliance, such as some EU public administrations, are guaranteed maximum fidelity without any effort.

In contrast, the complexity and ambiguity of the OOXML format, combined with the gap between the published specifications and the actual implementation, make the format almost as opaque in practice as a proprietary binary format. Technically, it is possible to access XML files, but making sense of them or achieving interoperability is another matter entirely.

LibreOffice supports the ODF format natively, which eliminates the risk of vendor lock-in and ensures that documents remain accessible in the long term, regardless of the commercial choices of a private company. This is an increasingly important consideration for European public administrations, particularly in light of EU digital sovereignty policies.

Flexible and customisable interface

LibreOffice offers several user interface modes, which users can switch between depending on their workflow and familiarity: the classic interface with toolbar, the tabbed user interface (ribbon style, for users familiar with Microsoft 365), the compact tabbed variant, the compact grouped bar, the single contextual toolbar and the sidebar-centric layout.

Microsoft 365, WPS Office, and OnlyOffice have only one user interface, which in the first case is original and in the other two cases is a simple clone, forcing users to adapt to choices dictated in one case by patent-based protection strategies, and in the others – I suspect – by a total inability to develop an original solution.

Incidentally, the characterisation of ribbon-style interfaces as “modern” or “standard”, used by several users, is not based on any objective usability parameter or design principle, but is the result of Microsoft’s dominance in the market and the huge investments made when the ribbon was introduced in Office 2007 as a new paradigm for productivity software.

From a human-computer interaction perspective, there is no consensus that the ribbon represents superior usability. In fact, it was controversial at launch and remains so among experienced users, who often find it faster to navigate menu hierarchies, once learned, than a ribbon that emphasises breadth over depth.

LibreOffice’s toolbar and menu interface reflect decades of refinement in that paradigm, and are demonstrably more efficient for users who are already familiar with it.

The idea that “modern” equals “similar to a ribbon” is a normalisation effect: the Microsoft interface has become a benchmark because of its ubiquity, not because of its proven advantages in terms of usability. Added to this is the fact that many users evaluate office software through the lens of familiarity with Microsoft Office and consider deviation from it as a problem rather than a design choice.

LibreOffice’s multiple interface options are undoubtedly a more thoughtful response to user needs than the one-size-fits-all ribbon approach. Offering users the ability to choose their own interaction model (classic menus, ribbon tabs, or grouped and compact toolbars) is a sign of design maturity, not backwardness.

Other advantages of LibreOffice over proprietary solutions

No monetisation of users. LibreOffice has no advertising, does not profile users, has no upsells, no lock-in pressure through the cloud, and no feature gating.

More options for macros and scripting. LibreOffice retains its own Basic, and adds Python, JavaScript, and BeanShell to offer experienced users extensive automation capabilities, making it significantly more flexible and capable than other software in this specific area.

Access to source code. LibreOffice is developed under the auspices of The Document Foundation, a non-profit foundation, according to the ethical principles of FOSS, and therefore with full transparency of the source code, which allows users and organisations to verify exactly what the software does.

Data privacy assurance. LibreOffice does not collect personal data, usage metrics or diagnostic information, and offers full control over documents, which is essential for data sovereignty, with encryption options to protect files with passwords and even options to remove any type of personal information from files.

Balance between platforms. LibreOffice offers full versions for Windows, macOS and Linux that are identical in terms of features and functionality, to protect the user’s right to choose their preferred operating system, with the only difference being in the installation procedure.

In summary, for users who prioritise FOSS principles – such as standard document format, access to source code and data privacy – and are not easily swayed by proprietary software strategies for the user interface, LibreOffice is the best choice overall.

Those who argue otherwise, hiding behind baseless justifications such as interoperability and modernity of the user interface (where the real advantage lies with LibreOffice), clearly need to clarify their ideas regarding support for FOSS, which is a choice where “convenience” is not a factor.

The Document Foundation Releases LibreOffice 26.2.1 with Contributions from Community and Ecosystem Partners

Videos describing new features available on YouTube and PeerTube

Berlin, 26 February 2026 – The Document Foundation today announced the release of LibreOffice 26.2.1, the first maintenance update to the LibreOffice 26.2 branch. Building on the major feature release published on February 4, 2026, this update delivers targeted bug fixes and stability improvements contributed by a global community of developers, QA engineers, and ecosystem companies.

LibreOffice 26.2.1 is available for immediate download for Windows, macOS, and Linux.

LibreOffice 26.2 introduced a broad set of improvements to daily productivity workflows, including Markdown import and export, connector shapes in Calc, multi-user Base, faster EPUB export, and mandatory Skia rendering on macOS and Windows for better graphics performance. LibreOffice 26.2.1 consolidates these advances with a focused set of fixes, addressing issues identified by users and testers since the initial release.

Videos describing the new features of the LibreOffice 25.2 family area available on PeerTube and YouTube.

A significant share of the fixes in LibreOffice 26.2.1 originates from the companies that form the LibreOffice ecosystem. These organisations employ experienced developers who contribute code upstream, ensuring that improvements benefit the entire LibreOffice user base — whether they run the community build or a vendor-supported distribution.

The Document Foundation thanks all ecosystem partners for their sustained investment in the health and quality of the shared codebase.

List of fixes in RC1: wiki.documentfoundation.org/Releases/26.2.1/RC1. List of fixes in RC2: wiki.documentfoundation.org/Releases/26.2.1/RC2.

LibreOffice users, free software advocates and community members can support The Document Foundation and the LibreOffice project with a donation at www.libreoffice.org/donate.