Pagination Design pattern

Problem summary

The user needs to view a subset of sorted data that is not easily displayed on one page.




  • Use when there is more data than what is comfortably fitted into one screen.
  • Use when the dataset is ordered into amount of interest (that usually means newest first)
  • Do not use when you don’t want the user to pause for navigating to the next page.


Break the complete dataset of items into smaller sequential parts and show these on separate sequential pages. Provide pagination control to browse from page to page. Let the user browse to the previous and next pages by providing links to such actions. Also, provide links to the absolute start and end of the dataset (first and last).

If the dataset is of defined quantity, also show a link to the last page. If the dataset to show possibly is of varying size (for instance as a result from a search), do not bother to show a link to the last page.


First and foremost, pagination parts large datasets into smaller bits that are manageable for the user to read and cope with. Secondly, pagination controls conveys information to the user about, how big the dataset is, and how much is left to read or check out and how much have they already checked out.

Pagination provides the user with a natural break from reading or scanning the contents of the dataset, and allows them to reevaluate whether they wish to continue looking through more data, or navigate away from the page. This is also why pagination controls are most often placed below the list: to provide the user with an option to continue reading through the larger dataset.

More example images of the 'Pagination' pattern


Post a comment

Required. Real name or initials only.
Required. Will not be published.
Vote down Vote up
Out of 85 votes, 60.00% like this one.

Related links