How do I calculate pages from rows per page?

Divide the total row count by the rows per page and round up. For example, 1,234 rows at 25 rows per page is 1,234 ÷ 25 = 49.36, so 50 pages, with 9 rows on the last page.

What does "Rows per page: 50, 1–1 of 1" mean under a table?

It is a pagination footer. "Rows per page: 50" is the page-size setting, so the table shows up to 50 rows at once, and "1–1 of 1" means it is displaying row 1 through row 1 of 1 matching row, which fits on a single page.

What is LIMIT/OFFSET pagination?

LIMIT/OFFSET is the most common database pagination technique. LIMIT controls how many rows are returned per page, and OFFSET skips a number of rows to reach the desired page. For page N with page size P, the query is: SELECT ... LIMIT P OFFSET (N-1)*P.

Why does the last page sometimes have fewer rows?

If the total row count is not evenly divisible by the page size, the final page contains only the remainder rows. For example, 105 rows with a page size of 10 gives 10 full pages plus a final page with 5 rows.

What is the performance impact of large OFFSET values?

Large OFFSET values can be slow because the database must scan and discard all preceding rows before returning the desired page. For very large tables, consider keyset (cursor) pagination using an indexed column instead.

How many rows per page should I use: 10, 25, 50 or 100?

Common page sizes are 10, 20, 25, 50, and 100. Smaller page sizes reduce query time and memory use per request but increase the total number of requests for full scans. For APIs, 20-50 is typical; for admin dashboards, 25-100 works well.

Does this tool work for any SQL database?

Yes. LIMIT/OFFSET syntax is supported by PostgreSQL, MySQL, MariaDB, SQLite, and most other relational databases. Oracle uses FETCH NEXT ... ROWS ONLY or ROWNUM, but the math is identical.

What does "page 1" offset equal?

Page 1 always has an OFFSET of 0, meaning no rows are skipped. The formula is OFFSET = (page_number - 1) * page_size.

How many rows fit on a SQL Server data page?

Microsoft's formula is Rows_Per_Page = 8096 ÷ (Row_Size + 2), rounded down, where Row_Size = fixed-length bytes + variable data (2 + 2 per variable column + their bytes) + null bitmap (2 + (columns + 7) ÷ 8) + 4. A 6-column row with 24 fixed bytes and two variable columns holding 60 bytes is 97 bytes, so 81 rows fit on a page and 1,000,000 rows need 12,346 pages, about 96.5 MB.

How many rows fit in a PostgreSQL 8 KB page?

Each row costs a 4-byte line pointer plus its tuple: a 23-byte header (padded to 24) and the column data, rounded up to a multiple of 8. A page has 8,192 bytes minus a 24-byte header, and at most 291 rows. The same 24 fixed bytes plus 60 bytes of text in two columns makes a 112-byte tuple, 116 bytes per row, so 70 rows per page.

How do I show "Showing 26–50 of 1,234" for a page?

The first row on page n is (n − 1) × page size + 1 and the last is the smaller of n × page size and the total. Page 2 at 25 rows per page shows 26–50 of 1,234; page 50 shows 1,226–1,234 (9 rows). The page explorer prints this label with the SQL for that page.

Rows Per Page Calc

Enter total rows and a page size or page count for total pages, the rows on any page and ready SQL; or describe a table row to see how many rows fit in an 8 KB database page and how large the table is.

Rows per page is how many records a table or query shows on each page.

Pagination Inputs

Total Rows

Calculation Mode

Rows Per Page

SQL dialect

Sort column used in the snippets; a unique, indexed column keeps pages stable.

Enter your values and press Calculate

Rows per database page (storage)

How many rows fit in one 8 KB SQL Server or PostgreSQL data page, how many pages the table needs and how big it is on disk.

Database engine

Rows in table

Total columns

Fixed-length bytes

Variable-length columns

Avg variable bytes / row

Fill factor (%)

Byte sizes: int 4, bigint 8, date 3 (SQL Server) / 4 (PostgreSQL), datetime2/timestamp 8, decimal(18,2) 9, uniqueidentifier/uuid 16, char(n) n; varchar holds its actual length, nvarchar 2 bytes per character.

—

Bytes per row

—

Rows per page

—

Data pages

—

Table size

Copied!

Quick answer

Rows per page is how many records a table or query shows on each page. Total pages = total rows ÷ rows per page, rounded up; the last page holds the remainder, and page N starts at OFFSET (N − 1) × rows per page in SQL.

Examples

Rows per page	Pages for 1,234 rows	Rows on last page
10	124	4
25	50	9
50	25	34
100	13	34

Enter your row count for total pages and LIMIT/OFFSET SQL for any page.

Summary

The Rows Per Page Calculator covers both meanings of "rows per page". For pagination, enter the total row count and a page size or page count to get total pages, the last-page row count, the "showing 26–50 of 1,234" range for any page and copy-ready SQL in LIMIT/OFFSET or OFFSET … FETCH form, plus a keyset (seek) query for deep pages. For storage, describe a row (columns, fixed-length bytes, variable-length data) and it applies the Microsoft SQL Server heap formula (8,096 usable bytes, 2-byte slot per row), the PostgreSQL page layout (24-byte page header, 23-byte tuple header, 4-byte line pointer, 8-byte alignment) or an InnoDB approximation to give rows per page, data pages and table size. All computation runs in the browser.

How it works

Enter the total number of rows in your dataset.
Choose a calculation mode: fix the page size and calculate page count, or fix the page count and calculate page size.
Enter your page size or desired page count.
The tool calculates total pages, rows on the last page, and generates SQL snippets.
Use the page explorer to get the row range and the exact LIMIT/OFFSET (or OFFSET … FETCH) for any page.
Copy any SQL snippet to your clipboard with one click.
For storage sizing, choose the database engine and enter the column count and byte sizes to get rows per data page, page count and table size.

Use cases

Plan pagination for a large database table before writing queries.
Calculate the correct LIMIT and OFFSET values for a specific page.
Estimate how many pages a result set will span for UI design.
Determine page size for REST API cursor or offset pagination.
Quickly convert between page count and page size for reporting tools.
Validate that your pagination logic handles the last (partial) page correctly.
Generate ready-to-copy SQL snippets for PostgreSQL, MySQL, or SQLite.
Teach junior developers how LIMIT/OFFSET pagination works.

Frequently Asked Questions

Last updated: 2026-10-09 · Reviewed by Nham Vu

Rows Per Page Calc

Pagination Inputs

SQL Snippets

Page Explorer

Keyset (seek) pagination — next page

Rows per database page (storage)

Quick answer

Examples

Summary

How it works

Use cases

Frequently Asked Questions

Rows Per Page Calc

Use the Rows Per Page Calc

Pagination Inputs

SQL Snippets

Page Explorer

Keyset (seek) pagination — next page

Rows per database page (storage)

Quick answer

Examples

Summary

How it works

Use cases

Frequently Asked Questions