Download E-Hentai archive as zip file
Download E-Hentai archive as zip file :package:
| Browser | GreaseMonkey | Tampermonkey | Violentmonkey |
|---|---|---|---|
| Firefox (56-) | 3.2 beta2+ | ||
| Firefox (57+) | 4.1 beta5+ | 4.0.5054+ | 2.8.18+ |
| Chrome | 3.5.3630+ | 2.2.6+ | |
| Chrome (133+) | 5.0.0+ (5) | Incompatible (6) | |
| Opera (15+) | 3.5.3630+ | 2.1.10+ | |
| Safari (10.1+) (1) | 4.3.5421+ | ||
| Edge (18-) (2) | 4.2.5284+ | ||
| Edge (79+) | 4.10.6111+ | 2.12.8+ | |
| Edge (133+) | 5.0.0+ (5) | ||
| Maxthon | 2.1.10+ | ||
| Yandex Browser for Android (3) | 4.2.5291+ | 2.2.6+ | |
| Kiwi Browser (3) | 4.11+ | 2.12.8+ | |
| Firefox for Android (68-)(3) | Incompatible | Incompatible | 2.12.8+ |
| Firefox Nightly for Android (85+) (3)(4) | Incompatible | 4.11.6120+ | 2.12.8+ |
(1) You must upgrade your Windows 10 to 14393 which supports Edge extension.
(2) You must upgrade your macOS to 10.12.4 which supportsdownloadattribute of<a>tag.
(3) It's not a good idea to use it on mobile with limited RAM, but it can work, so it's up to you.
(4) Firefox Nightly user requires to follow this steps to install extensions not in default list.
(5) Chrome with forcing Manifest v3 Extension (probably 133+) requires to enable Developer Mode to load userscript, and Chrome 138+ may require to enable Allow User Scripts permission. Make sure to follow this steps or the script will not load.
(6) Chrome with forcing Manifest v3 Extension (probably 133+) requires to enable Manifest V2 extension to load extension by enablingchrome://flags/#allow-legacy-mv2-extensions, but it may not working anymore since 139+.
Tips:
This script won't download archive from E-Hentai archive download page, so it won't spend your GPs or credits. It will fetch all the pages of the gallery and get their images' URL. Then script will use GM_xmlhttpRequest API (in order to cross origin) to download them. After that, it will package them to a Zip file with JSZip and give it to you with FileSaver.js.
Here are some other compatible information (and some of them are backed to around 10 years ago), which is not important.
GM_xhr.response content (transfers String to ArrayBuffer everytime), so it'll stuck for 1~3 seconds or more after downloaded image (depend on your device). If you are using Microsoft Edge, you may often see the working tab is stuck, saying it's not responding. Just let it go and do nothing. And if you are using Firefox, it's better to use GreaseMonkey from this sidehath.network domain to access images, and it's now listed in @connect, so you're not needed to set this with latest Tampermonkey.GM_xhr cannot handle large content, so it's not supported.The script will store ALL the data in RAM, not in HDD. This will increase the memory usage of current tab process. So if you don't have enough RAM, or the archive is too large (see file size limit section), please pay attention to your memory usage, or try other download tools.
"Out of memory" problem is the most limitaion of the script (in fact, all the sections of "Warning And Limitation" are about RAM problem, and here is also a specific out of memory tag to label all related issues). If you get an error like out of memory, see solution here. And if you usually have the problem, try other tools.
To help us debug, the script will output some logs into console (F12 -> Console). If you find a bug, you can keep opening devtools to see and copy the logs. But note that it may increase memory usage and reduce running efficiency. So don't open console only if you want to see the output logs.
(This part is a bit long, you can just read the table)
Different browsers have different maximum file size limits. Here is a table to show the maximum size the supported browser can handle.
| Browser | Maximum Size |
|---|---|
| Chrome 56- | 500 MB |
| Chrome 57+ | 2 GB or (total RAM / 5) |
| Chrome (with File System) | 1 GB / > 2GB (with 1.33+) |
| Firefox | 2 GB |
| Opera 15+ | Same as Chrome |
| Edge 18- | ? |
| Edge 79+ | Same as Chrome |
| Safari 10.1+ | ? |
| Maxthon | ? |
For Google Chrome 56-, it has a hard limit at 500 MB on Blob Storage for years. That means all the files that in storage cannot be larger than 500MB in total, and if the storage doesn't have enough free space to save the next file, it'll return a fake Blob instance silently without any errors. Also for Chrome 45-, Blob.close() didn't implement (and it's depreated so no browser supports it now), so we cannot free those used Blob immediately at that time, only to pary the browser will GC them ASAP (and for most of time it didn't work). That's why here is a wiki page to help you work around this.
So to help you save larger files, the script can save the Zip file into File System, a deprecated HTML5 API but still works on Chrome (as it's Chrome introduce the standard first). With the API, you can handle larger file because the file data will be writing to your disk instead of storing in Blob Storage, its limit is also big enough (10% of your disk free storage, 15 GB in maximum). But when processing the file, the files are still keeping in RAM, and if datas are too large, Chrome may also cannot handle them. From my test the maximum limit maybe 1 GB if you only have 8 GB RAM, but it may also depends on your device. If you have enough RAM, you can download a gallery larger than 2 GB with 1.33+.
Chrome 57+ fixes the 500 MB limit of Blob Storage, so that it can handler larger files i
No open issues yet, or sync has not completed.