When is keyset pagination better than OFFSET/LIMIT or OFFSET/FETCH?

Explain keyset pagination versus offset pagination

Compares offset and keyset pagination for stable API lists, large tables, and user-facing result consistency.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Offset pagination is simple: skip N rows and take the next page. It works well for small lists and admin screens where jumping to a page number matters. Keyset pagination uses the last seen sort key as a cursor, such as created_at and id, then asks for rows after that cursor. It is often better for large, scrolling lists because the database can continue from an indexed position instead of counting past many rows.

Full answer below

Practice focus

Pagination correctness, stable ordering, index support, large offsets, and API cursor design.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Pagination looks like an API detail, but the database shape decides whether a list stays fast and stable. This is a practical bridge between SQL and backend design.
Offset pagination is simple: skip N rows and take the next page. It works well for small lists and admin screens where jumping to a page number matters. Keyset pagination uses the last seen sort key as a cursor, such as created_at and id, then asks for rows after that cursor. It is often better for large, scrolling lists because the database can continue from an indexed position instead of counting past many rows.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would choose keyset pagination when the list is large, frequently changing, or user-facing as an infinite scroll. The ordering must be stable and unique, so I would sort by created_at plus id or another deterministic pair. Offset pagination can produce duplicates or missing rows when new data appears between requests, and high offsets become expensive. Keyset pagination gives up arbitrary page jumps, but it usually gives better consistency and performance.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using high-offset pagination on very large tables.
Sorting by a non-unique column without a tie-breaker.
Changing filters while reusing an old cursor.
Choosing keyset pagination when users truly need page numbers.

When is keyset pagination better than OFFSET/LIMIT or OFFSET/FETCH?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Tech stacks

Skill areas

Suggest an improvement