Pagination vs infinite scroll vs load more

How content is revealed has a direct impact on usability. Pagination, infinite scroll, and load more buttons are three common approaches.

• Pagination splits content into separate pages with clear navigation.
• Infinite scroll automatically loads more content as the user scrolls.
• Load more uses a button to reveal additional items on demand.

Selecting the right method depends on context, content type, and user needs.

Guidelines for selecting and implementing content loading patterns.

Use pagination for structured, findable content

Best for search results, documentation, or archives where users need clear sense of progress and ability to return to specific pages.

References:

• Pagination design guidelines – Nielsen Norman Group
• Designing interfaces – Jenifer Tidwell

Use infinite scroll for discovery-driven experiences

Suitable for feeds (for example: social media), where users don’t need a specific endpoint and are encouraged to explore continuously.

References:

• Infinite scroll usability – Baymard Institute

Use load more for balance between control and performance

A load more button reduces cognitive load by chunking content while still keeping the user in control. It performs better than pure infinite scroll for many e-commerce or gallery contexts.

• Show the load more number if the system loads a fixed number of items each time and you know the total number of remaining items. It improves predictability and reduces uncertainty.
• Use consistent phrasing across the product (don’t mix “Load more” and “Show more”).

References:

• Infinite scrolling alternatives – Nielsen Norman Group

Always provide clear indicators of progress

Users must know how much content is left and where they are. Use page numbers, item counts, or progress indicators.

References:

• Jakob Nielsen's web usability heuristics – Nielsen Norman Group

Support accessibility and navigation

Ensure keyboard users and screen readers can navigate across pages or loaded sections. Use ARIA landmarks, maintain focus after loading, and provide skip links.

References:

• ARIA Authoring Practices – W3C

Frequent mistakes when choosing or implementing content loading patterns.

Using infinite scroll for goal-driven tasks

Users searching for specific information get lost without an endpoint.

Not preserving user position across pagination

Returning to page 1 after clicking back frustrates users.

Overloading infinite scroll without performance optimization

Leads to sluggish interfaces and crashes on mobile devices.

Removing footer access with infinite scroll

Users lose access to critical navigation or site information.

Key takeaways for pagination, infinite scroll, and load more.

• Use pagination for structured, goal-driven content.
• Use infinite scroll for discovery-focused experiences.
• Use load more when balancing exploration with performance.
• Always provide progress indicators and accessible navigation.

The right choice improves usability, accessibility, and performance. The wrong choice frustrates users and harms discoverability.

Scenario: Choosing the right pattern

Use when deciding between pagination, infinite scroll, and load more for any content list: search results, product listings, feeds, or galleries.

You are a UX-focused design agent. Design the content loading pattern for [content list: search results / product listing / social feed / gallery].

Rules:
- Use pagination when:
  Users look for specific items and need to return to a position
  Content is structured: search results, documentation, archives, tables
  Users need a sense of progress and location ("Page 3 of 24")
  Users will share or bookmark specific pages

- Use infinite scroll when:
  Content is discovery-driven with no specific endpoint
  Users are exploring, not searching: social feeds, news feeds
  There is no important footer with navigation links
  Never use for goal-driven tasks — users get lost with no way back

- Use load more when:
  You want user control with manageable performance
  E-commerce, galleries, filtered lists
  Show how many items will load: "Load 20 more (64 remaining)"
  Use consistent label: never mix "Load more" and "Show more"

- Always provide progress indicators regardless of pattern:
  Pagination: page numbers, item count ("Showing 41–60 of 247 results")
  Load more: remaining item count
  Infinite scroll: scroll position indicator or section markers

- Preserve user position on back navigation:
  Pagination: return to correct page
  Infinite scroll / load more: restore scroll position

Accessibility:
- Pagination: keyboard operable prev/next + numbered page links
- Load more button: keyboard operable, aria-label describes what will load
- Infinite scroll: provide a keyboard-accessible alternative (load more button fallback)

Constraints:
- Never use infinite scroll for search results or filtered content
- Never remove progress indicators
- Never mix "Load more" and "Show more" phrasing in the same product