LibreOffice 26.8 pulled in 1,031,162 downloads from the project's own website in its first seven days, the highest first-week total the office suite has ever recorded, and it did that while The Document Foundation was busy telling the world exactly why it still refuses to ship a single generative AI feature. The download figure is nearly two weeks old, but a Document Foundation blog post defending that stance resurfaced on Hacker News this evening, climbing to 82 points in under half an hour of active discussion.

What did The Document Foundation actually say about AI?

The post, titled "Yes, no AI is now a feature," was written as a direct reply to a reader comment asking exactly that question. The Document Foundation's answer wasn't a blanket rejection of the technology. It laid out six conditions that any AI feature would have to meet before it ships in LibreOffice's default configuration, given that the suite runs in schools, hospitals, courts, and government offices where a document's contents are often legally protected:

RelatedNext.js 16.3 Is Built for AI Agents, Not Just Developers

  • User-controlled execution: the user picks whether inference runs locally, on infrastructure they control, or on a service they independently chose.
  • No content leaves the computer without explicit authorization.
  • No telemetry of any kind, a rule that already governs every other part of LibreOffice.
  • No dependency locking users into a single vendor's model or API.
  • No compromises on the underlying file format.
  • The feature must be entirely optional, never forced into a default workflow.
How an AI feature would have to clear LibreOffice's local-first gate Diagram showing an AI feature idea passing through a six-point local-first gate covering user control, no data leakage, no telemetry, no vendor lock-in, no format changes, and optionality. So far nothing has shipped built into LibreOffice by default; the only path that has actually shipped is an opt-in extension connecting to a locally run model via Ollama or LM Studio. Below that, a stat panel shows the resulting download record: 1,031,162 downloads in the first seven days, the highest first-week total of any LibreOffice release. THE LOCAL-FIRST GATE AI feature idea 6-point local-first gate control · no leaks · no telemetry no lock-in · no format break · optional Ships built-in none yet Opt-in extension Ollama / LM Studio THE RECORD, IN NUMBERS 1,031,162 downloads, first 7 days Highest first-week total of any LibreOffice release ever genztech.blog
Fig 1 Nothing has cleared LibreOffice's six-point gate to ship built-in yet; the only AI path that exists today runs through an opt-in extension talking to a model on your own machine.

Is a million downloads actually a big deal for an office suite?

For context, LibreOffice has been downloaded well over 200 million times across its lifetime, and most users get updates automatically through Linux distribution repositories, which this figure doesn't even count. So 1,031,162 direct downloads from the project's own site in one week is a genuine outlier, not a rounding blip. The Document Foundation's own framing, "the highest number of downloads in the first week of any LibreOffice release," is a claim about relative performance against the suite's own history, not an absolute record against Word or Google Docs. Still, for a volunteer-driven open source project with a fraction of Microsoft's marketing budget, a spike like that almost always traces back to a specific trigger rather than steady organic growth, and the timing lines up neatly with the AI conversation.

Why would refusing a popular feature pull in more users?

Because a lot of the people downloading office software right now are doing it specifically to get away from AI, not to find more of it. Microsoft has been folding Copilot into Microsoft 365 subscriptions and raising prices to cover it, whether or not a given household or business actually wants the feature. Google has done something similar by wiring Gemini into Workspace. Every enterprise IT department that handles regulated data, healthcare records, legal filings, financial documents, has spent the last two years fielding the same question from compliance teams: where does this data actually go when the AI button gets pressed? LibreOffice's answer, that nothing leaves the machine because there's no outbound AI pipeline to leak through, is a compliance argument dressed up as a product philosophy, and it happens to be a very persuasive one to exactly the institutions the six principles name: schools, hospitals, courts, public bodies.

What's the fight with Collabora, and why does it matter here?

This is the part most of the download-record coverage today skips entirely. Collabora is the largest corporate contributor to LibreOffice's actual code, the company behind Collabora Online and a major sponsor of engineering work that ships in every LibreOffice release, including calculated fields and multi-page-size support in 26.8 itself. In April 2026, The Document Foundation's membership committee removed every Collabora staffer from TDF membership in one action, over 30 people, in a governance dispute that split the project's commercial backbone from its nonprofit steward. Collabora kept shipping its own downstream product anyway, and in Collabora Office 26.04 it added AI as an optional, disabled-by-default feature where users supply their own model and their own API credentials.

So the same underlying codebase now has two different public AI postures depending on which organization is distributing it, months after the two sides that build it publicly fell out. TDF's blog post reads, in that light, less like abstract philosophy and more like a direct answer to a question its own former members had already answered differently in a shipping product. The technical collaboration between the two hasn't actually stopped, engineers on both sides keep contributing code across the split, but the AI stance is now a place where the split is visible to end users, not just to people following TDF's governance mailing lists.

RelatedOpenShot 4.0 Brings Built-In Recording and Color Grading

SuiteAI by defaultData leaves deviceVendor lock-in
LibreOffice 26.8No, none shippedNo pipeline existsNone
Collabora Office 26.04Optional, off by defaultOnly if you choose a cloud modelNone, bring your own model
Microsoft 365 CopilotIncreasingly bundledYes, processed on Microsoft's cloudTied to Microsoft's models
Google Workspace + GeminiIncreasingly bundledYes, processed on Google's cloudTied to Google's models

Can you still get AI features inside LibreOffice if you want them?

Yes, just not from The Document Foundation directly. Community-built extensions exist that connect Writer, Calc, and Impress to a locally-run model through Ollama, LM Studio, or any other endpoint that speaks the OpenAI-compatible API. Because the inference happens on hardware you control, the document genuinely never leaves the machine, which is the exact property TDF's six principles are trying to guarantee before it will bless anything as a first-party feature. The tradeoff is setup effort: installing and running a local model is a heavier lift than clicking "enable Copilot," and the quality ceiling depends on what your own hardware can run, not on whatever frontier model Microsoft or Google has under contract.

  1. Apr 2026TDF removes over 30 Collabora staffers from membership governance split between nonprofit steward and top corporate contributor
  2. Aug 26, 2026LibreOffice 26.8 ships Paragraph Composer, variable fonts, zero generative AI
  3. Sep 3, 2026TDF publishes "Yes, no AI is now a feature" lays out the six-point local-first gate
  4. Sep 8, 2026Download-record coverage climbs Hacker News 82 points and climbing within 30 minutes
What to watch · Sep-Oct 2026
  • Whether TDF ever certifies a built-in feature. The six-point gate is strict enough that it may simply never be cleared by anything, which would make "no AI" a permanent identity rather than a temporary holdout.
  • Enterprise procurement language. If government and healthcare RFPs start explicitly requiring "no outbound AI pipeline," that's a sign TDF's framing has moved from marketing copy into procurement checklists, which is where open source projects actually win institutional users.
  • Whether Collabora's opt-in model closes the gap. If Collabora Office's disabled-by-default, bring-your-own-model approach gets adopted more widely, the AI question might resolve as an interface layer choice rather than a philosophical one.

Our take

The download number is real and worth reporting, but the more interesting story is what's sitting underneath it. Refusing to add a popular technology rarely wins new users on its own merits, it wins them when refusing solves a problem those users already had. Compliance officers, IT admins at public institutions, and anyone who has had to explain to a client why their AI assistant just summarized a document into a vendor's training pipeline all have that problem right now. The Collabora split adds a wrinkle nobody asked for: LibreOffice's loudest current answer on AI is arriving right after the company that wrote a lot of the underlying code publicly chose a different one for its own product. Both things can be true at once, and readers evaluating whether to move an organization onto LibreOffice should look past the download headline and ask which of the two AI postures, TDF's or Collabora's, actually fits how they plan to deploy the suite.

Primary sources

This one's ours, not a wire rewrite. Sources: The Document Foundation.