简体中文
EnglishWhat Is an Endless Page and How Do Auto Pagers Create It?
Updated
An endless page is a browsing experience where the next page of content loads automatically as you reach the bottom of the current one, so you never have to click "Next" or "Load More." Auto pager tools create it by detecting the link to the following page, fetching that page, and merging its content into the page you're already reading. Pagetual, for example, is a userscript that does this on Chrome, Firefox, Edge, and Safari, and its developers state it works on roughly 90% of websites without any custom setup.
How an auto pager turns paginated pages into one scroll
The mechanism is simpler than it looks. When you scroll near the bottom of a page, the tool:
- Scans the page structure to find the link or button that points to the next page (the "Next," "Older posts," or numbered pagination link).
- Requests that next page in the background.
- Extracts the main content from the response and appends it below what you've already read.
- Repeats as you keep scrolling, so the page effectively never ends.
Because the merge happens in your browser, the site itself doesn't need to support infinite scroll. You're just chaining its existing pages together.
Why "no rules" matters
Older auto pagers relied on site-specific rules: someone had to write a configuration for each website describing where the next link lives. That breaks whenever a site redesigns, and it means new or obscure sites don't work until someone contributes a rule.
Pagetual takes a different approach. According to its documentation, it analyzes a page's structure on the fly and locates the next link by itself, which is why it claims to work out of the box on most sites and to keep working after redesigns. It also supports over 3,800 existing rules from other pagers for edge cases, but the selling point is that you usually don't need them. Power users can still write custom rules for complex sites.
Endless page vs. native infinite scroll
These look identical while you're scrolling, but they're built differently:
| Native infinite scroll | Auto pager (endless page) | |
|---|---|---|
| Who implements it | The website itself | A browser extension or userscript |
| Works on | Only that site | Almost any paginated site |
| Content source | Site's own API or feed | The site's existing next-page links |
| Setup | None (built in) | Install the tool once |
Native infinite scroll only exists where a site chooses to build it. An auto pager gives you the same continuous experience on sites that still use traditional pagination — which is most of the web.
What it's good for
The endless page pattern fits any task where you're consuming a long sequence of similar items:
- Binge-reading — news sites, long articles, and forum threads that span dozens of pages.
- Galleries — image sites and portfolios where you want to keep scrolling without interruption.
- Product browsing — working through page after page of listings while comparison shopping.
If you regularly find yourself clicking "Next" every few seconds, an auto pager removes that friction with a one-time install and no per-site configuration in most cases.