Spreadsheet rendering SDK · self-hosted CLI, Docker, and .NET no Office · no LibreOffice · BUSL-1.1
01Comparison · Rendlio Sheets vs LibreOffice headless

Rendlio Sheets vs LibreOffice headless

Facts only for server-side XLSX→PDF: how Rendlio Sheets and headless LibreOffice differ on licensing, deployment, security, and reporting. No fidelity numbers.

Checked against LibreOffice headless 26.2 · last reviewed 2026-08-24

02Price · what production use costs

What each one costs to run.

price · published list terms, not quotes reviewed 2026-08-24
LineRendlio SheetsLibreOffice headless
Entry priceNo price row Rendlio Sheets wins. What the $1,499 buys is the contract in the table below. $1,499 one-time — Professional, per legal entity. $0. Free and open source under the Mozilla Public License v2.0.
Entity-wide licence Included — unlimited developers, servers and CI runners inside one legal entity. Nothing is counted. Not applicable. There is no licence to buy, so nothing is counted either.
SaaS/OEM use Included in every paid tier — no separate SKU and no royalty. Stated on the pricing page, written into the EULA. Permitted under MPL-2.0 terms; embedding and SaaS use are allowed, with the licence's conditions applying to modifications of LibreOffice itself.
Free tier Community tier — free below $1M annual revenue. The whole project is free, at any revenue.
03The comparison · facts only

Licensing, deployment, architecture.
Nothing that needs an asterisk.

Every row states something both engines publish or that their behaviour documents. Where we cannot verify a competitor's answer from a published source, the row says unknown rather than guessing. If anything here is out of date, tell us and we will correct it.

facts only · no fidelity or performance numbers on this page LibreOffice headless 26.2 · reviewed 2026-08-24
CapabilityRendlio SheetsLibreOffice headlessDetail
No office suite anywhere in the conversion pipeline YES NO Rendlio Sheets is a self-contained SDK — CLI binary, Docker image, .NET library — with a native rendering engine. The headless-LibreOffice path converts by driving the office application itself (the soffice process), usually containerised or wrapped by a service such as Gotenberg.
Library-shaped integration, with no external process to supervise YES NO Process lifecycle, concurrency and restart-on-hang are the caller's engineering work in a headless LibreOffice deployment; Rendlio Sheets is linked or invoked directly.
Machine-readable compatibility report with every conversion YES NO Rendlio Sheets names each feature, states its status and warning code, and returns a non-zero exit code a pipeline can gate on. Headless conversion is best-effort and silent: a feature that renders differently from Excel's print output does so without any per-file signal.
Source code available to read and audit YES YES Rendlio Sheets is source-available under BUSL-1.1, and every version becomes Apache-2.0 four years after its release. LibreOffice ships its complete source under MPL-2.0.
OSI-approved open-source licence NO YES BUSL-1.1 is source-available, not open source, until its four-year Apache-2.0 conversion. LibreOffice is fully open source, with public development and community governance. This row goes to LibreOffice.
Macro execution and external-data refresh off by construction YES PARTIAL Rendlio Sheets' parser executes no macros, refreshes no external data and opens no network connections from the engine — enforced by analyzers in CI. LibreOffice can be restricted by configuration and sandboxing, but it is a large desktop-suite codebase processing untrusted input, with its own CVE history; the isolation is your work.
A vendor accountable for a rendering defect YES PARTIAL Rendlio Sheets ships email support during your maintenance period, priority on Enterprise, against a published per-conversion compatibility contract. LibreOffice offers community support from the project, with commercial support available from ecosystem vendors rather than from the project itself; rendering differences are handled as bug reports, on the project's timeline.
Published fidelity results against Excel's own print output PLANNED UNKNOWN Rendlio Sheets' corpus harness scores every build against Microsoft Excel's print output, and those results publish together with the corpus and the method at GA so anyone can re-run them — including runs of LibreOffice on the same corpus. Nothing is published today, so no fidelity claim appears on this page. We know of no comparable per-release measurement published by the LibreOffice project, which is what “unknown” means here.

LibreOffice headless and its name are the property of their respective owners; Rendlio Sheets is neither affiliated with nor endorsed by them.

On fidelity numbers · none appear on this page by design

Fidelity scores ship with our public corpus at GA; we publish reproducible numbers, not adjectives. Rendlio Sheets is pre-alpha today — the corpus harness scores every build against Microsoft Excel's own print output, and when those results publish, they publish with the corpus and the method so anyone can re-run them, on any engine. Until then, no fidelity comparison appears here. How scoring works is on the fidelity evidence page.

04FAQ · the questions this comparison raises

Questions we would ask too.

Is Rendlio Sheets a drop-in replacement for headless LibreOffice?

No. LibreOffice converts an enormous range of document formats; Rendlio Sheets renders XLSX and XLSM to PDF, PDF/A and PNG and does nothing else. If your pipeline also converts text documents or presentations, Rendlio Sheets does not replace that part of it.

LibreOffice is free. Why would we pay for Rendlio Sheets?

For two things headless conversion does not give you: output that targets Excel's own print output, and a machine-readable report naming every feature the engine could not render faithfully, with an exit code your CI can gate on. If silent best-effort conversion is acceptable for your PDFs, LibreOffice is the better deal, and we would rather say so than argue with it.

Do you publish fidelity numbers comparing the two engines?

Not yet, and not until the corpus that would make them reproducible is public. Rendlio Sheets is pre-alpha; the corpus harness scores every build against Microsoft Excel's print output, and when those results publish they publish with the corpus and the method so anyone can re-run them, LibreOffice included. Until then this page carries licensing, deployment and architecture facts only.

Can we ship Rendlio Sheets inside our own SaaS or product?

Yes. SaaS and OEM redistribution are included in every paid tier — no separate SKU and no royalty. MPL-2.0 likewise permits embedding and SaaS use of LibreOffice, with the licence's conditions applying to modifications of LibreOffice itself.

Is Rendlio Sheets open source?

No, and we would rather state that plainly than blur it. Rendlio Sheets is source-available under BUSL-1.1 — you can read the code that parses your files, and every version becomes Apache-2.0 four years after release. LibreOffice is fully open source. On that row LibreOffice is stronger, and it is in the table above saying so.

The comparison that matters is yours

Evaluate on your own workbooks.

Drop a real file into the playground and read the compatibility report it comes back with — that is the only comparison that answers your question.