Foundation guide

Virtual data grid documentation

Virtualization controls how much of the grid stays mounted at once. Keep it on in most cases, and tune row or column buffers only when measured scrolling behavior requires it.

What it means

Virtualization controls how much of the grid stays mounted at once. It reduces browser work on long or wide grids.

When to use it

Keep row and horizontal virtualization on for most production grids. Cell-content virtualization is off by default and should be enabled only for measurably expensive cell renderers. Start with the default buffers. Increase them only when fast scrolling exposes blank work, or reduce them when mounted DOM cost is the bottleneck.

Implementation notes

Treat virtualization as a performance setting, not a visual feature. Validate custom cell renderers early. They are the most common reason teams try to change virtualization defaults.

Relevant API

Start with virtual.enableVirtualization, virtual.enableHorizontalVirtualization, virtual.enableCellContentVirtualization, virtual.rowBufferPx, virtual.columnBufferPx. Open the live API reference for types and defaults.