What it is
Read-only LibreOffice core repo - no pull request (use gerrit instead https://gerrit.libreoffice.org/) - don't download zip, use https://dev-www.libreoffice.org/bundles/ instead R GitHub popularity snapshot captured on 2026-07-16: 4,144 stars and 888 forks.
Teams can evaluate LibreOffice as an open alternative to Microsoft Word while keeping the implementation, license, and repository signals visible. Confirm the official documentation against your exact workflow before treating it as a production dependency.
- Categories
Content & Collaboration- Tags
- libreofficetdf
- Built with
C++
Github Actions
JavaScript
CSS
Bash
Eslint- Alternatives to
Microsoft Word
Google Docs
Google Workspace
Microsoft 365
Who it’s for — and when to skip it
Knowledge teams
Use it when collaborative content should remain exportable and under your control.
Skip if required editing, permissions, or migration features are missing.
Community operators
Consider it when customization and transparent moderation workflows matter.
Skip if your team cannot run community safety and support operations.
Distributed teams
Evaluate it when shared content and communication need an open deployment path.
Skip if realtime scale or mobile experience is not proven for your use case.
Strengths and trade-offs
Why teams consider it
libreoffice
tdf
C++
Source code and GPL-3.0 license are visible before adoption
Repository activity is available as a current maintenance signal
What to validate
A public repository does not automatically guarantee a documented self-hosting path
GitHub popularity is not a security, quality, or product-fit guarantee
The GPL-3.0 license still needs review against your distribution and commercial model
Support quality, migration effort, and production hardening vary by project
Pricing
Free and open source
No commercial plan is documented in this catalog entry. Self-hosting or third-party infrastructure may still incur operating costs.
Open source
$0Project license- Source available under the listed license
- No catalog-documented paid edition
- Infrastructure costs depend on how you run it
Capabilities and stack fit
Catalog metadata supports discovery, not installation. Verify supported versions, dependencies, deployment topology, and production requirements in the official repository.
Guides for LibreOffice
Use the learning library to find a guide by technology, category, or difficulty.
Browse guidesRelated articles
Approved community reviews
Ratings appear on directory cards only after at least three approved reviews, reducing the impact of one-off scores.
★★★★★Good for beginners but lacks advanced capabilities.
Before you adopt it
- 01
Read the license and confirm it fits your intended use and distribution model.
- 02
Review recent commits, open issues, releases, and the maintainer response pattern.
- 03
Run a small proof of concept with representative data, users, and integrations.
- 04
Confirm whether an official deployment or self-hosting guide exists.
- 05
Document an export or migration path before storing critical data.
