# E-Hentai Downloader's newest release tag is from 2015 and its browser matrix has a column of Incompatible > A Tampermonkey userscript that walks a gallery page by page, fetches image URLs with GM_xmlhttpRequest and zips them with JSZip, with hard browser ceilings at 2 GB and 4 GB and an author who recommends torrents instead. GPL-3.0, last commit 2026-05-12. **ccloli/E-Hentai-Downloader** — Download E-Hentai archive as zip file - Repository: https://github.com/ccloli/E-Hentai-Downloader - Stars: 2,439 · Forks: 148 - Language: JavaScript - License: GPL-3.0 - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/ccloli-e-hentai-downloader ## It reads the gallery instead of the archive endpoint The mechanism is stated in four steps. The script does not download an archive from the E-Hentai archive download page, so it does not spend gallery points or credits. Instead it fetches all the pages of the gallery and collects the image URLs from them, then downloads the images and packages them into a zip, which it then hands to the browser as a download. Three libraries do the work. `GM_xmlhttpRequest` is what makes the image fetches possible at all, since the images live on a different origin from the gallery page and a normal page script would be blocked by the same-origin policy. JSZip builds the archive in the browser, and FileSaver.js turns the resulting blob into a file save. Doing it this way is why the tool has the shape it has. No archive endpoint means no points spent, but also no server-side repackaging, which puts the zip assembly and the whole memory budget on the machine running the browser. ## Two gigabytes of blob and four gigabytes of zip are the real limits The failure modes are named with the errors they produce: an out of memory message on Firefox, and a file not found message on Chrome. The suggested remedy is the same in both cases, keep each archive under 500 MB by setting the Pages Range option, and either enable File System on Chrome or add memory to the machine. Underneath that sits a pair of ceilings the script cannot raise. There is a 2 GB limit on a browser Blob object, and a 4 GB limit on a zip file itself. Those are properties of the platform, so a gallery that would produce a six gigabyte result cannot be assembled in a tab no matter how much RAM is behind it. For those cases, and for stability in general, the documentation points at gallery-dl as another tool. That is the honest boundary of this project: inside the browser size limits it is convenient, and outside them the recommendation is to stop using the browser. ## The release list has one entry and it is eleven years old There is a single tagged release, v1.17.4, published on 2015-09-17, and its title is Last version to support single-thread download. Read as a changelog entry rather than a release note, it says the project moved to concurrent downloads after that point and never tagged a version for anything since. The commit history has not stopped. The last push to the repository is dated 2026-05-12, more than a decade after the tag. So the artifact people install from GreasyFork or from the raw file on GitHub is, in the general case, built from a decade of commits that carry no version number. That is the ordinary state of a userscript project rather than a scandal, but it does mean the compatibility table below the install links is a better guide to whether the script still loads than any version number is. The table changes when browsers change, and it is the part of the page carrying dated browser versions. ## The browser table is thirteen rows of moving parts The required-environment table crosses three userscript managers, GreaseMonkey, Tampermonkey and Violentmonkey, against thirteen browser rows, and most cells are a minimum version rather than a yes. Firefox splits at 57, with GreaseMonkey 3.2 beta2 for the older line and 4.1 beta5 for the newer one. Chrome and Edge both have a second row for version 133 and later, which exists because of Manifest v3. That second row is where the footnotes do the work. Tampermonkey 5.0.0+ works on Chrome 133+ only if Developer Mode is enabled, and Chrome 138+ may also require the Allow User Scripts permission, with the script simply not loading otherwise. Violentmonkey on the same row is marked Incompatible. The note for the Manifest v2 route says to enable `chrome://flags/#allow-legacy-mv2-extensions`, and adds that it may not be working anymore since 139+. Two other cells are honest dead ends: on Firefox for Android 68 and earlier, both GreaseMonkey and Tampermonkey are Incompatible, and the mobile footnote says it is not a good idea to use on a phone with limited RAM even where it does work. Kiwi Browser and Yandex for Android are listed, with a version column and nothing else to explain. ## A page of workarounds with most of them struck through The bottom of the README is a compatibility log, and it opens by saying some of it is backed to around ten years ago and is not important. Most of what follows is struck through. The main entry describes Tampermonkey giving `GM_xhr.response` content by a dirty route, transferring a String to an ArrayBuffer every time, which stuck the script for one to three seconds or more after each downloaded image depending on the device. On Microsoft Edge the symptom was a working tab that reported itself as not responding. That entry is struck through and marked fixed in Tampermonkey 4.12.6125, with the upstream issue linked. The next entry begins describing a problem with the latest Tampermonkey and stops mid-sentence. That is the shape of the whole section: a list of browser and extension bugs that were once the project's main support burden, kept for reference, mostly retired, and not fully maintained. ## The author recommends torrents and the official archiver instead The warning is the longest paragraph in the README and it argues against the tool. The script is not provided by the official, automated scripts and tools are not encouraged, and use may trigger a throttle limit or an account ban. It asks readers not to bother anyone in the site forums with script-related issues and to use it at their own risk. The recommendation that follows points elsewhere. For a large gallery, use torrents if they are available, or use the official archiver for a better and more stable experience, and the cost should be close to what the script costs anyway once the gallery is old enough to use gallery points. The torrent paragraph gives the reasons: a stable download, bonus content that is mostly in cosplay galleries, gallery points and credit earned rather than spent, and less pressure on the original servers. Both the viewing limits page and the gallery-dl link are pointed at from the same section, so a reader who hits a ceiling has three documented exits and one of them is not this script. ## Conclusion This is a reasonable tool for one gallery at a time on a desktop with plenty of memory, and a poor one for anything large. Before you rely on it, check three things: whether your browser and userscript manager still appear in the compatibility table at all, since the newest entry is Chrome 133+ and the Manifest v2 escape hatch is described as possibly dead since 139+, whether your gallery has a torrent, which the author recommends over the script, and how big the result will get, because the 2 GB blob ceiling and the 4 GB zip ceiling are properties of the browser and not of the script. The author is explicit that the script is not official, that automated tools may be throttled or banned, and that large galleries are better left to torrents or the official archiver. The repository has one release, tagged in 2015, and the last commit is dated 2026-05-12. ## FAQ ### Does E-Hentai Downloader cost gallery points or credits? No. It does not download from the E-Hentai archive download page, which is what would spend gallery points or credits. It fetches every page of the gallery, collects the image URLs, downloads them with GM_xmlhttpRequest and packs them into a zip with JSZip and FileSaver.js. ### Why does E-Hentai Downloader fail with an out of memory error or a file not found message? On Firefox the symptom is an out of memory message and on Chrome it is a file not found message. The suggested fix is to set Pages Range so each zip stays under 500 MB, and to enable File System on Chrome or add memory. There are also hard platform limits of 2 GB on a browser Blob and 4 GB on a zip file, and gallery-dl is suggested for those cases. ### Which browsers can run E-Hentai Downloader? The compatibility table crosses GreaseMonkey, Tampermonkey and Violentmonkey against thirteen browser rows with minimum versions. On Chrome and Edge 133 and later, Tampermonkey 5.0.0+ needs Developer Mode enabled and Chrome 138+ may need the Allow User Scripts permission, while Violentmonkey on that row is marked Incompatible. Firefox for Android 68 and earlier is Incompatible for both GreaseMonkey and Tampermonkey. ### How do I install E-Hentai Downloader? There is no build step. Two links are given: the raw e-hentai-downloader.user.js file on GitHub and the GreasyFork page. The repository root holds LICENSE, README.md, e-hentai-downloader.meta.js, e-hentai-downloader.user.js and a src directory. After installing, open a gallery and use the Download Archive box that the script adds to the page. ### Is it safe to download a large gallery with E-Hentai Downloader? The project says it is not safe. The README states the script is not provided by the official, that automated tools are not encouraged and may trigger a throttle limit or an account ban, and that you should use it at your own risk. For a large gallery it recommends torrents where available, or the official archiver. ## Sources - [ccloli/E-Hentai-Downloader on GitHub](https://github.com/ccloli/E-Hentai-Downloader) - [Issues](https://github.com/ccloli/E-Hentai-Downloader/issues) - [License: GPL-3.0](https://github.com/ccloli/E-Hentai-Downloader/blob/master/LICENSE) - [README](https://github.com/ccloli/E-Hentai-Downloader/blob/master/README.md) - [Releases](https://github.com/ccloli/E-Hentai-Downloader/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ccloli-e-hentai-downloader