Learn how LibreOffice and ONLYOFFICE Docs differ in their key features, development activity, technology stack and community adoption, so you can decide which of these document editors is best for you.
Last 30 days
Last commit
Repository age
License
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both LibreOffice and ONLYOFFICE Docs have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
ONLYOFFICE Docs leads in popularity with 6,885 stars vs 4,335 stars for LibreOffice. The 59% higher star count indicates stronger community adoption. In terms of developer contributions, ONLYOFFICE Docs has 1,307 forks, indicating strong developer engagement.
LibreOffice is growing faster, adding 128 stars in the last 30 days (+3%) against adding 86 stars for ONLYOFFICE Docs (+1.3%). LibreOffice is the smaller project of the two, so it is closing the gap rather than extending a lead.
LibreOffice shows more recent development activity with its last commit 14 hours ago, while ONLYOFFICE Docs was last updated 2 months ago. This suggests LibreOffice is being more actively maintained.
Both tools share common technology foundations, being built with Bash. However, they differ in their additional technology choices: LibreOffice uses JavaScript, CSS, Python, Rust, C, Objective-C, Java, C++, Kotlin, MATLAB, C#, Perl, GLSL, Visual Basic .NET.
Both projects started around the same time, with LibreOffice beginning 13 years ago and ONLYOFFICE Docs 12 years ago.
The projects use different licenses: LibreOffice is licensed under GPL-3.0 while ONLYOFFICE Docs uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Document Editors.
ONLYOFFICE Docs provides self-hosting options for complete data control and customization, while LibreOffice may be primarily cloud-based or require different deployment approaches.