# hoothin/UserScripts: A Greasemonkey Script Collection for Pagination, Image Zooming and Content Downloading > hoothin/UserScripts is a monorepo of Tampermonkey and Greasemonkey scripts whose best-known piece is Pagetual, an auto-pager. It is a collection, not a framework, so adoption means picking individual scripts and accepting that the README documents almost nothing. **hoothin/UserScripts** — Greasemonkey scripts ( Pagetual / Picviewer CE+ / DownloadAllContent ) 油猴腳本集 ユーザースクリプト集 - Repository: https://github.com/hoothin/UserScripts - Website: https://greasyfork.org/users/8227-hoothin - Stars: 4,309 · Forks: 598 - Language: JavaScript - License: not declared - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/hoothin-userscripts ## What hoothin/UserScripts actually ships This is a repository of user scripts, not a single application. The top-level directories are the products: Pagetual, SearchJumper, Picviewer CE+, DownloadAllContent, Easy offline, Switch Traditional Chinese and Simplified Chinese, Greasyfork Search with Sleazyfork Results include, Highlight Every Code, MoreSteamRatings, Select All Checkboxes, True URL downloads, HacgGodTurn, JiandanHero, and a long tail of smaller site-specific fixes such as Kill Baidu AD, Kill TieBa AD, T66y tool, Appinn Comment and Bilibili Bangumi Cover. The README is a link list, one line per script, most with a short English description and a Chinese name. The audience is people who already run a userscript manager. Pagetual is described as an auto pager that fetches the next page automatically for infinite scroll. Picviewer CE+ is described as a picture viewing tool that can popup, scale, rotate and batch save pictures. DownloadAllContent is described as a lightweight web scraping script that fetches and downloads main textual content from the current page, with special support for novels. Those three carry most of the repository's weight. The rest range from single-purpose utilities to joke scripts, and several target Chinese-language sites only. Because the unit of adoption is one script, the repository's size is not a feature. You do not install hoothin/UserScripts. You install Pagetual, or you install nothing. ## How a userscript runs, and what that means for this collection A userscript is JavaScript injected into a page by a browser extension such as Tampermonkey, Greasemonkey or Violentmonkey. The script carries a metadata block at the top with keys like @name, @match, @grant and @version. The manager reads that block, decides which URLs the script applies to, and runs the code in that page's context. There is no build step, no package manager and no server. The repository layout reflects this: each top-level folder holds the script source plus, in several cases, a page of its own. The mechanism matters for judging the collection. Pagetual cannot change how a site paginates; it can only fetch the next URL and append the result to the current document, then repeat. That means its reliability is bounded by the target site's markup. When a site changes its list structure or serves content through a client-side router, an auto-pager that parses HTML has less to work with. Picviewer CE+ works the same way in reverse: it scans the page for image elements and wraps them with its own viewer, so its behaviour depends on what the page exposes in the DOM rather than on any cooperation from the site. The @match and @grant lines in each script are the real contract. They determine which origins the script touches and what privileged APIs it is allowed to call. The README does not document them, so the script header is the only reliable source. ## Installing a script from the collection There is no install command in the README. The README points at per-script pages: Pagetual has its own site at pagetual.hoothin.com, SearchJumper at search.hoothin.com, and the repository links to a Greasy Fork user page at greasyfork.org/users/8227-hoothin. Those pages are where a browser with a userscript manager installed can pick up a script. The README does not describe a manual installation procedure, so the steps below are the generic ones for any userscript manager, not instructions copied from this project. First confirm a manager is present. In Tampermonkey the dashboard is the entry point: ```bash # No CLI install exists for this repository. # Open the userscript manager dashboard in the browser instead. # Tampermonkey: chrome-extension://dhdgffkkebhmkfjojejmpbldmpobfkfo/options.html ``` Second, open the script page and let the manager intercept it. Tampermonkey shows an install screen with the script's metadata and an Install button. The metadata block is what you should read before clicking, because it names the sites the script will run on: ```js // ==UserScript== // @name Pagetual // @namespace https://pagetual.hoothin.com/ // @match *://*/* // @grant none // ==/UserScript== ``` The keys above are the standard userscript metadata keys; the values shown are illustrative of the shape, and the exact @match and @grant lines are in the script file in the Pagetual folder. After installation the script appears in the manager's installed list, and its toggle controls whether it runs at all. Third, verify on a real page. The README gives no troubleshooting section, so the practical check is the manager's own indicator: open a paginated article or gallery, scroll to the bottom, and see whether the script's badge or menu entry appears. If nothing happens, the manager's console for that tab is the only diagnostic this repository offers. ## Pagetual, Picviewer CE+ and DownloadAllContent compared The three headline scripts solve different problems and fail differently. Pagetual is the auto-pager. Its promise is that you stop clicking Next. The constraint is that it re-implements pagination per site, so coverage is a matter of how many site rules exist rather than of any general algorithm. On a site whose next-page link is a plain anchor, appending the next document is straightforward. On a site that loads results through an API call triggered by scroll position, the script has to detect and replay that call, which is a different and more fragile problem. Nothing in the README states how many sites are covered. Picviewer CE+ is a viewer. It enlarges, rotates and batch-saves images found on the page. This is the least invasive of the three because it does not need to fetch anything from the network; it operates on images already loaded. Its practical limit is the page's own loading behaviour. If a gallery lazy-loads thumbnails only when they enter the viewport, the viewer sees only what has already been requested. DownloadAllContent is the odd one out. It extracts main textual content and saves it, with explicit support for novels. Text extraction is a readability problem, and readability heuristics misjudge pages that interleave comments, chapter navigation or advertisements with the body. The README calls it lightweight and does not describe its extraction rules, so the honest expectation is that it works well on serialised fiction pages and less predictably elsewhere. Pick by task. Do not install all three and assume they compose cleanly; each manipulates the same document. ## Where the collection falls short The README is a link list. It does not document configuration, per-script options, browser compatibility beyond a Chrome, Firefox and Edge badge, or what happens when a script breaks. For a collection this size that is the main limitation, and it is a documentation problem rather than a code problem. The licence is the second gap. The README carries an MIT badge linking to the repository, but the repository metadata reports the licence as unknown. Those two signals disagree, and the scripts themselves may carry their own headers. Anyone planning to fork, redistribute or vendor a script into a product should read the header in the script file rather than trusting the badge. Third, several scripts are site-specific in a way that makes them useless outside their target. Kill Baidu AD, Kill TieBa AD, Appinn Comment, T66y tool, JiandanHero and Bilibili Bangumi Cover address particular Chinese-language sites. They are not general-purpose ad blockers or readers, and treating them as such will disappoint. Finally, userscript collections age with their targets. This repository's last push was on 2026-09-22, so it is current, but that says nothing about any individual script's coverage of any individual site. A script can be freshly pushed and still fail on the site you care about. ## Alternatives and how they differ If you want auto-paging and nothing else, AutoPagerize is the obvious comparison. It is built around a shared set of site rules that the community maintains, so its behaviour is defined by a data file rather than by code shipped in one repository. Pagetual, by contrast, keeps its logic inside the script and has its own site at pagetual.hoothin.com. The practical difference is where you go when a site breaks: AutoPagerize users contribute a rule to the shared set, while Pagetual users wait for the script to be updated or write their own handling. If you want image viewing, dedicated extensions such as Imagus or the browser's own zoom behaviour cover part of the ground. Picviewer CE+ differs by adding batch saving to the same interface, which is the reason to choose it over a pure hover-zoom tool. If you want text extraction, a reader-mode implementation built into the browser does the same job without a userscript manager. DownloadAllContent's reason to exist is the novel case, where chapter-by-chapter saving matters more than a clean reading view. The general alternative is to install nothing and use extensions. Extensions are reviewed by the browser vendor and updated through the store; userscripts are updated by whoever maintains the script. That trade is the whole decision. ## Maintenance cost and licence implications The repository was last pushed on 2026-09-22, so it is not dormant. There are no releases recorded, which fits the userscript model: versioning lives in each script's @version field, and distribution happens through Greasy Fork or the project's own sites rather than through tagged releases. Upgrading therefore means re-installing or letting the manager check for a new version, not running a package manager. The cost of adoption is monitoring, and it is per script. A site redesign can break Pagetual on that site while leaving the rest of the collection untouched. Because the README documents no compatibility matrix, you will discover breakage by using the script, not by reading about it. On licensing, the README shows an MIT badge and the repository metadata reports the licence as unknown. MIT permits reuse with attribution and without warranty, but a badge is not a licence file, and no LICENSE file appears at the repository root. If you intend to redistribute a script, check the header of that specific script and, if the terms are unclear, contact the maintainer through the Gmail address listed in the README. This is a description of what the repository shows, not legal advice. ## Conclusion Adopt individual scripts from hoothin/UserScripts if you already run Tampermonkey or Greasemonkey and want Pagetual's auto-paging or Picviewer CE+'s image handling on sites you do not control. Do not adopt it as a library or expect a documented API: the repository is a folder-per-script collection, the README lists names and links, and the licence badge says MIT while GitHub reports the licence as unknown, so confirm the terms in the script header before redistributing anything. Before installing, open the script's folder, read its metadata block, and check which hosts it matches. ## FAQ ### What is hoothin/UserScripts? It is a GitHub repository collecting Greasemonkey and Tampermonkey user scripts, with Pagetual, Picviewer CE+ and DownloadAllContent as the most prominent ones. The README presents it as a link list of individual scripts rather than a single application. ### How do I allow user scripts in Chrome for hoothin/UserScripts? The README does not give install steps. It links to per-script pages such as pagetual.hoothin.com and to a Greasy Fork user page, which a browser with a userscript manager installed can use to install a script. ### How do I use the scripts in hoothin/UserScripts? Each script is installed into a userscript manager and then runs automatically on the pages its metadata block matches. The README does not document configuration options, so the script header is the source for which sites it applies to. ### How do I use hoothin/UserScripts in Safari? The README shows a support badge for Chrome, Firefox and Edge only. It does not mention Safari, iOS or Android, so no claim can be made about those platforms from the repository documentation. ### How do I install hoothin/UserScripts on iOS? The README lists no iOS installation path and its support badge names Chrome, Firefox and Edge. The only distribution points it gives are the per-script sites and the Greasy Fork user page. ## Sources - [hoothin/UserScripts on GitHub](https://github.com/hoothin/UserScripts) - [Issues](https://github.com/hoothin/UserScripts/issues) - [Project website](https://greasyfork.org/users/8227-hoothin) - [README](https://github.com/hoothin/UserScripts/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/hoothin-userscripts