What is the Open Document Format (ODF)?

An introduction to the Open Document Format

The documents we create today, whether reports, spreadsheets or presentations, are essential for communicating, sharing and storing knowledge. However, the format in which these documents are saved often goes unnoticed. This is where the Open Document Format (ODF) comes in. ODF is a technical standard and a tool that ensures documents remain accessible, editable and usable over time without being tied to a specific vendor or product.

Approved by OASIS as an open standard document format in May 2005 and by ISO/IEC in May 2006, ODF has been around for over 20 years. Despite 20 years having passed, most productivity software users are not familiar with the format and therefore do not use it, as it is not as widespread as its proprietary counterpart, Microsoft OOXML.

This means that a huge number of documents — equivalent to over 100 zettabytes of data in 2025 — are subject to the commercial strategies of a company and completely beyond the control of their authors. These authors may suddenly find themselves unable to manage their own content unless they use specific software.

This also means that the enormous wealth of information contained in these documents does not contribute to the growth of collective intelligence because they are limited in terms of interoperability due to being tied to a single, specific, proprietary software.

Furthermore, Microsoft’s touted backward compatibility feature prevents true innovation in document formats because the presence of proprietary elements from old binary formats, which are not included in the ODF standard, forces documents to remain with technologies that have long been obsolete and incompatible with future developments.

What is ODF?

ODF is an open standard for saving and exchanging office documents. It includes text files (.odt), spreadsheets (.ods), presentations (.odp), and other types of documents, such as drawings (.odg). Developed by OASIS, an organisation that promotes structured information standards, it was approved by ISO/IEC as the international standard ISO/IEC 26300 in 2006.

Put simply, ODF is a universal language for documents, ensuring they can be read and written by any compatible software without locking users into a single ecosystem.

To understand the importance of ODF, it is helpful to know how proprietary formats work. When a document is saved in a Microsoft format, such as .docx, or an Apple format, such as .pages, it is often designed to work best with that company’s software only. Over time, this can cause problems such as limited compatibility, vendor lock-in, and the risk of obsolescence if the proprietary format is abandoned or changed significantly, as older documents may become unreadable.

ODF avoids these problems. It is completely open and free, meaning that anyone can implement it in their software, and users can switch between tools without losing access to their files.

ODF is not limited to text documents, but includes a wide range of office document types, including .odt (OpenDocument Text) for text documents such as reports, letters and books; .ods (OpenDocument Spreadsheet) for data analysis, tables and financial models; .odp (OpenDocument Presentation) for presentations with visual content; .odg (OpenDocument Graphics) for diagrams and vector graphics, as well as documents containing text and images; and .odf (OpenFormula) for formulas used in ODS spreadsheets.

Each of these document types is structured in such a way as to allow maximum compatibility while maintaining formatting and advanced software features.

How does ODF compare with Microsoft document formats?

Feature ODF Microsoft (docx. xlsx, pptx)
Open Standard Yes No
Long Term Archiving Solid Support Risk of Format Changes
Risk of Online Dependency
Offline Support Fully Supported Supported
Editable without Vendor Software Yes Limited

Common misconceptions about ODF

It is not as feature-rich as .docx or .xlsx

False. ODF supports complex formatting, styles, images, tables, charts, macros and more. Its feature set is robust and evolving thanks to contributions from a global community of developers and users.

No one uses ODF

This is also false. In fact, millions of users worldwide use ODF-compatible software every day. LibreOffice alone has tens of millions of active users worldwide.

It doesn’t work with my existing documents

ODF-compatible software, such as LibreOffice, can open, edit and export many formats, including .docx and .xlsx. Switching to ODF is easy and you won’t lose access to your existing files.

The future of ODF

The growing importance of digital documents in every sector, including education, public administration and business, is bound to impact the adoption of the ODF format because users cannot continue to use a format that disadvantages them in every way. Furthermore, the number of countries adopting policies based on open standards and demanding transparency and control over their data is growing all the time, and this can only lead to increased adoption of ODF in the long term.

Documents should belong to their authors, not to a software vendor through the file format used. In the case of a country, documents should belong to its citizens. ODF is the only effective way to regain control and ensure that data remains open, accessible and future-proof. ODF embodies the principles of digital freedom, collaboration, and user empowerment.

Whether you are an individual seeking control over your digital life, a teacher aiming to share knowledge using open tools to ensure its long-term availability to the community, a public official seeking long-term transparency, or a politician representing citizens’ interests, ODF is the smart, sustainable choice.

DISCLAIMER: Artificial Intelligence has helped in putting together background data in a matter of seconds, thus dramatically reducing the time needed to draft the article. I have over 4GB of background documents on my online storage, and although I have read most of them, it is impossible for my humble brain to retain all information. Here, Artificial Intelligence helps a lot, especially a 70 years old guy.

Month of LibreOffice, May 2025 – Half-way point!

Month of LibreOffice banner

So we’re half-way through the Month of LibreOffice, May 2025. And already, 216 contributors have won cool LibreOffice sticker packs! Details on how to claim them will be provided at the end of the month, but if you don’t see your name (or username) on that page, it’s not too late to join…

How to take part

There are many ways you can help out – and you don’t need to be a developer. For instance, you can be a:

  • Handy Helper, answering questions from users on Ask LibreOffice. We’re keeping an eye on that site so if you give someone useful advice, you can claim your shiny stickers.
  • First Responder, helping to confirm new bug reports: Go to our Bugzilla page and look for new bugs. If you can recreate one, add a comment like “CONFIRMED on Windows 11 and LibreOffice 25.2.3”.
  • Drum Beater, spreading the word: Tell everyone about LibreOffice on Mastodon, Bluesky or X (Twitter)! Just say why you love it or what you’re using it for, add the #libreoffice hashtag, and at the end of the month you can claim your stickers.
  • Globetrotter, translating the user interface: LibreOffice is available in a wide range of languages, but its interface translations need to be kept up-to-date. Or maybe you want to translate the suite to a whole new language? Get involved here.
  • Docs Doctor, writing documentation: Whether you want to update the online help or add chapters to the handbooks, here’s where to start.

So, two more weeks to go! We’ll be posting more updates on this blog and our Mastodon, Bluesky and X (Twitter) accounts…

Projects selected for LibreOffice in the Google Summer of Code 2025

The LibreOffice Google Summer of Code projects have been selected for 2025.

  • Adam Seskunas – Implement Report Builder in C++: replacing the current Java-based Report Builder with a new solution will improve maintainability and remove one of the last remaining dependencies on Java.
  • Karthik Godha – New dialog to edit Table Styles: Writer and Calc have a feature called AutoFormat styles with the possibility to add custom styles. This project will make it possible to edit existing table styles.
  • Devansh Varshney – BASIC IDE code auto-completion: rudimentary auto-completion for BASIC macro authors is already available, but this project will make the feature much more helpful.
  • Manish Bera – Python code auto-completion: currently there is no support at all for Python auto-completion when developing scripts for LibreOffice, so this will be quite a welcome addition.
  • Mohamed Ali Mohamed – Rust UNO language binding: last year LibreOffice received support for Lua and the latest .NET and now it’s time to make it possible to use the API with Rust.
  • Ujjawal Kumar – Import Markdown files into Writer: Markdown is a rather popular markup language for quickly formatting text in blog content, comments, chats and more. Requests to support it have increased recently, so it makes sense to tackle it.
  • Shardul Vikram Singh – Rework Impress slideshow to use DrawingLayer primitives: this is one of those projects that are incomprehensible to most users, but really important for the long term maintenance of the code.

Good luck to the contributors – we appreciate their work on these important features and improvements! And thanks to our mentors for assisting them: Thorsten Behrens, Stephan Bergmann and Sarper Akdemir (allotropia); Rafael Lima; Jonathan Clark, Heiko Tietze, Xisco Faulí, Michael Weghorn and Hossein Nourikhah (TDF).

Between August 25 and September 1, contributors will submit their code, project summaries, and final evaluations of their mentors. Find out more about the timeline here, and check out more details about the projects on this page.

TDF and LibreOffice website, blogs and social media – Annual Report 2024

TDF Annual Report 2024 banner

Our two main websites are vital sources of information for The Document Foundation and the LibreOffice software. We also use our social media channels to raise awareness about our work, share information and encourage new contributors to join us

(This is part of The Document Foundation’s Annual Report for 2024 – we’ll post the full version here soon.)

TDF website

The Document Foundation website provides general information about the foundation (overview, statutes, code of conduct, financials and reports) and its governance (board of directors, membership committee, members, advisory board, and engineering steering committee), and about LibreOffice certification, including a list of certified developers, and professionals for migrations and trainings.

During 2024, the foundation’s website was visited 98,499 times, with 146,456 page views – a slight reduction in visits but also a slight growth in page views from 2023. Continent-wise, the largest chunk of visits were from Europe (52%), followed by North America (24%) and Asia (16%). And regarding software: the most visits were from PCs using the Windows (65%) operating system, followed by GNU/Linux (10%) and macOS (8%) and devices uses Android (6.2%), while for browsers: Chrome had 39%, followed by Firefox (16%) and Microsoft Edge (15%).

Matomo graph of visits to the website

LibreOffice website

The LibreOffice website provides information about the office suite and the document format, the various download options, how to get help, how to contribute to the project, events where users can get to know the LibreOffice community, and how to make a donation to support the project and the community.

In 2024, we continued to make improvements and tweaks to the website, updating the “Discover” and “New Features” sections of the site to reflect new versions of the software.

During 2024, the English-language LibreOffice website was visited 19,298,517 times (a 0.6% gain over 2023), with 46,065,236 page views (a 0.1% gain). Most visits were from Europe (52%), followed by Asia (20%), North America (15%) and South America (9%), from PCs using the Windows operating system (82%), followed by macOS (6%) and Linux (23%). Regarding web browsers, Chrome was the most popular (41%), followed by Microsoft Edge (29%) and Firefox (13%).

Matomo graph of visits to the website

Blogs

TDF’s blogs (like this one) are essential for communicating activities inside and around the project, including new releases of LibreOffice, community events and support for other free and open source initiatives. In 2024, we used them to post regular interviews with community members and provide updates from team members about documentation, marketing, QA, design and more.

Photo of Ndidi Folasade Ogboi

Blogs were also maintained by various native language communities including Japanese, Spanish, German and others. Thanks to the hard work of community members, we had press releases, tips and other articles translated into many languages, and picked up by local media organisations.

These native language blogs complement the information provided by the main blog in English, and by the two blogs managed by members of the design and the quality assurance projects, which provide updates about activities for the upcoming major releases.
In 2024, the blog had 100,180 visits and 131,174 page views – a drop in both cases of around 30% from the previous year. The press releases for LibreOffice 24.2 and 24.8 were the most popular posts, followed by the posts about the German state of Schleswig-Holstein moving 30,000 PCs from Microsoft Office/365 to LibreOffice.

Social media

In January 2024, our X (formerly known as Twitter) account (@LibreOffice) had 63,060 followers; by the end of the year, we had grown this to 68,870. Our most popular posts were for major releases of LibreOffice, and news about migrations to the suite. We posted customised images for “Community Member Monday” interviews with short quotes, encouraging more users to get involved with LibreOffice projects.

In addition, we focused not only on our own posts, but also retweeting announcements from the LibreOffice community members. We liked and reposted messages of support from end users – many of whom were surprised and thankful that a large project would show them support. To keep the content flowing, we reposted popular older tweets, and responded to individual messages.

On other social media platforms, we focused on growing our account on Mastodon, a Twitter-like open source, federated and self-hosted microblogging service. In 2024 we worked more on expanding our activities on our account @libreoffice@fosstodon.org, and from January to December, we grew our follower base from 25,440 to 29,326. We also joined Bluesky in late 2023 thanks to invites from a community member, and by December 2024 our follower count had reached 2,900.

Screenshot of LibreOffice account on Bluesky

Our Facebook page growth was smaller, from 63,348 page followers to 64,239. We’ve noticed a gradual reduction in activity on Facebook over the last few years, which reflects its changing audience, and the move towards other social media platforms. Nonetheless, Facebook still provides a good opportunity to interact with end users of LibreOffice, and every day we checked in to answer questions, get feedback, and post announcements/tips about the software.

YouTube channel

Our YouTube channel grew from 20,638 subscribers and 3,243,107 video views in January 2024 to 22,586 subscribers and 3,534,370 video views by the end of the year. The most popular videos were the “New Features” videos for LibreOffice 24.2 and 24.8, and we also added videos of talks, presentations and workshops from the LibreOffice Conference 2024.

At the end of 2024, we posted the first video from the new LibreOffice Podcast series, where Italo Vignoli and Mike Saunders from TDF talked about the challenges and opportunities in marketing free and open source software like LibreOffice. More podcasts are planned for 2025.

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

Like what we do? Support the LibreOffice project and The Document Foundation – get involved and help our volunteers, or make a donation. Thank you!

LibreOffice Quality Assurance (QA) in 2024 – TDF’s Annual Report

TDF Annual Report 2024 banner

Quality Assurance (QA) is a cornerstone of the LibreOffice project, thanks to the activity of a large number of volunteers and the feedback of many users who help in reporting bugs and regressions

(This is part of The Document Foundation’s Annual Report for 2024 – we’ll post the full version here soon.)

QA team work

In 2024, the QA team triaged thousands of bugs, bisected hundreds of regressions, and answered questions from countless bug reporters. As one of the most visible groups directly responding to end users, the QA team must be nimble and able to adapt to changes. In addition, it must deal with specific requests for help from other teams.

The QA team meets regularly on IRC on the #libreoffice-qa channel, which is the best medium for discussing bugs and regressions. The IRC channel provides an excellent opportunity to remain in close contact with team members, and to tutor new members in the art and skill of LibreOffice QA. This is bridged to the Telegram group.

During 2024, 5351 bugs were reported by 2463 users, which means 103 new bugs were reported every week on average. The QA team prepared monthly reports about their activity and posted on the QA blog.

Top 10 bug reporters

  • Eyal Rozenberg (211)
  • Gabor Kelemen (193)
  • Mike Kaganski (137)
  • Telesto (86)
  • Regina Henschel (85)
  • Xisco Faulí (82)
  • Stéphane Guillou (78)
  • peter josvai (75)
  • Rafael Lima (72)
  • Heiko Tietze (54)

Triaging

During 2024, 5086 bugs were triaged by 328 people. The top 10 bug triagers were:

  • Stéphane Guillou (stragu) (762)
  • Buovjaga (684)
  • m_a_riosv (499)
  • Heiko Tietze (374)
  • V Stuart Foote (241)
  • Mike Kaganski (232)
  • Julien Nabet (186)
  • Xisco Faulí (175)
  • ady (144)
  • Dieter (144)

Bibisecting

Also, during 2024, the QA team performed 561 bibisects of regressions by 30 people. The top 10 bisecters were:

  • raal (121)
  • Buovjaga (111)
  • Stéphane Guillou (104)
  • Xisco Faulí (91)
  • Gabor Kelemen (24)
  • Aron Budea (23)
  • Timur (14)
  • zcrhonek (10)
  • Mike Kaganski (9)
  • Justin L (8)

Like what we do? Support the LibreOffice project and The Document Foundation – get involved and help our volunteers, or make a donation. Thank you!

ODF 20th Anniversary Video

On May 1st, 2005, the Open Document Format (ODF) become an OASIS standard. One year after, it became an ISO/IEC standard. After two decades, it is the only true open standard for document formats available on the market, and the only one protecting users from proprietary lock in and ensuring a full control over contents. The presentation provides an overview over ODF features and explains why ODF should be used versus Microsoft OOXML (DOCX, XLSX and PPTX).

PeerTube: https://peertube.opencloud.lu/w/2b9JeZw1M884V5BK21RioW

YouTube: https://youtu.be/Z-Xo9v9-1YU (please note that once you leave this blog to access the video, a different set of privacy rules will apply)

Open Document Format (ODF) has been designed as a document standard for the next 20-50 years, to liberate users from the lock-in strategy built into yesterday’s and today’s proprietary formats and foster interoperability. On the contrary, OOXML – approved by ISO/IEC in 2008 in a version never implemented by MS Office – has been designed as a document pseudo-standard format to propagate yesterday’s document issues and lock-in strategy for the next 20-50 years, to the detriment of users and interoperability.

The philosophy behind the ODF standard document format was to design a mechanism in a vendor neutral manner from the ground up, using existing standards wherever possible. Although this means that software vendors had to tweak their individual packages more than if they continued down their original routes, the benefits for interoperability were important enough to justify this objective. The OOXML pseudo-standard document format was designed by Microsoft for Microsoft products, and to interoperate with the Microsoft environment. Little thought appears to have been exercised for interoperability with non-Microsoft environments, or compliance with established vendor-neutral standards.