Pagination

Pagination is the row of controls at the foot of a long set that says which slice is on screen and moves the reader to another one. It is the cheapest way to make a position nameable: a page can be linked, bookmarked, reloaded and read aloud to a colleague, none of which is true of a scroll position. Paired with a count, it also tells the reader how big the set actually is before they commit to working through it.

Most of the design is in what the row refuses to do. The window of page numbers holds a fixed set of slots, so it never changes width as the reader moves and the button under the pointer never walks away. The ellipsis is a gap and not a control: no border, no hover, nothing behind it. Arrows at the ends fade rather than vanish, for the same reason. And how many rows a page holds is half the feature, usually bolted on last.

18 blocks

Chevron ends

A tight row where the ends need to be reachable rather than explained

Of-N stepper

A narrow footer: one number, its total, and a way to jump straight to a page

Labelled ends

A footer with room for words: Previous and Next survive translation and a screen reader better

Go to page

Long sets where paging one at a time is not the point: type the page and go

Rows per page

The other half of paging: how many rows a page is, before which page you are on

Raised Next

A screen where moving between pages is the main thing happening

Chevron ends, Lens

A tight row where the motion should say which way you went

Chevron ends, Scrub

Sets where the middle pages matter as much as the neighbours

Of-N stepper, Type in place

A narrow footer where people know the page they want

Of-N stepper, Capsule

A compact pager that also shows how far through the set you are

Labelled ends, Destinations

Docs and long reads where the next page has a name

Labelled ends, Load more

Feeds and long lists where pages are an implementation detail

Go to page, Jump field

Long sets where people type the page and want to see it is valid first

Go to page, By name

Alphabetical sets where people remember a surname, not a page number

Rows per page, Table footer

Data tables that need the footer everyone expects

Rows per page, Keeps your place

Tables people read down, where a new page size should not lose the row

Raised Next, Next leads

Readers who mostly go forward

Raised Next, Segments

A short set where the shape of the whole thing is worth seeing

01

Using Pagination

Reach for it when

  • A result set long enough that people jump to a page rather than scroll to one.
  • Under a table, where the reader also has to choose how many rows a page is.
  • Queries paged on the server, where a page is a request rather than a slice of something already loaded.
  • A position that has to survive a reload, a shared link or a colleague reading it out.

Reach for something else when

  • A feed read in order with no particular destination: a Load more button or continuous scrolling matches how people actually move through it.
  • Records that shift position while the set is being read: a cursor anchored to the last record seen beats page numbers that renumber underneath the reader.
  • A set that fits on one screen: show all of it; a pager under a list that was never going to be cut is a control with nothing to do.
02

Where it shows up

01

Table footers

Under a record table, next to a rows-per-page control and a count. The count is what turns an abstract row of numbers into a set with a known size, rather than a next button that might go on forever.

02

Search results

Result lists where relevance falls off with depth. Nearly all the traffic sits on the first page, so reaching the previous page and seeing an honest total matter more than a jump to the end.

03

Back-office queues

Screens where one person works through records over days and has to resume where they stopped. A page number kept in the address survives a reload and a shared link; a scroll position survives neither.

04

Server-paged queries

Sets too large to fetch at once, where a page is the request itself. How many rows a page holds is part of that request, which is why the choice belongs beside the pager rather than in a settings menu.

03

Questions

How many page numbers should be visible at once?

Enough to reach the first page, the last page and the neighbours of the current one, and always the same number of them. A window that grows and shrinks as the reader moves makes buttons wander under the pointer. When the whole set fits inside that window, draw every page: an ellipsis standing in for a single page hides nothing and costs a click.

Is pagination better than infinite scroll?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.