> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/general-tools-and-features/table-pagination-and-rows-per-page-selector.md).
# Table Pagination & Rows per Page Selector
## Purpose
Pagination and the Rows per Page Selector provide a clear and efficient way to navigate through large datasets without overloading the interface.
Instead of rendering hundreds of entries at once, this feature divides data into manageable segments, improving performance, readability, and user control.
These controls ensure that users can view, scroll, and interact with data quickly, even in tables with extensive records.
{% hint style="info" %}
[Learn how to use Search and Filter Data](/general-tools-and-features/search-and-filter-bar.md)
{% endhint %}
***
## How to Use Navigating Pages
The pagination bar appears at the bottom of the table and includes the following controls:
**First Page** – Jump to the first page of data.
**Previous Page** – Move back one page.
**Page Numbers** – Click a specific number to jump directly to that page.
**Next Page** – Move forward one page.
**Last Page** – Jump to the final page.
Users can click through pages to view additional records without leaving the table view.
***
## How to Use Selecting Rows per Page
On the top left of all tables is a **Rows per Page Selector**, represented by a dropdown menu.
Clicking it opens a list of options such as:
Selecting a new value automatically updates the table and adjusts how many rows are displayed on each page.
You can choose to display:
* 7 rows
* 10 rows
* 50 rows
* 100 rows
***
## How It Works in Practice
* The table only loads and renders the records relevant to the active page and the selected row limit.
* When the row count is changed, the table recalculates the number of pages and resets to Page 1.
* Pagination actions (Next, Previous, or Page Number) dynamically fetch and display only the required data.
* This ensures a responsive experience even with large datasets, reducing unnecessary data processing and improving performance.
***
## Best Practices
* **Start Small:** Set a small default (for example, 7 or 10 rows) to ensure faster load times and a cleaner display.
* **Preserve User Preferences:** If possible, remember the user’s last selected page size and page number for continuity.
* **Display Totals:** Include “Page X of Y” or “Showing X–Y of Z” information for clear context.
* **Avoid Overloading:** Do not include very high row count options (for example, 500 or 1000). Large loads may cause slow rendering on mobile devices or lower-performance systems.
* **Maintain Accessibility:** Ensure pagination buttons and dropdown menus are easily clickable and screen-reader friendly.
* **Consistent Placement:** Keep pagination controls at the bottom-right or center-bottom of tables for intuitive user interaction.
> **Tips:**
>
> * Allow page-jump functionality in tables with very large record counts.
> * Combine pagination with search and filter tools to make data navigation faster and more precise.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cloudscaff.com/general-tools-and-features/table-pagination-and-rows-per-page-selector.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.