# Infinite Scroll

Infinite scroll progressively loads more items as a user approaches the end of a collection, replacing explicit page-by-page navigation.

- Type: practice
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/infinite-scroll/>)

## What it means

Infinite scroll is a collection-loading behavior in which additional batches appear during scrolling. It can support open-ended browsing, but it changes navigation, position restoration, footer access, performance, and assistive-technology behavior compared with pagination or an explicit Load more control.

## Why it matters

Continuous loading reduces interruption for exploratory feeds, yet it can remove users' sense of progress and make items difficult to relocate. The choice affects product behavior, accessibility, analytics, URLs, memory use, and perceived control.

## When to use it

Use infinite scroll for exploratory, frequently changing feeds where users browse without a known endpoint. Prefer pagination or Load more for goal-directed search, comparison, finite result sets, footer-dependent pages, or tasks that require stable position and shareable boundaries.

## How it works

1. Confirm that continuous exploration matches the user goal better than locating or comparing known items.
2. Load bounded batches before the viewport reaches the end and communicate loading and failure states.
3. Preserve item identity, scroll position, focus, and browser history when users open and return from an item.
4. Provide keyboard and assistive-technology access to newly inserted content and a reachable end or alternative control.
5. Measure performance, repeated exposure, abandonment, and successful return—not only additional scrolling.

## A practical example

A visual inspiration feed loads cards in batches as people explore. Opening a card records the feed state in history, Back restores the exact position, failures offer Retry, and a preference switches to paginated results for users who want stable boundaries.

## Where it breaks

The pattern can encourage unbounded consumption, consume memory and data, destabilize analytics, and make footers unreachable. Dynamic insertion may disorient keyboard and screen-reader users, and position restoration is technically demanding.

## Common mistakes

- Choosing infinite scroll solely to increase engagement time.
- Resetting users to the top after they inspect an item.
- Appending content without an accessible loading or failure state.
- Using it for search results that users need to compare or revisit.

## Sources

1. [Feed Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/feed/>) — W3C Web Accessibility Initiative · Technical guidance
2. [Infinite Scrolling Is Not for Every Website](<https://www.nngroup.com/articles/infinite-scrolling-tips/>) — Nielsen Norman Group · Usability guidance

## Related topics

- [Loading State](<https://wiki.soroush.uk/topic/loading-state/>)
- [Client-Side Routing](<https://wiki.soroush.uk/topic/client-side-routing/>)
- [Faceted Navigation](<https://wiki.soroush.uk/topic/faceted-navigation/>)
