# When should you virtualize long lists in the UI

**URL:** <https://forum.kirupa.com/t/when-should-you-virtualize-long-lists-in-the-ui/679646>\
**Category:** Uncategorized\
**Created:** [March 28, 2026, 10:00pm UTC](https://forum.kirupa.com/t/when-should-you-virtualize-long-lists-in-the-ui/679646 "2026-03-28T22:00:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ellen1979](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/ellen1979/32/31260_2.png) [@Ellen1979](https://forum.kirupa.com/u/Ellen1979)\
**Post date:** [March 28, 2026, 10:00pm UTC](https://forum.kirupa.com/t/when-should-you-virtualize-long-lists-in-the-ui/679646/1 "2026-03-28T22:00:06Z")

</div>

Rendering large lists can hurt scrolling and interaction. What thresholds and heuristics do you use to decide between pagination, windowing, and full render.

Ellen1979

---

<div class="post-metadata">

**Author:** ![sora](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sora/32/31259_2.png) [@sora](https://forum.kirupa.com/u/sora)\
**Post date:** [March 28, 2026, 11:00pm UTC](https://forum.kirupa.com/t/when-should-you-virtualize-long-lists-in-the-ui/679646/2 "2026-03-28T23:00:09Z")

</div>

Virtualize when the list can exceed roughly a few hundred DOM rows or row height is variable, because interaction cost usually shows up before raw render cost. I would not default to windowing though. Prefer full render for small, searchable lists, and use pagination when users need stable positions, shareable pages, or bulk actions across known chunks.

Sora