ReoGrid One

V4 and V5, side by side. One license covers both.

ReoGrid One licenses are version-independent. There is no forced upgrade and no end-of-life for V4 — you choose per project, and your existing key works with V5 as-is, with no re-issue.

The license is version-independent

One key, both versions

A key issued for V4 activates V5 — and vice versa. Nothing to re-issue, nothing to exchange. One license also covers WinForms, WPF and Avalonia (V5+).

V4 is not going away

V4 stays on sale and supported. There is no end-of-sale or end-of-life planned, so staying on V4 — for one project or all of them — is a fully supported choice.

Perpetual, no kill switch

Licenses are buy-once and perpetual. The first year of updates & support is included; renewing is optional, and your installed versions keep working either way.

Installing both, without conflicts

V5 ships under a separate package family precisely so the two versions never collide: different NuGet IDs, different assemblies, different namespaces. A solution can contain V4 projects and V5 projects side by side. The recommended pattern is one version per project — for example, keep an existing V4 desktop app unchanged while new server-side code targets unvell.ReoGrid.One.Core — and exchange data between them via XLSX.

V4 V5
NuGet packages unvell.ReoGrid4 / unvell.ReoGrid4.Wpf (frozen at 4.x) unvell.ReoGrid.One / .One.Wpf / .One.Avalonia / .One.Core
Assemblies unvell.ReoGrid.dll unvell.ReoGrid.One*.dll
Root namespace unvell.ReoGrid unvell.ReoGrid.Core (+ platform namespaces)
.NET .NET Framework 4.8 / .NET 8 .NET 10
License & key One ReoGrid One license The same license and the same key

Data exchange: V5 does not read RGF files — save as XLSX from V4 (while V4 is installed) and read it in V5. XLSX round-trips between both versions and with Excel.

Choosing per project

Reach for V4 when…

  • You need a V4 feature that is not in V5 yet (see the list below)
  • The project cannot move to .NET 10 yet (.NET Framework 4.8 / .NET 8)
  • You rely on RGF files or ReoScript

Reach for V5 when…

  • Large sheets — V5 uses ~16–23 bytes per cell (measured) vs ~150–200 bytes in V4
  • Cross-platform desktop with Avalonia (Windows / macOS / Linux)
  • Server-side or batch processing with the headless, UI-independent core
  • PDF export on servers and in containers — headless on Windows, Linux and macOS, CJK font embedded

Either way, the license is the same — so the choice is purely technical, and you can revisit it per project. Every feature is compared below.

Not in V5 yet

As of ReoGrid One 5.2, the following V4 features are not in V5. There is no committed date for them — they are considered based on demand, and the roadmap shows what is being looked at. V4 will continue to be sold and supported, and the same license and key cover both versions, so a project that needs one of these today can simply use V4.

More cell types (date picker, radio, number input)Multi-level column headersData binding (IDataSource)ChartsThreaded comments (notes are supported)Shapes & text boxes

Not coming to V5

These were left out of V5 by design. Keep using V4 where a project depends on them.

RGF files (save as XLSX from V4)ReoScript

V4 / V5 feature comparison

Every feature, side by side. The V5 column reflects ReoGrid One 5.2, released October 22, 2026.

Feature V4 V5
Core & performance
Fully virtualized core (work scales with the visible window)
Memory per cell ~150–200 B ~16–23 B (measured)
Excel-size sheets (1,048,576 × 16,384) always available Rows allocated up front Sparse — costs nothing until used
UI-independent core (headless / server / batch)
Platforms
WinForms / WPF
Avalonia (Windows / macOS / Linux)
.NET versions .NET Framework 4.8 / .NET 8 .NET 10
Native high-DPI rendering Limited
GPU rendering on WinForms (Direct2D) Yes, 5.2+ (opt-in)
Formulas & formatting
Built-in formula functions 100+ 149, with dependency-based recalculation
Cross-sheet references & defined names
Number formats ReoGrid-specific flags Excel format-code strings (lossless XLSX round-trip)
Conditional formatting OOXML-complete, incl. icon sets round-trip
Rich text in cells
Banded rows, text rotation & indent Banding resolved at render time — survives sorting and filtering
Cell types & editing
Built-in cell types Checkbox, dropdown, button, hyperlink, date picker, radio, number input, image… Checkbox, dropdown, progress, button, hyperlink, sparkline (new) + custom
Multi-level column headers
Undo / redo, sort, filter, outline, clipboard, auto-fill
Data binding (IDataSource) Not yet — write the rows with a loop
Data validation IValidator + validation events Excel-compatible rules — lists, comparisons, custom formulas, XLSX round-trip
Find & replace Values, formulas and notes; regex; range or whole workbook
Sheet protection & cell locks Sheet and range read-only Excel's two-layer model — per-cell locks, permission flags, XLSX round-trip
Charts & drawing
Charts Not yet — keep using V4 on the same license
Cell notes (comments) Notes with the XLSX round-trip (threaded comments are not)
Shapes & text boxes Not yet (cell-anchored images are supported)
Images anchored to cells
I/O & printing
XLSX read / write Streaming reader + per-sheet lazy load for huge files
CSV / JSON CSV CSV + reogrid-json (shared with ReoGrid Web)
RGF (legacy format) Not supported — migrate via XLSX
PDF export Direct export from WinForms apps (4.6+) Direct, dependency-free, CJK font embedded — works on Linux/macOS servers
Printing WinForms / WPF, one shared pagination engine, print titles and headers/footers (Avalonia printing not yet)
Scripting & licensing
ReoScript Permanently removed
License One ReoGrid One license covers both Same license & key — no re-issue needed

Requirements: V5 targets .NET 10 (SDK 10.0.301+) — WinForms and WPF on Windows, Avalonia on Windows, macOS and Linux. V4 targets .NET Framework 4.8 and .NET 8.

Ready to go deeper?