The ongoing tension between open-source software advocates and proprietary technology giants has once again come into focus as the developers behind LibreOffice issued a strong statement criticizing Microsoft’s practices around document file formats. This latest critique centers on how Microsoft continues to design its Office applications in ways that create barriers for users attempting to switch to alternative programs. The document, released through the Document Foundation, highlights specific technical choices that make collaboration and data portability more difficult than necessary.
LibreOffice, a free and open-source office productivity package, has positioned itself as a direct alternative to Microsoft Office for years. Its community of contributors argues that while Microsoft has made public commitments to openness, the company’s actual implementation of file formats like OOXML often includes undocumented elements that only function properly within its own ecosystem. According to the article on XDA Developers, the LibreOffice team accuses Microsoft of deliberately maintaining compatibility gaps that discourage users from adopting competing software.
At the heart of the complaint lies the .docx, .xlsx, and .pptx file formats. When Microsoft first introduced these formats in the mid-2000s, it submitted them to standards bodies as an open specification. Many observers hoped this move would lead to genuine interoperability between different office applications. Instead, the LibreOffice developers claim that Microsoft has added proprietary extensions and behaviors that cause documents to render differently or lose functionality when opened in non-Microsoft programs. These subtle differences can include formatting quirks, macro behaviors, or embedded objects that work flawlessly in Word, Excel, or PowerPoint but break or display warnings in LibreOffice.
The timing of this statement coincides with growing adoption of open-source tools across governments, educational institutions, and businesses seeking to reduce dependency on single vendors. Several European countries have actively promoted the use of open document formats such as ODF, which LibreOffice supports natively and consistently. Microsoft’s Office applications can read and write ODF files, but the conversion process often introduces visual or functional changes. The Document Foundation suggests this inconsistency is not accidental but part of a calculated approach to maintain market dominance.
Users frequently encounter these issues when sharing files between colleagues or organizations that use different software. A spreadsheet created in Excel might display correct formulas and charts when opened in Microsoft’s desktop application, yet show misalignment or broken references when loaded into LibreOffice Calc. Similarly, complex PowerPoint presentations containing custom animations or embedded media often require adjustments after being saved from Microsoft software and opened elsewhere. These repeated adjustments consume time and create frustration that ultimately pushes users back toward the familiar Microsoft environment.
The LibreOffice team points out that modern cloud-based versions of Office further complicate the situation. Documents stored in OneDrive or edited through the web interface sometimes include metadata or structural elements that Microsoft’s desktop applications understand but that remain invisible or problematic for other programs. This creates an additional layer of lock-in because teams that begin collaboration in the cloud often feel compelled to continue using Microsoft tools to avoid compatibility headaches.
Technical experts following this debate reference historical patterns in the software industry. Microsoft faced similar accusations during the browser wars of the 1990s when its Internet Explorer included proprietary HTML extensions that worked only in its own product. Antitrust regulators eventually intervened, forcing changes to those practices. Today’s document format concerns echo those earlier controversies, though the mechanisms differ. Instead of directly blocking competitors, the strategy appears to rely on friction and inconvenience that gradually steers users toward the path of least resistance.
Microsoft has responded to such criticisms in the past by emphasizing the complexity of maintaining perfect compatibility across decades of evolving file formats. The company maintains that billions of existing documents created over multiple versions of Office must continue to function, creating legitimate engineering challenges. Microsoft also notes that it participates in standards organizations and publishes extensive documentation for its formats. However, the LibreOffice developers counter that while documentation exists, certain behaviors remain undocumented or subject to change without notice, making reliable implementation difficult for independent developers.
The practical impact extends beyond individual users to entire organizations. Government agencies handling sensitive data often prefer open-source solutions for security and sovereignty reasons. When those agencies receive documents from contractors using Microsoft Office, they face a choice between accepting potential formatting issues or requiring all parties to adopt the same proprietary software. This dynamic reinforces existing market positions and slows the broader adoption of vendor-neutral formats.
Education represents another significant area of concern. Schools and universities increasingly provide students with laptops or tablets, and many default to Microsoft 365 licenses because of widespread familiarity. Yet this early exposure creates habits that persist into professional life. Students who rarely encounter alternative office applications may assume that compatibility problems stem from the alternative software rather than from design decisions in the dominant product. Over time, this perception becomes self-reinforcing.
LibreOffice has made substantial progress in improving compatibility over recent releases. The developers regularly analyze Microsoft-generated files to identify and replicate undocumented behaviors. Their test suite contains thousands of sample documents that reveal subtle differences in how formulas calculate, how charts render, or how text layouts adjust. Each new version typically includes fixes for specific compatibility issues reported by users. Despite these efforts, the fundamental challenge remains that Microsoft controls the reference implementation and can introduce changes faster than the open-source community can respond.
The Document Foundation encourages users to save files in the OpenDocument Format whenever possible. ODF was designed from the beginning as an truly open standard without hidden extensions or proprietary hooks. Files saved in .odt, .ods, or .odp formats maintain their structure and appearance across different applications, including older versions of Microsoft Office that support the format through plugins or built-in converters. By consistently using these formats, organizations can reduce their vulnerability to vendor-specific behaviors.
Microsoft’s subscription-based Microsoft 365 model has further shifted the dynamics of software usage. Rather than purchasing perpetual licenses for desktop applications, many users now rely on continuously updated cloud services. This approach provides Microsoft with regular revenue and allows rapid feature deployment, but it also means that document behavior can change without users explicitly upgrading their software. An update to the online version of Excel might alter how certain formulas evaluate, creating unexpected results for users who open the same file in desktop LibreOffice weeks later.
Advocates for open standards argue that true competition requires genuine data portability. When users cannot reliably move their documents between applications without loss of fidelity, the market becomes less competitive. This situation affects not only office productivity software but also sets precedents for other categories where dominant players might employ similar tactics. The LibreOffice statement serves as a reminder that technical decisions about file formats carry significant implications for user freedom and market fairness.
Organizations evaluating their office software strategy should consider several practical steps. First, they can audit existing document repositories to identify files saved in proprietary formats that might contain complex formatting or macros. Converting these files proactively to ODF can prevent future compatibility problems. Second, teams should establish clear policies about which file formats to use for internal and external sharing. Third, IT departments might test both Microsoft Office and LibreOffice side by side with representative documents to understand where differences occur and develop appropriate workarounds.
Software diversity benefits users by encouraging innovation and preventing monopolistic control over essential tools. While Microsoft Office remains the standard in many professional environments, alternatives like LibreOffice offer compelling advantages including no licensing costs, strong privacy protections, and the ability to customize the software to meet specific organizational needs. The continued efforts by its developers to address compatibility challenges demonstrate a commitment to making open-source office software a viable choice for everyone.
The debate over document formats ultimately reflects deeper questions about control, transparency, and user autonomy in computing. As more aspects of work and personal life move into digital formats, the systems used to create, store, and share that information take on increased significance. When those systems include artificial barriers that serve commercial interests rather than user needs, they deserve careful scrutiny. The LibreOffice community’s latest criticism adds to a long record of similar observations and keeps the pressure on Microsoft to deliver on its promises of openness.
Users who want to reduce their dependence on any single vendor can begin by installing LibreOffice alongside their existing Microsoft applications. Modern versions of both programs can coexist peacefully on the same computer, allowing gradual transition as comfort with the alternative interface grows. Over time, many users discover that for everyday tasks like writing reports, managing budgets, or creating presentations, the open-source option performs admirably while eliminating recurring licensing expenses.
The persistence of these compatibility discussions shows that the issue remains unresolved despite years of public debate and standards work. Until software vendors prioritize true interoperability over strategic advantage, users will continue facing unnecessary obstacles when trying to work with documents across different platforms. The latest statement from the LibreOffice developers serves as both a technical analysis and a call for greater transparency in how the world’s most popular office applications handle the files millions of people create every day. By raising awareness about these practices, they hope to encourage both individual users and large organizations to make more informed choices about the tools they adopt for their daily work.
WebProNews is an iEntry Publication