> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pagination

> Pagination helps users navigate large sets of data by dividing them into manageable pages. It allows for faster load times, better user control, and easier data scanning.

## Pagination

<Badge color="blue">v1.0.0</Badge> | [View in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-pagination--docs)

### When to use

* When there is a large dataset or long lists (tables, search results, item galleries).
* When performance or load times could be impacted by infinite scroll.
* When users need to reference or return to specific locations in a dataset.

### When to use something else

* Continuous, discovery-focused feeds: prefer infinite scroll or “Load more.”.
* Task completion requires consuming items in order: use wizards or dedicated flows instead of arbitrary page jumps.
* Switching unrelated page modes: use [Segmented control](/aura-design-system/primitives/segmented-control) or [Tabs](/aura-design-system/primitives/tabs) instead of page numbers.

### Dos and don'ts

* Do provide "Next" and "Previous" Buttons as these provide intuitive navigation for sequential browsing. Disable the "Next" and "Previous" Buttons if not relevant.
* Do provide "Results per page" options for large data sets. This lets users control how much data they see at once.
* Do place Pagination below the [Data grid](/aura-design-system/primitives/data-grid) (or page content), left aligned. This ensures side panels opening from the right will not overlap the Pagination.
* Do use the "results" section to indicate the number of items per page by default or when filtered.
* Do show a teleport when there are large datasets to help the user navigate to a specific page.
* Don't use Pagination when there are fewer than \~20 items per page as this can be cumbersome for the user.

### Behavior

* Ideally, every page should have its own URL so that links to specific pages can be bookmarked or shared.
* If possible, items on each page should load without reloading the entire page. Use a loader and skeletons to indicate that content is loading.
* Consider loading times when deciding whether to use Pagination or other alternatives such as lazy loading.
* When the teleport variation is being used, the user can navigate to a desired page by typing the page number and pressing Enter on the keyboard.
* If there are filters, selection, or search, preserve those as the user moves across pages.

### Often used with

* [Data grid](/aura-design-system/primitives/data-grid) or long lists; “rows per page” [Select](/aura-design-system/primitives/select); prev/next [Button](/aura-design-system/primitives/button)s; preserve active [Search](/aura-design-system/primitives/search) / filters across pages.