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
15 hours agoRepository age
13 yearsLicense
GPL-3.0Repository
libreoffice/core
Last 30 days
Last commit
13 days agoRepository age
12 yearsVersion
v10.0.0License
AGPL-3.0Self-hosted
YesRepository
documentserver
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 7,100 stars vs 4,618 stars for LibreOffice. The 54% higher star count indicates stronger community adoption. In terms of developer contributions, ONLYOFFICE Docs has 1,329 forks, indicating strong developer engagement.
LibreOffice is growing faster, adding 138 stars in the last 30 days (+3.1%) against adding 119 stars for ONLYOFFICE Docs (+1.7%). LibreOffice is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with LibreOffice last updated 15 hours ago and ONLYOFFICE Docs 13 days ago.
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.