Virtualization Feature Guide
MRT v1.4 and v1.5 have major virtualization upgrades after switching to
@tanstack/react-virtual
v3.0!
Virtualization is useful when you have a lot of data you want to display client-side all at once without having to use pagination. Material React Table makes this as simple as possible, thanks to @tanstack/react-virtual
with both row virtualization and column virtualization support.
NOTE: You should only enable row virtualization if you have a large number of rows. Depending on the size of the table, if you are rendering less than a couple dozen rows at a time, you will actually just be adding extra overhead to the table renders. Virtualization only becomes necessary when you have more than 50 rows or so at the same time with no pagination.
Relevant Table Options
# | Prop Name | Type | Default Value | More Info Links | |
---|---|---|---|---|---|
1 |
| ||||
2 |
| ||||
3 |
| MRT Virtualization Docs | |||
4 |
| MRT Virtualization Docs | |||
5 |
| ||||
6 |
| ||||
What is Virtualization?
Virtualization, or virtual scrolling, works by only rendering the rows or columns that are visible on the screen. This is useful for performance and user experience, as we can make it appear that there are hundreds, thousands, or even tens of thousands of rows in the table all at once, but in reality, the table will only render the couple dozen rows that are visible on the screen, or the handful of columns that are visible on the screen.
For more reading on the concept of virtualization, we recommend this blog post by LogRocket.
Does Your Table Even Need Virtualization?
If your table is paginated or you are not going to render more than 50 rows at once, you probably do not need row virtualization.
If your table does not have more than 12 columns, you probably do not need column virtualization.
There is a slight amount of extra overhead that gets added to your table's rendering when virtualization is enabled, so do not just enable it for every table. That being said, if your table does have well more than 100 rows that it is trying to render all at once without pagination, performance should improve significantly once it has been enabled.
Enable Row Virtualization
Enabling row virtualization is as simple as setting the enableRowVirtualization
table option to true
. However, you will probably also want to turn off pagination, which you can do by setting enablePagination
to false
.
<MaterialReactTablecolumns={columns}data={data}enablePagination={false}enableRowVirtualization/>
Take a look at the example below with 10,000 rows!
# | First Name | Middle Name | Last Name | Email Address | Address | Zip Code | City | State | Country |
---|
1import { useEffect, useMemo, useRef, useState } from 'react';2import {3 MaterialReactTable,4 type MRT_ColumnDef,5 type MRT_SortingState,6 type MRT_Virtualizer,7} from 'material-react-table';8import { makeData, type Person } from './makeData';910const Example = () => {11 const columns = useMemo<MRT_ColumnDef<Person>[]>(12 //column definitions...57 );5859 //optionally access the underlying virtualizer instance60 const rowVirtualizerInstanceRef =61 useRef<MRT_Virtualizer<HTMLDivElement, HTMLTableRowElement>>(null);6263 const [data, setData] = useState<Person[]>([]);64 const [isLoading, setIsLoading] = useState(true);65 const [sorting, setSorting] = useState<MRT_SortingState>([]);6667 useEffect(() => {68 if (typeof window !== 'undefined') {69 setData(makeData(10_000));70 setIsLoading(false);71 }72 }, []);7374 useEffect(() => {75 //scroll to the top of the table when the sorting changes76 try {77 rowVirtualizerInstanceRef.current?.scrollToIndex?.(0);78 } catch (error) {79 console.error(error);80 }81 }, [sorting]);8283 return (84 <MaterialReactTable85 columns={columns}86 data={data} //10,000 rows87 enableBottomToolbar={false}88 enableGlobalFilterModes89 enablePagination={false}90 enableRowNumbers91 enableRowVirtualization92 muiTableContainerProps={{ sx: { maxHeight: '600px' } }}93 onSortingChange={setSorting}94 state={{ isLoading, sorting }}95 rowVirtualizerInstanceRef={rowVirtualizerInstanceRef} //optional96 rowVirtualizerOptions={{ overscan: 8 }} //optionally customize the virtualizer97 />98 );99};100101//virtualizerInstanceRef was renamed to rowVirtualizerInstanceRef in v1.5.0102//virtualizerProps was renamed to rowVirtualizerOptions in v1.5.0103104export default Example;105
Enable Column Virtualization
Enabling column virtualization is also as simple as setting the enableColumnVirtualization
table option to true
.
<MaterialReactTable columns={columns} data={data} enableColumnVirtualization />
Take a look at the example below with 500 columns!
1import { useRef } from 'react';2import { MaterialReactTable, type MRT_Virtualizer } from 'material-react-table';3import { fakeColumns, fakeData } from './makeData';45const Example = () => {6 //optionally access the underlying virtualizer instance7 const columnVirtualizerInstanceRef =8 useRef<MRT_Virtualizer<HTMLDivElement, HTMLTableCellElement>>(null);910 return (11 <MaterialReactTable12 columnVirtualizerInstanceRef={columnVirtualizerInstanceRef} //optional13 columnVirtualizerOptions={{ overscan: 4 }} //optionally customize the virtualizer14 columns={fakeColumns} //500 columns15 data={fakeData}16 enableColumnVirtualization17 enableColumnPinning18 enableRowNumbers19 />20 );21};2223export default Example;24
WARNING: Do not enable row or column virtualization conditionally. This could break React's Rule of Hooks and/or cause other UI jumpiness.
Virtualization Side Effects
When either row or column virtualization is enabled, a few other props automatically get set internally.
layoutMode
Prop
In MRT Versions 1.3 and earlier, a CSS table-layout: fixed
style was automatically added to the <table>
element to prevent columns from wiggling back and forth during scrolling due to body cells having varying widths.
But now in MRT Versions 1.4 and later, the layoutMode
table option is automatically set to the 'grid'
value when either row or column virtualization is enabled, which means that all of the table markup will use CSS Grid and Flexbox instead of the traditional semantic styles that usually come with table tags. This is necessary to make the virtualization work properly with decent performance.
enableStickyHeader
Prop
The enableStickyHeader
table option is automatically set to true
when row virtualization is enabled. This keeps the table header sticky and visible while scrolling and adds a default max-height of 100vh to the table container.
Customize Virtualizer Props
You can adjust some of the virtualizer props that are used internally with the rowVirtualizerOptions
and columnVirtualizerOptions
props. The most useful virtualizer props are the overscan
and estimateSize
options. You may want to adjust these values if you have unusual row heights or column widths that are causing the default scrolling to behave strangely.
<MaterialReactTablecolumns={columns}data={data}enableColumnVirtualizationenablePagination={false}enableRowVirtualizationcolumnVirtualizerOptions={{overscan: 5, //adjust the number of columns that are rendered to the left and right of the visible area of the tableestimateSize: () => 400, //if your columns are wider or , try tweaking this value to make scrollbar size more accurate}}rowVirtualizerOptions={{overscan: 10, //adjust the number or rows that are rendered above and below the visible area of the tableestimateSize: () => 100, //if your rows are taller than normal, try tweaking this value to make scrollbar size more accurate}}/>
See the official TanStack Virtualizer Options API Docs for more information.
MRT v1.4 upgraded from
react-virtual
v2 to@tanstack/react-virtual
v3.0, which has some breaking changes and virtualizer option name changes. TypeScript hints should help you with any prop name changes, but you can also view the official TanStack Virtual Docs for guidance.
Access Underlying Virtualizer Instances
In a similar way that you can access the underlying table instance, you can also access the underlying virtualizer instances. This can be useful for accessing methods like the scrollToIndex
method, which can be used to programmatically scroll to a specific row or column.
const columnVirtualizerInstanceRef = useRef<Virtualizer>(null);const rowVirtualizerInstanceRef = useRef<Virtualizer>(null);useEffect(() => {if (rowVirtualizerInstanceRef.current) {//scroll to the top of the table when sorting changesrowVirtualizerInstanceRef.current.scrollToIndex(0);}}, [sorting]);return (<MaterialReactTablecolumns={columns}data={data}enableColumnVirtualizationenableRowVirtualizationrowVirtualizerInstanceRef={rowVirtualizerInstanceRef}columnVirtualizerInstanceRef={columnVirtualizerInstanceRef}/>);
See the official TanStack Virtualizer Instance API Docs for more information.
Full Row and Column Virtualization Example
Try out the performance of the fully virtualized example with 10,000 rows and over a dozen columns! Filtering, search, and sorting also maintain usable performance.
View Extra Storybook Examples