Rendlio Sheets vs Syncfusion XlsIO
Facts only for server-side XLSX→PDF: how Rendlio Sheets and Syncfusion XlsIO differ on the free-tier gate, licence shape and reporting. No fidelity numbers.
Checked against Syncfusion XlsIO 34.2.4 · last reviewed 2026-08-24
What each one costs to run.
| Line | Rendlio Sheets | Syncfusion XlsIO |
|---|---|---|
| Entry priceA price we cannot read is not a price we will guess at. Every Syncfusion figure on this page is one Syncfusion publishes; the paid price is not one of them. | $1,499 one-time — Professional, per legal entity. | Not published. Every Essential Studio SDK on Syncfusion's pricing page reads “Get a Custom Quote”, and the quote form asks how many developers you have. |
| Entity-wide licence | Included — unlimited developers, servers and CI runners inside one legal entity. Nothing is counted. | Quote-based, and a subscription rather than a purchase: Syncfusion's pricing page states a minimum one-year subscription, billed monthly or annually, with automatic renewals until cancelled. |
| SaaS/OEM use | Included in every paid tier — no separate SKU and no royalty. Stated on the pricing page, written into the EULA. | Governed by the Essential Studio licence agreement and by the terms of your quote. Syncfusion publishes no list-priced redistribution tier, and we make no claim about what any particular agreement grants. |
| Free tier | Community tier — free below $1M annual revenue, self-certified. One condition, with no headcount or funding caps. | Community licence — free, and genuinely the whole Essential Studio line rather than a cut-down build. The published gate is four conditions at once: under $1M USD annual gross revenue, 5 or fewer developers, 10 or fewer total employees, and never having received more than $3,000,000 USD from an outside source. |
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.
| Capability | Rendlio Sheets | Syncfusion XlsIO | Detail |
|---|---|---|---|
| Free tier that gates on revenue alone | YES | PARTIAL | Syncfusion's Community licence is free, covers the whole Essential Studio line rather than a cut-down build, and permits commercial applications — we would rather say so than argue with it. But it gates on four conditions at once, and a seed round, an eleventh hire or a sixth developer takes the whole company out of it. Rendlio Sheets' Community tier gates on one number, self-certified: under $1M annual revenue, any entity type, any headcount. |
| Published list price you can budget from without contacting sales | YES | NO | Rendlio Sheets publishes every tier including Enterprise, with self-serve checkout. Every Syncfusion SDK on the pricing page reads “Get a Custom Quote”, so the paid price is whatever your quote says and a public page cannot tell you what you will pay. |
| Priced per legal entity, not per developer | YES | NO | Rendlio Sheets counts nothing inside the entity — one price covers every developer, server and CI runner. Syncfusion's own quote form asks for a developer count per product, and its Community gate is written in developers and employees, so team size is the unit the price is built on. |
| Perpetual licence — the build you shipped keeps working after the term ends | YES | UNKNOWN | Rendlio Sheets' licence never expires; only updates do, and maintenance renewal is optional. Syncfusion publishes a minimum one-year subscription with automatic renewal, but what survives expiry is set by its licence agreement rather than by any page we could read, so this row says unknown rather than guessing. Read the current agreement before you plan around either answer. |
| No office suite anywhere in the conversion pipeline | YES | YES | Both are managed libraries with their own rendering path rather than wrappers around an office application. Syncfusion states XlsIO creates, reads and edits Excel documents without Microsoft Office dependencies. Credit where due — this row is a tie. |
| Machine-readable compatibility report with every conversion | YES | PARTIAL | XlsIO has an opt-in warning interface: implement IWarning, hand it to the Excel-to-PDF converter settings, and it reports skipped elements and substituted fonts. Syncfusion documents its scope as elements supported when creating a workbook but not when converting to PDF. Rendlio Sheets' report is not opt-in and not scoped that way — every run names each feature, states its status and warning code, and returns an exit code a pipeline can gate on. |
| Source code published for anyone to read before buying | YES | NO | Rendlio Sheets is source-available under BUSL-1.1 in a public repository, and every version becomes Apache-2.0 four years after its release. Syncfusion ships licensed assemblies and maintains no public repository for XlsIO. This row is about what is published for anyone to read, not about what a particular agreement might make available. |
| Full spreadsheet API — create, edit and recalculate workbooks | NO | YES | This row goes to XlsIO, and it is what teams adopt it for. It creates, reads and edits workbooks, computes formulas and exports to PDF, images, HTML, CSV and more. Rendlio Sheets renders XLSX and XLSM to PDF, PDF/A and PNG and does nothing else, so it does not replace the part of your stack that builds the workbook. |
| Macro execution and external-data refresh off by construction | YES | UNKNOWN | Rendlio Sheets' parser executes no macros, refreshes no external data and opens no network connections from the engine — enforced by analyzers in CI. Nothing in Syncfusion's documentation suggests XlsIO runs VBA either; what its documentation covers is preserving macro projects and their signatures across a resave, which is a different guarantee. We found no published statement that settles the architectural question, so the row says unknown instead of guessing in either direction. |
| 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 — XlsIO on the same corpus included. Nothing is published today, so no fidelity claim appears on this page. We know of no comparable per-release measurement published by Syncfusion, which is what “unknown” means here. |
Syncfusion XlsIO and its name are the property of their respective owners; Rendlio Sheets is neither affiliated with nor endorsed by them.
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.
Questions we would ask too.
We fit the Syncfusion Community gate. Should we still look at Rendlio Sheets?
If you fit the gate and XlsIO does the job, take the free licence — we would rather say that than pretend otherwise. The question worth asking is whether you still fit it in two years: the gate is four conditions at once, and outgrowing any one of them moves you to a quoted, per-developer subscription. Rendlio Sheets' free tier has one condition and its paid tier is a flat price per entity, so the shape of the bill does not change as you hire.
Why does this page not compare prices?
Because only one side of that comparison is published. Rendlio Sheets' tiers are all public with self-serve checkout; every Syncfusion SDK on its pricing page reads “Get a Custom Quote”. We can tell you the licence is quoted per developer on a minimum one-year subscription, because Syncfusion publishes that. We cannot tell you the number, so we do not.
Is Rendlio Sheets a replacement for XlsIO?
Only for one job. XlsIO is a general spreadsheet library — it builds workbooks, computes formulas and exports many formats. Rendlio Sheets renders XLSX and XLSM to PDF, PDF/A and PNG. If your code creates or edits workbooks, Rendlio Sheets replaces the conversion step and nothing else, and you would run both.
XlsIO reports conversion warnings. Is that the same as your compatibility report?
No, and Syncfusion is clear about the scope. Its IWarning interface is opt-in code you write, and its documented remit is elements supported when creating a workbook but not when converting to PDF. Rendlio Sheets emits a report for every run whether you asked or not, names each feature it could not render faithfully with a warning code, and returns a non-zero exit code your CI can gate on.
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, on any engine. Until then this page carries licensing, deployment and architecture facts only.
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.