EHWiki - User contributions [en]

Technical Issues

2026-08-27T19:00:17Z

Kagoraphobia: /* Archives */

This article is meant to assist users of E-Hentai with any technical problems that they may have.

Site status can be checked [https://forums.e-hentai.org/index.php?showtopic=274947 here].

==Universal==
<div id="503"></div>
*'''"Error 503 - Service Unavailable"'''
**The site is under maintenance or is having server issues. Please wait and try again later.

<div id="IE"></div><div id="ie"></div><div id="browser"></div><div id="Browser"></div>
*'''The site is stuck at a static resolution!'''
*'''The site looks / behaves strangely on Internet Explorer!'''
**Only [https://www.w3schools.com/css/css_grid.asp modern browsers] are recommended for this site. Support cannot be given for [https://letsencrypt.org/docs/certificate-compatibility/ other / older browsers].

<div id="blank"></div><div id="Blank"></div><div id="DNS"></div><div id="dns"></div>
*'''I get a blank page when I try to access the site!'''
**Make sure you are connecting via HTTPS, not HTTP.
**Clear cache and cookies relating to the site. Relogging may be required afterwards.
**Disable any [[#Common Problematic Software|Common Problematic Software]] and try again.
**Disable any anti-virus, firewall, or other software that is capable of blocking traffic that runs in the background and try again.
**[https://documentation.cpanel.net/display/CKB/How+To+Clear+Your+DNS+Cache Flush your DNS cache], restart your browser, and try again.
**Check your region's [https://www.cloudflarestatus.com/ CloudFlare status].
**Go into a command prompt and use "''nslookup e-hentai.org''". If there are any addresses in the results then it is not a DNS issue. Otherwise consider using a different DNS provider such as [https://developers.google.com/speed/public-dns/docs/using Google] or [https://1.1.1.1/#setup-instructions CloudFlare].
***You may also try reaching the site manually through one of its [[IPs]] instead of a domain name.
**Use a proxy or VPN to access the site. If this fails then it is an issue with your ISP.
***[[Image:Tor.png]] It is recommended not to access the site through the [https://en.wikipedia.org/wiki/Tor_%28anonymity_network%29 Tor network] as numerous exit nodes have been abused and thus banned or had their access severely limited.
**[[Image:Firefox.png]] Firefox 55+: disable first-party isolation (''about:config -> set "privacy.firstparty.isolate" to "false"'').
** [[Image:Firefox.png]] Firefox 73+: disable obfuscating host address (''about:config -> set "media.peerconnection.ice.obfuscate_host_addresses" to "false"'').
**In order to provide diagnostics on your ability to access the site please do the following:
***[[Image:WindowsOS.png]] Go into a command prompt and use "''pathping e-hentai.org''". [[Image:MacOS.png]] For Mac OS use "''traceroute e-hentai.org''". Paste the results in a forum post.
***[[Image:Firefox.png]] Press {{Keypress|Ctrl}}+{{Keypress|⇧Shift}}+{{Keypress|K}} in Firefox. Attempt to visit e-hentai.org through the address bar. Paste the contents of the Firefox Console lines starting with "GET" in a forum post.
***[[Image:Chrome.png]] Press {{Keypress|Ctrl}}+{{Keypress|⇧Shift}}+{{Keypress|C}} in Chrome and switch to the "Network" view. Attempt to visit e-hentai.org through the address bar. Document all results of the "Status" column in a forum post.

*'''"Page load has been aborted due to a fatal error. A report has been dispatched to site staff. Please try again later."'''
**There is a server-side error. Please try again later.

*'''"The site is currently in Read Only Mode. This page is therefore not available.'''"
*'''"The site is currently in Read Only/Failover Mode. Some functionality will not be available. Details may be available on [[Twitter]].'''"
**The front-end servers are under read-only mode and will not allow users to take any actions that involve their user data (Accessing [[My Home]], [[Archives]], [[Tagging]], etc.)

==Account==
*<span id="Password"></span>'''I forgot my password!'''
*<span id="Username"></span>'''I forgot my username!'''
**Fill in the [https://forums.e-hentai.org/index.php?act=Reg&CODE=10 Lost Password Form]. This can be used to recover usernames as well. You will need your username or e-mail address to do this. These e-mails are sent instantly.
***Mail providers such as [https://login.live.com/ Hotmail] are known to be poor at receiving recovery e-mails; check your junk/spam folder.
**Make sure you are using your ''account'' username and not your ''display'' name. The registration process allows you to pick both a display name (used on forums) and an account username (used for logins and not readily visible to others).
***You cannot use your email address in place of your username to log in, unless your username was set as your email address.
***If you have ever made a gallery [[comment]] or a [[forum]] post attempt to search for it using any keywords that you recall using. If you have uploaded a [[gallery]] attempt to [[search]] for it.
**You may also email support@e-hentai.org from the registered email address to request a password reset.
**<span style="color:#a56b0d">"''If you're not logged on, you don't know your password, and you can't access your recovery email, you can't recover the account''" - Tenboro</span>

*<span id="lost email"></span>'''I can't access the e-mail address I used to register!'''
**Without the password, an active session, or access to the recovery email address, your account [https://forums.e-hentai.org/index.php?act=findpost&pid=4811225 '''CANNOT'''] be recovered.
***If you still have access to an active session, you may [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] with a new recovery email address to recover your account. If forum access isn't working, send an email with the contents of your ipb_pass_hash cookie to support AT e-hentai DOT org.

<div id="delete"></div><div id="Delete"></div>
*'''I want to delete my account!'''
**This action cannot be requested. Just stop using your account.

*'''I want to change my e-mail!'''
**If you are logged in you may do so [https://forums.e-hentai.org/index.php?act=UserCP&CODE=08 here].

<div id="name"></div><div id="Name"></div>
*'''I want to change my display name!'''
**[[Stars#Bronze|Donators]] can change their display name once every 365 days. This function can be found by clicking [https://forums.e-hentai.org/index.php?act=UserCP&CODE=dname_start Change Display Name] under [https://forums.e-hentai.org/index.php?act=UserCP&CODE=00 My Controls] on the forum.
**Non-donators can no longer change their display name due to various abuse of this function. If you used your actual real name or email address by mistake, you may appeal for a name change by [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PMing Tenboro].
***Provide both an acceptable justification and the requested display name in your PM. Requests that fail to provide either will be ignored. This can take a couple of days; do not send multiple PMs or contact other moderators about this.
***Having one's name changed by the administrator counts as having used their yearly change.
**The display name will change for all system readouts, but there can be up to a 24 hour delay before all readouts use the new name. Forum edits, quotes and similar retain the display name that was used at the time.
**Your log-in username will not change and cannot be changed.

*'''I changed my username but the new name only shows up on the forums / galleries!'''
**This is due to database caching. It takes up to 24 hours for all caches to be refreshed.

*'''Certain characters in my username are not being permitted!'''
**Database sanitization. Suspicious usernames also potentially flag users as attempting to scam or impersonate other users or to abuse the system in some way. This may lead to a permanent [[ban]].

*'''I want to use more than 1 account!'''
**You may only have 1 active account. <span style="color:red">Multi-accounting for any reason will result in a [[ban]].</span>

*<span id="lockdown"></span>'''My account entered a lockdown!'''
**Accounts will enter a 24-hour security lockdown under certain conditions, including changing passwords. This disables access to [[MoogleMail]], the [[Bazaar|Equipment and Item Shop]], [[The Market]], the [[Shrine]], and the [[GP Exchange]]/[[Hath Exchange]] functions. It also disables the Salvage and Reforge options in the [[Forge]].

*'''"This page is currently not available, as your account has been suspended"'''
**You have been banned, likely for account sharing / multi-accounting.

===Registering===
*'''"Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information. The error returned was: Sorry, you are not permitted to use this board"'''
**The IP you are using is banned.

*<span id="Missing captcha">'''The CAPTCHA is missing!'''
**Disable any software that blocks ads or scripts.
**Try a different browser.

*'''When I try to register nothing happens!'''
**[[Image:Chrome.png]] If using Chrome disable incognito mode.
**[[Image:Tor.png]] The use of [https://www.torproject.org/ Tor] when registering is strictly prohibited.
**Try without special characters such as "<", "}", "/" etc. in the username/display name.

*'''<span id="validation">I'm not receiving a validation e-mail!'''
**These are not actually sent out. Accounts may be used right away.

*"'''<span id="Invalid captcha"></span>The registration code did not match the one displayed, a new code has been generated, please try again'''"
**Disable any software that blocks ads or scripts.
**Try without incognito/private windows.
***Disable any cookie blocking/modifying software.
***Disable any JavaScript blocking software.
**If using a VPN/Proxy, disable it.

==[[E-Hentai Galleries]]==
<div id="images"></div><div id="image"></div><div id="Images"></div>
*'''Images are not loading.'''
**Check your browser settings:
***Make sure you are using a [[#browser|modern browser]].
***Disable any proxies, add-ons, or scripts. <span style="color:red">'''There is no 3rd party software needed to access ANYTHING in E-Hentai or its related domains. Anything claiming otherwise may be an attempt to intercept your account credentials.'''</span>
***Due to the [[Hentai@Home]] system images require cross network traffic:
****[[Image:Firefox.png]] [https://forums.e-hentai.org/index.php?showtopic=201984 Firefox 51-57]: disable HSTS priming (''"security.mixed_content.send_hsts_priming"'' and ''"security.mixed_content.use_hsts"'' to ''"false"'').<br>Firefox 65+: If content blocking cannot be disabled for the site use the Strict or Custom setting (''"browser.contentblocking.control-center.ui.showAllowedLabels"'' to ''"true"'').
****[[Image:Opera.png]] Opera: enable Cross Network Navigation (''opera:config#Network|AllowCrossNetworkNavigation'').
****For [https://noscript.net/ NoScript] disable ABE or enable local resources to be accessed by "e-hentai.org".

**Try the "Click here if the image fails loading" link. This will attempt to pull the image from a new [[H@H]] client.
**Select "Default port clients only" in your [[My Settings]] page; this will only utilize [[H@H]] clients that use port 443.
**[[Donator]]s may append "?nl=1" to the end of the URL. This bypasses using the [[H@H]] cluster for that image. This can be permanently enabled via the [[My Settings]] page but this can quickly use up your bandwidth limit.
**Turn off any [[#Common Problematic Software|problematic software]] which may block E-H traffic.
*'''Images sometimes take a long time to load.'''
**If your ISP does not support IPv6, your browser may try to use IPv6 anyway, causing a 5+ second stall+timeout per image load.
***Firefox: Disable IPv6 by opening about:config then set network.dns.disableIPv6 to true
***Chrome: Disable IPv6 by starting Chrome with --disable-ipv6
*'''Thumbnails are not loading.'''
**Many adblockers have subscription-based rules that include an '''/ad/''' or '''^ad^''' filtering rule. This will catch '''all''' hexadecimal static ranges with /ad/ in them (e.g. /{00..ff}/ad/ or /ad/{00..ff}).
***Whitelist '''ehgt.org''' for the '''image''' content type or disable adblockers for the site.
***Disable any scripts/add-ons such as RequestPolicy and Smart Referrer.
*'''The image size is locked at 1280x or 1920x even though I have selected a higher resolution in the settings!'''
**You may have triggered the site's anti-bot mechanism. This is likely due to the use of a heavily-abused VPN/proxy node.
***Try switching your IP address may resolve this issue.
***[[Donators]] will not be affected by this limit.
**New 2560x resamples are no longer generated for galleries older than one year; 1920x resamples will be used instead.
***They can still be used on older galleries if they were already created.
<div id="509"></div><div id="509"></div>
*'''"Error 509 - Bandwidth Exceeded"'''
*'''"Error loading image: Could not get dispatch for image"'''
**<span id="image limit">You have viewed too many images. Either wait a few hours, [[My Home#Overview|reset the limit]] with [[GP]], or purchase the "More Pages" [[Hath Perk]].
**If you are on a shared connection consider using a proxy to browse E-Hentai.
**These limits are based only on IP address, not by account. The exception is for [[donators]] with [[stars]], wherein IPs are ignored.
<div id="414"></div>
*'''"Error 414 - Request-URI Too Large"'''
**Occurs if the URL being accessed is too long, often from advanced [[Searching|searches]].
***Depending on your search you can safely remove any non-relevant search parameters contained within the URL.
**You have performed a [[Searching#File_Search|file search]] that found too many results.
*'''"Please wait a bit longer between each file search."'''
**You have tried to do another [[Searching#File_Search|file search]] too quickly after the previous one. Wait 10 seconds before trying again.

*'''"The connection to the server was canceled during the page load."'''
**Your connection was automatically blocked for making too many connections.
**Wait for the ban to expire.

*'''<span id="image limit vpn">"I have used up my image quota even though I haven't been browsing."'''
**You are using a shared IP. This may be because of a proxy/VPN, or your ISP has recycled a recently used IP to you.
**A $20 [[donation]] or the "More Pages" [[Hath Perk]] ties the image limits to your account instead of your IP.

*'''"Content Warning - This gallery has been flagged as Offensive For Everyone. Due to its content, it should not be viewed by anyone. (And if you choose to ignore this warning, you lose all rights to complain about it in the future.)'''"
**This indicates that the gallery has been [[tagged]] with [[guro]], [[snuff]], or [[scat]]. You may choose to view the gallery, no longer receive these warnings ("Never Warn Me Again"), or go to the gallery front page.
**To re-enable this warning again simply delete the "nw" cookie.

*'''Thumbnails appear with inverted colors.'''
**This is a rare glitch which resolves itself over time. The actual images should appear as normal when viewed.

*'''"The proxy server received an invalid response from an upstream server."'''
**Check if you are on an ISP-level proxy [https://www.toolsvoid.com/proxy-test/ here]. Reverse proxies cannot be detected with tools like these; you may need to ask your ISP.
**Check if your browser settings have a proxy enabled.

<div id="fast"></div><div id="Fast"></div>
*'''"You are opening pages too fast, thus placing a heavy load on the server. Back down, or your IP address will be automatically banned."'''
**[[Image:Chrome.png]] This may be triggered by prefetching in Chrome; uncheck ''Settings -> Show advanced settings -> Privacy -> "Use a prediction service to load pages more quickly."''
**This may be triggered by add-ons/scripts that organize/update bookmarks to galleries automatically; such actions may induce page loads.

<div id="Ban"></div><div id="Banned"></div>
*'''"Your IP address has been temporarily banned for excessive pageloads which indicates that you are using automated mirroring/harvesting software."'''
**You have opened too many pages at once or you have used software that downloaded too many images from the site simultaneously.
***Wait until the ban expires.
**If you are certain that you have not performed excessive page loads your IP may be in use by other people.
***A $20 [[donation]] makes your account ignore any IP restrictions caused by other users.

*'''"Key missing, or incorrect key provided."'''
**The URL you are visiting is incorrect.

*'''When I save an image I only get blank.gif!'''
**The image did not have enough time to load. The blank.gif is a placeholder shown while waiting for image retrieval.

*'''I cannot rate a gallery!'''
**Sometimes the [[rating]] UI does not respond due to server congestion, try again later.
**You cannot rate your own galleries.
**You may be banned from [[rating]] galleries. You will receive a pop-up notification if this is the case.

*'''I am being redirected to other sites!'''
**Make sure you typed the URL correctly or that the link you followed has it spelled correctly.
**Check with your ISP about any blocked or redirected traffic.
**Any countries / territories noted [[:File:Countries_Blocking_E-Hentai.png|here]] are known to block E-Hentai.org.
**Check for malware such as browser hijacks.

<div id="Korea"></div><div id="korea"></div>
*'''I am being redirected to "warning.or.kr"!'''
**You live in South Korea. Move.
**The use of a proxy may work but be wary of the legalities in that jurisdiction.

<div id="Russia"></div><div id="russia"></div>
*'''"This content is not available in Russia."'''
**You live in Russia. Move.
**The use of a proxy may work but be wary of the legalities in that jurisdiction.

<div id="UK"></div><div id="uk"></div>
*'''"This content is not available in the United Kingdom."'''
**You live in the UK. Move.
**If you live in the UK, you can and should complain to your local MP [https://www.parliament.uk/get-involved/contact-an-mp-or-lord/contact-your-mp/ here].

<div id="Australia"></div><div id="australia"></div>
*'''"This content is not available in Australia."'''
**You live in Australia. Move.
**If you live in Australia, you can and should complain to your local Senator [https://www.aph.gov.au/Senators_and_Members/Contacting_Senators_and_Members here].

<div id="acl"></div><div id="ACL"></div>
*'''"Tool does not exist, or you have insufficient access to use it.'''"
*'''"You do not have access to this function.'''"
**You are not on the Access Control List of the tool you are attempting to use.
***For most users the [[Gallery_Tagging#Tag_History|tag history tool]] can only be used to check one's ''own'' tagging history.
***Please contact a [[E-Hentai Janitor|moderator]] if you wish to have something done via said tool.
**This may also happen if you are using outdated URLs for the [[expunge]]/[[rename]] tracker (e.g., tools.php). Update your bookmarked links with the ones displayed on the [https://forums.e-hentai.org/ forums].

*'''"Gallery not found. If you just added this gallery, you may have to wait a short while before it becomes available. It might also have been reverted to its previous version."'''
**The gallery you are attempting to visit is not yet fully integrated into the server. If this persists the gallery link is faulty.
**Alternatively, the gallery was reverted to a previous state, check its parent gallery.

*'''Gallery [[HentaiVerse Hotkeys|hotkeys]] aren't working!'''
**Make sure you have JavaScript enabled.

<div id="eeenope"></div><div id="nope"></div><div id="Nope"></div>
*'''"eeenope"'''
**You do not have access to the [[Multi-Page Viewer]]. Change the URL.

*'''"The connection to the server was canceled during the page load."'''
**Your IP was automatically blocked for opening a huge amount of connections.

<div id="KeepTrying"></div><div id="keeptrying"></div><div id="Keeptrying"></div><div id="Keep"></div><div id="keep"></div>
*'''"Keep trying."'''
**You are trying to access an image page but have an invalid page ID, gallery ID, or file ID.

*'''I cannot see new galleries until ~15 minutes after they have been published!'''
**This is intentional for non-registered visitors.
**Register an account to see these galleries sooner.

*'''<span id="veto expunge">"New expunges for this gallery can currently only be started by trusted users."'''
**The gallery chain was previously de-expunged and new expunges can only be started by [[Expunging#Limits|selected users]].
**If you believe that the gallery should be expunged, please make a post in [https://forums.e-hentai.org/index.php?showtopic=242797 this thread].

*'''I cannot file an appeal petition on this gallery!'''
**If the expunge petition went active more than 7 days ago, a new appeal petition can only be created by [[Expunging#Limits|selected users]].
**If you believe that the gallery should be de-expunged, please make a post in [https://forums.e-hentai.org/index.php?showtopic=242797 this thread].

*'''"This gallery is expunged, but no active expunge petitions were found. This usually means it was administratively expunged, which cannot be appealed here."'''
**No user-created [[Expunging#Appeal_an_Incorrect_Expunge|appeal]] petition is allowed for the gallery. If you believe that the gallery has been expunged incorrectly, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=242797 here].

*'''"You cannot currently start an expunge for this gallery."'''
**You are no longer permitted to use the [[expunge]] system. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**You may also get this message when your login session has expired. Please clear your cookies and log in again.

====<span style="color:#977933">Common Problematic Software</span>====
*Ghostery, PeerGuardian, PeerBlock, Protowall, Megakey, Transmission ([[torrent]] client), DuckDuckGOPrivacy (the plugin - you need to whitelist EH to see content), DuckDuckGo, DansGuardian, SquidGuard, HackShield (used as part of some MMOs).
*Any global/browser-based IP blockers can cause problems. For P2P applications use directly loaded IP lists.
*Any "web accelerators" or pre-fetching can cause routing issues (E-Hentai's [[IPs]] are not static).

===Gallery Not Available===
<div id="removed"></div><div id="Removed"></div>
*'''"This gallery has been removed or is unavailable."'''
**This is '''not''' the same as a gallery being deleted or [[expunged]].
**'''<span style="color:red">Do NOT re-upload it.</span>'''

*'''"This gallery is unavailable due to a copyright claim by {copyright holder}. Sorry about that."'''
**The gallery has been removed due to a DMCA takedown notice.
**'''<span style="color:red">Repeated attempts to re-upload galleries of this nature will lead to a [[Bans|ban]].</span>'''

===Your Galleries===
*'''My gallery disappeared!'''
**This is almost never due to a technical problem.
**Check if it is still listed in your [[Gallery Manager]]. If so, the reason it is not visible will be indicated there.
**Attempt to visit a direct link to your gallery.

<div id="expunged"><div id="Expunged"><div id="expunge"><div id="Expunge">
*'''My gallery was [[expunged]] unfairly!'''
**Check the gallery's expunge log for the reason(s).
**Make sure it was [[expunged]] and not removed or deleted. Each of these happen for very different reasons.
**Post the gallery's URL [https://forums.e-hentai.org/index.php?showtopic=242797 here] to inquire about it.

*'''<span id="delete gallery">I cannot delete my gallery!'''
**This is intentional. [https://e-hentai.org/tos.php Once a gallery has been published, it belongs to the community].
**A gallery may instead be [[My Galleries#Available Actions|disowned]] if the uploader wishes to remove association.
**<span style="color:red">'''False expunges will lead to a ban and the gallery reverted to its previous state.'''</span>

*'''<span id="cant upload">I cannot publish my gallery.'''
**Before publishing a gallery or a gallery update you must first read the [https://e-hentai.org/tos.php Terms of Service] and check the corresponding box, then choose a sorting order. If you do not wish to re-order, click "Apply with Current Ordering".

*'''My gallery has an incorrect name or [[category]]!'''
**Check if it is still listed in your [[Gallery Manager]]. The default category is [[Doujinshi]].
***If so, you may rename or re-categorize it from there.
***If a [[Renaming|rename petition]] was successful on your gallery but the name is still unsatisfactory, you may insert another petition option. Should this new option reach higher [[power]], the name will change over.

*'''I cannot [[rename]] my gallery from the [[Gallery Manager]]!'''
**This action is only permitted from the manager for 24 hours after publishing.
**A successful [[Renaming|rename petition]] was done on your gallery. See the above issue.
**[[Expunged]] galleries cannot be renamed in this manner.

*'''"You can no longer change the [[category]] of this gallery."'''
**The gallery has had its [[category]] changed via [[tagging]]. If the [[category]] is still unsatisfactory report it as a [[#Gallery Tagging|mistag]].

*'''"You cannot unlock galleries this old. Please make a new one, then request to have this one expunged."'''
**You are attempting to [[Making_Galleries#Updating|update]] an aged gallery (i.e., 365 days after its last publishing). Such galleries cannot have their files modified.
**Any necessary changes require re-uploading and replacement [[expunging]] the existing gallery. This starts a brand new gallery chain without any of the previous gallery's metadata.

*'''I'm afraid I can't let you do that.'''
*'''That gallery has been marked as deleted, and can no longer be modified.'''
**You are attempting to modify or delete a gallery that cannot or can no longer be deleted.
***This also applies to properly replaced galleries and is working as intended.

*'''"Could not rate gallery. Reason: You cannot rate your own gallery."'''
**Self-explanatory.

*'''"Could not obtain lock on gallery - if you are not running any active operations on this gallery, please wait about 15 minutes for the lock to expire."'''
**Occurs when a gallery being uploaded / managed is in the middle of being processed by the server. Please wait and try again later.
**Also occurs to galleries that were reverted to a previous state, thus the URL entered is no longer valid.

*'''My gallery has missing, unwanted, or wrongly ordered images!'''
**You can add, remove, and modify the order of all your gallery's images via the [[Gallery Manager]].
***Note that you may only update a gallery twice per every 30 days (some exceptions apply).
****This limit does not apply to unpublished / [[private]] galleries.
<div id="order"></div><div id="Order"></div><div id="out of order"></div>
*'''When people download my gallery the files are in the wrong order!'''
**Downloaded galleries use the filenames of the files ''when they were uploaded'', so they may be out of order even if you corrected the order manually via the gallery maintenance UI.
**Rename your files to the correct order '''''before''''' uploading them (''e.g. 001.jpg, 002.jpg, etc.'') to avoid this problem.
***This is further recommended since different OSes [https://support.microsoft.com/kb/319827 sort files differently].
<div id="rating"></div><div id="Rating"></div>

*'''<span id="bad ratings">People are giving my galleries low [[ratings]]!'''
**They are entitled to their opinions. Furthermore, ratings do not affect how well a gallery fares.
**Votes that deviate too much from the average rating are automatically discarded. This process is retroactive. Ratings, [[tags]] and [[favorites]] also carry over across all non-aged gallery updates.

*'''My gallery files are being resampled and converted to WEBP!'''
**This is intended for [[Making_Galleries#Limits|files over 10MB in size]]. A link still allows you to download the original source at a cost of 10 image hits per MB.

*'''My gallery's stats show low/no hits!'''
**Gallery stats are updated every ~4 hours. Please wait and check again later.

====[[Uploading]]====
*'''My uploads seem unusually slow.'''
*'''I am stuck on "Processing..."'''
**Try to upload your images in ZIP or RAR archives. Uploading a small amount of larger files is faster than many smaller files. Break your upload into smaller portions.
***To prevent [[out of order]] situations either prefix filenames (the same way the [[Archiver]] would) or upload archives sequentially.
**Disable any software that uses upload bandwidth while you are uploading to the site.

*'''Images appear outside of the scope / keep reappearing and I can't save changes!'''
*'''I've uploaded files but the gallery is empty!'''
*'''"The gallery is busy processing another task. Please wait until it is done before uploading more files."'''
**The recommended maximum data you should upload in a single instance is 500 MB. Do not upload more than <span title="1,258,291,200 bytes" style="border-bottom:1px dotted">1,200 MB</span> in a single instance.
**Do not upload in multiple tabs/windows at the same time; the files are liable to be discarded.
***Uploading files to different galleries simultaneously is also not recommended.

*'''My files take a lot of time to be processed.'''
**All files require indexing and thumbnail generation. PNG files additionally require decompression. Please be patient.
**It is recommended to use zero-compression (Store) ZIP/RAR archives; the filesize difference is negligible whilst processing will be much faster.

*'''"Could not retrieve lock for gallery"'''
*'''"The gallery has been deleted"'''
**You are trying to upload files to the wrong gallery chain (replaced chain) or a deleted gallery.

*'''"Upload is temporarily unavailable."'''
**The upload server is under maintenance. Please wait and try again later.

*'''"The file {filename} is corrupt, incomplete, too large, or not an accepted image file."'''
**Make sure the file is of an [[Making_Galleries#Limits|accepted format and is not over the size limit]], is not corrupt, and is not named with [[Making_Galleries#Checking|unacceptable characters]].

*'''"{Filename} has been blacklisted on this system"'''
**Any file that causes this message should '''NOT''' be uploaded as it is [[DNP]].

*'''"You have been temporarily barred from posting more galleries due to an excessive expunge rate."'''
**Too many of your galleries were [[expunged]], removed, or deleted, triggering an automated [[Making Galleries|upload]] block.
**Wait for the block to expire and do not create any more unacceptable uploads.
***The duration is a sliding window and may last up to a week.

*'''"You have been temporarily [[banned]] from [[Making Galleries|submitting galleries]] to this system. Read your PMs."'''
**A temporary upload ban has been manually placed on your account. This usually expires in a week, but the duration may vary. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**Consequently, you will also lose the ability to update all galleries published before the time of the manually placed ban.

*'''"You have been permanently [[banned]] from [[Making Galleries|submitting galleries]] to this system."'''
**Same as above, except permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"You can no longer modify that gallery."'''
**You are no longer allowed to update your galleries published before a specified time. An expired manually placed upload ban may also cause this.
**[https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] if you have a valid reason to update your old galleries.

*'''"Rate limitation for new posters in effect. You have to wait a few hours before you can post more [[Making Galleries|galleries]]."'''
**There is a rate limit that compares your recent upload volume to your post history of good galleries, the calculation determines how many galleries you can publish in succession. Wait for the limit to expire.
***Private / Unlisted galleries do not count as "good". <sup>[https://forums.e-hentai.org/index.php?s=&showtopic=252404&view=findpost&p=6011165 (Ref)]</sup>

*'''"You have earlier uploaded and published a gallery identical to the one you are now trying to publish. This gallery has been removed, and you will now be redirected to the old, identical gallery. If that gallery had previous been marked as deleted, it is now available again. You will be returned to the Management Interface momentarily."'''
**You uploaded an exact copy of a gallery you have already uploaded and published.
**This will undelete a gallery if it was deleted by its owner.

*'''"You cannot add files to galleries that are older than twelve months. Please make a new one, then request to have this one expunged. You will be returned to the Management Interface momentarily."'''
**This is what is known as an [[aged]] gallery.
**[[Expunging#Replaced|Replace]] your gallery if it is truly necessary to make changes to it.

*'''"{Filename} was generated by this system and has been replaced with the original copy."'''
**The image uploaded is a thumbnail that was already generated by the system and thus was replaced by its original version.

*'''I cannot select 'Save Changes', 'Start Upload', or 'Publish Gallery' after deleting an image!'''
**Use one of the sorting buttons after making such changes to confirm them.

*'''"You have posted too many [[private]] galleries in the last week."'''
**You have reached your weekly upload limit for [[private]] galleries.
**[[Donation#Stars|Bronze and Silver Star]] users are allowed to create up to 5 private galleries per week. This limit is bumped up to 10 galleries per week for [[Donation#Stars|Gold Star or above]] users.

*'''I cannot create any [[private]] gallery despite having a [[Donation#Stars|bronze star or above]]!'''
**Your account has been permanently blocked from uploading [[private]] galleries. This is likely due to excessive abuse of the function.

*'''All of my new uploads are automatically flagged as [AI Generated]!'''
**A restriction has been placed on your account, in which all new uploads will receive the [[AI Generated]] title indicator and be categorized into [[Misc]]. This is due to repeatedly uploading numerous [[AI Generated]] galleries without labeling them as such.
**If your new gallery isn't generated by AI, you may remove the indicator by filing a [[rename]] petition. Note that misusing the rename function would lead to a [[ban]].
***Uploaders who don't have sufficient [[mod power]] to file a rename petition on their own can submit a request [https://forums.e-hentai.org/index.php?showtopic=227712 here].

===[[Gallery Tagging]]===
*'''Some tag searches include additional results.'''
**Try using [[Gallery_Tagging#Exact_Tag_Searching|exact tag searching]].

*'''I cannot tag a gallery!'''
**The tag you are attempting to use may not be acceptable (e.g. too short or blacklisted).
**You may be banned from tagging galleries. You will receive a pop-up notification if this is the case.
**You may be attempting to upvote a downvoted tag (which may not give an error message). Be sure to read the tag's definition, [[Gallery Tagging|tagging guidelines]], or ask [https://forums.e-hentai.org/index.php?showtopic=274004 here] for upvotes.
**[[#Could Not Vote For Tag|See below]] for specific tagging error messages.

*'''I tried to tag something and it turned into a different tag!'''
**Your tag included non-alphanumeric characters which are not permitted. Only hyphens, periods, and spaces are allowed in tags.
**Due to the grouping system for tags any [[slave tag]] will become its respective master tag. If you are not satisfied with the grouping you may post [https://forums.e-hentai.org/index.php?showtopic=107861 here] to discuss it.

*'''I cannot select a [[namespace]] for my tag!'''
**If you are certain it should be assigned a namespace please contact a [[E-Hentai Janitor|namespacer]] or post [https://forums.e-hentai.org/index.php?showtopic=275305 here].
***At least one instance of the temp tag must exist for it to be namespaced. If you cannot add the tag due to lack of [[power]] or if the tag already exists within another namespace please also link to a gallery where the tag would be a valid addition. If the tag does not pass [[presence]] for a gallery but will likely be used in the future (e.g. a [[character]] tag) please specify this in your post.
****If you forgot where you made the tag checkers have a listing for new tags created within the last 7 days along with the names of users who voted on them.

*'''I accidentally created a wrong tag!'''
**Simply withdraw your tag before someone else upvotes it. If it's too late and you cannot downvote the tag completely by yourself ask for assistance in [https://forums.e-hentai.org/index.php?showtopic=274004 this thread].

*'''"Server communication failed. Server responded with:"'''
**Connection timed out. Check your connection, wait a few seconds and try again.

*'''Someone is voting down my tags!'''
*'''My gallery has incorrect tags!'''
**Double-check the tag's definition and [[Gallery_Tagging#Usage_Guidelines|tagging guidelines]].
**Vote the tags up/down only if you are absolutely certain.
**Post the gallery's URL [https://forums.e-hentai.org/index.php?showtopic=274004 here]. Please do not accuse any users of mistagging or request any [[bans]].

<div id="temp tag pop-up warning"></div>
*'''"You about to vote up an older temp tag. You may be prompted to provide sources for this tag, which is required. Are you sure you want to do this?"'''
**You are attempting to vote up a tag that has yet to be approved by a [[E-Hentai_Janitor|namespacer]].
***Upon hitting "OK", you will be brought to the [[Tag_Creation|New Tag Justification window]] if you have at least 15 [[mod power]] and no active tag creation [[Bans|ban]].
**'''Do NOT hit that button if you are not prepared or willing to provide [[Tag_Creation#Guidelines_for_Submission|relevant supporting materials]] for that temp tag.''' <span style="color:red>'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence may lead to a [[Bans|ban]].'''</span>

====Could Not Vote For Tag====
*'''"Could not vote for tag: You need at least 15 MP to vote on this tag."'''
**The tag you are attempting to vote on [[Tagging_Mechanics#Tag_Mod_Power|requires]] additional [[mod power]]. This is to prevent poor handling of the tag by newer users.

*'''"Could not vote for tag: You do not meet the requirements to vote for "{tagname}""'''
**The tag can only be voted by users who meet certain requirements. For more information, view the wiki article for the tag.

*'''"Could not vote for tag: The tag "{tagname}" currently requires at least {value} MP to upvote on this gallery due to existing downvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-vetoed]] and needs a matching or higher base [[mod power]] of the highest vote against it to vote it up.
**If you are sure that a tag was mistakenly downvoted, you can post in the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread.

*'''"Could not vote for tag: The tag "{tagname}" currently requires at least {value} MP to downvote on this gallery due to existing upvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-enforced]] and requires a [[mod power]] that matches or exceeds half of the value of the strongest upvote to vote it down, capped at 25 [[mod power]].
**If you believe the tag is definitely invalid, you can make a downvote request in the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread.

*'''"Could not vote for tag: The tag "{tagname}" is currently locked for further upvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-enforced]] or has reached the cap of 200 [[mod power]], and can no longer be upvoted.

*'''"Could not vote for tag: The tag "{tagname}" is currently locked for further downvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-vetoed]], and can no longer be downvoted. This error will usually appear if you attempt to downvote a tag that was already killed and 5 minutes elapsed without refreshing the page.

*'''"Could not vote for tag: The tag "{tagname}" has been blocked for use."'''
**You are attempting to add/upvote a tag that is blocked or blacklisted.

*'''"Could not vote for tag: The tag "{tagname}" is not allowed. Use {namespace}:{tagname} or {namespace}:{tagname}"'''
**The tag you are attempting to enter requires an accompanying [[namespace]]. The namespace must be one of the approved pairings for that particular tag.

*'''"Could not vote for tag: The tag "{tagname}" is scheduled for an automated action and cannot currently be voted on."'''
**You are downvoting a tag that has been slaved or blacklisted by a [[Janitor|moderator]]. This is not a required action as the autotagger will remove or replace these tags eventually.
**User may still withdraw their upvotes on a slaved/blocked tag should they have upvoted it before.

*'''"Could not vote for tag: Your vote can no longer be withdrawn."'''
**You are attempting to withdraw your upvote on a now-downvoted tag. This cannot be done to prevent abuse.

*'''"Could not vote for tag: Tags should be added on the most recent gallery in this chain."'''
**Only the most recent version of a gallery chain allows for tagging actions. The action will automatically be applied to all galleries in the chain.

*'''"Could not vote for tag: Invalid user"'''
**The API received an invalid user identification response while you were tagging.
***Your session may have expired. Use another browser or clear your cache/cookies.
***This will also occur when you are simply not logged in.

*'''"Could not vote for tag: No tags to add."'''
**You entered a term or phrase that is rendered as a blank tag.

*'''"Could not vote for tag: Missing arguments"'''
**You submitted a blank tag.

*'''"Could not vote for tag: Missing or malformed tags"'''
**Your request is longer than the maximum allowed for the input field.
***[[API]] requests are limited to the default tag input field maximum length (200 characters).

*'''"Could not vote for tag: You cannot possibly have taken the time to look at the gallery in that short time. You must wait 10 seconds between tagging different galleries."'''
**You attempted to vote on a tag on a gallery too quickly after doing so on a different gallery.
**This limit can be reduced with increased [[power]].

*'''"Could not vote for tag: User fault detected. Replace user and try again"'''
**You entered in the default text on the tag form ("Enter new tags, separated with comma").

*'''"Could not vote for tag: The tag {tagname} is vetoed on this gallery and cannot be upvoted. Please read the wiki."'''
**The tag you are attempting to add has been [[Tagging_Mechanics#Tag_Veto|vetoed]] on the gallery. If you believe that tag has been vetoed incorrectly, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=274004 here].

*'''"Could not vote for tag: The tag {tagname} is enforced on this gallery and cannot be downvoted. Please read the wiki."'''
**The tag you are attempting to downvote has been [[Tagging_Mechanics#Tag_Veto|enforced]] on the gallery. If you believe that tag is invalid, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=274004 here].

*'''"Could not vote for tag: The tag {tagname} has never been used. Use temp:{tagname} to create a temporary tag."'''
**You are adding a [[Namespace#Restricted_Namespaces|temporary]] tag without defining the "temp" [[namespace]]. Please include "temp:" in front of the tag name.

*'''"Could not vote for tag: The tag {tagname} does not exist. You can request new tags in the Tag Creation/Namespacing Request Thread."'''
**The [[namespace]] you are attempting to use has not been approved by a namespacer.
**This error also occurs when you are attempting to create a [[Namespace#Restricted_Namespaces|temporary tag]] with less than 15 [[mod power]], or with an active tag creation [[Bans|ban]].
***If you are certain it should be usable, please post [https://forums.e-hentai.org/index.php?showtopic=275305 here] to have it added.

*'''"Could not vote for tag: The tag {tagname} has an invalid namespace."'''
**The [[namespace]] being used is not a correct one. Check your spelling.
**Make sure not to use a colon when tagging something except to indicate a namespace.

*'''"Could not vote for tag: The tag {tagname} is derived from the gallery title and cannot be directly voted on."'''
**The tag has been added due to the presence of a special indicator in the gallery title. For more information, view the wiki article for the tag.

*'''"Could not vote for tag: Gallery not found"'''
**The gallery is no longer formally in the system.

*'''"Could not vote for tag: You have been banned from tagging galleries"'''
**Your tagging privilege has been permanently revoked. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

===[[Archives]]===
*'''The [[archive]] link returns a blank page with the message "err".'''
**Clear your cache and cookies.

*'''I get a 503 error when I download an [[archive]]!'''
**The site may be experiencing [[#503|maintenance or other issues]].
**You may be attempting to use more than 4 simultaneous download threads. If using a download manager make sure that it does not exceed that amount.
**You may have exhausted your allowed download attempts.

*'''My download speed is much slower than expected!'''
**After ensuring the issue is not on your end, you may be downloading from a capped or saturated archive server due to various reasons.
***The issue can be mitigated by using segmented downloading (use at your own risk) or just being patient. Alternately, if a very healthy [[torrent]] is available, please consider using this option.
***It is not possible to change servers after the archive is generated. Available servers are randomly assigned upon request and the archive then is only valid for the assigned archive server.

*'''A gallery I downloaded says "Unexpected end of archive."'''
**The download was interrupted at some point. Please try to download it again.

*'''"IP quota exhausted"'''
**Too many addresses from the same IP range tried downloading the same [[archive]].
**Wait a week, generate another archive link, and '''do not share this link''' with anyone.

*'''"The file is already being processed. Please contact staff if it is not ready within a few minutes."'''
**Your browser should automatically refresh the page from time to time. You may refresh it manually if this is not the case.
**Processing may take more than a few minutes. Waiting longer may eventually resolve the issue.

*'''"Failed to prepare one or more files for the archive. Please try again in an hour. Contact staff if this error persists."'''
**Self-explanatory.

*'''"Failed - Unknown server error. Please try again, or contact the server administrator."'''
**Try downloading from a different IP address or VPN. If the issue persists, make an inquiry in the [https://forums.e-hentai.org/index.php?showforum=7 Site Discussion & Help Desk] forum.

*'''"You have clocked too many downloaded bytes on this gallery."'''
**You download the same gallery's archive multiple times or the prior downloads kept failing and restarting. Cancel the download session and repurchase the archive.
**You downloaded the original archive and are now trying to download the resampled archive. Sometimes this errors, use the cancel button and repurchase the archive.
***If you require both the resampled and original archive, it is recommended to download the resample first to avoid this.

*'''"You cannot have any more simultaneous downloads."'''
**You are attempting to download way too many galleries at once. Slow down.
**Please note that no more than 5 simultaneous streams per server are allowed.

===[[Renaming]]===
*'''Someone else's gallery has an incorrect name or [[category]]!'''
**See [[Renaming]] for name changing.
**See [[Gallery Tagging#Categories|Gallery Tagging - Categories]] for category changing.
**You may also post links to such galleries [https://forums.e-hentai.org/index.php?showtopic=227712 here]. Please indicate the correct name/category in your post.

*'''"That is already one of the suggested names."'''
**You attempted to add a [[rename]] petition with the same text as an existing one for that gallery.

*'''"New suggested title is too short."'''
**You attempted to add a blank name as a [[rename]] petition. Pay attention to which option button is used.

*'''"You have been blocked from renaming galleries."'''
**You are no longer allowed to vote on or create [[rename]] petition. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

===[[Commenting]]===
*'''My gallery comment disappeared!'''
**Comments will become hidden under [[Gallery_Commenting#Hidden_Comments|certain criteria]].
**For galleries with more than 50 comments only the top 50 (depending on which viewing order is used) are displayed by default; the rest are hidden.

*'''I cannot delete my gallery comment!'''
**This is intentional.

*'''"Due to reported abuse, you have been blocked from adding more comments."'''
**Numerous comments that you have made were severely downvoted.

*'''"You have been banned from posting comments."'''
**Your commenting privilege has been suspended due to the violation of the [[Gallery_Commenting#Examples_of_Bad_Comments|comment rules]]. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"You can only add comments for active galleries."'''
**Deleted galleries may not have comments added to them.

*'''I cannot rate a gallery comment!'''
**You cannot rate comments if you have added a comment to the same gallery.
***Any existing comment ratings for a gallery will be removed if you add a comment to that gallery.

*'''I can upvote just fine but my comment downvotes do not have any effect!'''
**You have downvoted too many comments and the system acknowledged you as a potential mass-downvoter.

*'''"You have to wait 60 seconds between each comment."'''
**This is to prevent spam. This limitation is reduced to 10 seconds for users with at least 25 [[power]].

*'''"Your gallery comment is too short."'''
**Comments must be at least 10 characters long.

*'''"You did not enter a valid comment."'''
**You entered in the default text into the comment form ("Enter your comments here, then hit Post Comment. If the last comment posted is yours, this will be appended to that post.")

*'''"You did not enter a comment."'''
**You either entered no text in the comment field or text that renders as nothing.

*'''"Could not vote for comment. Reason: Correlation factor between reviewer and voter has exceeded reasonable limits. Vote blocked."'''
**You have voted on a particular user's comments too much. Upvote other useful comments.

*'''"Could not vote for comment: Cannot vote when own comment exists in gallery"'''
**You are trying to vote after posting a comment. Refresh the page to display your comment (unless it is perma-hidden).

*'''"Could not vote for comment: You have been banned from voting on comments"'''
**You are no longer allowed to vote on other comments. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"Could not get editable comment: Can only edit own comment"'''
**You are trying to edit someone else's comment. Refresh the page to display your own comment.

*'''"You have been temporarily restricted from adding comments'''"
**This is due to a limit on newer users to prevent potential spam. It will resolve over time.

===[[My Tags]]===
*'''I am unable to add/remove tags from [[My Tags]], or add/remove [[My Tags#Sets|tag sets]]!
**Commonly because of an outdated browser. Update your browser and try again.

==[[HentaiVerse]]==
('''<span style=color:#FF5555>For in-game error messages see [[HentaiVerse_Bugs_%26_Errors|HentaiVerse Bugs & Errors]]</span>''')

*'''HentaiVerse is slow for me!'''
**Disable any [[scripts]] or browser add-ons. Re-enable them individually to isolate which one(s) may be causing the slowdown.

*'''"Failed to initialize player state. Try again later."'''
*'''"HV is temporarily unavailable, as the battle state tracker or master database is currently offline."'''
*'''"HentaiVerse is not available on this cluster. If you are seeing this message, contact staff."'''
*'''"Snowflake and the moogles are basking in the summer sun. Check back later."'''
**Wait a few minutes and try again or use the alternative ''alt.hentaiverse.org''.

*'''I can't see everything in the HentaiVerse window!'''
**The minimum recommended resolution for HV is 1280x768.

<div id="dawn"></div><div id="Dawn"></div>
*'''[[Dawn of a New Day]] / [[Random Encounter]] message does not appear.'''
**There is a limit of 24 random encounters per day.
**You need to visit either the E-Hentai [https://e-hentai.org/news.php news page], or any gallery on the [https://e-hentai.org/ main website]. Visiting any other pages will not trigger the events.
***If you have just logged in, reload the page. If it still isn't working, wait a few minutes and try again.
**Even if the message did not appear, check to see if the rewards from the Dawn have been received.
***Note that daily income from dawn does not show up on the credit log.
**Disable any ad-blockers or other add-ons that may prevent the message from appearing.

*'''Posting in [[E-Hentai Forums|the forums]] is not giving an [[EXP]] gain bonus.'''
**The EXP bonus takes 1 hour after the posting to take effect.

*'''I can't enable my abilities!'''
**Use a browser that supports HTML5.
<div id="exp"></div><div id="EXP"></div><div id="noexp"></div><div id="noEXP"></div>
*'''I'm not receiving any [[EXP]]!'''
**Your [[Stamina]] has dropped below 2.

*'''"Nope"'''
**You are attempting to access an [[equipment]] piece's link with an invalid ID or key.

*'''Holding down hotkeys doesn't work!'''
**[[Image:Firefox.png]] If you are using NoScript, navigate Firefox to ''about:config'' and set ''noscript.clearClick.rapidFireCheck'' to "false".

*'''I jumped to a new fight instead of going to the next turn!'''
**The server cluster lost a node temporarily. Just wait a few minutes and it should re-establish the connection to the node and load your battle again.

*'''Some of the graphics don't show!'''
**Try {{Keypress|Ctrl}} + {{Keypress|F5}} to force reload them.

<div ID="ShopBot"></div><div ID="Profit"></div><div ID="Bazaar"></div><div ID="bazaar"></div><div ID="profit"></div><div ID="shopbot"></div>
*'''I sold an [[item]] to the [[Bazaar]] and got more [[credits]] than what it indicated.'''
**[[Item Bot]] [[Bazaar#Item_Shop|profit sharing]].

*'''My [[EXP]] required for the next level is showing as a negative!'''
**This is purely an aesthetic bug. It can occur when triggering a [[Dawn|dawn]] event that gives enough [[EXP]] to [[level up]] whilst in a [[battle]].

*'''"Your account has been suspended, or you have been blocked from accessing the HV minigame."'''
**Your account has been banned, likely due to [[Bans|rules]] violations. This is permanent.

<div id="H@H"></div>

==[[H@H]]==
;Always make sure you have the latest stable version of [https://www.java.com/en/download/ Java Runtime Environment] and that your internet speed is sufficient when running the client.

*'''Does H@H have any dependencies?
**H@H has zero dependencies other than Java itself.

*'''Does H@H include Log4j?'''
**No. H@H has zero dependencies other than Java itself.

*'''What's my Client ID?'''
**You will not have one if you did not sign up for H@H.
**Check [https://e-hentai.org/hentaiathome.php here] for it.
**Client IDs that have been inactive for more than 6 months (~180 days) are revoked. Re-applying is permitted.

*'''My client's status is fine but I don't earn any [[Hath]] from it!'''
**Hath will not be granted if a client's speed is below the minimum requirements<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=215951&view=findpost&p=5139875]</sup>.
***Make sure the client can constantly sustain at least 200KB/s of burst speed.

*'''My client isn't doing anything!'''
**Make sure the client is [[H@H#Activity|healthy]].
**If you are running a brand new client wait for your cache to fill (and subsequently [[static range]]s). Caches generally only fill for clients that have been running for at least 24 hours.
**Cached content itself will not affect hitrate; the only factors involved are burst speed, client quality, client region, and assigned [[static range]]s.

*'''I am not being assigned static ranges!'''
**Ensure your client is stable and active with sufficient dedicated disk space. Keep it running for as long as possible.
**There is a limit on how many times a range can be assigned to live clients in a region. If that limit is reached for all ranges, it won't assign any more until some clients go away.<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=234458&view=findpost&p=5758006]</sup>

*'''Disk usage is too high! Is there a way to limit this?'''
**To reduce disk seeks lower the cache size, a higher percentage of file accesses will be cached in RAM.<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=215709&view=findpost&p=5138580]</sup>
***'''All static ranges unable to fit within the new cache size will be lost.''' Ranges will be gradually reassigned once the cache becomes bigger again and the client is qualified to earn more ranges.

*'''HTTP 400 (Bad Request) responses show up in the client!'''
**This is normal as long as the client is within its region's average failure rate.
**If this happens a lot the client's ISP may have poor connectivity to the querying region. This can also be due to packet loss.

*'''My client has low trust!'''
**This commonly occurs after a bad shutdown since the server continues to attempt contact with your client after it went offline.
**Leave the client running, it will gradually regain trust if no other problems exist.
**If its trust is not recovering at all it may indicate a communication or file corruption issue. Check your cache.
**Low trust can also happen when your drive is full. It can happen on certain systems despite setting a free disc space in your panel. You can reduce your Maximum Disk Cache Size setting in your panel (and check "Remove static ranges if necessary") to fix that issue.

*'''My client's trust is fine but my quality drops!'''
**This is usually caused by transient routing problems in the short-term and prevents single malfunctioning clients from causing entire network issues by lowering their priority accordingly.
**Sudden and large drops are normal for newer clients; waiting for a few weeks will generally give a stable baseline.

*'''"Request host did not send Content-Length, aborting transfer."'''
**Something is blocking your requests; disable any [[#Common Problematic Software|problematic software]] that may be doing this.
**Disable [https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security Xfinity's xFi Advanced Security].

*'''"We appear to have reached the image limit. Attempting to contact the server to ask for a limit increase..."'''
**You have downloaded up to your daily limit via H@H downloader; you must wait 24 hours.
**This limit can be reset at your [[My Home]] area or increased by purchasing the "More Pages" [[Hath Perks]].

*'''"Server reported expired key; attempting to refresh time from server and retrying."'''
**Ignore this unless it persists.

*'''My client has been revoked!'''
**Your client has been banned for failing to adhere to the [[Hentai@Home#Signing_Up|uptime requirements]] by a significant margin, or having an unreasonably high cache/ranges reset count.
***Revoked clients can sometimes be reactivated by sending an unblock request to [https://forums.e-hentai.org/index.php?showuser=6 Tenboro]. This will be decided on a case-by-case basis, and can only happen when there is a very strong justification for your case.
***Note that claiming ignorance of the H@H uptime requirements or the automated warnings on your excessive cache/ranges resets is '''NOT''' considered an acceptable justification.
**This can also occur if any of your cache files were deleted and your cache database was not updated to reflect this. Do '''NOT''' manually delete files from your cache.
***If you need to reduce your cache size simply reduce the value in the client's setting. The client will automatically remove excess cache files.

*'''"Critical Error: java.sql.SQLException: disk I/O error"'''
*'''"java.lang.NullPointerException - [ERR] at org.hath.base.CacheHandler.initializeCacheHandler(CacheHandler.java:214)"'''
*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)} at org.sqlite.Conn.setAutoCommit(Conn.java:336)"'''
*'''"[ERR] java.sql.SQLException: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed)"'''
**Delete hath.db and rename hath.db.bak to hath.db, then restart the client.
***If this fails delete both files and restart the client.
**Make sure that the user you're running H@H as has write access to the directory from which you run it.
**If all else fails run [https://en.wikipedia.org/wiki/CHKDSK chkdsk] on the drive that stores H@H.

*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)} java.lang.InternalError: HTHEME is null"'''
**This is an aesthetic issue. [[Image:WindowsOS.png]] If the Themes service is disabled on a Windows OS and a client is running in the H@H GUI this error will happen whenever it is given focus as it fails to parse themes.
**Use the command-line client or enable the Themes service.

*'''"Cache Handler: cannot meet space constraints: Disk free space limit reached."'''
**Your free disk space was detected as too low. The client will stop getting new files until this is remedied.
**Change your disk space setting ("Minimum space to leave on disk") (minimum 100 MB even if not set) or remove non-H@H files from the drive that H@H uses.

*'''I'm having high memory usage running H@H under OpenVZ!'''
**Because of how OpenVZ calculates resident memory size H@H can appear to use as much as 1 GB of RAM even though its actual resident memory size is usually 50-100 MB.
**There is no known workaround at this time.

*'''My client's country on the H@H status page is shown in <span style="color:#ff0000">red</span>!'''
**Your client has been moved from its first-time startup location ("''home region''") to a different region. e.g., the client started in the United States, then moved to Japan at a later point.
**When the system detects that a client is operating outside of its ''home region'', this will have multiple effects<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=234458&view=findpost&p=6376141]</sup>:
***Clients outside the ''home region'' will no longer be assigned new [[Hentai@Home#Static_Ranges|ranges]] or be considered for range priority promotions.
***If there are multiple clients with the same range/priority in the region, clients outside its ''home region'' will always be demoted first, and the client in the ''home region'' will be preferred for routing traffic.
***No [[Hath]] will be awarded for clients located outside of its ''home region''.
**To resolve this, you will need to contact [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] directly. Note that in most cases, resetting the ''home region'' of an H@H client will result in the demotion of all of the client's P1 ranges to P2 to allow the system to optimally rebalance range priority.
**This may also happen if the auto-detected country is simply wrong. In this case, a geolocation override may be applied without the demotion of [[Hentai@Home#Priority_Ranges|priority ranges]].

*'''My country is incorrect on my H@H page!'''
**This does not matter for clients in Canada/United States.
**If the indicated country is geographically very far away from what it should be an override for the client ID may be necessary. Please contact [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] directly.

*'''My client key is "Not Set"!'''
**You must enter all the configuration details (speed, disk size, etc.) before the key is given.

*'''The SSL handshake times out!'''
**This happens on some routers where the WAN is through PPPoE, although rare.
**If you have access to your router configuration you can change this with iptables:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -t mangle -A FORWARD -p tcp -i pppoe-wan -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu</pre>

For an ISP provided router you may need to switch the router into modem mode and append second router in front of it.

===Startup Errors===
*'''"Startup notification failed."'''
**(This is a generic message, but if no other message accompanies it then this section may apply).
**Your speed was measured as too low. Turn off any bandwidth-consuming applications and try again.
**Java may be binding an IPv6 port. Try launching H@H with <tt>java -Djava.net.preferIPv4Stack=true -jar HentaiAtHome.jar</tt>.
**You failed to contact the main server. Try again later.
**Turn off any anti-DDoS settings on your router which prevent multiple connections from occurring simultaneously.

*'''"The client has failed the external connection test."'''
**Your port for H@H was not detected as open. You may test it [https://canyouseeme.org/ here].
**Make sure that the port you are opening matches the one set in your H@H settings.
**Read a [https://portforward.com/ guide] to help with the opening of ports.
**Make sure you have a public IP address. ISPs may use [https://en.wikipedia.org/wiki/Carrier-grade_NAT CG-NAT], preventing others on the internet from seeing your computer.
**Check the IP of your router/modem. If it is [https://en.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces within a private range], you may have to ask your ISP to grant you a public address.

*'''My entire cache is being verified when I start the client!'''
**This happens whenever there was a bad shutdown. This is to ensure the integrity of your cache is still in good standing.
**The client should run normally after the checking is complete. Please be patient.

*'''"The database could not be loaded."'''
*'''"Critical Error: Failed to buffer requested data for cache list write."'''
**Delete hath.db, rename hath.db.bak to hath.db, then re-launch the client.
***If this fails, delete both files and re-launch the client.
**Make sure you have ownership of the files and folders that H@H uses.

*'''"Rejecting connection request during startup."'''
**If this doesn't happen very often just ignore it. Other users are simply contacting your client too soon.
**Check if your firewall or other software is blocking Java connections.

*'''"Required library file sqlitejdbc-v056.jar could not be found."'''
**The file is missing, re-download H@H.
**It you run H@H through a command line, make sure to <tt>cd</tt> to the same directory as the HentaiAtHome.jar file before running. You may also add that <tt>cd</tt> command to the batch file.

*'''"[WARN] Unknown host rpc.hentaiathome.net, aborting.."'''
*'''"[ERR] java.net.UnknownHostException: e-hentai.org"'''
**This may be a DNS issue. Try [https://documentation.cpanel.net/display/CKB/How+To+Clear+Your+DNS+Cache flushing your DNS cache] and restarting the client.
**Try switching to [https://developers.google.com/speed/public-dns/docs/using Google's public DNS].

*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}"'''
*'''"Could not start the internal HTTP server."'''
**Something besides H@H is already using the port that it was assigned. Try closing any program that may be doing this or set H@H to use a different port.
<div id="ports"></div><div id="Ports"></div><div id="port"></div><div id="Port"></div>

*'''It doesn't allow me to use a specific port!'''
**The following ports aren't available due to browser blocking and other compatibility issues: 80, 2049, 3659, 4045, 6000, 6665, 6666, 6667, 6668, 6669.

==[[E-Hentai Forums]]==
*'''"Sorry, you are not permitted to use this board."'''
**Your IP address may be banned. Try to change it.
**[https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] with your IP if this continues or if you cannot change it.
**[[Image:Opera.png]] You are using the Opera Mini browser/network. Try an alternate browser.
<div id="NoURLs"></div>

<div id="Attachment"></div>
*'''I can't post URLs or attachments!'''
**New users may not do so until they have made at least '''2''' posts.
**Some subforums and threads disallow attachments.
***If there is a serious need to post an image in such a thread simply upload to and link to a filehost.

*'''My post count is not going up!'''
**Posts made in certain subforums do not increase post counts.
**[[Forums#Rewards|There is no benefit to inflating one's post count anyway]].

<div id="TenboroPM"></div><div id="PMTenboro"></div>
*'''My PMs to [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] are not being answered!'''
**He receives a lot of them, please be patient.

*'''I accidentally deleted a private message!'''
**Unfortunately it is too difficult to restore individual PMs from the site's backups.
**It is best to maintain [https://forums.e-hentai.org/index.php?act=Msg&CODE=14 archives] of important PMs on your own.

*'''My sent PMs are not showing up in my 'Sent' folder!'''
**You must check off "Add a copy of this message to my sent items folder" when you send messages.

*'''My post / thread disappeared!'''
**They were likely deleted by a moderator due to rule violations.
**Do '''not''' repost the offending content.

*'''I don't receive notification e-mails for private messages!
**Email notifications have been disabled. [https://forums.e-hentai.org/index.php?showtopic=239754&st=0&p=5717185&#entry5717185]
***Username/Password recovery emails, and PM archives requested to be sent to the registered email, are still enabled.
***Registration emails are not sent. A valid email address is not required to register an account, albeit a valid email is recommended for recovery purposes.

*'''I receive a warning e-mail from the forum!'''
**The forum will send a warning to your original e-mail address whenever the password or e-mail associated with the account is changed.

*'''I cannot see the CAPTCHA for posting.'''
**Disable any software that blocks ads or scripts.
**Try with a different browser.

*'''I made a [[donation]] recently but don't see the corresponding [[awards]]!'''
*'''I'm missing a [[award|confectionery]]!'''
*'''I don't get the corresponding [[Dawn]] rewards!'''
**Refresh your account by performing an action such as changing [[HentaiVerse]], [[Gallery]], or [[My Home]] settings, custom forum title, or buying/selling from the [[GP Exchange]] or [[Hath Exchange]].

*'''"Sorry, your posting rights have been temporarily suspended. The suspension is due to end on {date}."'''
**You have been blocked from submitting new threads or replies temporarily. This restriction will automatically expire eventually. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**<span style="color:red">'''Further violation of the [[forum rules]] will lead to a permanent [[Bans|ban]].'''</span>

*'''"Your posting permissions have been removed"'''
**You have been banned from making new threads or replies. This is permanent.

*'''"You are not allowed to use the messenger feature on this board"'''
**You have been banned from sending private messages due to repeated harassment or spam sent to other users.

==[[Bounty]]==
*'''I cannot contribute [[GP]] to a bounty.'''
**You may only use [[Hath]] or [[Credits]]. Use the [[GP Exchange]] to convert your gallery points to credits.

*'''I cannot claim a bounty!'''
**Check if you have met the [[bounty#Hunter_Ranks|Hunter Ranks]]. Note that Unranked is above Rank D.
**The bounty may be closed (a [https://e-hentai.org/bounty.php?s=c pending claim] already exists or [https://e-hentai.org/bounty.php?s=r the bounty is reserved]). Check its status.

*'''I claimed a bounty but even after 7 days, the claim was not accepted.'''
**Working as intended (see above). The bounty poster may no longer dispute the claim but you should PM/contact them to remind them as accepts are manual to prevent abuse.

*'''I cannot rescind a reward!'''
**Rewards can only be rescinded within 15 minutes of posting, after 30 days or by cancelling the bounty if it is yours. They also cannot be rescinded if the bounty enters a closed status (Closed/Claimed or Closed/Reserved).

*'''Bounties do not properly value Hath.'''
**Hath to Credit conversion uses the [[Hath Exchange]] average over 24 hours<sup>verification needed</sup>, not a static amount of 5,000 credits per Hath - the minimal amount is intended as a guideline.

*'''I cannot set bounty restrictions above rank A.'''
**Working as intended. If you notice users of rank A or above claiming bounties in bad faith, PM them politely or report them in the relevant thread to let other users know.
**If accounts reach rank A unusually fast and then immediately start claiming bounties in bad faith, you should contact Tenboro to have him investigate and, if applicable, ban all involved accounts. Please be patient.

*'''The requested bounty was not found.'''
**If you get this message when clicking on a link from the [[forums]], the [https://e-hentai.org/logs.php?t=credits credit log] or a private message, the bounty does not exist or was deleted by the bounty poster or Tenboro.
**Bounties you contributed to will be immediately refunded when deleted.

*'''"You have been banned from posting bounties."'''
*'''"You have been banned from claiming bounties."'''
**You are no longer allowed to use certain function(s) of the [[bounty]] system. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

==[[EHTracker]]==
*'''My stats are not being tracked!'''
**Make sure you are using the personalized torrent and not the public one.
**You may have reset your personal key. Any torrents with older personal keys need to be re-downloaded.
***Seedmins only count towards torrents you created yourself.

*'''My stats stopped updating even though I'm seeding properly!'''
**This generally happens if you are disconnected while seeding and have a dynamic IP address.
**Stop all torrents, then resume them in order to force a tracker announce check.

*'''I'm seeding but not gaining any GP!'''
**This only occurs [[EHTracker#Rewards|if you are the torrent's or gallery's uploader]].

*'''"Torrent not found"'''
**All torrents for the gallery have been expunged.

*'''"Upload Error: Failed uploading file (code=4)."'''
**The server didn't receive any file. Try uploading with another browser.

*'''"Invalid auth"'''
**Refresh the page and try to upload the torrent again.

*'''"Torrent Error: This torrent is already uploaded for this gallery."'''
**You are trying to upload an exact duplicate of a torrent that already exists for that gallery.

*'''"Upload Error: You have too many recently uploaded torrents with no completions. Make sure your torrents are seeded before adding more."'''
**You have uploaded [https://ehwiki.org/wiki/EHTracker#Limits too many torrents with 0 completes].

*'''"You have been banned from uploading torrents."'''
**You are no longer allowed to upload any torrent to the tracker. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

==[[EHWiki]]==
*'''I'm not receiving a verification e-mail!'''
**You may change the e-mail address for the account and revalidate.

*'''I can't edit/create anything!'''
**You need to be in the 'Creator' group in order to edit/create pages. Please contact a [[E-Hentai Janitor|wiki admin]].

*'''I can't edit certain articles!'''
**Some articles are protected due to their importance or past abuse and thus cannot be edited by non-admins. Please [[E-Hentai Janitor|contact one of them]] if you have information to add/edit.

*'''I can't create an account!'''
**If your IP may be listed on the wiki's DNSBL.
**Change your IP and try again.

==See also==
*[https://forums.e-hentai.org/index.php?showforum=7 Forum - Site Discussion, Help & Feedback]

[[Category:Site Features]][[Category:E-Hentai Forums]][[Category:EHwiki]][[Category:HentaiVerse]][[Category:E-Hentai Galleries]]

Fetish Listing

2026-08-22T22:34:11Z

Kagoraphobia: /* Location */

A listing of all fetish/content tags usable in the E-Hentai [[galleries]], organized in different tag categories.

Unlike [[Talk:Gallery_Tagging#Content_Tag_Types | tag types]], tag categories have no influence on how a tag should be applied, and is only used for categorization purposes on this page.

==Age==
[[age progression]], [[age regression]], [[dilf]] ♂, [[infantilism]], [[kodomo doushi]], <span title="also 'low lolicon'" style="border-bottom:1px dotted">[[lolicon]]</span> ♀, [[milf]] ♀, [[old lady]] ♀, [[old man]] ♂, <span title="also 'low shotacon'" style="border-bottom:1px dotted">[[shotacon]]</span> ♂, [[toddlercon]]

==Body==
[[adventitious penis]], [[adventitious vagina]], [[amputee]], [[big muscles]], [[body modification]], [[body swap]], [[conjoined]], [[doll joints]], [[gijinka]], [[invisible]], [[multiple arms]], [[multiple breasts]] ♀, [[multiple nipples]], [[multiple penises]], [[multiple vaginas]] ♀, [[muscle]], [[muscle growth]], [[petrification]], [[shapening]], [[shrinking]], [[stretching]], [[tailjob]], [[transformation]], [[weight gain]], [[wingjob]], [[wings]]

===[[Change]]===
[[absorption]], [[age progression]], [[age regression]], [[ass expansion]], [[balls expansion]], [[body modification]], [[body swap]], [[breast expansion]], [[breast reduction]] ♀, [[clit growth]] ♀, [[corruption]], [[feminization]] ♂, [[futanarization]] ♀, [[gender change]], [[gender morph]], [[growth]], [[moral degeneration]], [[muscle growth]], [[nipple expansion]] ♀, [[penis enlargement]], [[penis reduction]], [[personality excretion]], [[petrification]], [[shrinking]], [[transformation]], [[weight gain]]

===Height===
[[giant]] ♂, [[giantess]] ♀, [[growth]], [[midget]], [[minigirl]] ♀, [[miniguy]] ♂, [[shrinking]], [[tall girl]] ♀, [[tall man]] ♂

===Skin===
[[albino]], [[bite mark]], [[body painting]], [[body writing]], [[crotch tattoo]], [[dark skin]], [[depth grading]], [[freckles]], [[gyaru]] ♀, [[gyaru-oh‎]] ♂, [[large tattoo]], [[lipstick mark]], [[oil]], [[scar]], [[skinsuit]], [[sweating]], [[tanlines]]

===Weight===
[[anorexic]], [[bbm]] ♂, [[bbw]] ♀, [[ssbbm]] ♂, [[ssbbw]] ♀, [[weight gain]]

==Head==
[[ahegao]], [[beauty mark]], [[brain fuck]], [[cockslapping]], [[crown]], [[ear fuck]], [[elf]], [[facesitting]], [[facial hair]], [[gasmask]], [[halo]], [[headless]], [[hood]], [[horns]], [[makeup]], [[masked face]], [[thick eyebrows]], [[tiara]]

===Hair===
[[afro]], [[bald]], [[drill hair]], [[eye-covering bang]], [[hair buns]], [[hairjob]], [[pixie cut]], [[ponytail]], [[prehensile hair]], [[shaved head]], [[twintails]], [[very long hair]]

===Mind===
[[body swap]], [[chloroform]], [[corruption]], [[drugs]], [[drunk]], [[emotionless sex]], [[mind break]], [[mind control]], [[moral degeneration]], [[parasite]], [[personality excretion]], [[possession]], [[shared senses]], [[sleeping]], [[yandere]]

===Eyes===
[[additional eyes]], [[blind]], [[blindfold]], [[closed eyes]], [[crying]], [[cum in eye]], [[dark sclera]], [[eye penetration]], [[eyemask]], [[eyepatch]], [[glasses]], [[heterochromia]], [[monoeye]], [[sunglasses]], [[unusual pupils]]

===Nose===
[[nose fuck]], [[nose hook]], [[smell]]

===Mouth===
[[adventitious mouth]], [[autofellatio]], [[ball sucking]], [[big lips]], [[blowjob]], [[blowjob face]], [[braces]], [[burping]], [[coprophagia]], [[cunnilingus]], [[deepthroat]], [[double blowjob]], [[foot licking]], [[gag]], [[gokkun]], [[kissing]], [[long tongue]], [[multimouth blowjob]], [[piss drinking]], [[rimjob]], [[saliva]], [[smoking]], [[split tongue]], [[tooth brushing]], [[unusual teeth]], [[vampire]], [[vomit]], [[vore]]

==Neck==
[[asphyxiation]], [[collar]], [[hanging]], [[leash]]

==Arms==
[[armpit licking]], [[armpit sex]], [[detached sleeves]], [[hairy armpits]], [[multiple arms]]

===Hands===
[[fingering]], [[fisting]], [[gloves]], [[handjob]], [[multiple handjob]]

==Chest==
===Breasts===
[[autopaizuri]] ♀, [[big areolae]], [[big breasts]], [[breast expansion]], [[breast feeding]], [[breast reduction]] ♀, [[clothed paizuri]], [[gigantic breasts]] ♀, [[huge breasts]] ♀, [[lactation]], [[milking]], [[multiple breasts]] ♀, [[multiple paizuri]] ♀, [[oppai loli]] ♀, [[paizuri]], [[small breasts]] ♀

====Nipples====
[[big nipples]], [[dark nipples]], [[dicknipples]], [[inverted nipples]], [[multiple nipples]] ♀, [[nipple birth]], [[nipple expansion]] ♀, [[nipple fuck]], [[nipple piercing]], [[nipple stimulation]]

==Torso==
[[cumflation]], [[inflation]], [[navel birth]], [[navel fuck]], [[pregnant]], [[stomach deformation]], [[weight gain]]

==Lower Body==
===Crotch===
[[bike shorts]], [[bloomers]], [[chastity belt]], [[crotch tattoo]], [[diaper]], [[fundoshi]], [[genital piercing]], [[gymshorts]], [[hairy]], [[hotpants]], [[mesuiki‎]], [[multiple orgasms]], [[pantyjob]], [[pubic stubble]], [[shimapan]], [[urethra insertion]]

====Penile====
[[adventitious penis]], [[ball caressing]], [[balls expansion]], [[ball-less shemale]] ♀, [[ball sucking]], [[balljob]], [[big balls]], [[big penis]], [[cbt]], [[cloaca insertion]], [[cockphagia]], [[cock ring]], [[cockslapping]], [[dickgirl on dickgirl]] ♀, [[dickgirl on female]] ♀, [[dickgirl on male]] ♂, [[dickgirls only]] ♀, [[frottage]], [[full-packaged futanari]] ♀, [[futanari]] ♀, [[futanarization]] ♀, [[horse cock]], [[huge penis]], [[male on dickgirl]] ♀, [[multiple penises]], [[no balls]] ♂, [[penis birth]], [[penis bumps]], [[penis enlargement]], [[penis reduction]], [[phimosis]], [[prostate massage]], [[retractable penis]], [[scrotal lingerie]], [[shemale]] ♀, [[small penis]], <span title="also 'low smegma'" style="border-bottom:1px dotted">[[smegma]]</span>

====Vaginal====
[[adventitious vagina]] ♀, [[big clit]] ♀, [[big vagina]] ♀, [[cervix penetration]] ♀, [[cervix prolapse]], [[clit growth]] ♀, [[clit insertion]], [[clit stimulation]], [[cunnilingus]], [[cuntboy]] ♂, [[cuntbusting]] ♀, [[defloration]] ♀, [[double vaginal]] ♀, [[multiple vaginas]] ♀, [[squirting]] ♀, [[strap-on]], [[tribadism]] ♀, [[triple vaginal]] ♀, [[unbirth]], [[vaginal birth]], [[vaginal sticker]] ♀

===Buttocks===
<span title="also 'focus anal'" style="border-bottom:1px dotted">[[anal]]</span>, [[anal birth]], [[anal intercourse]], [[analphagia]], [[anal prolapse]], [[ass expansion]], [[assjob]], [[big ass]], [[butt plug]], [[double anal]], [[enema]], [[farting]], [[multiple assjob]], [[multiple tails]], [[pegging]] ♂, [[rimjob]], <span title="also 'low scat'" style="border-bottom:1px dotted">[[scat]]</span>, [[spanking]], [[tail]], [[tailjob]], [[tail plug]], [[tailphagia]], [[triple anal]]

===Either Hole===
[[eggs]], [[gaping]], [[large insertions]], [[nakadashi]], [[prolapse]], [[sex toys]], [[speculum]], [[unusual insertions]]

==Legs==
[[garter belt]], [[kneepit sex]] ♀, [[leg lock]], [[legjob]], [[pantyhose]], [[stirrup legwear]], [[stockings]], [[sumata]]

==Feet==
[[denki anma]], [[foot insertion]], [[foot licking]], [[footjob]], [[high heels]], [[multiple footjob]], [[sockjob]], [[stirrup legwear]], [[tabi socks]], [[thigh high boots]]

==Creature==
[[alien]] ♂, [[alien girl]] ♀, [[angel]], [[bat boy]] ♂, [[bat girl]] ♀, [[bear boy]] ♂, [[bear girl]] ♀, [[bee boy]] ♂, [[bee girl]] ♀, [[bird boy]] ♂, [[bird girl]] ♀, [[bunny boy]] ♂, [[bunny girl]] ♀, [[catboy]] ♂, [[catgirl]] ♀, [[centaur]], [[corpse]], [[cowgirl]] ♀, [[cowman]] ♂, [[deer boy]] ♂, [[deer girl]] ♀, [[demon]] ♂, [[demon girl]] ♀, [[dog boy]] ♂, [[dog girl]] ♀, [[draenei]], [[elephant boy]] ♂, [[elephant girl]] ♀, [[fairy]], [[fox boy]] ♂, [[fox girl]] ♀, [[frog boy]] ♂, [[frog girl]] ♀, [[furry]], [[ghost]], [[giraffe boy‎]] ♂, [[giraffe girl‎]] ♀, [[goblin]], [[harpy]], [[hedgehog boy]] ♂, [[hedgehog girl]] ♀, [[hippo boy]] ♂, [[hippo girl]] ♀, [[horse boy]] ♂, [[horse girl]] ♀, [[human on furry]], [[hyena boy]] ♂, [[hyena girl]] ♀, [[insect boy]] ♂, [[insect girl]] ♀, [[kangaroo boy]] ♂, [[kangaroo girl‎]] ♀, [[kappa]], [[kemonomimi]], [[lizard girl]] ♀, [[lizard guy]] ♂, [[mermaid]] ♀, [[merman]] ♂, [[minotaur]] ♂, [[monkey boy]] ♂, [[monkey girl]] ♀, [[monoeye]], [[monster]] ♂, [[monster girl]] ♀, [[moth boy]] ♂, [[moth girl]] ♀, [[mouse boy]] ♂, [[mouse girl]] ♀, [[mushroom boy]] ♂, [[mushroom girl]] ♀, [[necrophilia]], [[oni]], [[orc]], [[otter boy]] ♂, [[otter girl]] ♀, [[panda boy]] ♂, [[panda girl]] ♀, [[pig girl]] ♀, [[pig man]] ♂, [[plant boy]] ♂, [[plant girl]] ♀, [[raccoon boy]] ♂, [[raccoon girl‎]] ♀, [[rhinoceros boy]] ♂, [[rhinoceros girl‎]] ♀, [[robot]], [[shark boy]] ♂, [[shark girl]] ♀, [[sheep boy]] ♂, [[sheep girl]] ♀, [[skeleton]], [[skunk boy]] ♂, [[skunk girl]] ♀, [[slime]], [[slime boy‎]] ♂, [[slime girl]] ♀, [[snail girl]] ♀, [[snake boy]] ♂, [[snake girl]] ♀, [[spider boy]] ♂, [[spider girl]] ♀, [[squid boy]] ♂, [[squid girl]] ♀, [[squirrel boy]] ♂, [[squirrel girl]] ♀, [[tentacles]], [[vampire]], [[wolf boy]] ♂, [[wolf girl]] ♀, [[yukkuri]], [[zombie]]

===[[Animal]]===
[[animal on animal]], [[animal on furry]], [[bear]], <span title="also 'low bestiality'" style="border-bottom:1px dotted">[[bestiality]]</span>, [[bull]] ♂, [[camel]], [[cat]], [[cow]] ♀, [[crab]], [[deer]], [[dinosaur]], [[dog]], [[dolphin]], [[donkey]], [[dragon]], [[eel]], [[elephant]], [[fish]], [[fox]], [[frog]], [[goat]], [[gorilla]], [[horse]], [[insect]], [[kangaroo]], [[lion]] ♂, [[lioness]] ♀, [[maggot]], [[monkey]], [[mouse]], [[octopus]], [[ostrich]], [[panther]], [[pegasus]], [[pig]], [[rabbit]], [[reptile]], [[rhinoceros]], [[shark]], [[sheep]], [[slug]], [[snake]], [[spider]], [[tiger]], [[turtle]], [[unicorn]], [[whale]], [[wolf]], [[worm]], [[zebra]]

==Costume==
[[animegao]], [[apparel bukkake]], [[apron]], [[bandages]], [[bandaid]] ♀, [[bat boy]] ♂, [[bat girl]] ♀, [[bike shorts]], [[bikini]], [[blindfold]], [[bloomers]], [[bodystocking]], [[bodysuit]], [[bride]], [[bunny boy]] ♂, [[bunny girl]] ♀, [[business suit]], [[butler]], [[cashier]], [[catboy]] ♂, [[catgirl]] ♀, [[cheerleader]], [[chinese dress]], [[christmas]], [[clothed female nude male]] ♂, [[clothed male nude female]] ♀, [[clown]], [[cock ring]], [[collar]], [[condom]], [[corset]], [[cosplaying]], [[cowgirl]] ♀, [[cowman]] ♂, [[crossdressing]], [[detached sleeves]], [[diaper]], [[dougi]], [[exposed clothing]], [[eyemask]], [[eyepatch]], [[fishnets]], [[fundoshi]], [[gag]], [[garter belt]], [[gasmask]], [[genital piercing]], [[glasses]], [[gloves]], [[gothic lolita]], [[gymshorts]], [[haigure]], [[headphones]], [[hedgehog boy]] ♂, [[hedgehog girl]] ♀, [[high heels]], [[hijab]], [[hotpants]], [[hyena boy]] ♂, [[hyena girl]] ♀, [[kemonomimi]], [[kigurumi pajama]], [[kimono]], [[kindergarten uniform]], [[kunoichi]], [[lab coat]], [[latex]], [[leash]], [[leotard]], [[lingerie]], [[living clothes]], [[magical girl]], [[maid]], [[mecha boy‎]] ♂, [[mecha girl]] ♀, [[metal armor]], [[miko]], [[military]], [[moth girl]] ♀, [[mouth mask]], [[mushroom boy]] ♂, [[mushroom girl]] ♀, [[nazi]], [[ninja]] ♂, [[nipple piercing]], [[nose hook]], [[nudism]], [[nun]], [[nurse]], [[painted nails]], [[pantyhose]], [[pasties]], [[piercing]], [[pirate]], [[policeman]] ♂, [[policewoman]] ♀, [[ponygirl]] ♀, [[priest]] ♂, [[race queen]] ♀, [[randoseru]], [[rhinoceros boy]] ♂, [[rhinoceros girl‎]] ♀, [[sarashi]], [[schoolboy uniform]], [[schoolgirl uniform]], [[school gym uniform]], [[school swimsuit]], [[scrotal lingerie]], [[shimapan]], [[stewardess]], [[steward]] ♂, [[stirrup legwear]], [[stockings]], [[straitjacket]], [[sundress]], [[sunglasses]], [[swimsuit]], [[tabi socks]], [[thigh high boots]], [[tiara]], [[tights]], [[tracksuit]], [[transparent clothing]], [[vaginal sticker]] ♀, [[waiter]], [[waitress]], [[wet clothes]], [[witch]]

==Multiple Activities==
[[bisexual]], [[double anal]], [[double blowjob]], [[double vaginal]] ♀, [[fff threesome]] ♀, [[ffm threesome]], [[fft threesome]] ♀, [[gang rape]], [[group]], [[harem]], [[layer cake]], [[mmf threesome]], [[mmm threesome]] ♂, [[mmt threesome]], [[mtf threesome]], [[multimouth blowjob]], [[multiple assjob]], [[multiple footjob]], [[multiple handjob]], [[multiple pairings]], [[multiple paizuri]] ♀, [[multiple straddling]], [[oyakodon‎]], [[shimaidon]], [[triple anal]], [[triple vaginal]] ♀, [[ttf threesome]] ♀, [[ttm threesome]], [[ttt threesome]] ♀, [[twins]]

===Multiple Holes===
[[all the way through]], [[double penetration]], [[triple penetration]]

==Tools==
[[blindfold]], [[butt plug]], [[clamp]], [[dakimakura]], [[gag]], [[glory hole]], [[hidden toy]], [[machine]], [[onahole]], [[pillory]], [[pole dancing]], [[real doll]], [[sex toys]], [[speculum]], [[strap-on]], [[syringe]], [[table masturbation]], [[tail plug]], [[tube]], [[unusual insertions]], [[vacbed]], [[whip]], [[wooden horse]], [[wormhole]]

==Fluids==
[[oil]], [[slime]], [[slime boy‎]] ♂, [[slime girl]] ♀, [[underwater sex]]

===Bodily Fluids===
[[blood]], [[crying]], [[lactation]], [[milking]], [[saliva]], [[squirting]] ♀

====Semen====
[[apparel bukkake]], [[bukkake]], [[cum bath]], [[cum in eye]] ♀, [[cum swap]] ♀, [[cumflation]], [[giant sperm]], [[gokkun]], [[nakadashi]]

<div id="Bodily Waste"></div>

====Waste====
[[coprophagia]], [[internal urination]], [[menstruation]] ♀, [[omorashi]], [[piss drinking]], [[public use]], <span title="also 'low scat'" style="border-bottom:1px dotted">[[scat]]</span>, [[scat insertion]], [[sweating]], [[urination]], [[vomit]]

==Force==
[[blackmail]], [[chikan]], [[confinement]], [[rape]], [[sleeping]], [[time stop]]

===Sadomasochism===
[[bdsm]], [[bodysuit]], [[blindfold]], [[clamp]], [[collar]], [[domination loss]], [[femdom]] ♀, [[food on body]], [[forniphilia]], [[human cattle]], [[ruined orgasm]], [[property tag]], [[josou seme]] ♂, [[latex]], [[orgasm denial]], [[petplay]], [[slave]], [[smalldom]], [[tickling]]

===Bondage===
[[bondage]], [[fanny packing]], [[gag]], [[harness]], [[pillory]], [[ponygirl]], [[shibari]], [[straitjacket]], [[stuck in wall]], [[suspended]], [[vacbed]]

===Violence===
[[abortion]], [[bite mark]], [[blood]], [[cannibalism]], [[catfight]] ♀, [[cbt]], [[cuntbusting]], [[dismantling]], [[electric shocks]], <span title="also 'low guro'" style="border-bottom:1px dotted">[[guro]]</span>, [[ryona]], [[snuff]], [[torture]], [[trampling]], [[whip]], [[wrestling]]

==Privacy==
[[exhibitionism]], [[filming]], [[forced exposure]], [[hidden sex]], [[humiliation]], [[voyeurism]]

==Self Pleasure==
[[autofellatio]], [[autopaizuri]] ♀, [[clone]], [[masturbation]], [[phone sex]], [[selfcest]], [[solo action]], [[table masturbation]]

==Disability==
[[amputee]], [[blind]], [[handicapped]], [[mute]]

==Consumption==
[[absorption]], [[analphagia]], [[breast feeding]], [[cannibalism]], [[cockphagia]], [[coprophagia]], [[full tour]], [[gokkun]], [[piss drinking]], [[tailphagia]], [[vore]], [[weight gain]]

==Gender==
[[cuntboy]] ♂, [[feminization]] ♂, [[futanari]] ♀, [[gender change]], [[gender morph]], [[otokofutanari]] ♂, [[shemale]] ♀

===Inter-gender Relations===
[[bisexual]], [[dickgirl on dickgirl]] ♀, [[dickgirl on female]] ♀, [[dickgirl on male]] ♂, [[fft threesome]] ♀, [[male on dickgirl]] ♀, [[mmt threesome]], [[mtf threesome]], [[ttf threesome]] ♀, [[ttm threesome]], [[yaoi]] ♂, [[yuri]] ♀

==[[Contextual]]==
[[blackmail]], [[coach]], [[confinement]], [[defloration]] ♀, [[dickgirls only]] ♀, [[females only]] ♀, [[impregnation]], [[kodomo only]], [[males only]] ♂, [[mesugaki]], [[no penetration]], [[nudity only]], [[object insertion only]], [[oyakodon‎]], [[prostitution]], [[pussyboys only]] ♂, [[shimaidon]], [[sole dickgirl]] ♀, [[sole female]] ♀, [[sole male]] ♂, [[sole pussyboy]] ♂, [[teacher]], [[tomboy]] ♀, [[tomgirl]] ♂, [[tutor]], [[virginity]] ♂, [[vtuber]], [[widow]] ♀, [[widower]] ♂, [[yandere]]

===Infidelity===
[[cheating]], [[netorare]], [[netorase]], [[swinging]]

===Incest===
[[aunt]] ♀, [[brother]] ♂, [[cousin]], [[daughter]] ♀, [[father]] ♂, [[granddaughter]] ♀, [[grandfather]] ♂, [[grandmother]] ♀, [[incest]], [[inseki]], [[mother]] ♀, [[niece]] ♀, [[sister]] ♀, [[uncle]] ♂

==[[Location]]==
[[bathing room]], [[beach]], [[classroom]], [[infirmary]], [[onsen]], [[sauna]], [[sentou]], [[swimming pool]]

==Low Presence==
[[low bestiality]], [[low guro]], [[low incest]], [[low lolicon]] ♀, [[low scat]], [[low shotacon]] ♂, [[low smegma]]

==High Presence==
[[focus anal]], [[focus blowjob]], [[focus cunnilingus]], [[focus handjob]], [[focus paizuri]], [[focus rimjob]]

==[[Gallery-Wide]]==
[[dickgirls only]] ♀, [[females only]] ♀, [[full censorship]], [[full color]], [[kodomo only]], [[males only]] ♂, [[mosaic censorship]], [[no penetration]], [[non-nude]], [[nudity only]], [[object insertion only]], [[pussyboys only]] ♂, [[sole dickgirl]] ♀, [[sole female]] ♀, [[sole male]] ♂, [[sole pussyboy]] ♂, [[themeless]], [[uncensored]], [[variant set]]

==[[Format]]==
[[3d imageset]], [[anthology]], [[artbook]], [[comic]], [[goudoushi]], [[how to]], [[multi-work series]], [[non-h game manual]], [[non-h imageset]], [[sample]], [[soushuuhen]], [[story arc]], [[tankoubon]], [[western cg]], [[webtoon]], [[western non-h‎]], [[western imageset]]

==Technical==
[[3d]], [[ai generated]], [[anaglyph]], [[animated]], [[caption]], [[extraneous ads]], [[figure]], [[first person perspective]], [[full color]], [[multipanel sequence]], [[novel]], [[original]], [[paperchild]], [[pixel art]], [[redraw]], [[screenshots]], [[sketch lines]], [[stereoscopic]], [[themeless]], [[variant set]], [[various]], [[x-ray]]

===Censorship===
[[full censorship]], [[mosaic censorship]], [[uncensored]]

===[[Cosplay]]===
[[hardcore]], [[non-nude]]

===[[Expunging]]===
[[already uploaded]], [[defaced]], [[forbidden content]], [[realporn]], [[replaced]]

====Semi-[[Expunging]]====
[[compilation]], [[incomplete]], [[missing cover]], [[out of order]], [[sample]], [[scanmark]], [[watermarked]]

===Language===
[[afrikaans]], [[albanian]], [[arabic]], [[aramaic]], [[armenian]], [[bengali]], [[bosnian]], [[bulgarian]], [[burmese]], [[catalan]], [[cebuano]], [[chinese]], [[cree]], [[creole]], [[croatian]], [[czech]], [[danish]], [[dutch]], [[english]], [[esperanto]], [[estonian]], [[finnish]], [[french]], [[georgian]], [[german]], [[greek]], [[gujarati]], [[hebrew]], [[hindi]], [[hmong]], [[hungarian]], [[icelandic]], [[indonesian]], [[irish]], [[italian]], [[japanese]], [[javanese]], [[kannada]], [[kazakh]], [[khmer]], [[korean]], [[kurdish]], [[ladino]], [[lao]], [[latin]], [[latvian]], [[marathi]], [[mongolian]], [[ndebele]], [[nepali]], [[norwegian]], [[oromo]], [[papiamento]], [[pashto]], [[persian]], [[polish]], [[portuguese]], [[punjabi]], [[romanian]], [[russian]], [[sango]], [[sanskrit]], [[serbian]], [[shona]], [[slovak]], [[slovenian]], [[somali]], [[spanish]], [[swahili]], [[swedish]], [[tagalog]], [[tamil]], [[telugu]], [[thai]], [[tibetan]], [[tigrinya]], [[turkish]], [[ukrainian]], [[urdu]], [[vietnamese]], [[welsh]], [[yiddish]], [[zulu]]

====Meta-Language====
[[rewrite]], [[rough grammar]], [[rough translation]], [[text cleaned]], [[textless narrative]], [[translated]]

==See also==
*[[Gallery Tagging]]
*[[:Category:Tag|Alphabetical Listing]]

{{EHGNav}}

[[Category:E-Hentai Galleries]]

Template:NewTags

2026-08-22T22:32:22Z

Kagoraphobia:

*[[swimming pool]]<small><sup>'''N'''</sup></small>
*[[textless narrative]]<small><sup>'''C'''</sup></small> (tag rename; was called [[speechless]])
*[[gender change]]/[[gender morph]]<small><sup>'''C'''</sup></small> (Clarification)
*[[focus handjob]]<small><sup>'''N'''</sup></small>
*[[hippo boy]]/[[hippo girl]]<small><sup>'''N'''</sup></small>
*[[animated]]<small><sup>'''C'''</sup></small>
*[[mushroom girl]]/[[mushroom boy]]<small><sup>'''N'''</sup></small>
*[[hanging]]<small><sup>'''C'''</sup></small>
*[[suspended]]<small><sup>'''N'''</sup></small>
*[[hidden toy]]<small><sup>'''N'''</sup></small>
[[Category:E-Hentai Galleries]]

swimming pool

2026-08-22T22:31:38Z

Kagoraphobia: Created page with "{{ContentTag |type=Location |subtype1=Location |description=One or more participants explicitly nude or having sex/sexual activity in or around a swimming pool. |note=Only applicable when the pool is large enough to swim in. Small inflatable pools do not qualify. :::Scenes occurring inside an enclosed space (e.g., a tent or shed) despite being near the pool do not count towards presence. |japanese=スイミングプール |loctaggroupid=521180 }}"

{{ContentTag
|type=Location
|subtype1=Location
|description=One or more participants explicitly nude or having sex/sexual activity in or around a swimming pool.
|note=Only applicable when the pool is large enough to swim in. Small inflatable pools do not qualify.
:::Scenes occurring inside an enclosed space (e.g., a tent or shed) despite being near the pool do not count towards [[presence]].
|japanese=スイミングプール
|loctaggroupid=521180
}}

Making Galleries/Chinese

2026-08-17T22:47:35Z

Kagoraphobia: /* 更新 */

[[Category:E-Hentai_Galleries/Chinese]]
對於上傳畫廊的指南

= 檢查 =

=== 在上傳之前: ===

* 請確認不存在'''[[Expunging/Chinese|禁止上傳]]'''的內容；這主要取決於內容的出版方。
* 檢查一下內容是否已經上傳過了。所有被標記為“可見”的畫廊被認為存在於系統之中。對於[[Gallery Categories#Image Set|圖片集]]分類的畫廊，這一步一般不重要。
** 檢查的方式包括：
*** [[Gallery_Searching/Chinese|搜索]]畫廊的標題，藝術家，或是可接受的[[Gallery_Tagging/Chinese#標簽目錄|標籤]]
*** 對至少一件圖畫進行[[Gallery_Searching/Chinese#文件搜索|文件搜索]]
*** 使用內部圖像搜索的方法，比如在[[Search Guide|搜索指南]]里列出的方法
** 如果是為了替換一個已存在的畫廊，那麼請確保上傳的內容是[[Expunging/Chinese#替換|更優的版本]]。請不要上傳放大後的圖像。
* 在上傳之前請移除任何空白的圖像
* 畫廊如果是包含已存在完整作品的[[compilation/Chinese|編纂]]則有被[[Expunging/Chinese|剔除]]的風險。 [[Gallery_Categories/Chinese#圖片集|圖片集]]分類的畫廊應當僅含有未出現在作者已出版的作品當中的零散圖片。
* 給圖畫排序，並移除任何夾雜的圖片（如[[Gallery_Categories/Chinese#角色扮演|角色扮演]]，[[Gallery Categories/Chinese#多功能類|3D]]和描畫圖片不應當出現在同類別的畫廊中，東方和[[Gallery_Categories/Chinese#西方|西方作者]]的圖像同樣地不應混合。）給畫廊[[Gallery_Categories/Chinese|分類]]是有理由的。

=== 文件名稱 ===

* 在適用的情況下，請再檢查一遍圖畫的順序是否正確。
** 最好是將圖畫的文件名命名為方便機器排序的名稱，推薦為三位的數字，如001.jpg，002.jpg之類。 [http://www.bulkrenameutility.co.uk/Download.php Bulk Rename Utility] 或是 [https://www.advancedrenamer.com/ Advanced Renamer]等軟件可以批量更改文件名稱。
* 文件名稱只能包含英文字母，橫線和下劃線。任何非[https://en.wikipedia.org/wiki/ASCII ASCII]字符會被忽略。
** 對於含有其他字符的圖片，可能會在不顯示錯誤信息的情況下不被畫廊系統接受。請在添加新文件之前在發布準備頁面檢查一下。文件的非ASCII字符名稱會顯示成[https://en.wikipedia.org/wiki/Mojibake 亂碼]並且可能會導致文件在不出現任何錯誤的情況下消失。
** 如果文件夾的原始名稱包含任何有用的原始信息，請保持它們不變，但使用下劃線或橫線來分隔。

== 上傳 ==

# 點擊 "[[My Galleries/Chinese|My Uploads]]"
# 點擊 "[https://upld.e-hentai.org/managegallery?act=new Create New Gallery]"
# 填寫足夠的信息（[[Renaming/Chinese|名稱]]和畫廊的[[description|描述]]）。每一個畫廊都必須要有英文/羅馬字的主標題。日文的標題（對於非亞洲作者作品）'''並非'''必須，如果不清楚要填什麼可以留空。
# 選擇畫廊所屬的[[Gallery Categories/Chinese|分類]]。
#* 默認的分類是[[Gallery Categories/Chinese#同人誌|同人誌]]，對於其他類型的畫廊請切換的正確的分類。
#* [[Gallery_Categories/Chinese#私人畫廊|Private/Unlisted]]分類只對最低開啟銅星的[[Donation/Chinese|捐贈]]者開放。
# 選擇[[Languages|語言]]。
#* 默認的語言類別是日語/其他,請切換到正確的分類。
#**如果選擇翻譯，則有指定本畫廊是否為熟練翻譯者人工翻譯（非機翻）的額外的確認框以備勾選。
#***[[Image:Point.png]]長期錯標或者故意錯標新手翻譯畫廊為“熟練人工翻譯”可能會影響用戶在以後上傳時勾選這個選框的能力。
#* 在畫廊發布之後將無法變更語言選項，僅能通過貼語言[[Gallery_Tagging/Chinese|標籤]]來更改。
#** 如果某個語言標籤被錯誤地貼上了，請到論壇的[https://forums.e-hentai.org/index.php?showtopic=274004 這個地方]申請移除這個標籤。
#* 無對話標籤（[[textless narrative|Textless Narrative]]）不適用於[[imageset|Image set]]，[[Game CG]] 或是其他沒有明顯可見的故事的畫廊。
#* 翻譯標籤（[[translated|Translated]]）不適用於第一方接受的翻譯的畫廊。
# 為你的畫廊選擇一個歸類的文件夾。默認文件夾是“Unsorted”，這個動作只影響畫廊在“[[My Galleries/Chinese|My Galleries]]”裡的位置。
# 請點擊“您已閱讀並同意e-hentai.org的[https://e-hentai.org/tos.php 服務條款]”
# 添加圖像或是zip壓縮包以充實畫廊的內容，最多可以添加2000張圖像。然後點擊“Start Upload” 按鈕。
# 等待上傳完成。網頁會在完成後自動保存並刷新。上傳帶寬較小的用戶應當多次上傳較少的內容。
#* 有完全同樣文件名的重複圖像會在上傳時被自動移除。
# 可以在底部的“Sorting Methods”裡選擇一種排序方式。選擇自然排序（Nature Sort）或是詞項排序（Lexical Sort），然後點擊進行自動排序（Perform Auto Sort）。
#* 文件名不同的重複的圖像可以在排序選項裡選擇“Remove Exact Duplicates”來移除。
#* 更新畫廊時有更多的排序選項。可以選擇按圖畫添加的日期來進行自然排序或是詞項排序，或是保持當前的順序。
#* 檢查添加的內容，添加，移除，或者重新排序任何圖像。點擊“應用更改”（apply change）來鎖定變更後的順序。
# 當你對畫廊的內容滿意後，點擊“Publish Gallery”來發布畫廊。 '''這麼做之後發布者承認“此畫廊發布後屬於社區”'''。
#* 如果上傳者希望將他們的名字從畫廊中移除，則可以在畫廊管理頁面中選擇”捨棄此畫廊“（disown）。上傳者捨棄畫廊後，其名字會在畫廊發布一周後移除，但是可以在畫廊發布之後任意時段捨棄。發布超過一周的畫廊在被上傳者捨棄之後上傳者的名字會被立刻移除。
#**[[Image:Point.png|link=]] 捨棄的畫廊會從上傳者的畫廊管理頁面中消失，並且它將再也無法被編輯。此效果立即生效，無論何時發布。

在畫廊發布之前無論何時對畫廊做的變更都可以通過點擊”save changes“按鈕來保存。（除了上傳文件，這個由系統自動保存）當畫廊發布之時，需要等待一段時間才會出現在畫廊列表中。即便如此，畫廊依然可以通過它的鏈接直接訪問。畫廊的小號縮略圖會在新發布或是更新後的畫廊的縮略圖生成後自動作成。注：存放超過365天的未發布的畫廊會被畫廊管理員刪除。對畫廊進行任何形式的更新將會重置這個365天的計數器。事實上，只需要點擊”save change“按鈕即可，不需要實際上的更新。

=== 限制 ===

* 各種允許的文件格式以及他們的單個文件大小限制：

{| class="wikitable"
!格式
!文件大小
|-
|GIF || 10MB
|-
|<span title="JPEG 會自動重命名至 JPG" style="border-bottom:1px dotted">JPG</span> || 20MB
|-
|WEBP || 20MB
|-
|<span title="PNG文件會重采樣至WEBP，見下" style="border-bottom:1px dotted">PNG</span> || 50MB
|}

* 圖像分辨率必須至少為100 x 100（總像素數不得少於251）；最大不超過20,000 x 20,000。大號縮略圖將會被縮放到200 x 300合適大小的WEBP圖像 (封面為250 x 375)。
** 超過2,400px寬或大於10MB的圖像會被縮小，重新採樣並且如果可用的話，為默認視圖轉換為WEBP格式。
** 超過文件大小限制的圖像可能會因壓縮文件大小而被轉換成其他文件（可能因此造成圖像質量的損失）。畫廊[[description|描述]]裡必須陳述這一事實，並應在[[EHTracker/Chinese|種子]]裡提供畫廊的原始文件。
* 單個畫廊最大容納2000張圖片。
** 對於超過2000張圖片的完整作品，可以允許為此作品添加多個畫廊。每個畫廊裡的圖像順序必須被合理分配。
* 儘管本站允許上傳GIF動圖，但是沒有對APNG的支持。 PNG動圖在默認視圖下會被轉換成WEBP。如可能的話推薦上傳GIF格式的動圖，並在種子裡包含畫廊所代表的源文件。
* 單個畫廊最大允許的大小為10GB。
* 每一個上傳者都有一個上傳限制。這個限制取決於最近上傳的量與該上傳者歷史上傳的有質量的畫廊的比值。這個參數決定了每個上傳者可以陸續上傳的畫廊的數量。如果上傳者達到了這個限制，那麼他們需要等待一段時間才能繼續上傳新的畫廊。 '''Private/Unlisted'''分類不計算在”有質量的畫廊”之內。([https://forums.e-hentai.org/index.php?s=&showtopic=252404&view=findpost&p=6011165 Ref])

=== 壓縮包 ===

* 允許的壓縮包格式：ZIP
**[[Image:Point.png]] '''強烈建議不要把多個文件夾放置在同一壓縮包內。'''上傳者應當對每個文件夾僅創建一個zip包，並按順序上傳它們。這樣可以預防出現[[out of order|亂序]]的問題。
*** 如果同時上傳多個文件夾，請確保每個文件夾內的文件都是必須的，並且文件沒有重名。受到ZIP壓縮技術的限制，壓縮包內重名的文件不會被上傳。
** 壓縮方式應當為 Deflate，LZMA，PPMd或者無壓縮。文字長度不應超過32字符，不允許對壓縮包加密。
* 每個單次上傳動作最大允許的大小是<span title="524,288,000 bytes / 0.48 GB" style="border-bottom:1px dotted">500MB</span>。一次性上傳超過這個大小會導致上傳靜默失效並且當完成時自動被捨棄。

== 更新 ==
對於畫廊的全部變更都可以在[[My_Galleries/Chinese|My Galleries]]裡完成。

* 畫廊的[[description|描述]]可以隨時變更。
** 畫廊的[[Gallery_Categories/Chinese|分類]]只能在發布後24小時內變更，之後只能通過標籤。
** 發布之後的畫廊不可變更為 '''Private/Unlisted''' 分類。
** 當父畫廊為公開狀態時，子畫廊的分類不可變更，並且只能通過[[Gallery_Tagging/Chinese#Categories|分類標籤]]進行變更。
**'''Private/Unlisted''' 分類的畫廊可以隨時變更分類。
** 被標籤重新分類的畫廊不能再在畫廊管理頁面變更它的分類。如果還需要變更其分類，只能貼上新的[[Gallery Tagging/Chinese#Categories|分類標籤]]。
* 畫廊的名稱在畫廊公開發布 24 小時後，或一個[[Renaming/Chinese|更名投票]]通過後就不可再在畫廊管理頁面裡編輯。如仍需變更名稱，請發起新的更名投票，且票數必須高於當前的名稱。
* 當畫廊完成添加，移除，重新排列圖像之後，會在原有畫廊的基礎上創建新的子畫廊。子畫廊會在發布之時立即替換父畫廊，並且完全繼承父畫廊的名稱，[[Gallery_Tagging/Chinese#標簽目錄|標籤]]，[[Favorites/Chinese|收藏數]]，[[ratings|評分]]，畫廊描述以及[[Gallery_Commenting/Chinese|評論區]]。
** 在畫廊描述裡記錄變更內容是一種禮節。
** [[Image:Point.png|link=https://ehwiki.org/wiki/File:Point.png]] '''頂貼限制：''' 為防止濫用，在30天內更新超過兩次的畫廊會被鎖定。
*** 例外：
**** 任何合法的畫廊內容質量更新，如進行中的漫畫/CG 包，或是進行中的翻譯工作。這些都必須以作者/翻譯者的進度為準。
**** 任何為修復畫廊移除性的修復性操作，如刪除禁止上傳的圖像等。

=== 老舊畫廊 ===
任何畫廊在發布後365天后會成為老舊的畫廊。這些畫廊不能再進行任何更新。任何有必要的更新必須重新上傳新的畫廊然後取代舊的畫廊。新上傳的畫廊是全新的獨立畫廊，並且不會與舊畫廊產生父子鏈接。

== [[EHTracker/Chinese|做種]] ==

* 任何用戶都可以為已經上傳的畫廊做種。這些種子文件可以包含不存在於畫廊中的文件。
** 種子包含的文件必須遵守[https://e-hentai.org/tos.php 相關規則]並且必須與畫廊有關。任何對種子系統的濫用會導致封禁
** 做種的用戶並不必須是畫廊的上傳者。

== [[Rewards/Chinese|獎勵]] ==
畫廊的每一次訪問都會獎勵上傳者[[Gallery_Points/Chinese|GP]]。上傳者'''不會'''收到畫廊的獎勵，除非畫廊在發布經過4小時之後並且沒有被[[Expunging/Chinese|剔除]]。在畫廊得到足夠的訪問次數，上傳者會在上傳者/畫廊[[Toplists/Chinese|排行榜]]中獲取他的名次。

=== [[Bounty_System/Chinese|賞金]] ===
如果有人針對某個畫廊發布了賞金，不要忘了提醒上轉者去收取賞金。

== 發布之後 ==

* 所有正式的作品必須盡可能接近作者的原版出版物。
* 不受支持的文件格式，如BMP和PPM必須被轉換成同等分辨率的PNG格式圖片。
** 如果都是作者的原版作品，上傳混合的JPG和PNG是允許的。
** 文件的大小應當保持在合適的範圍。為了通過上傳文件的大小限製而壓縮圖片是可以允許的，但是[[EHTracker/Chinese|種子]]裡必須包含原版文件而不是被壓縮的版本。
** PDF文件不應被轉換為[[Expunging/Chinese#更優的版本|放大]]的圖片。（比如原文件分辨率是1360x1920，那就不應上傳4534x6405）。推薦在畫廊裡上傳最合適的圖片大小，但在種子裡提供pdf文件。

== 參見 ==

* [[My_Galleries/Chinese|My Galleries]]
* [[E-Hentai_Galleries_FAQ/Chinese#上傳|FAQ - 上傳]]
* [[Technical_Issues/Chinese#你的畫廊|技術問題 - 你的畫廊]]

{{ChineseEHGnav}}

potential no text

2026-08-17T13:59:24Z

Kagoraphobia: Created page with "<!--{{ContentTag |nopreremind=true |type=Technical |subtype1=Technical |description=The gallery was tagged with textless narrative, previously named "speechless". This technical tag may be useful as a filter for those who wish to contribute to tagging japanese on older galleries. |note=Cannot be voted on by users. Designated to be hidden from view after a year. It will remain searchable by using the [https://e-hentai.org/?f_search=other%3A%22potential+no+text%24%..."

E-Hentai Janitor

2026-08-14T11:37:09Z

Kagoraphobia: username change

Certain members have been given special abilities or access to restricted tools due to their expertise and/or historic diligence and willingness to help make E-Hentai a better place.

Tag vetoers will be classed as "inactive" under [[Talk:E-Hentai Janitor| certain conditions]]. These users are indicated with a gray <span style="opacity:0.3">✔</span>.

Removal of janitor role(s) is generally done due to extended inactivity or by own request. Re-assignment is possible should the user return from inactivity.

{| class="wikitable sortable" width="100%" style="text-align: center"
! rowspan="2" |Name
! rowspan="2" width="12%" |[[Forum]] Mod
! rowspan="2" |[[IRC]] Op
! rowspan="2" |[[EHWiki]] Admin
! colspan="3" |[[Tagging]]
! colspan="2" |[[namespace|Namespacer]]
! colspan="4" |[[Galleries]]
! rowspan="2" |Additional
|-
! width="6.5%" |Cleaning!!Vetoing!!Checking
! width="6.5%" |Approving!!Grouping
! width="6.5%" |Expunging!!Locking!!Moderating!!Banning
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4791588 -Lumina-]|| || || ||✔|| || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=243587 Binglo]|| || ||✔||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=485420 BlackHimari]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3201420 Byza]||<span title="The Vigilante" style="border-bottom:1px dotted">Section</span>|| || ||✔||✔||✔||✔||✔
|✔||✔||✔ || ||ES-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=359756 chriseras]|| ||✔|| || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1207129 Cipher-kun]|| || || ||✔||✔||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=95571 CornerCactus]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1908893 Dnkz]|| || || ||✔||✔||✔||✔||
|✔||✔||✔|| ||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=5845370 Doof071]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2115725 Eboshi]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||KR-EN<br>JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4103205 ehaa]|| || || || || || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2790 elgringo]|| ||✔|| ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=367313 ericeric91]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=384226 EsotericSatire]||<span title="Adult Chat, Anime & Manga Chat, Culture Corner, Gamers Chat, Tech Chat" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=6011981 Feftak]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3737344 Glovelove.]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=561643 jm320]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4850902 Kagoraphobia]||Global||✔||✔||✔||✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge<br>CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7508384 krvn64]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=560909 Mags_]|| || || || || || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=589675 Maximum_Joe]|| || || || || || || ||
| || || || ||''<span title="Thank you for everything you have done for the site. Rest in peace, Joe." style="border-bottom:1px dotted">Retired</span>''
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=204246 meow_pao]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1898816 Mrsuperhappy]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3655031 Muffinlemon]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3169265 nasu]||<span title="Site Discussion & Helpdesk, The Vigilante" style="border-bottom:1px dotted">Section</span>
| || ||✔||✔||✔||✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=867559 Nezu]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2977124 Noni]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>||✔|| || || ||✔||✔||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=600260 noones]|| || || || || || ||✔||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=892479 peterson123]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3139892 poiuytrewqazx]|| || || ||✔|| || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=958849 rinruririn]||<span title="Introduction, Site Discussion & Helpdesk, The Vigilante, Requests and Bounties" style="border-bottom:1px dotted">Section</span>
| || ||✔|| || || ||
| ||✔|| || || JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1913944 Rogabute]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=989173 Shank]||Global||✔||✔||✔||✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2714686 shiluo]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1732804 simplesimon32]|| ||✔|| ||✔|| || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=352564 SIRIUSs]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2203 Spectre]||Global|| ✔|| ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=976341 svines85]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4842635 terry]||Global|| || ||✔||✔||✔||✔||✔
|✔||✔||✔||✔||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=582527 TheGreyPanther]|| || || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1194701 tobeunforgiven2]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3172187 Waitugreat]|| || || || || || || ||
| ✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=374857 海想列車]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7752125 雪莉酱]|| || || || || || ||✔||
| || || || ||
|}

==Explanations==
Some janitor roles come with implicit permission(s), which may be seen [[Talk:E-Hentai_Janitor|here]].
{| class="wikitable"
!Position
!Capabilities
|-
|Forum Mod||Edit or delete [[forum]] posts. Global Mods can impose posting restrictions on accounts with severe [[forum rules]] violations.
|-
|IRC Op ||Kick or ban users from the [[IRC]] channel.
|-
|EHWiki Admin ||Manage wiki editing permissions. Can also edit pages that are marked as protected.
|-
|Tag '''Cleaning'''||Users with this privilege are able to:
*Downvote tags at full [[power]].
* Bypass the minimum MP requirement for downvoting locked-in solid tags.
*Cancel out implied language tags from the uploader [[Making_Galleries#Uploading|language setting]] with a -100 [[power]] downvote.
*Have elevated voting power (3 votes) in [https://forums.e-hentai.org/index.php?showforum=89 tag suggestions].
|-
|Tag '''Vetoing'''||These users are given additional tagging privileges:
*[[Tagging_Mechanics#Tag_Veto|Veto/Enforce]] tags on a gallery, preventing them from being resurrected or killed respectively.
* Bypass the minimum MP requirement for reviving downvoted tags.
*Vote against incorrectly vetoed/enforced tags.
*Bypass the MP requirement of [[:Category:Power_Restricted|power-restricted]] tags.
*Bypass whitelists for certain special tags (e.g., [[rough translation]]).
*Instantly remove [[rough translation]] tags added by autotagger.
*Create temp tags even without meeting the [[power|power requirement]] (i.e., 25).
*Participate in the [https://forums.e-hentai.org/index.php?showtopic=136551 community veto] process presuming the user is an [[Talk:E-Hentai_Janitor| active tag vetoer]].
|-
|Tag '''Checking'''||View any user's or gallery's [[Gallery_Tagging#Tag_History|tag histories]].
|-
|Namespacer - '''Approving'''||Approve, rename, and set [[namespace]]s on the pending tags from the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Namespacer - '''Grouping'''||[[slave tag|Group tags]], as well as set blocks, [[namespace]]s, and aliases on any existing tags. Can also reject pending tags on the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Galleries '''Expunging'''
|Start an [[expunge]] on a gallery that has previously been de-expunged by the community or administration. Can also file an [[Expunging#Appeal_an_Incorrect_Expunge|appeal]] on aged expunges.
|-
|Galleries '''Locking'''|| Lock galleries with any depictions of real children, or other illicit content (e.g., real-life snuff and gore).
|-
|Galleries '''Moderating'''||Moderators with the following gallery privileges:
*Receive a base [[power]] boost of +10.
* Block further [[Making_Galleries#Updating|updates]] on galleries that are excessively bumped.
* Delete malicious [[EHTracker#Expunges|torrents]].
*Both [[comment]] and vote on other comments in the same gallery.
*Permanently hide gallery comments with a downvote, assuming they have reached -100 [[power]].
*Review recently posted comments that have been [[Gallery_Commenting#Perma-Hidden_Comments|permanently hidden]].
*Check the original ownership of a [[disowned]] gallery.
*Enforce the [[AI Generated]] indicator when it is falsely denied by the uploader.
*Add [[rough translation]] without a detailed comment when the work is [[Talk:rough translation|clearly a machine/AI translation]].
|-
|Galleries '''Banning'''||Restrict users from performing certain gallery activities due to major site rule violations (e.g., spamming). All [[Bans|ban]] actions will be reviewed by the administration.
|-
|Tag Judge ||Make judgement calls on [[Fetish_Listing|fetish/content tags]].
|-
|<span title="Quality Control" style="border-bottom:1px dotted">QC</span> Judge||Make judgement calls on [[Expunging#Superior_Versions|gallery superiority]].
|-
|Rename Judge||Make judgement calls on [[renaming]].
|-
|JP-EN||Heightened trust in Japanese-English translations/transliterations.<br>Similar positions exist for other languages (CN-EN, ES-EN, KR-EN).
|}

[[Category:Users]]

E-Hentai Forums

2026-08-12T18:05:29Z

Kagoraphobia: /* Subforums */

The [https://forums.e-hentai.org/index.php?act=idx E-Hentai Forums] are the current social gathering place for all members and guests of E-Hentai.org.

==Signing Up==
Registering is free and uses no confirmation e-mail. All forums accounts function for use in the [[galleries]].

[[Image:Point.png]] '''<span style="color:red">Only 1 active account is permitted per person. Multi-accounting will result in a total [[Ban| ban]].</span>'''

==Subforums==
{|class="wikitable"
|+
!Subforums
!Description
|-
|colspan="2" align="center"|'''E-Hentai BBS Forums'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=5 Forum Rules & FAQs]
|
*Rules pertaining to E-Hentai; users with questions are advised to use other subforums.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=3 Introductions]'''
|
*New users may introduce themselves here.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=4 Test Forum]'''
|
*Test signatures, bbcode, or anything else here.
|-
|colspan="2" align="center" |'''E-Hentai Website Forums'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=2 E-Hentai News and Updates]'''
|
*Official site announcements.
*Threads will be locked once a newer update supersedes the older ones or when events have ended.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=7 Site Discussion & Feedback]'''
|
*Suggestions for site features, [[technical issues]], or for bug reports.
*Pornographic images and upload requests should not be posted here.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=74 The Vigilante]'''
|
*[[Expunging]], [[tagging]], [[renaming]], and other [[gallery]] cleanup coordination.
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=89 Tag Suggestions]'''
|
*Proposals for new [[Fetish Listing| fetish/content tags]], and definition adjustments.
*'''DO NOT request new creator/parody tags here.''' See [https://forums.e-hentai.org/index.php?showtopic=278368 this thread] for details.
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=95 Gallery Reports]'''
|
*Reports on active spams and/or malicious behaviors on the [[gallery]] system.
*<b>Refrain from posting unless it is a legitimate report.</b>
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=87 Feature Feedback]'''
|
*Feedback on site feature additions, changes, and removals.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=50 Contests and Competitions]'''
|
*For official E-Hentai [[contests]].
|-
|colspan="2" align="center" |'''The HentaiVerse'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=79 HentaiVerse Release Notes]'''
|
*Patch notes and comments for the [[HentaiVerse]].
*Does not allow attachments.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=72 HentaiVerse Resources & Scripts]'''
|
*Guides, userscripts, and other resources for the [[HentaiVerse]] minigame.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=76 The HentaiVerse Chat]'''
|
*General [[HentaiVerse]] discussions and advice.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=77 WTS]'''
|
*Users selling their [[items]] and [[Equipment Basics|equipment]].
|-
|'''[https://forums.e-hentai.org/index.php?showforum=78 WTB]'''
|
*Users placing requests for [[items]] or [[Equipment Basics|equipment]] they wish to procure.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=90 Isekai Trade]'''
|
*For trading in the [[Isekai]] game mode.
|-
|colspan="2" align="center" |'''Discussion Forums'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=12 General Chat]'''
|
*Off-topic; not related to any other subforums.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=38 Serious Debates]'''
|
*More political and social topics.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=37 Free Speech Zone]'''
|
*Unmoderated.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=13 Adult Chat]'''
|
*Sexual topics.
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=14 Anime & Manga Chat]'''
|
*All animation or written works of Asian origin.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=26 Culture Corner]'''
|
*Movies, television programs, music, books, etc.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=15 Gamers Chat]'''
|
*Video games and related topics.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=64 Tech Chat]'''
|
*Computers, cars, gadgets, audio/visual, etc.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=16 Artists and Authors]'''
|
*Artists sharing their work and feedback.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=81 Cove of Translators]'''
|
*Translation and scanning guides, advice, coordination, and feedback.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=82 Translation Bounties]'''
|
*Threads are atomically created by the [[bounty]] system upon a bounty-maker's request.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=83 Translation Requests]'''
|
*Requests for translations without a [[bounty]].
|-
|'''[https://forums.e-hentai.org/index.php?showforum=44 Torrents, Files, and Site Links]'''
|
*Torrents or links to direct downloads for hentai material.
*'''ALL posts advertising other sites must be posted in this forum.'''
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=45 Requests and Bounties]'''
|
*Requests for uploads or information pertaining to hentai.
*'''ALL requests of this nature go here.'''
*Hidden to guests.
|-
|colspan="2" align="center" |'''<span title="Hidden to users outside of the corresponding groups." style="border-bottom:1px dotted">Restricted Forums</span>'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=66 Gold Star Club]'''
|
*[[Gold Star]]s only.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=73 The Catgirl Camarilla]'''
|
*[[Stars#Catgirl|Catgirls]] only.
|-
|colspan="2" align="center" |'''<span title="Read only, no new posts or replies can be made." style="border-bottom:1px dotted">Retired Forums</span>'''
|-
|'''[https://forums.e-hentai.org/index.php?showforum=52 Pictures and CG Sets]'''
|
*Imagesets or official CG sets either as external galleries, E-Hentai [[galleries]], or attachments.
*Hidden to guests.
|-
|'''[https://forums.e-hentai.org/index.php?showforum=53 Doujinshi and Manga]'''
|
*Complete hentai books either as external galleries, E-Hentai [[galleries]], or attachments.
*Hidden to guests.
|}

==Groups==
{|class="wikitable" width="100%"
!Name
!Traits
!width="15%"| Members
!Name Designation
|-
|Validating || Users who have not yet activated their accounts. || (Varies) || N/A
|-
|Lurkers || Users with little to no forum activities. || (>8,398,170) || Normal
|-
|Admin || Administrators. || [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] || <span style="color:#FF1493">'''Pink'''</span>
|-
|Banned || Users who are no longer permitted on the forums. ''No longer utilized.'' || (23) || Same as pre-[[ban]]
|-
|Global Mods || Moderators for every subforum. || [https://forums.e-hentai.org/index.php?act=Members&max_results=30&filter=7&sort_order=asc&sort_key=members_display_name&st=0&b=1 (6)] || <span style="color:red">'''Red'''</span>
|-
|[[Gold Star]] Club || Users who have [[donated]] between 100-999 USD. || (7,456) || <span style="color:#DAA520">'''Gold'''</span>
|-
|Members || Users who posted on the forum on at least 10 different days (day resets at midnight UTC). || (>14,950) || '''Bold'''
|-
|Service || Bots in charge of automated tasks (e.g., dispatching PMs for [[Toplist]] rewards and [[Bounties]]). They do not respond to PMs. || [https://forums.e-hentai.org/index.php?showuser=5 Snowflake], [https://forums.e-hentai.org/index.php?showuser=4 Gallery System], [https://forums.e-hentai.org/index.php?showuser=9 AutoTagger] || Normal
|-
|Recruits || Users who posted on the forum on at least three different days (day resets at midnight UTC). || (>30,800) || Normal
|-
|[[Stars#Catgirl|Catgirl Camarilla]] || Users who have [[donated]] 1,000+ USD. || (382) || <span style="color:#16C5FE">'''Cyan'''</span>
|-
|''(Bots)'' || Crawlers for search engines and other services. ''Not a formal group.'' || Archive.org, Googlebot, MSN Bot, Yahoo || Unlinkable
|}

===Benefits===
*Recruits (or higher) can set signatures, modify profile information, send PMs with non-plain URLs, and send e-mails to members of the board.
*Members (or higher) have their PM storage space increased from 50 to 1,000, and attachment storage space increased from 50 MB to 1,000 MB.
*[[Gold Star]] (or higher) have more avatar height (up to 180px) and 2,000 PM storage space.
*[[Stars#Catgirl|Catgirls]] have 10,000 PM storage space, and a [[Alternate_Catgirl_Images|custom banner]].

==Reporting==

[[Image:Point.png]] '''<span style="color:red">Reporting posts that do not constitute harassment or rule violations may result in a [[ban]]. Please do not cause unnecessary work for forum moderators. Thank you.</span>'''

In case of duplicated or otherwise unwanted posts (e.g. rule violations) simply use the ''Report'' button located at the bottom left of the post. The same applies to threads. Thread creators may wish to change the thread title to "Delete" in order to assist a moderator.

<div id="spam"><div id="spamming"><div id="Spam"><div id="Spamming"><div id="Ban"><div id="ban">

==Rewards==
Posters who are "active" (1 post per day) very gradually receive [[power]] after a lengthy period of time. Users receive a 100% [[EXP]] bonus in the [[HentaiVerse]] if they have made at least one post in the last 30 days. The [[credits]] rewarded at the [[Dawn|dawn]] event are also tied to a user's forum activity.

[[Image:Point.png]] '''There is absolutely no benefit to posting more than once per day.'''

[[Image:Point.png]] '''A user's post count has no impact on any of their capabilities'''; the only exception being [[#Groups|lurker]] limitations.

[[Image:Point.png]] '''<span style="color:red">Users who spam the forums for any reason may be [[banned]] at a moderator's discretion.</span>'''

==Profiles==
A forum profile shows the following:
*Avatar
*Forum Title & Post Pips
*[[#Groups|Group]]
*Post Count
*Join Date
*[[HentaiVerse]] level and [[Rank]]
*[[Stars]] and [[Awards]]
*Signature

===Forum Titles===
The following are the default titles available on the forums.
{|class="wikitable"
!Post Count
!Rank
!Pips
|-
|0
|Lurker ||
|-
|10
| rowspan=2 | Newcomer
|☐
|-
|50
|☐☐
|-
|100
| rowspan=2 | Casual Poster
|☐☐☐
|-
|250
|☐☐☐☐
|-
|500
| rowspan=2 | Regular Poster
|☐☐☐☐☐
|-
|750
|☐☐☐☐☐☐
|-
|1,000
|Active Poster
|☐☐☐☐☐☐☐
|-
|2,500
|Veteran Poster
|☐☐☐☐☐☐☐☐
|-
|5,000
| rowspan=2 | Elite Poster
|☐☐☐☐☐☐☐☐☐
|-
|7,500
|☐☐☐☐☐☐☐☐☐☐
|-
|10,000
|Legendary Poster
|☐☐☐☐☐☐☐☐☐☐☐
|-
|25,000
|Forever Alone
|☐☐☐☐☐☐☐☐☐☐☐☐
|}

===Cutie Marks===
Some members have images relating to My Little Pony: Friendship Is Magic at the top right of all of their posts. These were handed out after the 2012 New Years event<sup>[https://forums.e-hentai.org/index.php?showtopic=53463][https://forums.e-hentai.org/index.php?showtopic=55200]</sup>.
*[[Donation#Gold|Gold Star or above]] donators can request a cutie mark by [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6| contacting Tenboro]. Please be patient for a reply.
**Cutie marks may be found [[:Category:Cutie Marks|here]].

==Filters==
[[Image:Point.png]] There are word filters in place preventing the posting of certain words and phrases. Do '''NOT''' attempt to circumvent these filters for any reason; doing so may result in a [[ban]].

==Limits==
*E-mails regarding Private Messages have been disabled.<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=239754&view=findpost&p=5717185]</sup>
*Posts are capped at 20 forum quotes.
*Posts are capped at 65,531 characters.
*Thread titles must be at least 2 characters.
*Custom member titles are capped at 60 characters.
*Displayed frame rate for APNG and GIF avatars is capped at 1/10s per frame.
*New users ([[E-Hentai_Forums#Groups|Lurkers]]):
**May not post URLs.
**May be required to complete CAPTCHAs in order to post.
**Limited on the number of PMs they can send in a day.
**Limited on the amount of people they can PM in a day.
**Cannot submit [[E-Hentai_Forums#Reporting|forum reports]].

==See also==
*[[Forum Rules]]
*[[IRC]]
*[[Technical_Issues#E-Hentai_Forums|Technical Issues - E-Hentai Forums]]
*[https://forums.e-hentai.org/index.php?act=members Forum Member List]

[[Category:Site Features]][[Category:E-Hentai Forums]]

no text

2026-08-12T18:01:20Z

Kagoraphobia:

ai generated

2026-08-12T17:59:53Z

Kagoraphobia:

<center><span style=color:green>[[Image:Point.png]] '''This tag is handled by an auto-tagger.''' [[Image:Point.png]]</span></center>
{{ContentTag
|nopreremind=true
|type=Technical
|description=Contains the [AI Generated] indicator within the title.
|note=May not be directly voted and is applied automatically when the indicator is included in, or renamed to be included in, the title. The tag is removed automatically when the gallery is [[Renaming|renamed]] to remove the indicator. Renames must follow the indicator requirements and formatting set below.
|othertaggroupid=491694
}}
==Indicator==
*'''R Field''': [AI Generated]<br>
*'''J Field''': [AI生成]<br>
*'''Description''': The [AI Generated] indicator standardizes the gallery title, indicating that illustrations within the gallery were created with artificial intelligence software (e.g. NovelAI and Stable Diffusion). Do '''NOT''' add this to galleries where AI involvement was directly denied by the uploader in the uploader comment, within the work, or on the credits page of the uploader/group. Specific cases may be discussed [https://forums.e-hentai.org/index.php?showtopic=265497 here].
*'''Notes''': Should only be applied to clearly AI images that represent at least half of the gallery.
::: It is not applicable if AI was only used as a tool in the process of creating something that does not have the obvious visual appearance of being AI-generated, e.g. if it was painted over.
::: Counts as a special indicator. For image sets, the title should not be disrupted other than correcting the [AI Generated] indicator if necessary, or special situations listed on the [[Talk:ai_generated|talk page]].
::: When the uploader is falsely denying a blatant use of AI, the indicator may still be added if their statement is overruled by a [[E-Hentai Janitor | gallery moderator]].
::: Please see [[Talk:ai_generated|here]] if you do not want to see AI generated content.
==See Also==
*[[Renaming]]

{{EHGNav}}

rough translation

2026-08-12T17:59:45Z

Kagoraphobia:

<center><span style=color:green>[[Image:Point.png]] '''Voting is restricted to users on the whitelist. See the [[Talk:rough_translation|talk page]] for details.''' [[Image:Point.png]]</span></center>
{{ContentTag
|type=Technical
|subtype1=Meta-Language
|description=Any 3rd party translation consisting of a required amount of text boxes/bubbles with a translation error. The requirement is defined by: Either 25% of the number of total translated pages (rounded to the nearest whole number), or 10, whichever is higher. Translation errors include missing context, missing author intent, omitted story/situation-relevant text on translated pages, or incorrect meaning.
|note=[[Image:Point.png]] When not indicated by the uploader, a gallery [[comment]] '''MUST''' detail the mistakes otherwise the tag is invalid. The comment needs to be written in a constructive, respectful manner.
:::See the [[Talk:rough_translation|talk page]] for cases when it may be tagged without a detailed comment.
:::[[rewrite|Rewrites]] do not qualify. Not to be tagged on alternative translations that are otherwise correct.
:::Should '''NOT''' be confused with [[rough grammar]].
:::If the tag is incorrectly added, you may request for removal in the [https://forums.e-hentai.org/index.php?showtopic=254552 Translations Evaluation] thread.
|othertaggroupid=482292
}}

original

2026-08-12T17:59:28Z

Kagoraphobia:

<center><span style=color:green>[[Image:Point.png]] '''This tag is handled primarily by an auto-tagger.''' [[Image:Point.png]]</span></center>
{{ContentTag
|nopreremind=true
|type=TechnicalOrGallery-Wide
|subtype1=Technical
|description=For [[Doujinshi]] or [[Artist CG]] that do not feature any characters or series from any known media/franchises.
|note=Is not disqualified by non-parody content, but is disqualified by any valid [[:Category:Character Tag|character]] or other valid [[parody]] tag.
:::<span style=color:red>'''Not to be used outside of the [[Doujinshi]] or [[Artist CG]] category.'''</span>
:::Should not be used in gallery naming.
:::May not be started manually on any gallery that the tag has never been present. Autotagger will add it automatically on galleries when parody or character tags are not present within the correct [[categories]].
|parodytaggroupid=3996
}}

no text

2026-08-12T17:34:28Z

Kagoraphobia: Created page with "<!--<center><span style=color:green>Image:Point.png'''This tag is handled by an auto-tagger.'''Image:Point.png</span></center> {{ContentTag |nopreremind=true |type=Technical |subtype1=Language |description=No other tag(s) in the language namespace are applied to the gallery. This generally indicates that the gallery has little to no text. Will designate the gallery's languages as "N/A". |note=Only applicable in the Doujinshi, Manga, Non-H, and ..."

Tag Creation

2026-08-12T04:06:00Z

Kagoraphobia: /* Guidelines for Submission */

[[Image:Tag Creation UI.png|thumb|The tag creation UI]]

<span style="color:red">'''Adding to the tracker follows normal voting rules. If you are unsure about the validity of a tag, whether that be what namespace it should be, the name, whether it's valid on the gallery, etc, request in the [https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread] and not the tracker.'''

__TOC__
Users with a minimum of 15 [[Mod Power]] are allowed to create tags that have never been created before (under the ''temp'' [[namespace]]), assuming that sufficient justification has been provided.
*Only artist, group, cosplayer, parody, or character tags can be created in this manner.
**Users with less than 15 [[Mod Power]] may request the above-mentioned tags to be created by posting in the [https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread].
*[[Image:Point.png]] <span style="color:#ff0000">'''The creation of [[Fetish_Listing|fetish/content tags]] CANNOT be handled through this system.'''</span> See [[Gallery_Tagging#newtag|here]] for the proper procedures on proposing these tags.

==How To==

'''Step 1:''' Visit the gallery where the new tag would be applicable.

'''Step 2:''' Type in the proposed tag name with the ''temp:'' prefix (e.g., temp:kaguya shinomiya). Submitting the entry will open up the '''New Tag Justification''' window.
*You will be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
**'''Hitting the "OK" button will also bring up the New Tag Justification window if you have at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
**[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence may lead to a [[Bans|ban]].'''</span>
**If the temp tag is incorrectly named, i.e. wrong spelling, or localization instead of the romanization, '''do not''' create a second temp tag to fix this.
**If no more specific tag exists, and it is not being used to tag other kinds of content, upvote the temp and add a note to rename into the justification.
***If used for other content, OR there are multiple temp tags for the same content, OR a more specific already namespaced tag exists, request in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping] thread instead.
*<u>Note</u>: The system will only recognize characters a-z, 1-0, hyphens "-", periods ".", and spaces between characters " ". Everything else will be discarded automatically.
*[[Image:Point.png]] When requesting a more specific tag for approval that already has another tag <span style="color:red">'''DO NOT'''</span> downvote the already existing namespaced tag until/if it has been approved. The request may get denied, and the existing tag may be correct, for technical reasons or otherwise.
**In most cases, such tags should be requested in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread] rather than the tracker.

'''Step 3:''' Select the correct [[namespace]] for the newly created tag, together with necessary notes and references, and anything else that is helpful for the validation process.
*You must first describe the nature of the temp tag. External sources to support the proposed tag must also be provided.
**[[Image:Point.png]] '''Sufficient justification must be provided, or else the temp tag will be rejected by a moderator.'''
**For what can be considered a reliable and valid third-party source for the temp tag, please read the [[Tag_Creation#Guidelines_for_Submission|Guidelines for Submission]] section.
*Suggested Formats:
<pre>This tag is for a parody character named "Kaguya Shinomiya", who appeared on pages 2-12, 15-18, and 20.

References:
https://kaguyasama-wa-kokurasetai.fandom.com/wiki/Kaguya_Shinomiya
https://myanimelist.net/character/136359/Kaguya_Shinomiya
https://en.wikipedia.org/wiki/List_of_Kaguya-sama:_Love_Is_War_characters</pre>
<pre>This tag is for an artist named "Andy Price".

References:
https://en.wikipedia.org/wiki/Andy_Price_(artist)
https://andypriceart.bigcartel.com/
https://twitter.com/AndyPriceArt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor</pre>

'''Step 4:''' Hit "Save Changes" after submitting all the relevant materials. This will notify a [[Janitor|namespacer]] to process your request(s), please be patient for a response.
*A list of your pending temp tag requests can be accessed via [https://e-hentai.org/tagjustification.php this link]. You may also edit the sources provided as needed.

'''Step 5:''' A [[Janitor|namespacer]] will either approve or reject the temp tag. The requester will receive a final [[forum]] PM with the result.
*'''In the event that your new tag is rejected, it will be deleted from the database and will no longer be usable.'''
**You may submit an inquiry on the rejection(s) by posting in the [https://forums.e-hentai.org/index.php?showtopic=107861 General tag discussion] thread.
*Aside from approval or rejection, a [[Janitor|namespacer]] may instead request for a revision on the provided sources. This will usually be because of bad formatting, lacking supporting materials, or requesting clarification.
**The requester will be sent a [[forum]] PM to notify them. To revise, simply open [https://e-hentai.org/tagjustification.php this page] and click on the tag name marked with <span style="color:red">'''REVISE'''</span>.
**Specific instruction on the source revision can also be found in comments with the ''(flagged for revision)'' flag.

==Tag Approval Tracker==
*A list of active temp tag requests can be found at https://repo.e-hentai.org/tools/tagapprove. The page is split into the following categories:
**<u>Pending Tags</u>: Lists any tags that still require a [[Janitor|namespacer]] or the tag requester attention.
***Tags that are in black have yet to be processed, tags in red require further information or clarification from the requester.
***The tag sources for pending tags may be modified at any time by the initial tag requester.
**<u>Approved Tags</u>: Lists processed tags that have been given a namespace or slaved.
**<u>Rejected Tags</u>: Lists processed tags that have been rejected, if you are sure your tag was rejected wrongly, you may make a post in the [https://forums.e-hentai.org/index.php?showtopic=107861 General tag discussion] thread.
*Users with at least 2 [[Mod Power]] may leave comments on a pending request. Please note that '''the comments should be providing additional information or clarification only'''. Tags created through this tool do not require additional support, so comments only in support should not be made.

===Trivia===
[[File:hanabi.jpg|250px|none|caption]]The tracker being fully cleared of pending requests will display fireworks.

==Guidelines for Submission==
;<div id="Sources"></div>Supporting Materials
:Sources are preferred to be official where possible. These may include the artist's own website or social media, signatures within the work, colophon, etc.
:*Official sources are required for any [[Tag_Creation#Romanization|romanization]] that is not revised Wapuro Hepburn.
:*Social Media <span style="text-decoration:underline;">urls</span> are not generally considered a valid source. If an artists social media account is named John Smith, while its url is @john123, it will not be considered as a supporting material for a request for a:john123, but would be considered for a request for a:john smith.
:**Exceptions may sometimes apply. Usually, this is for cases where their name is too common/already in use, or to give clarity on the romanization of kanji that has multiple readings, etc.
:Unofficial sources are accepted when official ones are unavailable. These may be fan sites, Wikipedia, distribution sites, etc.
:*Such sources should generally have at a bare minimum the original kanji or kana.
:*Some unofficial sources may not have enough trust, so it is advisable to provide as many supporting materials as possible.
:<div id="badsources"></div>Some sources are considered not trustworthy at all, and will not be relied on without additional supporting materials, these include:
:*Google Translate, or any automated translation software
:*English DLsite
:*DMM
:*Anthologies table of contents pages
:*Booru sites (e.g., Danbooru)
:**Exceptions may be granted for artists that have an account with one of the booru sites and only uploads to it.
:*NamuWiki
:Video links will not be accepted unless there is a good faith belief that no other source exists. In such cases, the suggestion should be made in the [https://forums.e-hentai.org/index.php?showtopic=275305 tag creation] thread, due to the increased amount of time it takes to check these.
:*The name must appear within the video. The only acceptable instance of the video title being justification for a tag, is when the video is provided by a first-party source.
;<div id="nameorder"></div>Name Order
:For ''artist'' and ''cosplayer'' tags, the name order defaults to the order of the originating country. For example, a tag for a Japanese artist should be submitted as ''surname'' then ''given name''.
:*Exceptions could be granted for cases where the content creator consistently uses a different name order.
:For ''character'' tags, the name order is standardized in the Western order (i.e., ''given name'' then ''surname''). Rare exceptions exist but they are not granted usually.
:*<u>Standardized Exceptions</u>: [[touken ranbu]] characters that are named after swords, as well as [[vtuber|vtubers]] are created in the original written order (e.g., ''赤井はあと'' --> ''akai haato'').
:*Additional rulings on character tags can be found [[Gallery_Tagging#Good_Tags|here]] under the "Participants" subsection.
;<div id="Romanization"></div>Romanization
:Romanization for new tags should be in revised Wapuro Hepburn. For example, さいとう would be "Saito<span style="color:red">u</span>" instead of "Saito". Exceptions for commonplace names may exist (e.g., Tokyo).
:*If the tag is requested in a different romanization method, an official source must be supplied in the justification.
:*If all other already namespaced tags in the series are not in revised Wapuro Hepburn, this may be used as justification instead of an official source, but example tags must be provided.
:Western localized names are usually only suitable as aliases and should not be created.
:*<div id="localized"></div>If other already namespaced tags in the series already use the localized name, it is acceptable to create the localized version, but example tags must be provided.
:If there is no example of localized names being used within the parody, the tag should be requested in revised Wapuro Hepburn of the original source name.
:*In some cases, a namespacer will still choose the localized name as the master and will rename it. Such cases will usually be, but not always and not limited to, very popular parodies that are not well known in the west by anything other than the localized name.
;<div id="Presence"></div>[[Presence]]
:Tags require sufficient [[presence]] to be namespaced. When requesting, please provide enough page numbers to indicate presence.
:*This is '''always''' required for the following: long galleries, galleries with multiple creators when requesting creator tags, or galleries where it is not immediately obvious which pages count.
;<div id="relevancy"></div>Content Relevancy
:Some works always count as 0 presence for namespacing purposes only. These include, but are not limited to:
:*[[screenshots|Screenshots]]
:*Non-parody works (e.g., first party [[artbook]] of a series)
:*[[non-h game manual|Non-H game manuals]]
:*Anything that [[Expunging#Forbidden.2FOther|does not fit the theme of the site]]
:*[[Asian Porn]]
:**This extends to models in the [[cosplay]] category that are not cosplaying
:*Galleries that were [[expunged]] correctly
;Series Segregation
:Certain parodies will be slaved under a generic series tag depending on various factors. For instance, "diablo 2" and "diablo 3" are slaved under "parody:diablo" due to high connectivity.
:*Judgment criteria and existing rulings can be found on the [[Series Segregation]] page.
;<div id="renaming"></div><div id="tag_slaving"></div><div id="blocking"></div>Tag Renaming/Slaving/Blocking Requests
:Do '''NOT''' create or upvote any temp tag for the purpose of renaming already namespaced tags, or for slaving.
:You should also '''NOT''' upvote existing temp tags not yet on the tracker for the purpose of requesting a tag block.
:*For these requests, please make a post in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread].
;<div id="unacceptable tags"></div>Unacceptable Tags
:Certain tags will be rejected outright. Please see [[Gallery_Tagging#Bad_Tags|here]] for more examples, as well as the following:
:*Writers.
:*Software.
:*Talent agencies.
:**[[Hololive]] and [[Nijisanji]] are the only exceptions.
:*Character tag requests should be for fictional characters only. [[vtuber|VTubers]] are considered as fictional characters.
:*AI galleries are not accepted for new tag requests, without some level of effort (see [[Talk:Tag_Creation|here]] for details). This will usually be if it's been structured as a comic, or that they have only used AI to assist their own art, etc. This applies to group/artist tags, as well as parody/character tags.
:'''Note:''' If you spot a dated temp tag that should be blocked (e.g., typo, fetish tag without approval), please submit a blocking request in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread].

==See also==
*[[Gallery Tagging]]
*[[Namespace]]
*[https://repo.e-hentai.org/tools/tagapprove Tag Approval Tracker] - A list of pending, accepted, or rejected temp tag requests.
*[https://e-hentai.org/tagjustification.php Tag Justification Index] - Shows all of the pending temp tags created by yourself. You may update your requests via this page.

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread] - For submitting tag creation requests should you have a [[Mod Power]] under 15.
*[https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread] - For tag slaving, aliasing, renaming, and blocking requests.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion] - You may ask questions related to the namespacing mechanism here.

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]

Gallery Tagging

2026-08-09T09:05:23Z

Kagoraphobia: /* Tag History */

Tagging is a system of the [[E-Hentai Galleries]] to assist users in identifying the major contents and properties of a gallery.

<i>Additional rulings and clarifications can be found on the [[Talk:Gallery_Tagging | talk page]].</i>

[[File:Tagging_Guidelines.png|frame|567px|right|The Tagging Guidelines pop-up appears the first time a user attempts to tag a gallery. Users agree to having fully read and acknowledged these rules.]]

<div id="Rules"></div><div id="Rule"></div><div id="Guidelines"></div>
==General Usage Guidelines ==
<div id="Presence"></div><div id="Rule1"></div>
{| class="wikitable" width="100%"
!Rule
!Details
!Examples / Exceptions
|-
|'''Presence'''||[[Image:Point.png]] <font size="5">In general do '''<span style="color:#ff0000">NOT</span>''' tag something unless it has a fair amount of presence in a gallery. In general, do not tag content that is only featured in a few images.</font>
||<u>Example</u>: The following presence examples always qualifies a normal presence tag:
*25% of any sized gallery.
*10 or more sequential images in an 80 or less pages gallery.
*20 or more sequential images on any sized gallery.

<u>Notes</u>: The no. of minimal required images does not always scale up/down with the gallery size 1:1. Although a 10 sequential in 80 pages gallery is acceptable, 5 in 40 is not.
*A presence-passing count in a large gallery also generally holds in the smaller galleries. Therefore, since 10/80 (sequential) is ok, sequential 10/40 or 10/60 would be as well.

See the [[Talk:Gallery_Tagging#Presence_Notes|talk page]] for further details.

<u>Exceptions</u>: [[Talk:Gallery_Tagging#1-Image_Only_Tags|1-Image Only Tags]].<div id="Definition">
|-
|'''Definition'''||The meanings of various tags on this site may not match those of other sites. Please read the definition of each tag before using it.
||<u>Example</u>: [[brother]] is only used in cases of [[yaoi]] [[incest]].<div id="Formatting">
|-
| rowspan="2" |'''Formatting'''||Tags only allow for alphanumeric characters, spaces, periods, and hyphens. Tags must be at least 3 characters long.
||<u>Exceptions</u>: [[3d]] or anything with a [[namespace]] (e.g. a:23).
|-
|Due to the aforementioned limitation certain terms are tagged differently than how they are normally written.||<u>Example</u>: The circle "#define" is tagged as "g:sharp define", and artist "hhh_hudiki" as "a:hhh-hudiki".
<div id="Namespace"></div>
|-
|'''Namespace'''||[[Fetish]] tags use a female, male, or mixed namespace to indicate which gender(s) is applicable. For these purposes [[futanari]] and [[shemale]] are considered female.
||<u>Example</u>: m:[[glasses]] if a male is wearing them, f:[[glasses]] for a female.
<div id="Conflicting"></div><div id="Conflicts"></div><div id="Conflict"></div>
|-
|'''Conflicting'''|| Tags such as [[dark skin]] and [[tanlines]], or [[swimsuit]] and [[school swimsuit]] do not go together as they are mutually exclusive; they can only be tagged if they both occur separately.
||<u>Example</u>: A participant with tanlines having sex followed by a dark skinned one in another instance would suffice for both tags.<div id="newtag"></div>
|-
|'''New'''||
*Artist, Group, Cosplayer, Parody and Character tags may be requested with citations.
*Entering temp: followed by the desired tag will prompt you to provide a source for the tag. See [[Tag Creation]] for detailed instructions.
*Users will also be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
*'''Hitting the "OK" button will also bring up the New Tag Justification window if the user has at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
||<u>Warning</u>: The creation of new fetish/content tags is highly restricted. Please use the [[forums]] to discuss new tag possibilities of this nature.
*[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence, or repeated misuse of the tag creation tool including repeated creation of fetish tags may lead to a [[Bans|ban]].'''</span>
|}

==Presence Recognition Types==
<div id="Visual"><div id="Visuals">
{| class="wikitable" width="100%"
!Rule
! Details
!Examples / Exceptions
|-
|'''Visual'''||Nearly all fetish tags are based on visuals, not text (''see the next rule''). If there is any conflict between what is being said and what is shown the visual wins.||<u>Example</u>: A young-looking girl saying she is old does not qualify for the [[milf]] / [[old lady]] tags.
<div id="Context"></div><div id="Contextual"></div>
|-
|'''Contextual'''||[[Fetish_Listing#Contextual|Contextual tags]] do not require visual presence but must have dialogue/story presence. These should '''NOT''' be tagged unless they are fairly obvious to a casual reader.
||<u>Example</u>: A woman saying the man with whom she's having sex is not her husband counts as [[cheating]].
</div>
|}

==Special Tag Types==
<div id="Gallery-Wide">
{| class="wikitable" width="100%"
!Rule
!Details
! Examples / Exceptions
|-
|'''Gallery-Wide'''||Gallery-Wide tags apply to an entire gallery. They have single page requirements to tag, but do not qualify if a single conflicting image is present.
||<u>Note</u>:

* 1 image is enough to qualify or disqualify most of these tags. Omake/covers/credits/colophons are ignored.
*Gallery-Wide tags that indicate the gender of the participants, for example [[sole female]], [[males only]], etc. allow for minimal amounts (no more than a single page) of conflicting content so long as the depicted actors are not vividly displaying sexual activity beyond nudity, and are not real or in-universe participants, e.g. being depicted in a magazine.<div id="Costume"></div><div id="Clothing"></div><div id="Clothes"></div><div id="Costumes">
|-
|'''Clothing'''||Costume tags such as [[schoolgirl uniform]] only apply if they are kept on (at least partially) during sexual activities. If they are absent or removed beforehand they should '''NOT''' be tagged.
||<u>Exceptions</u>: For non-pornographic galleries the clothing does not need to be removed in any way.<div id="Locations"></div><div id="Location"></div>
|-
|-
|'''Location'''||Location tags only apply if relevant during sexual activities. If the location is used without any sexual activity/nudity they should '''NOT''' be tagged.
||<u>Note</u>:
*For non-pornographic galleries the location tags are not applicable.<div id="Visual"></div><div id="Change"></div>
*There needs to be a sufficient amount of visual indications to confirm that the scenes take place in a certain location, before the tag in question is applicable. For example, merely wearing a swimsuit outdoors on a sunny day is '''NOT''' sufficient for the [[beach]] tag.
|-
|'''Change'''||For all (but four) change tags only the images involving the change itself are counted towards presence.||<u>Exceptions</u>:
*For [[gender change]] / [[gender morph]] the duration of the individual being a different gender also qualifies.
*For [[futanarization]], the duration of the character being a dickgirl also counts.
*For [[body swap]], post-swap images also count for presence.<div id="Animal"></div><div id="Animals">
|-
|'''Animal'''
|All animal tags require that an animal be explicitly involved in sex or nudity (e.g. [[animal on animal]], [[bestiality]]).
|<u>Example</u>: Two canines mating allows for the [[dog]] tag; a [[furry]] [[dog girl]] having sex with a human does not.<div id="Format"></div><div id="Format">
|-
|'''Format'''
|Format tags work similarly to the [[category|gallery categorization]] system. The work must overall fulfill the gallery format as specified in the respective definition for it to be applicable.
|<u>Examples</u>:
*A loose 200-pages [[western imageset]] containing 20 sequential [[comic]] pages should '''NOT''' be tagged with [[comic]].
*Some CG images within a published western release that is still predominantly utilizing panels to convey their story should still be tagged with [[comic]], but '''NOT''' [[western cg]].
|}

==[[Tagging Mechanics]]==
Tags are voted on by the users of the site as such they are subject to potential errors. Tags with <span style="border:thin solid green;">solid</span> borders have a cumulative [[mod power]] that is equal to or higher than 100 (i.e., been upvoted by many users, or by a handful of individuals with high [[mod power]]). Tags with <span style="border:thin dashed green;">dashed</span> borders mean that their cumulative [[power]] is between 10 to 99, while <span style="border:thin dotted green;">dotted</span> tags have a cumulative [[power]] between 1 to 9. <span style="color:#ff0000">'''It is important to note that the cumulative [[power]] of a tag does NOT necessarily indicate its validity.'''</span> '''Precaution must always be exercised when judging whether a tag is correct or not.''' See the [[#Forum Links|forum links]] below to report any tag misuse. Tags do not indicate to which images and to which participants they are applicable within a gallery; this information can be provided by gallery [[comments]].

==Good Tags==
;Contents/Fetishes
:As long as they are relevant sexually and pass presence. Whenever in doubt it is better not to tag them.

;Languages
:Tagged in their English equivalent (e.g. ''<span style="color:green">Spanish</span>'' not ''<span style="color:red">Espanol</span>'').

;Circles
:Names of the circles/groups that published the work. Should '''NOT''' be added when they are not officially credited (e.g. most [[Manga]]).

;Artists
:Names of the artists who drew portions of or all of the work; must be officially credited as such. Japanese artists should be written using [https://en.wikipedia.org/wiki/Hepburn_romanization Hepburn romanization]; some exceptions exist for artists that consistently spell their names otherwise.

;Cosplayers
:If the cosplayer consistently uses a name order, use that. Otherwise, follow the name order of the cosplayer's country.
<div id="originalseries"></div>
;Original Series
:Names of the series that are being parodied. Should generally be as specific as possible (e.g. ''[[Dragon Quest VIII]]'' instead of just ''[[Dragon Quest]]'') if the sub-series passes presence. A combination of images from different sub-series that passes presence (but no one sub-series passes) uses the generic series tag instead.
*The following apply:
**All canon characters within a parody
**Canon races within the parody (e.g., Khajiit from [[the elder scrolls|The Elder Scrolls]])
**Costumes styled after a parody if that parody is specifically mentioned/has some context in the work.
<div id="Character"></div><div id="Characters"></div>
*The segregation or unification of subseries is based on [[Series_Segregation#Reasoning | a number of factors]].

;Participants
:Names of characters (including [[cosplaying]]) participating in the gallery. Original characters (non-parodies) that do not exist outside of their own works should not be tagged.
*Non-pornographic works may only have the '''most focused''' characters be tagged.
* Character names are preferred in full western order; given name(s) followed by family name. e.g. ''[[hinata hyuga]]''. There are rare exceptions.
*Any character who transforms '''beyond that of a costume change''' (to the point where a casual observer cannot tell they are the same person) is to be tagged with their alias (should they have one). e.g. ''[[peashy]]'' vs. ''[[yellow heart]]''.
* A [[gender change|gender changed]] character is preferred be tagged with their regular name.
*A character with no official name may be tagged based on their relationship with another character. e.g. ''[[dexters mom]]'' from ''[[Dexter's Laboratory]]''.<sup>([https://dexterslab.wikia.com/wiki/Mom#Trivia Ref])</sup>
*Characters that share the exact same name (e.g. ''c:sakura'' from ''[[Urusei Yatsura]]'', ''[[Fire Emblem Fates]]'', etc.) can not be differentiated except by other tags such as parodies or attributes.

<div id="Category"></div><div id="Categories"></div>
===[[Gallery Categories‎|Categories]]===
[https://repo.e-hentai.org/tools/taggroup?show=1 Reclass tags] should only be used to fix an improperly categorized gallery. Once a tag receives 100 [[power]] the category will switch.
*If there are conflicting category tags, the one with the earliest "[[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|lock-in]]" time determines the category.
**To make a new category tag take effect, the pre-existing category tag must be downvoted to at least [[Tagging_Mechanics#Tag_Mod_Power|non-solid border]].
*These tags are automatically pruned from galleries after 30 days of no voting activity.
*Please note that "reclass:asianporn" is no longer functional. See its [[asianporn|definition]] for details.

<div id="Directory"></div>

=== Tag Directory===
{{TagNav}}

== Information Sources==
The information used to tag should always be based solely on the contents of the images in the gallery itself. The gallery's title, comments, or 3rd party sites do NOT qualify as information sources in the majority of cases.

<u>Exceptions:</u>
*[[:Category:Series_Tag|Parodies]] have all of their canon counted as existing information (unless the dialogue indicates otherwise). This precludes informed attributes for visual tags (e.g. [[Lum]] from [[Urusei Yatsura]] can be tagged with [[oni]] but not with [[alien girl]]).
*If an artist's name is not present in the gallery it may be obtained from a verifiable source such as the circle's website or store listing.
*The title may be used as proof of [[incest]] (unless the dialogue indicates otherwise).
*Participants' genders being ''extremely'' vague may use a verifiable source to identify them.

==[[Know The Difference]]==
For tags that are often confused for one another.

==Bad Tags==
;Commissioners / Decensors / Scanners / Translators
:Do not produce the content.
;No Sexual Connection
:(e.g. baseball, celebrity, clouds, exercise, microphone, pillow, red eyes, sword)
;Opinionated / Pejorative
:(e.g. cute, extreme, funny, gross, hot, garbage, nice, sad, scary, terrible, ugly, weird)
;Publishers / Websites
:Do not actually produce the content. Rare exceptions apply if nothing else can be used to identify a work's creator.
;Software
:The tools the artist used to created the content are irrelevant.
;Too Common
: (e.g. anime, nymphomaniac, semen, sex, skirt, softcore, straight, upskirt, vaginal)
;Too Vague
: (e.g. areola, ass, fetish, nipples, pussy, shaved, wet)
;Writers
:Not to be confused with the artists.

== Do Not==
*Use category exclusive tags outside of their category (e.g. [[non-nude]] is only for [[Cosplay]], [[comic]] is only for [[Western]] or [[Misc]]).
*Use [[:Category:Language Tag|language tags]] for anything other than indicating a gallery's text.
*Use a language tag on [[imageset]]-style galleries unless a majority of it (50%+) contains text in that language.
*Tag [[mother]] when not in conjunction with [[incest]]. This includes women giving [[birth]], women who happen to have children, or [[milf]]s.
*Use the [[cosplay]] tag when characters in drawn works are dressed as other recognizable characters; use [[cosplaying]] instead.
*Downvote any "redundant" reclass tags (i.e. being the same as the gallery's current category).
*Downvote any tag(s) that becomes "invalid" due to the uploader attempting to remove valid content. The said gallery should be reported for a [[Expunging#Reverting_and_Splitting|reversion/spilt]] action.
**If the tag(s) remains invalid after the revert/split, they may be downvoted accordingly.
*Downvote [[Fetish_Listing#Expunging|expunging tags]] purely because an [[Expunging|expunge petition]] has not been created. The system will automatically prune them from an active gallery if they remain for longer than 30 days.
**If the expunge type is definitely not valid for the gallery, then it may be downvoted.

==== Temporary Tags ====
Upvoting these tags is generally unnecessary. Galleries may be fixed / updated which would render such tags invalid.
*[[incomplete]]
*[[missing cover]]
*[[out of order]]
*[[Expunging]] tags
<div id="Why Should I Tag?"></div>

==[[Rewards]]==
Tagging earns points towards the [[toplists]].

[[Image:Point.png]] Poor tagging will result in the user '''losing''' [[power]]. Any attempts at farming points, accuracy spoofing, or heavy misuse WILL result in a permanent [[ban]].

==Exact Tag Searching==
Searches for certain tags can return results from more tags than intended. This happens to tags that appear as partial strings inside longer tags.

<u>Example</u>: The tag ''f:wolf'' will match both [[wolf]] and [[wolf girl]]. This also impacts [[slave tag]]s; a search for ''f:anal'' may return a gallery tagged with [[sex toys]]. This happens because the search for ''anal'' matches "anal beads" which is slaved to [[sex toys]].

To avoid this users may search with a dollar sign at the end of the tag to search only for that string (e.g. ''f:wolf$'', ''f:anal$'', etc.)

==Tagging Hotkeys==
The following hotkeys can be used when a tag is selected.

{| class="wikitable" style="text-align: center;"
! rowspan="2" |Function
! colspan="4" |Hotkeys
|-
!Numpad!!Other
|-
|Show All Tagged Galleries||{{Keypress|4}}||{{Keypress|A}}
|-
|Show Tag Definition||{{Keypress|6}}||{{Keypress|D}}
|-
|Vote Up||{{Keypress|8}}||{{Keypress|W}}
|-
|Vote Down||{{Keypress|2}}||{{Keypress|S}}
|-
|Clear Selection||{{Keypress|5}}||{{Keypress|Spacebar}}
|}

==Tag Tracker==
Users may see recently added tags across all public galleries via https://repo.e-hentai.org/tools/tagtrack
*This tool is primarily for tag cleanup, including removing invalid tags and making strong valid ones.
*Tags are displayed per gallery, and show that that are:
**<span style="opacity:0.3">weak</span> (with 1-9 [[Mod Power|MP]])
**<span style="opacity:0.7">active</span> (with 10-99 MP)
**<span style="color:#0000a4">SOLID</span> (with ≥100 MP)
**<span style="color:#009b00">ENFORCED</span> (tags that were added, and were [[Tagging_Mechanics#Tag_Veto|hard enforced]])
**<span style="text-decoration:line-through; opacity:0.3">downed</span> (tags that were added, but reduced to 0 MP)
**<span style="text-decoration:line-through; opacity:0.3;color:#f00">vetoed</span> (tags that were added, but were [[Tagging_Mechanics#Tag_Veto|hard vetoed]]).
*The results may be filtered in the following ways:
**'''downed''' - Displays tags that were created and have been reduced to 0 MP without being vetoed.
**'''weak''' - Displays tags that were created and have between 1-9 MP inclusive.
**'''active''' - Displays tags that were created and have between 10-99 MP inclusive.
**'''solid''' - Displays tags that were created and have 100 MP or higher.
**'''aged galleries''' - Displays galleries that have been tagged after they are no longer considered new.
**'''revived tags''' - Displays tags that were killed, and have been revived.
**'''exclude expunged''' - Filters out expunged galleries from the list.
**'''exclude autotags''' - Filters out tags added by the system, e.g. p:[[original]], or tags added due to a [[Namespace|slaving action]], etc.
**'''Tag/NS''': Filters out all but the chosen tags, with the following formats:
***''tag'', with no namespace, e.g. [[hairy]], will search for tags in all namespaces that match it.
***''namespace:tag'', e.g. f:hairy, will search for all tags that match both the tag and namespace.
***''tagid'', will return results for only the tag that has the chosen tagid.
***''special:namespace'', e.g., special:female, will search for all tags with the chosen namespace.

==Tag History==
Users can check their own tag history (up to actions made within the last 60 days), accuracy ratings, and overall usage via this tool:

<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">https://repo.e-hentai.org/tools/taglist?uid={USERID}</pre>
*Replace {USERID} with a userID (can be found by going to a user's profile in the [[forums]]) then checking the URL.
**Example: [https://forums.e-hentai.org/index.php?showuser=5 Snowflake] (UID: 5) would use the URL https://repo.e-hentai.org/tools/taglist?uid=5
*A &from={UNIXTIME} string may be added at the end of the above-mentioned URL. This can be used to allow users to quickly review their tagging actions made on or before the specified time.
**The date and time provided in the string must be in the Unix time format.
**Example: If Snowflake wants to review their tag actions made on or before July 2, 2026, 15:34:17 UTC, they would use the URL https://repo.e-hentai.org/tools/taglist?uid=5&from=1783016057
**A "'''Show Older >'''" button is also available at the end of the page, allowing users to continue reviewing their tagging histories dating even further back in time.
*Votes are organized by gallery. The value next to each tag indicates the amount of [[power]] utilized for that action at the time.
**A <span style="color:#008000">green</span> positive value (e.g., <span style="color:#008000">'''+69'''</span>) indicates that the user upvoted that tag in the gallery.
**Meanwhile, a <span style="color:#ff0000">red</span> negative value (e.g., <span style="color:#ff0000">'''-69'''</span>) indicates a downvote on the tag from the user.
**An <em>italicized</em> entry (e.g., ''female:nakadashi'') indicates that the user started the said tag.
**A '''bolded''' entry (e.g., '''female:nakadashi''') indicates the said tag received enough upvotes to be classed as a [[Tagging_Mechanics#Tag_Mod_Power|solid border]] tag.
*Accuracy score calculations are delayed by 3 days. Further accuracy checks take place to ensure a tag vote remains correct. '''Accuracy values are not foolproof; users should always manually review their tags.'''
**Vote entries that are highlighted in <span style="color:#ff0000">red</span> (e.g., <span style="color:#ff0000">female:nakadashi</span>) either indicate a started/upvoted tag was killed, or a downvoted tag is still alive.
**Started/Upvoted tag killed will be assessed as a "bad" vote (e.g., <span style="color:#008000">'''+69'''</span> <span style="color:#ff0000">female:nakadashi</span>) and negatively affects your accuracy.
**A downvote on tag will also be assessed as "bad" (e.g., <span style="color:#ff0000">'''-69'''</span> <span style="color:#ff0000">female:nakadashi</span>) if another user upvotes it after your downvote. Your accuracy will also be negatively impacted.
***Should the tag becomes fully downvoted later, it will be retallied and no longer classed as a "bad" vote on your record.
***For this reason, users are encouraged to use the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread to ensure that the identified invalid tags are fully downvoted.
**Users may use the "Filter galleries with assessed bad tagvotes" toggle to quickly review their tag votes that were assed as "bad" by the system.
*Accuracy scores are split by month, year, and overall total. The metrics are further separated into "Started" and "Voted" accuracies.
**Only the most recent seven monthly accuracies will be shown to the user. Yearly accuracies reflect the user's average tagging performance over the last 12 months.
**"Started" indicates accuracy for tags the user added themselves. "Voted" indicates accuracy for votes on tags already on a gallery.
**Values of less than 100 tags will only show the number of tags voted in gray without an accuracy calculation.
**"-" indicates 0 tags were voted by the user during that time period.

*[[Janitor|Tag checkers]] may check the history of any user.
**[[Image:Point.png]] <span style="color:#ff0000">'''Having an accuracy metric highlighted in red puts the user at high risk for a [[ban]].'''</span>

==Limitations==
Users with < 2 [[power]] are unable to start tags or downvote tags.

==See also==
*[[Fetish Listing]] - A categorized list of all official fetish tags.
*[[Technical_Issues#Gallery_Tagging|Technical Issues - Gallery Tagging]]
*[[Toplists#Tagging_Toplists|Toplists - Tagging]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] - Please report any bad tagging here.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]
[[Category:Rules]]

Gallery Tagging

2026-08-09T09:04:30Z

Kagoraphobia: /* Tag History */

Tagging is a system of the [[E-Hentai Galleries]] to assist users in identifying the major contents and properties of a gallery.

<i>Additional rulings and clarifications can be found on the [[Talk:Gallery_Tagging | talk page]].</i>

[[File:Tagging_Guidelines.png|frame|567px|right|The Tagging Guidelines pop-up appears the first time a user attempts to tag a gallery. Users agree to having fully read and acknowledged these rules.]]

<div id="Rules"></div><div id="Rule"></div><div id="Guidelines"></div>
==General Usage Guidelines ==
<div id="Presence"></div><div id="Rule1"></div>
{| class="wikitable" width="100%"
!Rule
!Details
!Examples / Exceptions
|-
|'''Presence'''||[[Image:Point.png]] <font size="5">In general do '''<span style="color:#ff0000">NOT</span>''' tag something unless it has a fair amount of presence in a gallery. In general, do not tag content that is only featured in a few images.</font>
||<u>Example</u>: The following presence examples always qualifies a normal presence tag:
*25% of any sized gallery.
*10 or more sequential images in an 80 or less pages gallery.
*20 or more sequential images on any sized gallery.

<u>Notes</u>: The no. of minimal required images does not always scale up/down with the gallery size 1:1. Although a 10 sequential in 80 pages gallery is acceptable, 5 in 40 is not.
*A presence-passing count in a large gallery also generally holds in the smaller galleries. Therefore, since 10/80 (sequential) is ok, sequential 10/40 or 10/60 would be as well.

See the [[Talk:Gallery_Tagging#Presence_Notes|talk page]] for further details.

<u>Exceptions</u>: [[Talk:Gallery_Tagging#1-Image_Only_Tags|1-Image Only Tags]].<div id="Definition">
|-
|'''Definition'''||The meanings of various tags on this site may not match those of other sites. Please read the definition of each tag before using it.
||<u>Example</u>: [[brother]] is only used in cases of [[yaoi]] [[incest]].<div id="Formatting">
|-
| rowspan="2" |'''Formatting'''||Tags only allow for alphanumeric characters, spaces, periods, and hyphens. Tags must be at least 3 characters long.
||<u>Exceptions</u>: [[3d]] or anything with a [[namespace]] (e.g. a:23).
|-
|Due to the aforementioned limitation certain terms are tagged differently than how they are normally written.||<u>Example</u>: The circle "#define" is tagged as "g:sharp define", and artist "hhh_hudiki" as "a:hhh-hudiki".
<div id="Namespace"></div>
|-
|'''Namespace'''||[[Fetish]] tags use a female, male, or mixed namespace to indicate which gender(s) is applicable. For these purposes [[futanari]] and [[shemale]] are considered female.
||<u>Example</u>: m:[[glasses]] if a male is wearing them, f:[[glasses]] for a female.
<div id="Conflicting"></div><div id="Conflicts"></div><div id="Conflict"></div>
|-
|'''Conflicting'''|| Tags such as [[dark skin]] and [[tanlines]], or [[swimsuit]] and [[school swimsuit]] do not go together as they are mutually exclusive; they can only be tagged if they both occur separately.
||<u>Example</u>: A participant with tanlines having sex followed by a dark skinned one in another instance would suffice for both tags.<div id="newtag"></div>
|-
|'''New'''||
*Artist, Group, Cosplayer, Parody and Character tags may be requested with citations.
*Entering temp: followed by the desired tag will prompt you to provide a source for the tag. See [[Tag Creation]] for detailed instructions.
*Users will also be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
*'''Hitting the "OK" button will also bring up the New Tag Justification window if the user has at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
||<u>Warning</u>: The creation of new fetish/content tags is highly restricted. Please use the [[forums]] to discuss new tag possibilities of this nature.
*[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence, or repeated misuse of the tag creation tool including repeated creation of fetish tags may lead to a [[Bans|ban]].'''</span>
|}

==Presence Recognition Types==
<div id="Visual"><div id="Visuals">
{| class="wikitable" width="100%"
!Rule
! Details
!Examples / Exceptions
|-
|'''Visual'''||Nearly all fetish tags are based on visuals, not text (''see the next rule''). If there is any conflict between what is being said and what is shown the visual wins.||<u>Example</u>: A young-looking girl saying she is old does not qualify for the [[milf]] / [[old lady]] tags.
<div id="Context"></div><div id="Contextual"></div>
|-
|'''Contextual'''||[[Fetish_Listing#Contextual|Contextual tags]] do not require visual presence but must have dialogue/story presence. These should '''NOT''' be tagged unless they are fairly obvious to a casual reader.
||<u>Example</u>: A woman saying the man with whom she's having sex is not her husband counts as [[cheating]].
</div>
|}

==Special Tag Types==
<div id="Gallery-Wide">
{| class="wikitable" width="100%"
!Rule
!Details
! Examples / Exceptions
|-
|'''Gallery-Wide'''||Gallery-Wide tags apply to an entire gallery. They have single page requirements to tag, but do not qualify if a single conflicting image is present.
||<u>Note</u>:

* 1 image is enough to qualify or disqualify most of these tags. Omake/covers/credits/colophons are ignored.
*Gallery-Wide tags that indicate the gender of the participants, for example [[sole female]], [[males only]], etc. allow for minimal amounts (no more than a single page) of conflicting content so long as the depicted actors are not vividly displaying sexual activity beyond nudity, and are not real or in-universe participants, e.g. being depicted in a magazine.<div id="Costume"></div><div id="Clothing"></div><div id="Clothes"></div><div id="Costumes">
|-
|'''Clothing'''||Costume tags such as [[schoolgirl uniform]] only apply if they are kept on (at least partially) during sexual activities. If they are absent or removed beforehand they should '''NOT''' be tagged.
||<u>Exceptions</u>: For non-pornographic galleries the clothing does not need to be removed in any way.<div id="Locations"></div><div id="Location"></div>
|-
|-
|'''Location'''||Location tags only apply if relevant during sexual activities. If the location is used without any sexual activity/nudity they should '''NOT''' be tagged.
||<u>Note</u>:
*For non-pornographic galleries the location tags are not applicable.<div id="Visual"></div><div id="Change"></div>
*There needs to be a sufficient amount of visual indications to confirm that the scenes take place in a certain location, before the tag in question is applicable. For example, merely wearing a swimsuit outdoors on a sunny day is '''NOT''' sufficient for the [[beach]] tag.
|-
|'''Change'''||For all (but four) change tags only the images involving the change itself are counted towards presence.||<u>Exceptions</u>:
*For [[gender change]] / [[gender morph]] the duration of the individual being a different gender also qualifies.
*For [[futanarization]], the duration of the character being a dickgirl also counts.
*For [[body swap]], post-swap images also count for presence.<div id="Animal"></div><div id="Animals">
|-
|'''Animal'''
|All animal tags require that an animal be explicitly involved in sex or nudity (e.g. [[animal on animal]], [[bestiality]]).
|<u>Example</u>: Two canines mating allows for the [[dog]] tag; a [[furry]] [[dog girl]] having sex with a human does not.<div id="Format"></div><div id="Format">
|-
|'''Format'''
|Format tags work similarly to the [[category|gallery categorization]] system. The work must overall fulfill the gallery format as specified in the respective definition for it to be applicable.
|<u>Examples</u>:
*A loose 200-pages [[western imageset]] containing 20 sequential [[comic]] pages should '''NOT''' be tagged with [[comic]].
*Some CG images within a published western release that is still predominantly utilizing panels to convey their story should still be tagged with [[comic]], but '''NOT''' [[western cg]].
|}

==[[Tagging Mechanics]]==
Tags are voted on by the users of the site as such they are subject to potential errors. Tags with <span style="border:thin solid green;">solid</span> borders have a cumulative [[mod power]] that is equal to or higher than 100 (i.e., been upvoted by many users, or by a handful of individuals with high [[mod power]]). Tags with <span style="border:thin dashed green;">dashed</span> borders mean that their cumulative [[power]] is between 10 to 99, while <span style="border:thin dotted green;">dotted</span> tags have a cumulative [[power]] between 1 to 9. <span style="color:#ff0000">'''It is important to note that the cumulative [[power]] of a tag does NOT necessarily indicate its validity.'''</span> '''Precaution must always be exercised when judging whether a tag is correct or not.''' See the [[#Forum Links|forum links]] below to report any tag misuse. Tags do not indicate to which images and to which participants they are applicable within a gallery; this information can be provided by gallery [[comments]].

==Good Tags==
;Contents/Fetishes
:As long as they are relevant sexually and pass presence. Whenever in doubt it is better not to tag them.

;Languages
:Tagged in their English equivalent (e.g. ''<span style="color:green">Spanish</span>'' not ''<span style="color:red">Espanol</span>'').

;Circles
:Names of the circles/groups that published the work. Should '''NOT''' be added when they are not officially credited (e.g. most [[Manga]]).

;Artists
:Names of the artists who drew portions of or all of the work; must be officially credited as such. Japanese artists should be written using [https://en.wikipedia.org/wiki/Hepburn_romanization Hepburn romanization]; some exceptions exist for artists that consistently spell their names otherwise.

;Cosplayers
:If the cosplayer consistently uses a name order, use that. Otherwise, follow the name order of the cosplayer's country.
<div id="originalseries"></div>
;Original Series
:Names of the series that are being parodied. Should generally be as specific as possible (e.g. ''[[Dragon Quest VIII]]'' instead of just ''[[Dragon Quest]]'') if the sub-series passes presence. A combination of images from different sub-series that passes presence (but no one sub-series passes) uses the generic series tag instead.
*The following apply:
**All canon characters within a parody
**Canon races within the parody (e.g., Khajiit from [[the elder scrolls|The Elder Scrolls]])
**Costumes styled after a parody if that parody is specifically mentioned/has some context in the work.
<div id="Character"></div><div id="Characters"></div>
*The segregation or unification of subseries is based on [[Series_Segregation#Reasoning | a number of factors]].

;Participants
:Names of characters (including [[cosplaying]]) participating in the gallery. Original characters (non-parodies) that do not exist outside of their own works should not be tagged.
*Non-pornographic works may only have the '''most focused''' characters be tagged.
* Character names are preferred in full western order; given name(s) followed by family name. e.g. ''[[hinata hyuga]]''. There are rare exceptions.
*Any character who transforms '''beyond that of a costume change''' (to the point where a casual observer cannot tell they are the same person) is to be tagged with their alias (should they have one). e.g. ''[[peashy]]'' vs. ''[[yellow heart]]''.
* A [[gender change|gender changed]] character is preferred be tagged with their regular name.
*A character with no official name may be tagged based on their relationship with another character. e.g. ''[[dexters mom]]'' from ''[[Dexter's Laboratory]]''.<sup>([https://dexterslab.wikia.com/wiki/Mom#Trivia Ref])</sup>
*Characters that share the exact same name (e.g. ''c:sakura'' from ''[[Urusei Yatsura]]'', ''[[Fire Emblem Fates]]'', etc.) can not be differentiated except by other tags such as parodies or attributes.

<div id="Category"></div><div id="Categories"></div>
===[[Gallery Categories‎|Categories]]===
[https://repo.e-hentai.org/tools/taggroup?show=1 Reclass tags] should only be used to fix an improperly categorized gallery. Once a tag receives 100 [[power]] the category will switch.
*If there are conflicting category tags, the one with the earliest "[[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|lock-in]]" time determines the category.
**To make a new category tag take effect, the pre-existing category tag must be downvoted to at least [[Tagging_Mechanics#Tag_Mod_Power|non-solid border]].
*These tags are automatically pruned from galleries after 30 days of no voting activity.
*Please note that "reclass:asianporn" is no longer functional. See its [[asianporn|definition]] for details.

<div id="Directory"></div>

=== Tag Directory===
{{TagNav}}

== Information Sources==
The information used to tag should always be based solely on the contents of the images in the gallery itself. The gallery's title, comments, or 3rd party sites do NOT qualify as information sources in the majority of cases.

<u>Exceptions:</u>
*[[:Category:Series_Tag|Parodies]] have all of their canon counted as existing information (unless the dialogue indicates otherwise). This precludes informed attributes for visual tags (e.g. [[Lum]] from [[Urusei Yatsura]] can be tagged with [[oni]] but not with [[alien girl]]).
*If an artist's name is not present in the gallery it may be obtained from a verifiable source such as the circle's website or store listing.
*The title may be used as proof of [[incest]] (unless the dialogue indicates otherwise).
*Participants' genders being ''extremely'' vague may use a verifiable source to identify them.

==[[Know The Difference]]==
For tags that are often confused for one another.

==Bad Tags==
;Commissioners / Decensors / Scanners / Translators
:Do not produce the content.
;No Sexual Connection
:(e.g. baseball, celebrity, clouds, exercise, microphone, pillow, red eyes, sword)
;Opinionated / Pejorative
:(e.g. cute, extreme, funny, gross, hot, garbage, nice, sad, scary, terrible, ugly, weird)
;Publishers / Websites
:Do not actually produce the content. Rare exceptions apply if nothing else can be used to identify a work's creator.
;Software
:The tools the artist used to created the content are irrelevant.
;Too Common
: (e.g. anime, nymphomaniac, semen, sex, skirt, softcore, straight, upskirt, vaginal)
;Too Vague
: (e.g. areola, ass, fetish, nipples, pussy, shaved, wet)
;Writers
:Not to be confused with the artists.

== Do Not==
*Use category exclusive tags outside of their category (e.g. [[non-nude]] is only for [[Cosplay]], [[comic]] is only for [[Western]] or [[Misc]]).
*Use [[:Category:Language Tag|language tags]] for anything other than indicating a gallery's text.
*Use a language tag on [[imageset]]-style galleries unless a majority of it (50%+) contains text in that language.
*Tag [[mother]] when not in conjunction with [[incest]]. This includes women giving [[birth]], women who happen to have children, or [[milf]]s.
*Use the [[cosplay]] tag when characters in drawn works are dressed as other recognizable characters; use [[cosplaying]] instead.
*Downvote any "redundant" reclass tags (i.e. being the same as the gallery's current category).
*Downvote any tag(s) that becomes "invalid" due to the uploader attempting to remove valid content. The said gallery should be reported for a [[Expunging#Reverting_and_Splitting|reversion/spilt]] action.
**If the tag(s) remains invalid after the revert/split, they may be downvoted accordingly.
*Downvote [[Fetish_Listing#Expunging|expunging tags]] purely because an [[Expunging|expunge petition]] has not been created. The system will automatically prune them from an active gallery if they remain for longer than 30 days.
**If the expunge type is definitely not valid for the gallery, then it may be downvoted.

==== Temporary Tags ====
Upvoting these tags is generally unnecessary. Galleries may be fixed / updated which would render such tags invalid.
*[[incomplete]]
*[[missing cover]]
*[[out of order]]
*[[Expunging]] tags
<div id="Why Should I Tag?"></div>

==[[Rewards]]==
Tagging earns points towards the [[toplists]].

[[Image:Point.png]] Poor tagging will result in the user '''losing''' [[power]]. Any attempts at farming points, accuracy spoofing, or heavy misuse WILL result in a permanent [[ban]].

==Exact Tag Searching==
Searches for certain tags can return results from more tags than intended. This happens to tags that appear as partial strings inside longer tags.

<u>Example</u>: The tag ''f:wolf'' will match both [[wolf]] and [[wolf girl]]. This also impacts [[slave tag]]s; a search for ''f:anal'' may return a gallery tagged with [[sex toys]]. This happens because the search for ''anal'' matches "anal beads" which is slaved to [[sex toys]].

To avoid this users may search with a dollar sign at the end of the tag to search only for that string (e.g. ''f:wolf$'', ''f:anal$'', etc.)

==Tagging Hotkeys==
The following hotkeys can be used when a tag is selected.

{| class="wikitable" style="text-align: center;"
! rowspan="2" |Function
! colspan="4" |Hotkeys
|-
!Numpad!!Other
|-
|Show All Tagged Galleries||{{Keypress|4}}||{{Keypress|A}}
|-
|Show Tag Definition||{{Keypress|6}}||{{Keypress|D}}
|-
|Vote Up||{{Keypress|8}}||{{Keypress|W}}
|-
|Vote Down||{{Keypress|2}}||{{Keypress|S}}
|-
|Clear Selection||{{Keypress|5}}||{{Keypress|Spacebar}}
|}

==Tag Tracker==
Users may see recently added tags across all public galleries via https://repo.e-hentai.org/tools/tagtrack
*This tool is primarily for tag cleanup, including removing invalid tags and making strong valid ones.
*Tags are displayed per gallery, and show that that are:
**<span style="opacity:0.3">weak</span> (with 1-9 [[Mod Power|MP]])
**<span style="opacity:0.7">active</span> (with 10-99 MP)
**<span style="color:#0000a4">SOLID</span> (with ≥100 MP)
**<span style="color:#009b00">ENFORCED</span> (tags that were added, and were [[Tagging_Mechanics#Tag_Veto|hard enforced]])
**<span style="text-decoration:line-through; opacity:0.3">downed</span> (tags that were added, but reduced to 0 MP)
**<span style="text-decoration:line-through; opacity:0.3;color:#f00">vetoed</span> (tags that were added, but were [[Tagging_Mechanics#Tag_Veto|hard vetoed]]).
*The results may be filtered in the following ways:
**'''downed''' - Displays tags that were created and have been reduced to 0 MP without being vetoed.
**'''weak''' - Displays tags that were created and have between 1-9 MP inclusive.
**'''active''' - Displays tags that were created and have between 10-99 MP inclusive.
**'''solid''' - Displays tags that were created and have 100 MP or higher.
**'''aged galleries''' - Displays galleries that have been tagged after they are no longer considered new.
**'''revived tags''' - Displays tags that were killed, and have been revived.
**'''exclude expunged''' - Filters out expunged galleries from the list.
**'''exclude autotags''' - Filters out tags added by the system, e.g. p:[[original]], or tags added due to a [[Namespace|slaving action]], etc.
**'''Tag/NS''': Filters out all but the chosen tags, with the following formats:
***''tag'', with no namespace, e.g. [[hairy]], will search for tags in all namespaces that match it.
***''namespace:tag'', e.g. f:hairy, will search for all tags that match both the tag and namespace.
***''tagid'', will return results for only the tag that has the chosen tagid.
***''special:namespace'', e.g., special:female, will search for all tags with the chosen namespace.

==Tag History==
Users can check their own tag history (up to actions made within the last 60 days), accuracy ratings, and overall usage via this tool:

<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">https://repo.e-hentai.org/tools/taglist?uid={USERID}</pre>
*Replace {USERID} with a userID (can be found by going to a user's profile in the [[forums]]) then checking the URL.
**Example: [https://forums.e-hentai.org/index.php?showuser=5 Snowflake] (UID: 5) would use the URL https://repo.e-hentai.org/tools/taglist?uid=5
*A &from={UNIXTIME} string may be added at the end of the above-mentioned URL. This can be used to allow users to quickly review their tagging actions made on or before the specified time.
**The date and time provided in the string must be in the Unix time format.
**Example: If Snowflake wants to review their tag actions made on or before July 2, 2026, 15:34:17 UTC, they would use the URL https://repo.e-hentai.org/tools/taglist?uid=5&from=1783016057
**A "'''Show Older >'''" button is also available at the end of the page, allowing users to continue reviewing their tagging histories dating even further back in time.
*Votes are organized by gallery. The value next to each tag indicates the amount of [[power]] utilized for that action at the time.
**A <span style="color:#008000">green</span> positive value (e.g., <span style="color:#008000">'''+69'''</span>) indicates that the user upvoted that tag in the gallery.
**Meanwhile, a <span style="color:#ff0000">red</span> negative value (e.g., <span style="color:#ff0000">'''-69'''</span>) indicates a downvote on the tag from the user.
**An <em>italicized</em> entry (e.g., ''female:nakadashi'') indicates that the user started the said tag.
**A '''bolded''' entry (e.g., '''female:nakadashi''') indicates the said tag received enough upvotes to be classed as a [[Tagging_Mechanics#Tag_Mod_Power|solid border]] tag.
*Accuracy score calculations are delayed by 3 days. Further accuracy checks take place to ensure a tag vote remains correct. '''Accuracy values are not foolproof; users should always manually review their tags.'''
**Vote entries that are highlighted in <span style="color:#ff0000">red</span> (e.g., <span style="color:#ff0000">female:nakadashi</span>) either indicate a started/upvoted tag was killed, or a downvoted tag is still alive.
**Started/Upvoted tag killed will be assessed as a "bad" vote (e.g., <span style="color:#008000">'''+69'''</span> <span style="color:#ff0000">female:nakadashi</span>) and negatively affects your accuracy.
**A downvote on tag will also be assessed as "bad" (e.g., <span style="color:#ff0000">'''-69'''</span> <span style="color:#ff0000">female:nakadashi</span>) if another user upvotes it after your downvote. Your accuracy will also be negatively impacted.
***Should the tag becomes fully downvoted later, it will be retallied and no longer classed as a "bad" vote on your record.
***For this reason, users are encouraged to use the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread to ensure that the identified invalid tags are fully downvoted.
**Users may use the "Filter galleries with assessed bad tagvotes" toggle to quickly review their tag votes that were assed as "bad" by the system.
*Accuracy scores are split by month, year, and overall total. The metrics are further separated into "Started" and "Voted" accuracies.
**Only the most recent seven monthly accuracies will be shown to the user. Yearly accuracies reflect the user's average tagging performance over the last 12 months.
**"Started" indicates accuracy for tags the user added themselves. "Voted" indicates accuracy for votes on tags already on a gallery.
**Values of less than 100 tags will only show the number of tags voted in gray without an accuracy calculation.
**"-" indicates 0 tags were voted by the user during that time period.

*[[Janitor|Tag checkers]] may check the history of any user.
**[[Image:Point.png]] Having an accuracy metric highlighted in red puts the user at high risk for a [[ban]].

==Limitations==
Users with < 2 [[power]] are unable to start tags or downvote tags.

==See also==
*[[Fetish Listing]] - A categorized list of all official fetish tags.
*[[Technical_Issues#Gallery_Tagging|Technical Issues - Gallery Tagging]]
*[[Toplists#Tagging_Toplists|Toplists - Tagging]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] - Please report any bad tagging here.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]
[[Category:Rules]]

Gallery Tagging

2026-08-09T09:00:17Z

Kagoraphobia: /* Tag History */

Tagging is a system of the [[E-Hentai Galleries]] to assist users in identifying the major contents and properties of a gallery.

<i>Additional rulings and clarifications can be found on the [[Talk:Gallery_Tagging | talk page]].</i>

[[File:Tagging_Guidelines.png|frame|567px|right|The Tagging Guidelines pop-up appears the first time a user attempts to tag a gallery. Users agree to having fully read and acknowledged these rules.]]

<div id="Rules"></div><div id="Rule"></div><div id="Guidelines"></div>
==General Usage Guidelines ==
<div id="Presence"></div><div id="Rule1"></div>
{| class="wikitable" width="100%"
!Rule
!Details
!Examples / Exceptions
|-
|'''Presence'''||[[Image:Point.png]] <font size="5">In general do '''<span style="color:#ff0000">NOT</span>''' tag something unless it has a fair amount of presence in a gallery. In general, do not tag content that is only featured in a few images.</font>
||<u>Example</u>: The following presence examples always qualifies a normal presence tag:
*25% of any sized gallery.
*10 or more sequential images in an 80 or less pages gallery.
*20 or more sequential images on any sized gallery.

<u>Notes</u>: The no. of minimal required images does not always scale up/down with the gallery size 1:1. Although a 10 sequential in 80 pages gallery is acceptable, 5 in 40 is not.
*A presence-passing count in a large gallery also generally holds in the smaller galleries. Therefore, since 10/80 (sequential) is ok, sequential 10/40 or 10/60 would be as well.

See the [[Talk:Gallery_Tagging#Presence_Notes|talk page]] for further details.

<u>Exceptions</u>: [[Talk:Gallery_Tagging#1-Image_Only_Tags|1-Image Only Tags]].<div id="Definition">
|-
|'''Definition'''||The meanings of various tags on this site may not match those of other sites. Please read the definition of each tag before using it.
||<u>Example</u>: [[brother]] is only used in cases of [[yaoi]] [[incest]].<div id="Formatting">
|-
| rowspan="2" |'''Formatting'''||Tags only allow for alphanumeric characters, spaces, periods, and hyphens. Tags must be at least 3 characters long.
||<u>Exceptions</u>: [[3d]] or anything with a [[namespace]] (e.g. a:23).
|-
|Due to the aforementioned limitation certain terms are tagged differently than how they are normally written.||<u>Example</u>: The circle "#define" is tagged as "g:sharp define", and artist "hhh_hudiki" as "a:hhh-hudiki".
<div id="Namespace"></div>
|-
|'''Namespace'''||[[Fetish]] tags use a female, male, or mixed namespace to indicate which gender(s) is applicable. For these purposes [[futanari]] and [[shemale]] are considered female.
||<u>Example</u>: m:[[glasses]] if a male is wearing them, f:[[glasses]] for a female.
<div id="Conflicting"></div><div id="Conflicts"></div><div id="Conflict"></div>
|-
|'''Conflicting'''|| Tags such as [[dark skin]] and [[tanlines]], or [[swimsuit]] and [[school swimsuit]] do not go together as they are mutually exclusive; they can only be tagged if they both occur separately.
||<u>Example</u>: A participant with tanlines having sex followed by a dark skinned one in another instance would suffice for both tags.<div id="newtag"></div>
|-
|'''New'''||
*Artist, Group, Cosplayer, Parody and Character tags may be requested with citations.
*Entering temp: followed by the desired tag will prompt you to provide a source for the tag. See [[Tag Creation]] for detailed instructions.
*Users will also be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
*'''Hitting the "OK" button will also bring up the New Tag Justification window if the user has at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
||<u>Warning</u>: The creation of new fetish/content tags is highly restricted. Please use the [[forums]] to discuss new tag possibilities of this nature.
*[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence, or repeated misuse of the tag creation tool including repeated creation of fetish tags may lead to a [[Bans|ban]].'''</span>
|}

==Presence Recognition Types==
<div id="Visual"><div id="Visuals">
{| class="wikitable" width="100%"
!Rule
! Details
!Examples / Exceptions
|-
|'''Visual'''||Nearly all fetish tags are based on visuals, not text (''see the next rule''). If there is any conflict between what is being said and what is shown the visual wins.||<u>Example</u>: A young-looking girl saying she is old does not qualify for the [[milf]] / [[old lady]] tags.
<div id="Context"></div><div id="Contextual"></div>
|-
|'''Contextual'''||[[Fetish_Listing#Contextual|Contextual tags]] do not require visual presence but must have dialogue/story presence. These should '''NOT''' be tagged unless they are fairly obvious to a casual reader.
||<u>Example</u>: A woman saying the man with whom she's having sex is not her husband counts as [[cheating]].
</div>
|}

==Special Tag Types==
<div id="Gallery-Wide">
{| class="wikitable" width="100%"
!Rule
!Details
! Examples / Exceptions
|-
|'''Gallery-Wide'''||Gallery-Wide tags apply to an entire gallery. They have single page requirements to tag, but do not qualify if a single conflicting image is present.
||<u>Note</u>:

* 1 image is enough to qualify or disqualify most of these tags. Omake/covers/credits/colophons are ignored.
*Gallery-Wide tags that indicate the gender of the participants, for example [[sole female]], [[males only]], etc. allow for minimal amounts (no more than a single page) of conflicting content so long as the depicted actors are not vividly displaying sexual activity beyond nudity, and are not real or in-universe participants, e.g. being depicted in a magazine.<div id="Costume"></div><div id="Clothing"></div><div id="Clothes"></div><div id="Costumes">
|-
|'''Clothing'''||Costume tags such as [[schoolgirl uniform]] only apply if they are kept on (at least partially) during sexual activities. If they are absent or removed beforehand they should '''NOT''' be tagged.
||<u>Exceptions</u>: For non-pornographic galleries the clothing does not need to be removed in any way.<div id="Locations"></div><div id="Location"></div>
|-
|-
|'''Location'''||Location tags only apply if relevant during sexual activities. If the location is used without any sexual activity/nudity they should '''NOT''' be tagged.
||<u>Note</u>:
*For non-pornographic galleries the location tags are not applicable.<div id="Visual"></div><div id="Change"></div>
*There needs to be a sufficient amount of visual indications to confirm that the scenes take place in a certain location, before the tag in question is applicable. For example, merely wearing a swimsuit outdoors on a sunny day is '''NOT''' sufficient for the [[beach]] tag.
|-
|'''Change'''||For all (but four) change tags only the images involving the change itself are counted towards presence.||<u>Exceptions</u>:
*For [[gender change]] / [[gender morph]] the duration of the individual being a different gender also qualifies.
*For [[futanarization]], the duration of the character being a dickgirl also counts.
*For [[body swap]], post-swap images also count for presence.<div id="Animal"></div><div id="Animals">
|-
|'''Animal'''
|All animal tags require that an animal be explicitly involved in sex or nudity (e.g. [[animal on animal]], [[bestiality]]).
|<u>Example</u>: Two canines mating allows for the [[dog]] tag; a [[furry]] [[dog girl]] having sex with a human does not.<div id="Format"></div><div id="Format">
|-
|'''Format'''
|Format tags work similarly to the [[category|gallery categorization]] system. The work must overall fulfill the gallery format as specified in the respective definition for it to be applicable.
|<u>Examples</u>:
*A loose 200-pages [[western imageset]] containing 20 sequential [[comic]] pages should '''NOT''' be tagged with [[comic]].
*Some CG images within a published western release that is still predominantly utilizing panels to convey their story should still be tagged with [[comic]], but '''NOT''' [[western cg]].
|}

==[[Tagging Mechanics]]==
Tags are voted on by the users of the site as such they are subject to potential errors. Tags with <span style="border:thin solid green;">solid</span> borders have a cumulative [[mod power]] that is equal to or higher than 100 (i.e., been upvoted by many users, or by a handful of individuals with high [[mod power]]). Tags with <span style="border:thin dashed green;">dashed</span> borders mean that their cumulative [[power]] is between 10 to 99, while <span style="border:thin dotted green;">dotted</span> tags have a cumulative [[power]] between 1 to 9. <span style="color:#ff0000">'''It is important to note that the cumulative [[power]] of a tag does NOT necessarily indicate its validity.'''</span> '''Precaution must always be exercised when judging whether a tag is correct or not.''' See the [[#Forum Links|forum links]] below to report any tag misuse. Tags do not indicate to which images and to which participants they are applicable within a gallery; this information can be provided by gallery [[comments]].

==Good Tags==
;Contents/Fetishes
:As long as they are relevant sexually and pass presence. Whenever in doubt it is better not to tag them.

;Languages
:Tagged in their English equivalent (e.g. ''<span style="color:green">Spanish</span>'' not ''<span style="color:red">Espanol</span>'').

;Circles
:Names of the circles/groups that published the work. Should '''NOT''' be added when they are not officially credited (e.g. most [[Manga]]).

;Artists
:Names of the artists who drew portions of or all of the work; must be officially credited as such. Japanese artists should be written using [https://en.wikipedia.org/wiki/Hepburn_romanization Hepburn romanization]; some exceptions exist for artists that consistently spell their names otherwise.

;Cosplayers
:If the cosplayer consistently uses a name order, use that. Otherwise, follow the name order of the cosplayer's country.
<div id="originalseries"></div>
;Original Series
:Names of the series that are being parodied. Should generally be as specific as possible (e.g. ''[[Dragon Quest VIII]]'' instead of just ''[[Dragon Quest]]'') if the sub-series passes presence. A combination of images from different sub-series that passes presence (but no one sub-series passes) uses the generic series tag instead.
*The following apply:
**All canon characters within a parody
**Canon races within the parody (e.g., Khajiit from [[the elder scrolls|The Elder Scrolls]])
**Costumes styled after a parody if that parody is specifically mentioned/has some context in the work.
<div id="Character"></div><div id="Characters"></div>
*The segregation or unification of subseries is based on [[Series_Segregation#Reasoning | a number of factors]].

;Participants
:Names of characters (including [[cosplaying]]) participating in the gallery. Original characters (non-parodies) that do not exist outside of their own works should not be tagged.
*Non-pornographic works may only have the '''most focused''' characters be tagged.
* Character names are preferred in full western order; given name(s) followed by family name. e.g. ''[[hinata hyuga]]''. There are rare exceptions.
*Any character who transforms '''beyond that of a costume change''' (to the point where a casual observer cannot tell they are the same person) is to be tagged with their alias (should they have one). e.g. ''[[peashy]]'' vs. ''[[yellow heart]]''.
* A [[gender change|gender changed]] character is preferred be tagged with their regular name.
*A character with no official name may be tagged based on their relationship with another character. e.g. ''[[dexters mom]]'' from ''[[Dexter's Laboratory]]''.<sup>([https://dexterslab.wikia.com/wiki/Mom#Trivia Ref])</sup>
*Characters that share the exact same name (e.g. ''c:sakura'' from ''[[Urusei Yatsura]]'', ''[[Fire Emblem Fates]]'', etc.) can not be differentiated except by other tags such as parodies or attributes.

<div id="Category"></div><div id="Categories"></div>
===[[Gallery Categories‎|Categories]]===
[https://repo.e-hentai.org/tools/taggroup?show=1 Reclass tags] should only be used to fix an improperly categorized gallery. Once a tag receives 100 [[power]] the category will switch.
*If there are conflicting category tags, the one with the earliest "[[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|lock-in]]" time determines the category.
**To make a new category tag take effect, the pre-existing category tag must be downvoted to at least [[Tagging_Mechanics#Tag_Mod_Power|non-solid border]].
*These tags are automatically pruned from galleries after 30 days of no voting activity.
*Please note that "reclass:asianporn" is no longer functional. See its [[asianporn|definition]] for details.

<div id="Directory"></div>

=== Tag Directory===
{{TagNav}}

== Information Sources==
The information used to tag should always be based solely on the contents of the images in the gallery itself. The gallery's title, comments, or 3rd party sites do NOT qualify as information sources in the majority of cases.

<u>Exceptions:</u>
*[[:Category:Series_Tag|Parodies]] have all of their canon counted as existing information (unless the dialogue indicates otherwise). This precludes informed attributes for visual tags (e.g. [[Lum]] from [[Urusei Yatsura]] can be tagged with [[oni]] but not with [[alien girl]]).
*If an artist's name is not present in the gallery it may be obtained from a verifiable source such as the circle's website or store listing.
*The title may be used as proof of [[incest]] (unless the dialogue indicates otherwise).
*Participants' genders being ''extremely'' vague may use a verifiable source to identify them.

==[[Know The Difference]]==
For tags that are often confused for one another.

==Bad Tags==
;Commissioners / Decensors / Scanners / Translators
:Do not produce the content.
;No Sexual Connection
:(e.g. baseball, celebrity, clouds, exercise, microphone, pillow, red eyes, sword)
;Opinionated / Pejorative
:(e.g. cute, extreme, funny, gross, hot, garbage, nice, sad, scary, terrible, ugly, weird)
;Publishers / Websites
:Do not actually produce the content. Rare exceptions apply if nothing else can be used to identify a work's creator.
;Software
:The tools the artist used to created the content are irrelevant.
;Too Common
: (e.g. anime, nymphomaniac, semen, sex, skirt, softcore, straight, upskirt, vaginal)
;Too Vague
: (e.g. areola, ass, fetish, nipples, pussy, shaved, wet)
;Writers
:Not to be confused with the artists.

== Do Not==
*Use category exclusive tags outside of their category (e.g. [[non-nude]] is only for [[Cosplay]], [[comic]] is only for [[Western]] or [[Misc]]).
*Use [[:Category:Language Tag|language tags]] for anything other than indicating a gallery's text.
*Use a language tag on [[imageset]]-style galleries unless a majority of it (50%+) contains text in that language.
*Tag [[mother]] when not in conjunction with [[incest]]. This includes women giving [[birth]], women who happen to have children, or [[milf]]s.
*Use the [[cosplay]] tag when characters in drawn works are dressed as other recognizable characters; use [[cosplaying]] instead.
*Downvote any "redundant" reclass tags (i.e. being the same as the gallery's current category).
*Downvote any tag(s) that becomes "invalid" due to the uploader attempting to remove valid content. The said gallery should be reported for a [[Expunging#Reverting_and_Splitting|reversion/spilt]] action.
**If the tag(s) remains invalid after the revert/split, they may be downvoted accordingly.
*Downvote [[Fetish_Listing#Expunging|expunging tags]] purely because an [[Expunging|expunge petition]] has not been created. The system will automatically prune them from an active gallery if they remain for longer than 30 days.
**If the expunge type is definitely not valid for the gallery, then it may be downvoted.

==== Temporary Tags ====
Upvoting these tags is generally unnecessary. Galleries may be fixed / updated which would render such tags invalid.
*[[incomplete]]
*[[missing cover]]
*[[out of order]]
*[[Expunging]] tags
<div id="Why Should I Tag?"></div>

==[[Rewards]]==
Tagging earns points towards the [[toplists]].

[[Image:Point.png]] Poor tagging will result in the user '''losing''' [[power]]. Any attempts at farming points, accuracy spoofing, or heavy misuse WILL result in a permanent [[ban]].

==Exact Tag Searching==
Searches for certain tags can return results from more tags than intended. This happens to tags that appear as partial strings inside longer tags.

<u>Example</u>: The tag ''f:wolf'' will match both [[wolf]] and [[wolf girl]]. This also impacts [[slave tag]]s; a search for ''f:anal'' may return a gallery tagged with [[sex toys]]. This happens because the search for ''anal'' matches "anal beads" which is slaved to [[sex toys]].

To avoid this users may search with a dollar sign at the end of the tag to search only for that string (e.g. ''f:wolf$'', ''f:anal$'', etc.)

==Tagging Hotkeys==
The following hotkeys can be used when a tag is selected.

{| class="wikitable" style="text-align: center;"
! rowspan="2" |Function
! colspan="4" |Hotkeys
|-
!Numpad!!Other
|-
|Show All Tagged Galleries||{{Keypress|4}}||{{Keypress|A}}
|-
|Show Tag Definition||{{Keypress|6}}||{{Keypress|D}}
|-
|Vote Up||{{Keypress|8}}||{{Keypress|W}}
|-
|Vote Down||{{Keypress|2}}||{{Keypress|S}}
|-
|Clear Selection||{{Keypress|5}}||{{Keypress|Spacebar}}
|}

==Tag Tracker==
Users may see recently added tags across all public galleries via https://repo.e-hentai.org/tools/tagtrack
*This tool is primarily for tag cleanup, including removing invalid tags and making strong valid ones.
*Tags are displayed per gallery, and show that that are:
**<span style="opacity:0.3">weak</span> (with 1-9 [[Mod Power|MP]])
**<span style="opacity:0.7">active</span> (with 10-99 MP)
**<span style="color:#0000a4">SOLID</span> (with ≥100 MP)
**<span style="color:#009b00">ENFORCED</span> (tags that were added, and were [[Tagging_Mechanics#Tag_Veto|hard enforced]])
**<span style="text-decoration:line-through; opacity:0.3">downed</span> (tags that were added, but reduced to 0 MP)
**<span style="text-decoration:line-through; opacity:0.3;color:#f00">vetoed</span> (tags that were added, but were [[Tagging_Mechanics#Tag_Veto|hard vetoed]]).
*The results may be filtered in the following ways:
**'''downed''' - Displays tags that were created and have been reduced to 0 MP without being vetoed.
**'''weak''' - Displays tags that were created and have between 1-9 MP inclusive.
**'''active''' - Displays tags that were created and have between 10-99 MP inclusive.
**'''solid''' - Displays tags that were created and have 100 MP or higher.
**'''aged galleries''' - Displays galleries that have been tagged after they are no longer considered new.
**'''revived tags''' - Displays tags that were killed, and have been revived.
**'''exclude expunged''' - Filters out expunged galleries from the list.
**'''exclude autotags''' - Filters out tags added by the system, e.g. p:[[original]], or tags added due to a [[Namespace|slaving action]], etc.
**'''Tag/NS''': Filters out all but the chosen tags, with the following formats:
***''tag'', with no namespace, e.g. [[hairy]], will search for tags in all namespaces that match it.
***''namespace:tag'', e.g. f:hairy, will search for all tags that match both the tag and namespace.
***''tagid'', will return results for only the tag that has the chosen tagid.
***''special:namespace'', e.g., special:female, will search for all tags with the chosen namespace.

==Tag History==
Users can check their own tag history (up to actions made within the last 60 days), accuracy ratings, and overall usage via this tool:

<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">https://repo.e-hentai.org/tools/taglist?uid={USERID}</pre>
*Replace {USERID} with a userID (can be found by going to a user's profile in the [[forums]]) then checking the URL.
**Example: [https://forums.e-hentai.org/index.php?showuser=5 Snowflake] (UID: 5) would use the URL https://repo.e-hentai.org/tools/taglist?uid=5
*A &from={UNIXTIME} string may be added at the end of the above-mentioned URL. This can be used to allow users to quickly review their tagging actions made on or before the specified time.
**The date and time provided in the string must be in the Unix time format.
**Example: If Snowflake wants to review their tag actions made on or before July 2, 2026, 15:34:17 UTC, they would use the URL https://repo.e-hentai.org/tools/taglist?uid=5&from=1783016057
**A "'''Show Older >'''" button is also available at the end of the page, allowing users to continue reviewing their tagging histories dating even further back in time.
*Votes are organized by gallery. The value next to each tag indicates the amount of [[power]] utilized for that action at the time.
**A <span style="color:#008000">green</span> positive value (e.g., <span style="color:#008000">'''+69'''</span>) indicates that the user upvoted that tag in the gallery.
**Meanwhile, a <span style="color:#ff0000">red</span> negative value (e.g., <span style="color:#ff0000">'''-69'''</span>) indicates a downvote on the tag from the user.
**An <em>italicized</em> entry (e.g., ''female:nakadashi'') indicates that the user started the said tag.
**A '''bolded''' entry (e.g., '''female:nakadashi''') indicates the said tag received enough upvotes to be classed as a solid border tag.
*Accuracy score calculations are delayed by 3 days. Further accuracy checks take place to ensure a tag vote remains correct. '''Accuracy values are not foolproof; users should always manually review their tags.'''
**Vote entries that are highlighted in <span style="color:#ff0000">red</span> (e.g., <span style="color:#ff0000">female:nakadashi</span>) either indicate a started/upvoted tag was killed, or a downvoted tag is still alive.
**Started/Upvoted tag killed will be assessed as a "bad" vote (e.g., <span style="color:#008000">'''+69'''</span> <span style="color:#ff0000">female:nakadashi</span>) and negatively affects your accuracy.
**A downvote on tag will also be assessed as "bad" (e.g., <span style="color:#ff0000">'''-69'''</span> <span style="color:#ff0000">female:nakadashi</span>) if another user upvotes it after your downvote. Your accuracy will also be negatively impacted.
***Should the tag becomes fully downvoted later, it will be retallied and no longer classed as a "bad" vote on your record.
***For this reason, users are encouraged to use the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread to ensure that the identified invalid tags are fully downvoted.
**Users may use the "Filter galleries with assessed bad tagvotes" toggle to quickly review their tag votes that were assed as "bad" by the system.
*Accuracy scores are split by month, year, and overall total. The metrics are further separated into "Started" and "Voted" accuracies.
**Only the most recent seven monthly accuracies will be shown to the user. Yearly accuracies reflect the user's average tagging performance over the last 12 months.
**"Started" indicates accuracy for tags the user added themselves. "Voted" indicates accuracy for votes on tags already on a gallery.
**Values of less than 100 tags will only show the number of tags voted in gray without an accuracy calculation.
**"-" indicates 0 tags were voted by the user during that time period.

*[[Janitor|Tag checkers]] may check the history of any user.
**[[Image:Point.png]] Having an accuracy metric highlighted in red puts the user at high risk for a [[ban]].

==Limitations==
Users with < 2 [[power]] are unable to start tags or downvote tags.

==See also==
*[[Fetish Listing]] - A categorized list of all official fetish tags.
*[[Technical_Issues#Gallery_Tagging|Technical Issues - Gallery Tagging]]
*[[Toplists#Tagging_Toplists|Toplists - Tagging]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] - Please report any bad tagging here.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]
[[Category:Rules]]

E-Hentai Janitor

2026-08-08T01:19:12Z

Kagoraphobia:

Certain members have been given special abilities or access to restricted tools due to their expertise and/or historic diligence and willingness to help make E-Hentai a better place.

Tag vetoers will be classed as "inactive" under [[Talk:E-Hentai Janitor| certain conditions]]. These users are indicated with a gray <span style="opacity:0.3">✔</span>.

Removal of janitor role(s) is generally done due to extended inactivity or by own request. Re-assignment is possible should the user return from inactivity.

{| class="wikitable sortable" width="100%" style="text-align: center"
! rowspan="2" |Name
! rowspan="2" width="12%" |[[Forum]] Mod
! rowspan="2" |[[IRC]] Op
! rowspan="2" |[[EHWiki]] Admin
! colspan="3" |[[Tagging]]
! colspan="2" |[[namespace|Namespacer]]
! colspan="4" |[[Galleries]]
! rowspan="2" |Additional
|-
! width="6.5%" |Cleaning!!Vetoing!!Checking
! width="6.5%" |Approving!!Grouping
! width="6.5%" |Expunging!!Locking!!Moderating!!Banning
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4791588 -Lumina-]|| || || ||✔|| || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=243587 Binglo]|| || ||✔||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=485420 BlackHimari]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3201420 Byza]||<span title="The Vigilante" style="border-bottom:1px dotted">Section</span>|| || ||✔||✔||✔||✔||✔
|✔||✔||✔ || ||ES-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=359756 chriseras]|| ||✔|| || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1207129 Cipher-kun]|| || || ||✔||✔||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=95571 CornerCactus]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1908893 Dnkz]|| || || ||✔||✔||✔||✔||
|✔||✔||✔|| ||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=5845370 Doof071]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2115725 Eboshi]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||KR-EN<br>JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4103205 ehaa]|| || || || || || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2790 elgringo]|| ||✔|| ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=367313 ericeric91]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=384226 EsotericSatire]||<span title="Adult Chat, Anime & Manga Chat, Culture Corner, Gamers Chat, Tech Chat" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=6011981 Feftak]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3737344 Glovelove.]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=561643 jm320]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4850902 Kagoraphobia]||Global||✔||✔||✔||✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge<br>CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7508384 krvn64]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=560909 Mags_]|| || || || || || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=589675 Maximum_Joe]|| || || || || || || ||
| || || || ||''<span title="Thank you for everything you have done for the site. Rest in peace, Joe." style="border-bottom:1px dotted">Retired</span>''
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=204246 meow_pao]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1898816 Mrsuperhappy]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3655031 Muffinlemon]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3169265 nasu]||<span title="Site Discussion & Helpdesk, The Vigilante" style="border-bottom:1px dotted">Section</span>
| || ||✔||✔||✔||✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=867559 Nezu]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2977124 Noni]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>||✔|| || || ||✔||✔||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=600260 noones]|| || || || || || ||✔||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=892479 peterson123]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3139892 poiuytrewqazx]|| || || ||✔|| || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=958849 rinruririn]||<span title="Introduction, Site Discussion & Helpdesk, The Vigilante, Requests and Bounties" style="border-bottom:1px dotted">Section</span>
| || ||✔|| || || ||
| ||✔|| || || JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1913944 Rogabute]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=989173 Shank]||Global||✔||✔||✔||✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2714686 shiluo]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1732804 simplesimon32]|| ||✔|| ||✔|| || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=352564 SIRIUSs]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2203 Spectre]||Global|| ✔|| ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=976341 svines85]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4842635 terry]||Global|| || ||✔||✔||✔||✔||✔
|✔||✔||✔||✔||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=582527 TheGreyPanther]|| || || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1194701 tobeunforgiven2]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3172187 Waitugreat]|| || || || || || || ||
| ✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7752125 流萤啾啾]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=374857 海想列車]|| || || ||✔|| || || ||
| || || || ||
|}

==Explanations==
Some janitor roles come with implicit permission(s), which may be seen [[Talk:E-Hentai_Janitor|here]].
{| class="wikitable"
!Position
!Capabilities
|-
|Forum Mod||Edit or delete [[forum]] posts. Global Mods can impose posting restrictions on accounts with severe [[forum rules]] violations.
|-
|IRC Op ||Kick or ban users from the [[IRC]] channel.
|-
|EHWiki Admin ||Manage wiki editing permissions. Can also edit pages that are marked as protected.
|-
|Tag '''Cleaning'''||Users with this privilege are able to:
*Downvote tags at full [[power]].
* Bypass the minimum MP requirement for downvoting locked-in solid tags.
*Cancel out implied language tags from the uploader [[Making_Galleries#Uploading|language setting]] with a -100 [[power]] downvote.
*Have elevated voting power (3 votes) in [https://forums.e-hentai.org/index.php?showforum=89 tag suggestions].
|-
|Tag '''Vetoing'''||These users are given additional tagging privileges:
*[[Tagging_Mechanics#Tag_Veto|Veto/Enforce]] tags on a gallery, preventing them from being resurrected or killed respectively.
* Bypass the minimum MP requirement for reviving downvoted tags.
*Vote against incorrectly vetoed/enforced tags.
*Bypass the MP requirement of [[:Category:Power_Restricted|power-restricted]] tags.
*Bypass whitelists for certain special tags (e.g., [[rough translation]]).
*Instantly remove [[rough translation]] tags added by autotagger.
*Create temp tags even without meeting the [[power|power requirement]] (i.e., 25).
*Participate in the [https://forums.e-hentai.org/index.php?showtopic=136551 community veto] process presuming the user is an [[Talk:E-Hentai_Janitor| active tag vetoer]].
|-
|Tag '''Checking'''||View any user's or gallery's [[Gallery_Tagging#Tag_History|tag histories]].
|-
|Namespacer - '''Approving'''||Approve, rename, and set [[namespace]]s on the pending tags from the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Namespacer - '''Grouping'''||[[slave tag|Group tags]], as well as set blocks, [[namespace]]s, and aliases on any existing tags. Can also reject pending tags on the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Galleries '''Expunging'''
|Start an [[expunge]] on a gallery that has previously been de-expunged by the community or administration. Can also file an [[Expunging#Appeal_an_Incorrect_Expunge|appeal]] on aged expunges.
|-
|Galleries '''Locking'''|| Lock galleries with any depictions of real children, or other illicit content (e.g., real-life snuff and gore).
|-
|Galleries '''Moderating'''||Moderators with the following gallery privileges:
*Receive a base [[power]] boost of +10.
* Block further [[Making_Galleries#Updating|updates]] on galleries that are excessively bumped.
* Delete malicious [[EHTracker#Expunges|torrents]].
*Both [[comment]] and vote on other comments in the same gallery.
*Permanently hide gallery comments with a downvote, assuming they have reached -100 [[power]].
*Review recently posted comments that have been [[Gallery_Commenting#Perma-Hidden_Comments|permanently hidden]].
*Check the original ownership of a [[disowned]] gallery.
*Enforce the [[AI Generated]] indicator when it is falsely denied by the uploader.
*Add [[rough translation]] without a detailed comment when the work is [[Talk:rough translation|clearly a machine/AI translation]].
|-
|Galleries '''Banning'''||Restrict users from performing certain gallery activities due to major site rule violations (e.g., spamming). All [[Bans|ban]] actions will be reviewed by the administration.
|-
|Tag Judge ||Make judgement calls on [[Fetish_Listing|fetish/content tags]].
|-
|<span title="Quality Control" style="border-bottom:1px dotted">QC</span> Judge||Make judgement calls on [[Expunging#Superior_Versions|gallery superiority]].
|-
|Rename Judge||Make judgement calls on [[renaming]].
|-
|JP-EN||Heightened trust in Japanese-English translations/transliterations.<br>Similar positions exist for other languages (CN-EN, ES-EN, KR-EN).
|}

[[Category:Users]]

ilya

2026-08-07T02:13:15Z

Kagoraphobia:

*'''Series''': [[Rakudai Kenja no Gakuin Musou]]
*'''Gender''': Female
*'''Japanese''': イリア
*'''Note''': Not to be confused with [[Illyasviel von Einzbern]].

[[Category:Character Tag]]

ilya

2026-08-07T01:42:47Z

Kagoraphobia: Created page with "*'''Series''': Rakudai Kenja no Gakuin Musou *'''Gender''': Female *'''Japanese''': イリア *'''Note''': Note to be confused with Illyasviel von Einzbern Category:Character Tag"

*'''Series''': [[Rakudai Kenja no Gakuin Musou]]
*'''Gender''': Female
*'''Japanese''': イリア
*'''Note''': Note to be confused with [[Illyasviel von Einzbern]]

[[Category:Character Tag]]

Illyasviel von Einzbern

2026-08-07T01:42:40Z

Kagoraphobia: Redirected page to illyasviel von einzbern

#REDIRECT [[illyasviel von einzbern]]

Rakudai Kenja no Gakuin Musou

2026-08-07T01:40:12Z

Kagoraphobia: Redirected page to rakudai kenja no gakuin musou

#REDIRECT [[rakudai kenja no gakuin musou]]

rakudai kenja no gakuin musou

2026-08-07T01:39:05Z

Kagoraphobia: Created page with "*'''Type''': Anime *'''Japanese''': 落第賢者の学院無双 Category:Series Tag"

*'''Type''': Anime
*'''Japanese''': 落第賢者の学院無双

[[Category:Series Tag]]

Hentai@Home

2026-08-06T08:25:31Z

Kagoraphobia:

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]].
*If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*Applications for H@H clients in Europe are currently closed due to excess capacity. Users who are currently running H@H or [[donators]] may still apply for new clients in the region.
*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. Ensure that your PM includes the following information:
*Maximum bandwidth that will be reserved for H@H. This will be limited by your '''outgoing''' bandwidth, not the rate you can download at.
*Disk space that will be reserved for the image cache.

For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

[[Image:Point.png]] <span style="color:#ff0000">'''DO NOT reset static ranges unless your cache has been lost. Regular resets will result in the [[Hentai@Home#Revocations|revocation]] of your client.'''</span> It should '''ONLY''' and '''ALWAYS''' be reset if the cache has been deleted or is otherwise lost, or else the client will encounter serious [[Hentai@Home#Trust|trust]] issue.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive ~1 [[GP]] for each hit on their client, adjusted for the average served file size. They may also compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-06T06:04:32Z

Kagoraphobia: /* Obtaining Client Keys */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*Applications for H@H clients in Europe are currently closed due to excess capacity. Users who are currently running H@H or [[donators]] may still apply for new clients in the region.
*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. Ensure that your PM includes the following information:
*Maximum bandwidth that will be reserved for H@H. This will be limited by your '''outgoing''' bandwidth, not the rate you can download at.
*Disk space that will be reserved for the image cache.

For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

[[Image:Point.png]] <span style="color:#ff0000">'''DO NOT reset static ranges unless your cache has been lost. Regular resets will result in the [[Hentai@Home#Revocations|revocation]] of your client.'''</span> It should '''ONLY''' and '''ALWAYS''' be reset if the cache has been deleted or is otherwise lost, or else the client will encounter serious [[Hentai@Home#Trust|trust]] issue.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-06T05:48:47Z

Kagoraphobia: /* Static Ranges */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*Applications for H@H clients in Europe are currently closed due to excess capacity. Users who are currently running H@H or [[donators]] may still apply for new clients in the region.
*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

[[Image:Point.png]] <span style="color:#ff0000">'''DO NOT reset static ranges unless your cache has been lost. Regular resets will result in the [[Hentai@Home#Revocations|revocation]] of your client.'''</span> It should '''ONLY''' and '''ALWAYS''' be reset if the cache has been deleted or is otherwise lost, or else the client will encounter serious [[Hentai@Home#Trust|trust]] issue.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T20:53:50Z

Kagoraphobia: /* Minimum Requirements For New Clients */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*Applications for H@H clients in Europe are currently closed due to excess capacity. Users who are currently running H@H or [[donators]] may still apply for new clients in the region.
*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

momiji inubashiri

2026-08-05T20:48:43Z

Kagoraphobia: you fucking dumbass

*'''Series''': [[Touhou Project]]
*'''Gender''': Female
*'''Japanese''': 犬走椛
*'''Note''': See the [[Talk:momiji_inubashiri|Talk Page]] for rulings.
*[https://e-hentai.org/tools.php?act=taggroup&mastertag=15463 '''Slave Tags''']
[[Category:Character Tag]]

Tag Creation

2026-08-05T13:48:14Z

Kagoraphobia: /* Guidelines for Submission */

[[Image:Tag Creation UI.png|thumb|The tag creation UI]]

<span style="color:red">'''Adding to the tracker follows normal voting rules. If you are unsure about the validity of a tag, whether that be what namespace it should be, the name, whether it's valid on the gallery, etc, request in the [https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread] and not the tracker.'''

__TOC__
Users with a minimum of 15 [[Mod Power]] are allowed to create tags that have never been created before (under the ''temp'' [[namespace]]), assuming that sufficient justification has been provided.
*Only artist, group, cosplayer, parody, or character tags can be created in this manner.
**Users with less than 15 [[Mod Power]] may request the above-mentioned tags to be created by posting in the [https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread].
*[[Image:Point.png]] <span style="color:#ff0000">'''The creation of [[Fetish_Listing|fetish/content tags]] CANNOT be handled through this system.'''</span> See [[Gallery_Tagging#newtag|here]] for the proper procedures on proposing these tags.

==How To==

'''Step 1:''' Visit the gallery where the new tag would be applicable.

'''Step 2:''' Type in the proposed tag name with the ''temp:'' prefix (e.g., temp:kaguya shinomiya). Submitting the entry will open up the '''New Tag Justification''' window.
*You will be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
**'''Hitting the "OK" button will also bring up the New Tag Justification window if you have at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
**[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence may lead to a [[Bans|ban]].'''</span>
**If the temp tag is incorrectly named, i.e. wrong spelling, or localization instead of the romanization, '''do not''' create a second temp tag to fix this.
**If no more specific tag exists, and it is not being used to tag other kinds of content, upvote the temp and add a note to rename into the justification.
***If used for other content, OR there are multiple temp tags for the same content, OR a more specific already namespaced tag exists, request in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping] thread instead.
*<u>Note</u>: The system will only recognize characters a-z, 1-0, hyphens "-", periods ".", and spaces between characters " ". Everything else will be discarded automatically.
*[[Image:Point.png]] When requesting a more specific tag for approval that already has another tag <span style="color:red">'''DO NOT'''</span> downvote the already existing namespaced tag until/if it has been approved. The request may get denied, and the existing tag may be correct, for technical reasons or otherwise.
**In most cases, such tags should be requested in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread] rather than the tracker.

'''Step 3:''' Select the correct [[namespace]] for the newly created tag, together with necessary notes and references, and anything else that is helpful for the validation process.
*You must first describe the nature of the temp tag. External sources to support the proposed tag must also be provided.
**[[Image:Point.png]] '''Sufficient justification must be provided, or else the temp tag will be rejected by a moderator.'''
**For what can be considered a reliable and valid third-party source for the temp tag, please read the [[Tag_Creation#Guidelines_for_Submission|Guidelines for Submission]] section.
*Suggested Formats:
<pre>This tag is for a parody character named "Kaguya Shinomiya", who appeared on pages 2-12, 15-18, and 20.

References:
https://kaguyasama-wa-kokurasetai.fandom.com/wiki/Kaguya_Shinomiya
https://myanimelist.net/character/136359/Kaguya_Shinomiya
https://en.wikipedia.org/wiki/List_of_Kaguya-sama:_Love_Is_War_characters</pre>
<pre>This tag is for an artist named "Andy Price".

References:
https://en.wikipedia.org/wiki/Andy_Price_(artist)
https://andypriceart.bigcartel.com/
https://twitter.com/AndyPriceArt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor</pre>

'''Step 4:''' Hit "Save Changes" after submitting all the relevant materials. This will notify a [[Janitor|namespacer]] to process your request(s), please be patient for a response.
*A list of your pending temp tag requests can be accessed via [https://e-hentai.org/tagjustification.php this link]. You may also edit the sources provided as needed.

'''Step 5:''' A [[Janitor|namespacer]] will either approve or reject the temp tag. The requester will receive a final [[forum]] PM with the result.
*'''In the event that your new tag is rejected, it will be deleted from the database and will no longer be usable.'''
**You may submit an inquiry on the rejection(s) by posting in the [https://forums.e-hentai.org/index.php?showtopic=107861 General tag discussion] thread.
*Aside from approval or rejection, a [[Janitor|namespacer]] may instead request for a revision on the provided sources. This will usually be because of bad formatting, lacking supporting materials, or requesting clarification.
**The requester will be sent a [[forum]] PM to notify them. To revise, simply open [https://e-hentai.org/tagjustification.php this page] and click on the tag name marked with <span style="color:red">'''REVISE'''</span>.
**Specific instruction on the source revision can also be found in comments with the ''(flagged for revision)'' flag.

==Tag Approval Tracker==
*A list of active temp tag requests can be found at https://repo.e-hentai.org/tools/tagapprove. The page is split into the following categories:
**<u>Pending Tags</u>: Lists any tags that still require a [[Janitor|namespacer]] or the tag requester attention.
***Tags that are in black have yet to be processed, tags in red require further information or clarification from the requester.
***The tag sources for pending tags may be modified at any time by the initial tag requester.
**<u>Approved Tags</u>: Lists processed tags that have been given a namespace or slaved.
**<u>Rejected Tags</u>: Lists processed tags that have been rejected, if you are sure your tag was rejected wrongly, you may make a post in the [https://forums.e-hentai.org/index.php?showtopic=107861 General tag discussion] thread.
*Users with at least 2 [[Mod Power]] may leave comments on a pending request. Please note that '''the comments should be providing additional information or clarification only'''. Tags created through this tool do not require additional support, so comments only in support should not be made.

===Trivia===
[[File:hanabi.jpg|250px|none|caption]]The tracker being fully cleared of pending requests will display fireworks.

==Guidelines for Submission==
;<div id="Sources"></div>Supporting Materials
:Sources are preferred to be official where possible. These may include the artist's own website or social media, signatures within the work, colophon, etc.
:*Official sources are required for any [[Tag_Creation#Romanization|romanization]] that is not revised Wapuro Hepburn.
:*Social Media <span style="text-decoration:underline;">urls</span> are not generally considered a valid source. If an artists social media account is named John Smith, while its url is @john123, it will not be considered as a supporting material for a request for a:john123, but would be considered for a request for a:john smith.
:**Exceptions may sometimes apply. Usually, this is for cases where their name is too common/already in use, or to give clarity on the romanization of kanji that has multiple readings, etc.
:Unofficial sources are accepted when official ones are unavailable. These may be fan sites, Wikipedia, distribution sites, etc.
:*Such sources should generally have at a bare minimum the original kanji or kana.
:*Some unofficial sources may not have enough trust, so it is advisable to provide as many supporting materials as possible.
:<div id="badsources"></div>Some sources are considered not trustworthy at all, and will not be relied on without additional supporting materials, these include:
:*Google Translate, or any automated translation software
:*English DLsite
:*DMM
:*Anthologies table of contents pages
:*Booru sites (e.g., Danbooru)
:**Exceptions may be granted for artists that have an account with one of the booru sites and only uploads to it.
:Video links will not be accepted unless there is a good faith belief that no other source exists. In such cases, the suggestion should be made in the [https://forums.e-hentai.org/index.php?showtopic=275305 tag creation] thread, due to the increased amount of time it takes to check these.
:*The name must appear within the video. The only acceptable instance of the video title being justification for a tag, is when the video is provided by a first-party source.
;<div id="nameorder"></div>Name Order
:For ''artist'' and ''cosplayer'' tags, the name order defaults to the order of the originating country. For example, a tag for a Japanese artist should be submitted as ''surname'' then ''given name''.
:*Exceptions could be granted for cases where the content creator consistently uses a different name order.
:For ''character'' tags, the name order is standardized in the Western order (i.e., ''given name'' then ''surname''). Rare exceptions exist but they are not granted usually.
:*<u>Standardized Exceptions</u>: [[touken ranbu]] characters that are named after swords, as well as [[vtuber|vtubers]] are created in the original written order (e.g., ''赤井はあと'' --> ''akai haato'').
:*Additional rulings on character tags can be found [[Gallery_Tagging#Good_Tags|here]] under the "Participants" subsection.
;<div id="Romanization"></div>Romanization
:Romanization for new tags should be in revised Wapuro Hepburn. For example, さいとう would be "Saito<span style="color:red">u</span>" instead of "Saito". Exceptions for commonplace names may exist (e.g., Tokyo).
:*If the tag is requested in a different romanization method, an official source must be supplied in the justification.
:*If all other already namespaced tags in the series are not in revised Wapuro Hepburn, this may be used as justification instead of an official source, but example tags must be provided.
:Western localized names are usually only suitable as aliases and should not be created.
:*<div id="localized"></div>If other already namespaced tags in the series already use the localized name, it is acceptable to create the localized version, but example tags must be provided.
:If there is no example of localized names being used within the parody, the tag should be requested in revised Wapuro Hepburn of the original source name.
:*In some cases, a namespacer will still choose the localized name as the master and will rename it. Such cases will usually be, but not always and not limited to, very popular parodies that are not well known in the west by anything other than the localized name.
;<div id="Presence"></div>[[Presence]]
:Tags require sufficient [[presence]] to be namespaced. When requesting, please provide enough page numbers to indicate presence.
:*This is '''always''' required for the following: long galleries, galleries with multiple creators when requesting creator tags, or galleries where it is not immediately obvious which pages count.
;<div id="relevancy"></div>Content Relevancy
:Some works always count as 0 presence for namespacing purposes only. These include, but are not limited to:
:*[[screenshots|Screenshots]]
:*Non-parody works (e.g., first party [[artbook]] of a series)
:*[[non-h game manual|Non-H game manuals]]
:*Anything that [[Expunging#Forbidden.2FOther|does not fit the theme of the site]]
:*[[Asian Porn]]
:**This extends to models in the [[cosplay]] category that are not cosplaying
:*Galleries that were [[expunged]] correctly
;Series Segregation
:Certain parodies will be slaved under a generic series tag depending on various factors. For instance, "diablo 2" and "diablo 3" are slaved under "parody:diablo" due to high connectivity.
:*Judgment criteria and existing rulings can be found on the [[Series Segregation]] page.
;<div id="renaming"></div><div id="tag_slaving"></div><div id="blocking"></div>Tag Renaming/Slaving/Blocking Requests
:Do '''NOT''' create or upvote any temp tag for the purpose of renaming already namespaced tags, or for slaving.
:You should also '''NOT''' upvote existing temp tags not yet on the tracker for the purpose of requesting a tag block.
:*For these requests, please make a post in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread].
;<div id="unacceptable tags"></div>Unacceptable Tags
:Certain tags will be rejected outright. Please see [[Gallery_Tagging#Bad_Tags|here]] for more examples, as well as the following:
:*Writers.
:*Software.
:*Talent agencies.
:**[[Hololive]] and [[Nijisanji]] are the only exceptions.
:*Character tag requests should be for fictional characters only. [[vtuber|VTubers]] are considered as fictional characters.
:*AI galleries are not accepted for new tag requests, without some level of effort (see [[Talk:Tag_Creation|here]] for details). This will usually be if it's been structured as a comic, or that they have only used AI to assist their own art, etc. This applies to group/artist tags, as well as parody/character tags.
:'''Note:''' If you spot a dated temp tag that should be blocked (e.g., typo, fetish tag without approval), please submit a blocking request in the [https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread].

==See also==
*[[Gallery Tagging]]
*[[Namespace]]
*[https://repo.e-hentai.org/tools/tagapprove Tag Approval Tracker] - A list of pending, accepted, or rejected temp tag requests.
*[https://e-hentai.org/tagjustification.php Tag Justification Index] - Shows all of the pending temp tags created by yourself. You may update your requests via this page.

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=275305 Tag Creation/Namespacing Request Thread] - For submitting tag creation requests should you have a [[Mod Power]] under 15.
*[https://forums.e-hentai.org/index.php?showtopic=275306 Tag Grouping Request Thread] - For tag slaving, aliasing, renaming, and blocking requests.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion] - You may ask questions related to the namespacing mechanism here.

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]

Hentai@Home

2026-08-05T09:06:28Z

Kagoraphobia:

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T08:06:25Z

Kagoraphobia: /* Minimum Requirements For New Clients */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|
*Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|
*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Sufficient uptime
|
*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|-
|Located in compatible countries
|
*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
*Due to deteriorating network conditions, it is not possible to run H@H in the Russian Federation.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

My Home

2026-08-05T07:53:47Z

Kagoraphobia: /* My Settings */

The [https://e-hentai.org/home.php My Home] page is where users may observe or make use of various functions involving the [[E-Hentai Galleries]].

==Overview==
;Image Limits
:Displays the current limit of the user to view images. Also allows for this limit to be reset manually at the cost of [[GP]] (if no GP is available, [[Credits]] will be converted at the 24-hour "high" rate to cover the cost). This limit and regen rate (typically 3-5 per minute) vary based on server load.
* The limit is tracked by IP address by default; this can be changed to account-only tracking via a Bronze [[Star]] or higher, or the ''More Pages'' [[Hath Perk]].
** Alternatively, non-donators can unlock an account-based quota for 24 hours by spending 20,000 [[GP]]. This temporary image limit will be set at 10,000, and will regenerate and be consumed as normal. '''Note that clearing your cookies will revert you to IP-based limits.'''
* Force-reloading a failing image counts as 50 hits.
* Downloading an original image counts as (10 * filesize_in_MB) hits.
** Will instead cost [[GP]] under certain conditions. Please see [[Downloading|here]] for details.
* If the user opted out of [[Hentai@Home]] content delivery (under [[My_Home#My Settings|Image Load Settings]]) all [[API]] requests will count as 5 hits instead of 1, even if the image already is cached or the request fails.
** Only [[donator]]s may pick this option and should only do so if experiencing H@H issues. It is recommended to have the ''More Pages'' (or above) [[Hath Perk]] unlocked as this will drain image limits 5x as fast. This is especially true for [[MPV]], which preloads images, and larger [[galleries]].
;[[EHTracker]]
:Lists the various data and statistics for the user's torrent behavior.
;Total GP Gained
:Displays a summary of all [[GP]] earned.
;[[Toplists]]
:Displays the position the user has reached on any toplist if the user is within the top 1,000.
;Moderation Power
:Displays the user's sources and total [[mod power]].

==My Stats==
*Shows a total of all hits/visits a user's galleries have collectively received.
**Note that this displays the last 28-31 days' stats depending on the number of days in the preceding month, NOT the days since the start of the current month.

==My Settings==
Allows the adjustment of various visibility settings.
*Image load settings.
**The "Default port clients only" option restricts image loads to [[H@H]] clients using port 443.
***This will also bypass the [[H@H]] network when:
****Viewing original images smaller than 10 MiB in galleries that were posted in the last year.
****Regular browsing when the use of original images is enabled and the file would normally be resampled at 2400x.
****Using the "Download Original" button (i.e., [[Downloading|manual download]]). The cost will also be increased as a result.
****Using the [[Hentai@Home#H.40H_Downloader|H@H Downloader]].
**The "No" options will completely bypass the [[H@H]] network when loading any images. Only available for [[Donation|donators]]. Picking these options will quickly consume your [[My_Home#Overview|image limits]].
**The "H@H Region" option lets you override the region used to determine which part of the H@H network to load images from.

*Image size settings.
**Selecting the default horizontal resolution. The "Auto" option is generally 1280x, or 780x if browsing on mobile.
***2560x resamples will not be serviced for galleries older than one year; 1920x resamples will be used instead. They can still be used on older galleries if they were already created.
**Enabling/Disabling the use of original images instead of the resampled versions.
***This feature requires the ''Source Nexus'' [[Hath Perk]].
***Resampled images will still be used if:
****You select a default horizontal resolution different than "Auto" and the image in question is wider.
****The original image is larger than 10 MiB (or 4 MiB for galleries older than one year).

*Displaying the Romanized or Japanese [[Renaming|gallery name]].

*[[Archive]] download behavior.

*Selecting the default viewing mode and [[categories]] for the front/search pages.

*Enabling/disabling historic UI elements.

*Renaming [[Favorite]] categories, as well as setting the sort order for galleries on your favorites page.

*Choosing the search result count per page for the index/search page and [[EHTracker|torrent]] search pages.
**This feature requires the ''Paging Enlargement'' [[Hath Perk]].

*Adjusting the default thumbnail configurations, as well as thumbnail scaling for Thumbnail and Extended viewing modes.

*[[Rating]]s colorization.

*Adjusting [[My Tags]] thresholds.

*Enabling/disabling the filtered removal count readout ("Your custom filters removed XX galleries from this page").

*Excluding [[languages]] besides Japanese (requires the corresponding [[tags]] to be at 100 [[mod power]] or higher).
**"Other" refers to languages not already listed.
**"N/A" refers to [[textless narrative]] and [[text cleaned]] galleries.

*Excluding uploaders to prevent their galleries from being displayed.
**Users can exclude up to 100 uploaders.
**[[Donation#Stars | Gold Star]] or above donors can exclude up to 1,000 uploaders.

*Overriding the virtual width of the site for mobile devices.

*Choices for the order in which the gallery [[comments]] and [[tags]] are sorted.

*Configuring the label displayed below gallery thumbnails.

*Adjusting the configurations of [[Multi-Page Viewer]].
**This feature requires the ''Multi-Page Viewer'' [[Hath Perk]].

==[[My Tags]]==
*For filtering or highlighting galleries containing sets of [[tags]].

==[[Hentai@Home]]==
*For the adjustment of [[H@H]] client settings.
*Includes a download link of the [[H@H]] client software.

==[[Donations]]==
*For donation transactions; also displays the cumulative amount already donated.
*[[Adopt-A-Server]] is also managed from here.

==[[Hath Perks]]==
*For the purchase of hath perks in exchange for [[Hath]].

==[[Hath Exchange]]==
*For the purchasing and selling of [[Hath]] for [[credits]].

==[[GP Exchange]]==
*For the purchasing and selling of [[GP]] for [[credits]].

==[[Credit]] Log==
*A log of [[credit]] income and spending activities for the last 30 days (except for the [[Dawn]] event).

==[[Karma]] Log==
*A log of who has imbued [[karma]] and the messages they have left.

{{EHGNav}}

[[Category:E-Hentai Galleries]]

Hentai@Home

2026-08-05T07:47:50Z

Kagoraphobia: /* Revocations */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T07:42:52Z

Kagoraphobia: /* Limits */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''P4 ranges will be completely removed if there is any reduction in the cache size.'''

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T07:25:59Z

Kagoraphobia: /* Cache */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

Reducing cache size below the minimum requirement, as calculated by the formula above, will result in the demotion/loss of static ranges. Clients are not permitted to reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====Priority Levels====
Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T01:06:43Z

Kagoraphobia: /* Minimum Requirements For New Clients */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

Reducing cache size below the minimum requirement, as calculated by the formula above, will result in the demotion/loss of static ranges. Clients are not permitted to reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T01:04:41Z

Kagoraphobia: /* Limits */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

Reducing cache size below the minimum requirement, as calculated by the formula above, will result in the demotion/loss of static ranges. Clients are not permitted to reduce their cache size below 10 GiB.

Clients eligible for [[Hentai@Home#High-Capacity_Ranges|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T00:47:46Z

Kagoraphobia: /* High-Capacity Ranges */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, static_ranges * 512 / 1024)</pre>

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges a client can have is limited to 1 per 1 GiB of reserved disk space, taking into account the disk space already reserved for P1-3 ranges. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T00:44:24Z

Kagoraphobia: /* Cache */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, static_ranges * 512 / 1024)</pre>

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges that a client can have is limited to 1 per 1 GiB of reserved disk space. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Hentai@Home

2026-08-05T00:34:00Z

Kagoraphobia: /* Limits */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GiB) must be enough to maintain static ranges. [[Hentai@Home#Static_Ranges|P4 (Priority 4) ranges]] are not counted towards this requirement.

Clients in the primary regions (i.e., Asia, Europe, North America, and mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, static_ranges * 512 / 1024)</pre>

If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example if the client if offline for an extended period of time.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges that a client can have is limited to 1 per 1 GiB of reserved disk space. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

My Home

2026-08-05T00:16:12Z

Kagoraphobia: /* My Settings */

The [https://e-hentai.org/home.php My Home] page is where users may observe or make use of various functions involving the [[E-Hentai Galleries]].

==Overview==
;Image Limits
:Displays the current limit of the user to view images. Also allows for this limit to be reset manually at the cost of [[GP]] (if no GP is available, [[Credits]] will be converted at the 24-hour "high" rate to cover the cost). This limit and regen rate (typically 3-5 per minute) vary based on server load.
* The limit is tracked by IP address by default; this can be changed to account-only tracking via a Bronze [[Star]] or higher, or the ''More Pages'' [[Hath Perk]].
** Alternatively, non-donators can unlock an account-based quota for 24 hours by spending 20,000 [[GP]]. This temporary image limit will be set at 10,000, and will regenerate and be consumed as normal. '''Note that clearing your cookies will revert you to IP-based limits.'''
* Force-reloading a failing image counts as 50 hits.
* Downloading an original image counts as (10 * filesize_in_MB) hits.
** Will instead cost [[GP]] under certain conditions. Please see [[Downloading|here]] for details.
* If the user opted out of [[Hentai@Home]] content delivery (under [[My_Home#My Settings|Image Load Settings]]) all [[API]] requests will count as 5 hits instead of 1, even if the image already is cached or the request fails.
** Only [[donator]]s may pick this option and should only do so if experiencing H@H issues. It is recommended to have the ''More Pages'' (or above) [[Hath Perk]] unlocked as this will drain image limits 5x as fast. This is especially true for [[MPV]], which preloads images, and larger [[galleries]].
;[[EHTracker]]
:Lists the various data and statistics for the user's torrent behavior.
;Total GP Gained
:Displays a summary of all [[GP]] earned.
;[[Toplists]]
:Displays the position the user has reached on any toplist if the user is within the top 1,000.
;Moderation Power
:Displays the user's sources and total [[mod power]].

==My Stats==
*Shows a total of all hits/visits a user's galleries have collectively received.
**Note that this displays the last 28-31 days' stats depending on the number of days in the preceding month, NOT the days since the start of the current month.

==My Settings==
Allows the adjustment of various visibility settings.
*Image load settings.
**The "Default port clients only" option restricts image loads to [[H@H]] clients using port 443.
***This will also bypass the [[H@H]] network when:
****Viewing original images smaller than 10 MiB in galleries that were posted in the last year.
****Regular browsing when the use of original images is enabled and the file would normally be resampled at 2400x.
****Using the "Download Original" button (i.e., [[Downloading|manual download]]). The cost will also be increased as a result.
****Using the [[Hentai@Home#H.40H_Downloader|H@H Downloader]].
**The "No" options will completely bypass the [[H@H]] network when loading any images. Only available for [[Donation|donators]]. Picking these options will quickly consume your [[My_Home#Overview|image limits]].
**The "Browsing Country" option lets you override the country used to determine which part of the H@H network to load images from.

*Image size settings.
**Selecting the default horizontal resolution. The "Auto" option is generally 1280x, or 780x if browsing on mobile.
***2560x resamples will not be serviced for galleries older than one year; 1920x resamples will be used instead. They can still be used on older galleries if they were already created.
**Enabling/Disabling the use of original images instead of the resampled versions.
***This feature requires the ''Source Nexus'' [[Hath Perk]].
***Resampled images will still be used if:
****You select a default horizontal resolution different than "Auto" and the image in question is wider.
****The original image is larger than 10 MiB (or 4 MiB for galleries older than one year).

*Displaying the Romanized or Japanese [[Renaming|gallery name]].

*[[Archive]] download behavior.

*Selecting the default viewing mode and [[categories]] for the front/search pages.

*Enabling/disabling historic UI elements.

*Renaming [[Favorite]] categories, as well as setting the sort order for galleries on your favorites page.

*Choosing the search result count per page for the index/search page and [[EHTracker|torrent]] search pages.
**This feature requires the ''Paging Enlargement'' [[Hath Perk]].

*Adjusting the default thumbnail configurations, as well as thumbnail scaling for Thumbnail and Extended viewing modes.

*[[Rating]]s colorization.

*Adjusting [[My Tags]] thresholds.

*Enabling/disabling the filtered removal count readout ("Your custom filters removed XX galleries from this page").

*Excluding [[languages]] besides Japanese (requires the corresponding [[tags]] to be at 100 [[mod power]] or higher).
**"Other" refers to languages not already listed.
**"N/A" refers to [[textless narrative]] and [[text cleaned]] galleries.

*Excluding uploaders to prevent their galleries from being displayed.
**Users can exclude up to 100 uploaders.
**[[Donation#Stars | Gold Star]] or above donors can exclude up to 1,000 uploaders.

*Overriding the virtual width of the site for mobile devices.

*Choices for the order in which the gallery [[comments]] and [[tags]] are sorted.

*Configuring the label displayed below gallery thumbnails.

*Adjusting the configurations of [[Multi-Page Viewer]].
**This feature requires the ''Multi-Page Viewer'' [[Hath Perk]].

==[[My Tags]]==
*For filtering or highlighting galleries containing sets of [[tags]].

==[[Hentai@Home]]==
*For the adjustment of [[H@H]] client settings.
*Includes a download link of the [[H@H]] client software.

==[[Donations]]==
*For donation transactions; also displays the cumulative amount already donated.
*[[Adopt-A-Server]] is also managed from here.

==[[Hath Perks]]==
*For the purchase of hath perks in exchange for [[Hath]].

==[[Hath Exchange]]==
*For the purchasing and selling of [[Hath]] for [[credits]].

==[[GP Exchange]]==
*For the purchasing and selling of [[GP]] for [[credits]].

==[[Credit]] Log==
*A log of [[credit]] income and spending activities for the last 30 days (except for the [[Dawn]] event).

==[[Karma]] Log==
*A log of who has imbued [[karma]] and the messages they have left.

{{EHGNav}}

[[Category:E-Hentai Galleries]]

Technical Issues

2026-08-05T00:11:45Z

Kagoraphobia: /* E-Hentai Galleries */

This article is meant to assist users of E-Hentai with any technical problems that they may have.

Site status can be checked [https://forums.e-hentai.org/index.php?showtopic=274947 here].

==Universal==
<div id="503"></div>
*'''"Error 503 - Service Unavailable"'''
**The site is under maintenance or is having server issues. Please wait and try again later.

<div id="IE"></div><div id="ie"></div><div id="browser"></div><div id="Browser"></div>
*'''The site is stuck at a static resolution!'''
*'''The site looks / behaves strangely on Internet Explorer!'''
**Only [https://www.w3schools.com/css/css_grid.asp modern browsers] are recommended for this site. Support cannot be given for [https://letsencrypt.org/docs/certificate-compatibility/ other / older browsers].

<div id="blank"></div><div id="Blank"></div><div id="DNS"></div><div id="dns"></div>
*'''I get a blank page when I try to access the site!'''
**Make sure you are connecting via HTTPS, not HTTP.
**Clear cache and cookies relating to the site. Relogging may be required afterwards.
**Disable any [[#Common Problematic Software|Common Problematic Software]] and try again.
**Disable any anti-virus, firewall, or other software that is capable of blocking traffic that runs in the background and try again.
**[https://documentation.cpanel.net/display/CKB/How+To+Clear+Your+DNS+Cache Flush your DNS cache], restart your browser, and try again.
**Check your region's [https://www.cloudflarestatus.com/ CloudFlare status].
**Go into a command prompt and use "''nslookup e-hentai.org''". If there are any addresses in the results then it is not a DNS issue. Otherwise consider using a different DNS provider such as [https://developers.google.com/speed/public-dns/docs/using Google] or [https://1.1.1.1/#setup-instructions CloudFlare].
***You may also try reaching the site manually through one of its [[IPs]] instead of a domain name.
**Use a proxy or VPN to access the site. If this fails then it is an issue with your ISP.
***[[Image:Tor.png]] It is recommended not to access the site through the [https://en.wikipedia.org/wiki/Tor_%28anonymity_network%29 Tor network] as numerous exit nodes have been abused and thus banned or had their access severely limited.
**[[Image:Firefox.png]] Firefox 55+: disable first-party isolation (''about:config -> set "privacy.firstparty.isolate" to "false"'').
** [[Image:Firefox.png]] Firefox 73+: disable obfuscating host address (''about:config -> set "media.peerconnection.ice.obfuscate_host_addresses" to "false"'').
**In order to provide diagnostics on your ability to access the site please do the following:
***[[Image:WindowsOS.png]] Go into a command prompt and use "''pathping e-hentai.org''". [[Image:MacOS.png]] For Mac OS use "''traceroute e-hentai.org''". Paste the results in a forum post.
***[[Image:Firefox.png]] Press {{Keypress|Ctrl}}+{{Keypress|⇧Shift}}+{{Keypress|K}} in Firefox. Attempt to visit e-hentai.org through the address bar. Paste the contents of the Firefox Console lines starting with "GET" in a forum post.
***[[Image:Chrome.png]] Press {{Keypress|Ctrl}}+{{Keypress|⇧Shift}}+{{Keypress|C}} in Chrome and switch to the "Network" view. Attempt to visit e-hentai.org through the address bar. Document all results of the "Status" column in a forum post.

*'''"Page load has been aborted due to a fatal error. A report has been dispatched to site staff. Please try again later."'''
**There is a server-side error. Please try again later.

*'''"The site is currently in Read Only Mode. This page is therefore not available.'''"
*'''"The site is currently in Read Only/Failover Mode. Some functionality will not be available. Details may be available on [[Twitter]].'''"
**The front-end servers are under read-only mode and will not allow users to take any actions that involve their user data (Accessing [[My Home]], [[Archives]], [[Tagging]], etc.)

==Account==
*<span id="Password"></span>'''I forgot my password!'''
*<span id="Username"></span>'''I forgot my username!'''
**Fill in the [https://forums.e-hentai.org/index.php?act=Reg&CODE=10 Lost Password Form]. This can be used to recover usernames as well. You will need your username or e-mail address to do this. These e-mails are sent instantly.
***Mail providers such as [https://login.live.com/ Hotmail] are known to be poor at receiving recovery e-mails; check your junk/spam folder.
**Make sure you are using your ''account'' username and not your ''display'' name. The registration process allows you to pick both a display name (used on forums) and an account username (used for logins and not readily visible to others).
***You cannot use your email address in place of your username to log in, unless your username was set as your email address.
***If you have ever made a gallery [[comment]] or a [[forum]] post attempt to search for it using any keywords that you recall using. If you have uploaded a [[gallery]] attempt to [[search]] for it.
**You may also email support@e-hentai.org from the registered email address to request a password reset.
**<span style="color:#a56b0d">"''If you're not logged on, you don't know your password, and you can't access your recovery email, you can't recover the account''" - Tenboro</span>

*<span id="lost email"></span>'''I can't access the e-mail address I used to register!'''
**Without the password, an active session, or access to the recovery email address, your account [https://forums.e-hentai.org/index.php?act=findpost&pid=4811225 '''CANNOT'''] be recovered.
***If you still have access to an active session, you may [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] with a new recovery email address to recover your account. If forum access isn't working, send an email with the contents of your ipb_pass_hash cookie to support AT e-hentai DOT org.

<div id="delete"></div><div id="Delete"></div>
*'''I want to delete my account!'''
**This action cannot be requested. Just stop using your account.

*'''I want to change my e-mail!'''
**If you are logged in you may do so [https://forums.e-hentai.org/index.php?act=UserCP&CODE=08 here].

<div id="name"></div><div id="Name"></div>
*'''I want to change my display name!'''
**[[Stars#Bronze|Donators]] can change their display name once every 365 days. This function can be found by clicking [https://forums.e-hentai.org/index.php?act=UserCP&CODE=dname_start Change Display Name] under [https://forums.e-hentai.org/index.php?act=UserCP&CODE=00 My Controls] on the forum.
**Non-donators can no longer change their display name due to various abuse of this function. If you used your actual real name or email address by mistake, you may appeal for a name change by [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PMing Tenboro].
***Provide both an acceptable justification and the requested display name in your PM. Requests that fail to provide either will be ignored. This can take a couple of days; do not send multiple PMs or contact other moderators about this.
***Having one's name changed by the administrator counts as having used their yearly change.
**The display name will change for all system readouts, but there can be up to a 24 hour delay before all readouts use the new name. Forum edits, quotes and similar retain the display name that was used at the time.
**Your log-in username will not change and cannot be changed.

*'''I changed my username but the new name only shows up on the forums / galleries!'''
**This is due to database caching. It takes up to 24 hours for all caches to be refreshed.

*'''Certain characters in my username are not being permitted!'''
**Database sanitization. Suspicious usernames also potentially flag users as attempting to scam or impersonate other users or to abuse the system in some way. This may lead to a permanent [[ban]].

*'''I want to use more than 1 account!'''
**You may only have 1 active account. <span style="color:red">Multi-accounting for any reason will result in a [[ban]].</span>

*<span id="lockdown"></span>'''My account entered a lockdown!'''
**Accounts will enter a 24-hour security lockdown under certain conditions, including changing passwords. This disables access to [[MoogleMail]], the [[Bazaar|Equipment and Item Shop]], [[The Market]], the [[Shrine]], and the [[GP Exchange]]/[[Hath Exchange]] functions. It also disables the Salvage and Reforge options in the [[Forge]].

*'''"This page is currently not available, as your account has been suspended"'''
**You have been banned, likely for account sharing / multi-accounting.

===Registering===
*'''"Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information. The error returned was: Sorry, you are not permitted to use this board"'''
**The IP you are using is banned.

*<span id="Missing captcha">'''The CAPTCHA is missing!'''
**Disable any software that blocks ads or scripts.
**Try a different browser.

*'''When I try to register nothing happens!'''
**[[Image:Chrome.png]] If using Chrome disable incognito mode.
**[[Image:Tor.png]] The use of [https://www.torproject.org/ Tor] when registering is strictly prohibited.
**Try without special characters such as "<", "}", "/" etc. in the username/display name.

*'''<span id="validation">I'm not receiving a validation e-mail!'''
**These are not actually sent out. Accounts may be used right away.

*"'''<span id="Invalid captcha"></span>The registration code did not match the one displayed, a new code has been generated, please try again'''"
**Disable any software that blocks ads or scripts.
**Try without incognito/private windows.
***Disable any cookie blocking/modifying software.
***Disable any JavaScript blocking software.
**If using a VPN/Proxy, disable it.

==[[E-Hentai Galleries]]==
<div id="images"></div><div id="image"></div><div id="Images"></div>
*'''Images are not loading.'''
**Check your browser settings:
***Make sure you are using a [[#browser|modern browser]].
***Disable any proxies, add-ons, or scripts. <span style="color:red">'''There is no 3rd party software needed to access ANYTHING in E-Hentai or its related domains. Anything claiming otherwise may be an attempt to intercept your account credentials.'''</span>
***Due to the [[Hentai@Home]] system images require cross network traffic:
****[[Image:Firefox.png]] [https://forums.e-hentai.org/index.php?showtopic=201984 Firefox 51-57]: disable HSTS priming (''"security.mixed_content.send_hsts_priming"'' and ''"security.mixed_content.use_hsts"'' to ''"false"'').<br>Firefox 65+: If content blocking cannot be disabled for the site use the Strict or Custom setting (''"browser.contentblocking.control-center.ui.showAllowedLabels"'' to ''"true"'').
****[[Image:Opera.png]] Opera: enable Cross Network Navigation (''opera:config#Network|AllowCrossNetworkNavigation'').
****For [https://noscript.net/ NoScript] disable ABE or enable local resources to be accessed by "e-hentai.org".

**Try the "Click here if the image fails loading" link. This will attempt to pull the image from a new [[H@H]] client.
**Select "Default port clients only" in your [[My Settings]] page; this will only utilize [[H@H]] clients that use port 443.
**[[Donator]]s may append "?nl=1" to the end of the URL. This bypasses using the [[H@H]] cluster for that image. This can be permanently enabled via the [[My Settings]] page but this can quickly use up your bandwidth limit.
**Turn off any [[#Common Problematic Software|problematic software]] which may block E-H traffic.
*'''Images sometimes take a long time to load.'''
**If your ISP does not support IPv6, your browser may try to use IPv6 anyway, causing a 5+ second stall+timeout per image load.
***Firefox: Disable IPv6 by opening about:config then set network.dns.disableIPv6 to true
***Chrome: Disable IPv6 by starting Chrome with --disable-ipv6
*'''Thumbnails are not loading.'''
**Many adblockers have subscription-based rules that include an '''/ad/''' or '''^ad^''' filtering rule. This will catch '''all''' hexadecimal static ranges with /ad/ in them (e.g. /{00..ff}/ad/ or /ad/{00..ff}).
***Whitelist '''ehgt.org''' for the '''image''' content type or disable adblockers for the site.
***Disable any scripts/add-ons such as RequestPolicy and Smart Referrer.
*'''The image size is locked at 1280x or 1920x even though I have selected a higher resolution in the settings!'''
**You may have triggered the site's anti-bot mechanism. This is likely due to the use of a heavily-abused VPN/proxy node.
***Try switching your IP address may resolve this issue.
***[[Donators]] will not be affected by this limit.
**New 2560x resamples are no longer generated for galleries older than one year; 1920x resamples will be used instead.
***They can still be used on older galleries if they were already created.
<div id="509"></div><div id="509"></div>
*'''"Error 509 - Bandwidth Exceeded"'''
*'''"Error loading image: Could not get dispatch for image"'''
**<span id="image limit">You have viewed too many images. Either wait a few hours, [[My Home#Overview|reset the limit]] with [[GP]], or purchase the "More Pages" [[Hath Perk]].
**If you are on a shared connection consider using a proxy to browse E-Hentai.
**These limits are based only on IP address, not by account. The exception is for [[donators]] with [[stars]], wherein IPs are ignored.
<div id="414"></div>
*'''"Error 414 - Request-URI Too Large"'''
**Occurs if the URL being accessed is too long, often from advanced [[Searching|searches]].
***Depending on your search you can safely remove any non-relevant search parameters contained within the URL.
**You have performed a [[Searching#File_Search|file search]] that found too many results.
*'''"Please wait a bit longer between each file search."'''
**You have tried to do another [[Searching#File_Search|file search]] too quickly after the previous one. Wait 10 seconds before trying again.

*'''"The connection to the server was canceled during the page load."'''
**Your connection was automatically blocked for making too many connections.
**Wait for the ban to expire.

*'''<span id="image limit vpn">"I have used up my image quota even though I haven't been browsing."'''
**You are using a shared IP. This may be because of a proxy/VPN, or your ISP has recycled a recently used IP to you.
**A $20 [[donation]] or the "More Pages" [[Hath Perk]] ties the image limits to your account instead of your IP.

*'''"Content Warning - This gallery has been flagged as Offensive For Everyone. Due to its content, it should not be viewed by anyone. (And if you choose to ignore this warning, you lose all rights to complain about it in the future.)'''"
**This indicates that the gallery has been [[tagged]] with [[guro]], [[snuff]], or [[scat]]. You may choose to view the gallery, no longer receive these warnings ("Never Warn Me Again"), or go to the gallery front page.
**To re-enable this warning again simply delete the "nw" cookie.

*'''Thumbnails appear with inverted colors.'''
**This is a rare glitch which resolves itself over time. The actual images should appear as normal when viewed.

*'''"The proxy server received an invalid response from an upstream server."'''
**Check if you are on an ISP-level proxy [https://www.toolsvoid.com/proxy-test/ here]. Reverse proxies cannot be detected with tools like these; you may need to ask your ISP.
**Check if your browser settings have a proxy enabled.

<div id="fast"></div><div id="Fast"></div>
*'''"You are opening pages too fast, thus placing a heavy load on the server. Back down, or your IP address will be automatically banned."'''
**[[Image:Chrome.png]] This may be triggered by prefetching in Chrome; uncheck ''Settings -> Show advanced settings -> Privacy -> "Use a prediction service to load pages more quickly."''
**This may be triggered by add-ons/scripts that organize/update bookmarks to galleries automatically; such actions may induce page loads.

<div id="Ban"></div><div id="Banned"></div>
*'''"Your IP address has been temporarily banned for excessive pageloads which indicates that you are using automated mirroring/harvesting software."'''
**You have opened too many pages at once or you have used software that downloaded too many images from the site simultaneously.
***Wait until the ban expires.
**If you are certain that you have not performed excessive page loads your IP may be in use by other people.
***A $20 [[donation]] makes your account ignore any IP restrictions caused by other users.

*'''"Key missing, or incorrect key provided."'''
**The URL you are visiting is incorrect.

*'''When I save an image I only get blank.gif!'''
**The image did not have enough time to load. The blank.gif is a placeholder shown while waiting for image retrieval.

*'''I cannot rate a gallery!'''
**Sometimes the [[rating]] UI does not respond due to server congestion, try again later.
**You cannot rate your own galleries.
**You may be banned from [[rating]] galleries. You will receive a pop-up notification if this is the case.

*'''I am being redirected to other sites!'''
**Make sure you typed the URL correctly or that the link you followed has it spelled correctly.
**Check with your ISP about any blocked or redirected traffic.
**Any countries / territories noted [[:File:Countries_Blocking_E-Hentai.png|here]] are known to block E-Hentai.org.
**Check for malware such as browser hijacks.

<div id="Korea"></div><div id="korea"></div>
*'''I am being redirected to "warning.or.kr"!'''
**You live in South Korea. Move.
**The use of a proxy may work but be wary of the legalities in that jurisdiction.

<div id="Russia"></div><div id="russia"></div>
*'''"This content is not available in Russia."'''
**You live in Russia. Move.
**The use of a proxy may work but be wary of the legalities in that jurisdiction.

<div id="UK"></div><div id="uk"></div>
*'''"This content is not available in the United Kingdom."'''
**You live in the UK. Move.
**If you live in the UK, you can and should complain to your local MP [https://www.parliament.uk/get-involved/contact-an-mp-or-lord/contact-your-mp/ here].

<div id="Australia"></div><div id="australia"></div>
*'''"This content is not available in Australia."'''
**You live in Australia. Move.
**If you live in Australia, you can and should complain to your local Senator [https://www.aph.gov.au/Senators_and_Members/Contacting_Senators_and_Members here].

<div id="acl"></div><div id="ACL"></div>
*'''"Tool does not exist, or you have insufficient access to use it.'''"
*'''"You do not have access to this function.'''"
**You are not on the Access Control List of the tool you are attempting to use.
***For most users the [[Gallery_Tagging#Tag_History|tag history tool]] can only be used to check one's ''own'' tagging history.
***Please contact a [[E-Hentai Janitor|moderator]] if you wish to have something done via said tool.
**This may also happen if you are using outdated URLs for the [[expunge]]/[[rename]] tracker (e.g., tools.php). Update your bookmarked links with the ones displayed on the [https://forums.e-hentai.org/ forums].

*'''"Gallery not found. If you just added this gallery, you may have to wait a short while before it becomes available. It might also have been reverted to its previous version."'''
**The gallery you are attempting to visit is not yet fully integrated into the server. If this persists the gallery link is faulty.
**Alternatively, the gallery was reverted to a previous state, check its parent gallery.

*'''Gallery [[HentaiVerse Hotkeys|hotkeys]] aren't working!'''
**Make sure you have JavaScript enabled.

<div id="eeenope"></div><div id="nope"></div><div id="Nope"></div>
*'''"eeenope"'''
**You do not have access to the [[Multi-Page Viewer]]. Change the URL.

*'''"The connection to the server was canceled during the page load."'''
**Your IP was automatically blocked for opening a huge amount of connections.

<div id="KeepTrying"></div><div id="keeptrying"></div><div id="Keeptrying"></div><div id="Keep"></div><div id="keep"></div>
*'''"Keep trying."'''
**You are trying to access an image page but have an invalid page ID, gallery ID, or file ID.

*'''I cannot see new galleries until ~15 minutes after they have been published!'''
**This is intentional for non-registered visitors.
**Register an account to see these galleries sooner.

*'''<span id="veto expunge">"New expunges for this gallery can currently only be started by trusted users."'''
**The gallery chain was previously de-expunged and new expunges can only be started by [[Expunging#Limits|selected users]].
**If you believe that the gallery should be expunged, please make a post in [https://forums.e-hentai.org/index.php?showtopic=242797 this thread].

*'''I cannot file an appeal petition on this gallery!'''
**If the expunge petition went active more than 7 days ago, a new appeal petition can only be created by [[Expunging#Limits|selected users]].
**If you believe that the gallery should be de-expunged, please make a post in [https://forums.e-hentai.org/index.php?showtopic=242797 this thread].

*'''"This gallery is expunged, but no active expunge petitions were found. This usually means it was administratively expunged, which cannot be appealed here."'''
**No user-created [[Expunging#Appeal_an_Incorrect_Expunge|appeal]] petition is allowed for the gallery. If you believe that the gallery has been expunged incorrectly, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=242797 here].

*'''"You cannot currently start an expunge for this gallery."'''
**You are no longer permitted to use the [[expunge]] system. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**You may also get this message when your login session has expired. Please clear your cookies and log in again.

====<span style="color:#977933">Common Problematic Software</span>====
*Ghostery, PeerGuardian, PeerBlock, Protowall, Megakey, Transmission ([[torrent]] client), DuckDuckGOPrivacy (the plugin - you need to whitelist EH to see content), DuckDuckGo, DansGuardian, SquidGuard, HackShield (used as part of some MMOs).
*Any global/browser-based IP blockers can cause problems. For P2P applications use directly loaded IP lists.
*Any "web accelerators" or pre-fetching can cause routing issues (E-Hentai's [[IPs]] are not static).

===Gallery Not Available===
<div id="removed"></div><div id="Removed"></div>
*'''"This gallery has been removed or is unavailable."'''
**This is '''not''' the same as a gallery being deleted or [[expunged]].
**'''<span style="color:red">Do NOT re-upload it.</span>'''

*'''"This gallery is unavailable due to a copyright claim by {copyright holder}. Sorry about that."'''
**The gallery has been removed due to a DMCA takedown notice.
**'''<span style="color:red">Repeated attempts to re-upload galleries of this nature will lead to a [[Bans|ban]].</span>'''

===Your Galleries===
*'''My gallery disappeared!'''
**This is almost never due to a technical problem.
**Check if it is still listed in your [[Gallery Manager]]. If so, the reason it is not visible will be indicated there.
**Attempt to visit a direct link to your gallery.

<div id="expunged"><div id="Expunged"><div id="expunge"><div id="Expunge">
*'''My gallery was [[expunged]] unfairly!'''
**Check the gallery's expunge log for the reason(s).
**Make sure it was [[expunged]] and not removed or deleted. Each of these happen for very different reasons.
**Post the gallery's URL [https://forums.e-hentai.org/index.php?showtopic=242797 here] to inquire about it.

*'''<span id="delete gallery">I cannot delete my gallery!'''
**This is intentional. [https://e-hentai.org/tos.php Once a gallery has been published, it belongs to the community].
**A gallery may instead be [[My Galleries#Available Actions|disowned]] if the uploader wishes to remove association.
**<span style="color:red">'''False expunges will lead to a ban and the gallery reverted to its previous state.'''</span>

*'''<span id="cant upload">I cannot publish my gallery.'''
**Before publishing a gallery or a gallery update you must first read the [https://e-hentai.org/tos.php Terms of Service] and check the corresponding box, then choose a sorting order. If you do not wish to re-order, click "Apply with Current Ordering".

*'''My gallery has an incorrect name or [[category]]!'''
**Check if it is still listed in your [[Gallery Manager]]. The default category is [[Doujinshi]].
***If so, you may rename or re-categorize it from there.
***If a [[Renaming|rename petition]] was successful on your gallery but the name is still unsatisfactory, you may insert another petition option. Should this new option reach higher [[power]], the name will change over.

*'''I cannot [[rename]] my gallery from the [[Gallery Manager]]!'''
**This action is only permitted from the manager for 24 hours after publishing.
**A successful [[Renaming|rename petition]] was done on your gallery. See the above issue.
**[[Expunged]] galleries cannot be renamed in this manner.

*'''"You can no longer change the [[category]] of this gallery."'''
**The gallery has had its [[category]] changed via [[tagging]]. If the [[category]] is still unsatisfactory report it as a [[#Gallery Tagging|mistag]].

*'''"You cannot unlock galleries this old. Please make a new one, then request to have this one expunged."'''
**You are attempting to [[Making_Galleries#Updating|update]] an aged gallery (i.e., 365 days after its last publishing). Such galleries cannot have their files modified.
**Any necessary changes require re-uploading and replacement [[expunging]] the existing gallery. This starts a brand new gallery chain without any of the previous gallery's metadata.

*'''I'm afraid I can't let you do that.'''
*'''That gallery has been marked as deleted, and can no longer be modified.'''
**You are attempting to modify or delete a gallery that cannot or can no longer be deleted.
***This also applies to properly replaced galleries and is working as intended.

*'''"Could not rate gallery. Reason: You cannot rate your own gallery."'''
**Self-explanatory.

*'''"Could not obtain lock on gallery - if you are not running any active operations on this gallery, please wait about 15 minutes for the lock to expire."'''
**Occurs when a gallery being uploaded / managed is in the middle of being processed by the server. Please wait and try again later.
**Also occurs to galleries that were reverted to a previous state, thus the URL entered is no longer valid.

*'''My gallery has missing, unwanted, or wrongly ordered images!'''
**You can add, remove, and modify the order of all your gallery's images via the [[Gallery Manager]].
***Note that you may only update a gallery twice per every 30 days (some exceptions apply).
****This limit does not apply to unpublished / [[private]] galleries.
<div id="order"></div><div id="Order"></div><div id="out of order"></div>
*'''When people download my gallery the files are in the wrong order!'''
**Downloaded galleries use the filenames of the files ''when they were uploaded'', so they may be out of order even if you corrected the order manually via the gallery maintenance UI.
**Rename your files to the correct order '''''before''''' uploading them (''e.g. 001.jpg, 002.jpg, etc.'') to avoid this problem.
***This is further recommended since different OSes [https://support.microsoft.com/kb/319827 sort files differently].
<div id="rating"></div><div id="Rating"></div>

*'''<span id="bad ratings">People are giving my galleries low [[ratings]]!'''
**They are entitled to their opinions. Furthermore, ratings do not affect how well a gallery fares.
**Votes that deviate too much from the average rating are automatically discarded. This process is retroactive. Ratings, [[tags]] and [[favorites]] also carry over across all non-aged gallery updates.

*'''My gallery files are being resampled and converted to WEBP!'''
**This is intended for [[Making_Galleries#Limits|files over 10MB in size]]. A link still allows you to download the original source at a cost of 10 image hits per MB.

*'''My gallery's stats show low/no hits!'''
**Gallery stats are updated every ~4 hours. Please wait and check again later.

====[[Uploading]]====
*'''My uploads seem unusually slow.'''
*'''I am stuck on "Processing..."'''
**Try to upload your images in ZIP or RAR archives. Uploading a small amount of larger files is faster than many smaller files. Break your upload into smaller portions.
***To prevent [[out of order]] situations either prefix filenames (the same way the [[Archiver]] would) or upload archives sequentially.
**Disable any software that uses upload bandwidth while you are uploading to the site.

*'''Images appear outside of the scope / keep reappearing and I can't save changes!'''
*'''I've uploaded files but the gallery is empty!'''
*'''"The gallery is busy processing another task. Please wait until it is done before uploading more files."'''
**The recommended maximum data you should upload in a single instance is 500 MB. Do not upload more than <span title="1,258,291,200 bytes" style="border-bottom:1px dotted">1,200 MB</span> in a single instance.
**Do not upload in multiple tabs/windows at the same time; the files are liable to be discarded.
***Uploading files to different galleries simultaneously is also not recommended.

*'''My files take a lot of time to be processed.'''
**All files require indexing and thumbnail generation. PNG files additionally require decompression. Please be patient.
**It is recommended to use zero-compression (Store) ZIP/RAR archives; the filesize difference is negligible whilst processing will be much faster.

*'''"Could not retrieve lock for gallery"'''
*'''"The gallery has been deleted"'''
**You are trying to upload files to the wrong gallery chain (replaced chain) or a deleted gallery.

*'''"Upload is temporarily unavailable."'''
**The upload server is under maintenance. Please wait and try again later.

*'''"The file {filename} is corrupt, incomplete, too large, or not an accepted image file."'''
**Make sure the file is of an [[Making_Galleries#Limits|accepted format and is not over the size limit]], is not corrupt, and is not named with [[Making_Galleries#Checking|unacceptable characters]].

*'''"{Filename} has been blacklisted on this system"'''
**Any file that causes this message should '''NOT''' be uploaded as it is [[DNP]].

*'''"You have been temporarily barred from posting more galleries due to an excessive expunge rate."'''
**Too many of your galleries were [[expunged]], removed, or deleted, triggering an automated [[Making Galleries|upload]] block.
**Wait for the block to expire and do not create any more unacceptable uploads.
***The duration is a sliding window and may last up to a week.

*'''"You have been temporarily [[banned]] from [[Making Galleries|submitting galleries]] to this system. Read your PMs."'''
**A temporary upload ban has been manually placed on your account. This usually expires in a week, but the duration may vary. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**Consequently, you will also lose the ability to update all galleries published before the time of the manually placed ban.

*'''"You have been permanently [[banned]] from [[Making Galleries|submitting galleries]] to this system."'''
**Same as above, except permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"You can no longer modify that gallery."'''
**You are no longer allowed to update your galleries published before a specified time. An expired manually placed upload ban may also cause this.
**[https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] if you have a valid reason to update your old galleries.

*'''"Rate limitation for new posters in effect. You have to wait a few hours before you can post more [[Making Galleries|galleries]]."'''
**There is a rate limit that compares your recent upload volume to your post history of good galleries, the calculation determines how many galleries you can publish in succession. Wait for the limit to expire.
***Private / Unlisted galleries do not count as "good". <sup>[https://forums.e-hentai.org/index.php?s=&showtopic=252404&view=findpost&p=6011165 (Ref)]</sup>

*'''"You have earlier uploaded and published a gallery identical to the one you are now trying to publish. This gallery has been removed, and you will now be redirected to the old, identical gallery. If that gallery had previous been marked as deleted, it is now available again. You will be returned to the Management Interface momentarily."'''
**You uploaded an exact copy of a gallery you have already uploaded and published.
**This will undelete a gallery if it was deleted by its owner.

*'''"You cannot add files to galleries that are older than twelve months. Please make a new one, then request to have this one expunged. You will be returned to the Management Interface momentarily."'''
**This is what is known as an [[aged]] gallery.
**[[Expunging#Replaced|Replace]] your gallery if it is truly necessary to make changes to it.

*'''"{Filename} was generated by this system and has been replaced with the original copy."'''
**The image uploaded is a thumbnail that was already generated by the system and thus was replaced by its original version.

*'''I cannot select 'Save Changes', 'Start Upload', or 'Publish Gallery' after deleting an image!'''
**Use one of the sorting buttons after making such changes to confirm them.

*'''"You have posted too many [[private]] galleries in the last week."'''
**You have reached your weekly upload limit for [[private]] galleries.
**[[Donation#Stars|Bronze and Silver Star]] users are allowed to create up to 5 private galleries per week. This limit is bumped up to 10 galleries per week for [[Donation#Stars|Gold Star or above]] users.

*'''I cannot create any [[private]] gallery despite having a [[Donation#Stars|bronze star or above]]!'''
**Your account has been permanently blocked from uploading [[private]] galleries. This is likely due to excessive abuse of the function.

*'''All of my new uploads are automatically flagged as [AI Generated]!'''
**A restriction has been placed on your account, in which all new uploads will receive the [[AI Generated]] title indicator and be categorized into [[Misc]]. This is due to repeatedly uploading numerous [[AI Generated]] galleries without labeling them as such.
**If your new gallery isn't generated by AI, you may remove the indicator by filing a [[rename]] petition. Note that misusing the rename function would lead to a [[ban]].
***Uploaders who don't have sufficient [[mod power]] to file a rename petition on their own can submit a request [https://forums.e-hentai.org/index.php?showtopic=227712 here].

===[[Gallery Tagging]]===
*'''Some tag searches include additional results.'''
**Try using [[Gallery_Tagging#Exact_Tag_Searching|exact tag searching]].

*'''I cannot tag a gallery!'''
**The tag you are attempting to use may not be acceptable (e.g. too short or blacklisted).
**You may be banned from tagging galleries. You will receive a pop-up notification if this is the case.
**You may be attempting to upvote a downvoted tag (which may not give an error message). Be sure to read the tag's definition, [[Gallery Tagging|tagging guidelines]], or ask [https://forums.e-hentai.org/index.php?showtopic=274004 here] for upvotes.
**[[#Could Not Vote For Tag|See below]] for specific tagging error messages.

*'''I tried to tag something and it turned into a different tag!'''
**Your tag included non-alphanumeric characters which are not permitted. Only hyphens, periods, and spaces are allowed in tags.
**Due to the grouping system for tags any [[slave tag]] will become its respective master tag. If you are not satisfied with the grouping you may post [https://forums.e-hentai.org/index.php?showtopic=107861 here] to discuss it.

*'''I cannot select a [[namespace]] for my tag!'''
**If you are certain it should be assigned a namespace please contact a [[E-Hentai Janitor|namespacer]] or post [https://forums.e-hentai.org/index.php?showtopic=275305 here].
***At least one instance of the temp tag must exist for it to be namespaced. If you cannot add the tag due to lack of [[power]] or if the tag already exists within another namespace please also link to a gallery where the tag would be a valid addition. If the tag does not pass [[presence]] for a gallery but will likely be used in the future (e.g. a [[character]] tag) please specify this in your post.
****If you forgot where you made the tag checkers have a listing for new tags created within the last 7 days along with the names of users who voted on them.

*'''I accidentally created a wrong tag!'''
**Simply withdraw your tag before someone else upvotes it. If it's too late and you cannot downvote the tag completely by yourself ask for assistance in [https://forums.e-hentai.org/index.php?showtopic=274004 this thread].

*'''"Server communication failed. Server responded with:"'''
**Connection timed out. Check your connection, wait a few seconds and try again.

*'''Someone is voting down my tags!'''
*'''My gallery has incorrect tags!'''
**Double-check the tag's definition and [[Gallery_Tagging#Usage_Guidelines|tagging guidelines]].
**Vote the tags up/down only if you are absolutely certain.
**Post the gallery's URL [https://forums.e-hentai.org/index.php?showtopic=274004 here]. Please do not accuse any users of mistagging or request any [[bans]].

<div id="temp tag pop-up warning"></div>
*'''"You about to vote up an older temp tag. You may be prompted to provide sources for this tag, which is required. Are you sure you want to do this?"'''
**You are attempting to vote up a tag that has yet to be approved by a [[E-Hentai_Janitor|namespacer]].
***Upon hitting "OK", you will be brought to the [[Tag_Creation|New Tag Justification window]] if you have at least 15 [[mod power]] and no active tag creation [[Bans|ban]].
**'''Do NOT hit that button if you are not prepared or willing to provide [[Tag_Creation#Guidelines_for_Submission|relevant supporting materials]] for that temp tag.''' <span style="color:red>'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence may lead to a [[Bans|ban]].'''</span>

====Could Not Vote For Tag====
*'''"Could not vote for tag: You need at least 15 MP to vote on this tag."'''
**The tag you are attempting to vote on [[Tagging_Mechanics#Tag_Mod_Power|requires]] additional [[mod power]]. This is to prevent poor handling of the tag by newer users.

*'''"Could not vote for tag: You do not meet the requirements to vote for "{tagname}""'''
**The tag can only be voted by users who meet certain requirements. For more information, view the wiki article for the tag.

*'''"Could not vote for tag: The tag "{tagname}" currently requires at least {value} MP to upvote on this gallery due to existing downvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-vetoed]] and needs a matching or higher base [[mod power]] of the highest vote against it to vote it up.
**If you are sure that a tag was mistakenly downvoted, you can post in the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread.

*'''"Could not vote for tag: The tag "{tagname}" currently requires at least {value} MP to downvote on this gallery due to existing upvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-enforced]] and requires a [[mod power]] that matches or exceeds half of the value of the strongest upvote to vote it down, capped at 25 [[mod power]].
**If you believe the tag is definitely invalid, you can make a downvote request in the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread.

*'''"Could not vote for tag: The tag "{tagname}" is currently locked for further upvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-enforced]] or has reached the cap of 200 [[mod power]], and can no longer be upvoted.

*'''"Could not vote for tag: The tag "{tagname}" is currently locked for further downvotes."'''
**The tag you are attempting to vote on is [[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|soft-vetoed]], and can no longer be downvoted. This error will usually appear if you attempt to downvote a tag that was already killed and 5 minutes elapsed without refreshing the page.

*'''"Could not vote for tag: The tag "{tagname}" has been blocked for use."'''
**You are attempting to add/upvote a tag that is blocked or blacklisted.

*'''"Could not vote for tag: The tag "{tagname}" is not allowed. Use {namespace}:{tagname} or {namespace}:{tagname}"'''
**The tag you are attempting to enter requires an accompanying [[namespace]]. The namespace must be one of the approved pairings for that particular tag.

*'''"Could not vote for tag: The tag "{tagname}" is scheduled for an automated action and cannot currently be voted on."'''
**You are downvoting a tag that has been slaved or blacklisted by a [[Janitor|moderator]]. This is not a required action as the autotagger will remove or replace these tags eventually.
**User may still withdraw their upvotes on a slaved/blocked tag should they have upvoted it before.

*'''"Could not vote for tag: Your vote can no longer be withdrawn."'''
**You are attempting to withdraw your upvote on a now-downvoted tag. This cannot be done to prevent abuse.

*'''"Could not vote for tag: Tags should be added on the most recent gallery in this chain."'''
**Only the most recent version of a gallery chain allows for tagging actions. The action will automatically be applied to all galleries in the chain.

*'''"Could not vote for tag: Invalid user"'''
**The API received an invalid user identification response while you were tagging.
***Your session may have expired. Use another browser or clear your cache/cookies.
***This will also occur when you are simply not logged in.

*'''"Could not vote for tag: No tags to add."'''
**You entered a term or phrase that is rendered as a blank tag.

*'''"Could not vote for tag: Missing arguments"'''
**You submitted a blank tag.

*'''"Could not vote for tag: Missing or malformed tags"'''
**Your request is longer than the maximum allowed for the input field.
***[[API]] requests are limited to the default tag input field maximum length (200 characters).

*'''"Could not vote for tag: You cannot possibly have taken the time to look at the gallery in that short time. You must wait 10 seconds between tagging different galleries."'''
**You attempted to vote on a tag on a gallery too quickly after doing so on a different gallery.
**This limit can be reduced with increased [[power]].

*'''"Could not vote for tag: User fault detected. Replace user and try again"'''
**You entered in the default text on the tag form ("Enter new tags, separated with comma").

*'''"Could not vote for tag: The tag {tagname} is vetoed on this gallery and cannot be upvoted. Please read the wiki."'''
**The tag you are attempting to add has been [[Tagging_Mechanics#Tag_Veto|vetoed]] on the gallery. If you believe that tag has been vetoed incorrectly, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=274004 here].

*'''"Could not vote for tag: The tag {tagname} is enforced on this gallery and cannot be downvoted. Please read the wiki."'''
**The tag you are attempting to downvote has been [[Tagging_Mechanics#Tag_Veto|enforced]] on the gallery. If you believe that tag is invalid, please make an inquiry [https://forums.e-hentai.org/index.php?showtopic=274004 here].

*'''"Could not vote for tag: The tag {tagname} has never been used. Use temp:{tagname} to create a temporary tag."'''
**You are adding a [[Namespace#Restricted_Namespaces|temporary]] tag without defining the "temp" [[namespace]]. Please include "temp:" in front of the tag name.

*'''"Could not vote for tag: The tag {tagname} does not exist. You can request new tags in the Tag Creation/Namespacing Request Thread."'''
**The [[namespace]] you are attempting to use has not been approved by a namespacer.
**This error also occurs when you are attempting to create a [[Namespace#Restricted_Namespaces|temporary tag]] with less than 15 [[mod power]], or with an active tag creation [[Bans|ban]].
***If you are certain it should be usable, please post [https://forums.e-hentai.org/index.php?showtopic=275305 here] to have it added.

*'''"Could not vote for tag: The tag {tagname} has an invalid namespace."'''
**The [[namespace]] being used is not a correct one. Check your spelling.
**Make sure not to use a colon when tagging something except to indicate a namespace.

*'''"Could not vote for tag: The tag {tagname} is derived from the gallery title and cannot be directly voted on."'''
**The tag has been added due to the presence of a special indicator in the gallery title. For more information, view the wiki article for the tag.

*'''"Could not vote for tag: Gallery not found"'''
**The gallery is no longer formally in the system.

*'''"Could not vote for tag: You have been banned from tagging galleries"'''
**Your tagging privilege has been permanently revoked. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

===[[Archives]]===
*'''The [[archive]] link returns a blank page with the message "err".'''
**Clear your cache and cookies.

*'''I get a 503 error when I download an [[archive]]!'''
**The site may be experiencing [[#503|maintenance or other issues]].
**You may be attempting to use more than 4 simultaneous download threads. If using a download manager make sure that it does not exceed that amount.
**You may have exhausted your allowed download attempts.

*'''My download speed is much slower than expected!'''
**After ensuring the issue is not on your end, you may be downloading from a capped or saturated archive server due to various reasons.
***The issue can be mitigated by using segmented downloading (use at your own risk) or just being patient. Alternately, if a very healthy [[torrent]] is available, please consider using this option.
***It is not possible to change servers after the archive is generated. Available servers are randomly assigned upon request and the archive then is only valid for the assigned archive server.

*'''A gallery I downloaded says "Unexpected end of archive."'''
**The download was interrupted at some point. Please try to download it again.

*'''"IP quota exhausted"'''
**Too many addresses from the same IP range tried downloading the same [[archive]].
**Wait a week, generate another archive link, and '''do not share this link''' with anyone.

*'''"Failed to prepare one or more files for the archive. Please try again in an hour. Contact staff if this error persists."'''
**Self-explanatory.

*'''"You have clocked too many downloaded bytes on this gallery."'''
**You download the same gallery's archive multiple times or the prior downloads kept failing and restarting. Cancel the download session and repurchase the archive.
**You downloaded the original archive and are now trying to download the resampled archive. Sometimes this errors, use the cancel button and repurchase the archive.
***If you require both the resampled and original archive, it is recommended to download the resample first to avoid this.

===[[Renaming]]===
*'''Someone else's gallery has an incorrect name or [[category]]!'''
**See [[Renaming]] for name changing.
**See [[Gallery Tagging#Categories|Gallery Tagging - Categories]] for category changing.
**You may also post links to such galleries [https://forums.e-hentai.org/index.php?showtopic=227712 here]. Please indicate the correct name/category in your post.

*'''"That is already one of the suggested names."'''
**You attempted to add a [[rename]] petition with the same text as an existing one for that gallery.

*'''"New suggested title is too short."'''
**You attempted to add a blank name as a [[rename]] petition. Pay attention to which option button is used.

*'''"You have been blocked from renaming galleries."'''
**You are no longer allowed to vote on or create [[rename]] petition. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

===[[Commenting]]===
*'''My gallery comment disappeared!'''
**Comments will become hidden under [[Gallery_Commenting#Hidden_Comments|certain criteria]].
**For galleries with more than 50 comments only the top 50 (depending on which viewing order is used) are displayed by default; the rest are hidden.

*'''I cannot delete my gallery comment!'''
**This is intentional.

*'''"Due to reported abuse, you have been blocked from adding more comments."'''
**Numerous comments that you have made were severely downvoted.

*'''"You have been banned from posting comments."'''
**Your commenting privilege has been suspended due to the violation of the [[Gallery_Commenting#Examples_of_Bad_Comments|comment rules]]. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"You can only add comments for active galleries."'''
**Deleted galleries may not have comments added to them.

*'''I cannot rate a gallery comment!'''
**You cannot rate comments if you have added a comment to the same gallery.
***Any existing comment ratings for a gallery will be removed if you add a comment to that gallery.

*'''I can upvote just fine but my comment downvotes do not have any effect!'''
**You have downvoted too many comments and the system acknowledged you as a potential mass-downvoter.

*'''"You have to wait 60 seconds between each comment."'''
**This is to prevent spam. This limitation is reduced to 10 seconds for users with at least 25 [[power]].

*'''"Your gallery comment is too short."'''
**Comments must be at least 10 characters long.

*'''"You did not enter a valid comment."'''
**You entered in the default text into the comment form ("Enter your comments here, then hit Post Comment. If the last comment posted is yours, this will be appended to that post.")

*'''"You did not enter a comment."'''
**You either entered no text in the comment field or text that renders as nothing.

*'''"Could not vote for comment. Reason: Correlation factor between reviewer and voter has exceeded reasonable limits. Vote blocked."'''
**You have voted on a particular user's comments too much. Upvote other useful comments.

*'''"Could not vote for comment: Cannot vote when own comment exists in gallery"'''
**You are trying to vote after posting a comment. Refresh the page to display your comment (unless it is perma-hidden).

*'''"Could not vote for comment: You have been banned from voting on comments"'''
**You are no longer allowed to vote on other comments. This is permanent.
**Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

*'''"Could not get editable comment: Can only edit own comment"'''
**You are trying to edit someone else's comment. Refresh the page to display your own comment.

*'''"You have been temporarily restricted from adding comments'''"
**This is due to a limit on newer users to prevent potential spam. It will resolve over time.

===[[My Tags]]===
*'''I am unable to add/remove tags from [[My Tags]], or add/remove [[My Tags#Sets|tag sets]]!
**Commonly because of an outdated browser. Update your browser and try again.

==[[HentaiVerse]]==
('''<span style=color:#FF5555>For in-game error messages see [[HentaiVerse_Bugs_%26_Errors|HentaiVerse Bugs & Errors]]</span>''')

*'''HentaiVerse is slow for me!'''
**Disable any [[scripts]] or browser add-ons. Re-enable them individually to isolate which one(s) may be causing the slowdown.

*'''"Failed to initialize player state. Try again later."'''
*'''"HV is temporarily unavailable, as the battle state tracker or master database is currently offline."'''
*'''"HentaiVerse is not available on this cluster. If you are seeing this message, contact staff."'''
*'''"Snowflake and the moogles are basking in the summer sun. Check back later."'''
**Wait a few minutes and try again or use the alternative ''alt.hentaiverse.org''.

*'''I can't see everything in the HentaiVerse window!'''
**The minimum recommended resolution for HV is 1280x768.

<div id="dawn"></div><div id="Dawn"></div>
*'''[[Dawn of a New Day]] / [[Random Encounter]] message does not appear.'''
**There is a limit of 24 random encounters per day.
**You need to visit either the E-Hentai [https://e-hentai.org/news.php news page], or any gallery on the [https://e-hentai.org/ main website]. Visiting any other pages will not trigger the events.
***If you have just logged in, reload the page. If it still isn't working, wait a few minutes and try again.
**Even if the message did not appear, check to see if the rewards from the Dawn have been received.
***Note that daily income from dawn does not show up on the credit log.
**Disable any ad-blockers or other add-ons that may prevent the message from appearing.

*'''Posting in [[E-Hentai Forums|the forums]] is not giving an [[EXP]] gain bonus.'''
**The EXP bonus takes 1 hour after the posting to take effect.

*'''I can't enable my abilities!'''
**Use a browser that supports HTML5.
<div id="exp"></div><div id="EXP"></div><div id="noexp"></div><div id="noEXP"></div>
*'''I'm not receiving any [[EXP]]!'''
**Your [[Stamina]] has dropped below 2.

*'''"Nope"'''
**You are attempting to access an [[equipment]] piece's link with an invalid ID or key.

*'''Holding down hotkeys doesn't work!'''
**[[Image:Firefox.png]] If you are using NoScript, navigate Firefox to ''about:config'' and set ''noscript.clearClick.rapidFireCheck'' to "false".

*'''I jumped to a new fight instead of going to the next turn!'''
**The server cluster lost a node temporarily. Just wait a few minutes and it should re-establish the connection to the node and load your battle again.

*'''Some of the graphics don't show!'''
**Try {{Keypress|Ctrl}} + {{Keypress|F5}} to force reload them.

<div ID="ShopBot"></div><div ID="Profit"></div><div ID="Bazaar"></div><div ID="bazaar"></div><div ID="profit"></div><div ID="shopbot"></div>
*'''I sold an [[item]] to the [[Bazaar]] and got more [[credits]] than what it indicated.'''
**[[Item Bot]] [[Bazaar#Item_Shop|profit sharing]].

*'''My [[EXP]] required for the next level is showing as a negative!'''
**This is purely an aesthetic bug. It can occur when triggering a [[Dawn|dawn]] event that gives enough [[EXP]] to [[level up]] whilst in a [[battle]].

*'''"Your account has been suspended, or you have been blocked from accessing the HV minigame."'''
**Your account has been banned, likely due to [[Bans|rules]] violations. This is permanent.

<div id="H@H"></div>

==[[H@H]]==
;Always make sure you have the latest stable version of [https://www.java.com/en/download/ Java Runtime Environment] and that your internet speed is sufficient when running the client.

*'''Does H@H have any dependencies?
**H@H has zero dependencies other than Java itself.

*'''Does H@H include Log4j?'''
**No. H@H has zero dependencies other than Java itself.

*'''What's my Client ID?'''
**You will not have one if you did not sign up for H@H.
**Check [https://e-hentai.org/hentaiathome.php here] for it.
**Client IDs that have been inactive for more than 6 months (~180 days) are revoked. Re-applying is permitted.

*'''My client's status is fine but I don't earn any [[Hath]] from it!'''
**Hath will not be granted if a client's speed is below the minimum requirements<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=215951&view=findpost&p=5139875]</sup>.
***Make sure the client can constantly sustain at least 200KB/s of burst speed.

*'''My client isn't doing anything!'''
**Make sure the client is [[H@H#Activity|healthy]].
**If you are running a brand new client wait for your cache to fill (and subsequently [[static range]]s). Caches generally only fill for clients that have been running for at least 24 hours.
**Cached content itself will not affect hitrate; the only factors involved are burst speed, client quality, client region, and assigned [[static range]]s.

*'''I am not being assigned static ranges!'''
**Ensure your client is stable and active with sufficient dedicated disk space. Keep it running for as long as possible.
**There is a limit on how many times a range can be assigned to live clients in a region. If that limit is reached for all ranges, it won't assign any more until some clients go away.<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=234458&view=findpost&p=5758006]</sup>

*'''Disk usage is too high! Is there a way to limit this?'''
**To reduce disk seeks lower the cache size, a higher percentage of file accesses will be cached in RAM.<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=215709&view=findpost&p=5138580]</sup>
***'''All static ranges unable to fit within the new cache size will be lost.''' Ranges will be gradually reassigned once the cache becomes bigger again and the client is qualified to earn more ranges.

*'''HTTP 400 (Bad Request) responses show up in the client!'''
**This is normal as long as the client is within its region's average failure rate.
**If this happens a lot the client's ISP may have poor connectivity to the querying region. This can also be due to packet loss.

*'''My client has low trust!'''
**This commonly occurs after a bad shutdown since the server continues to attempt contact with your client after it went offline.
**Leave the client running, it will gradually regain trust if no other problems exist.
**If its trust is not recovering at all it may indicate a communication or file corruption issue. Check your cache.
**Low trust can also happen when your drive is full. It can happen on certain systems despite setting a free disc space in your panel. You can reduce your Maximum Disk Cache Size setting in your panel (and check "Remove static ranges if necessary") to fix that issue.

*'''My client's trust is fine but my quality drops!'''
**This is usually caused by transient routing problems in the short-term and prevents single malfunctioning clients from causing entire network issues by lowering their priority accordingly.
**Sudden and large drops are normal for newer clients; waiting for a few weeks will generally give a stable baseline.

*'''"Request host did not send Content-Length, aborting transfer."'''
**Something is blocking your requests; disable any [[#Common Problematic Software|problematic software]] that may be doing this.
**Disable [https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security Xfinity's xFi Advanced Security].

*'''"We appear to have reached the image limit. Attempting to contact the server to ask for a limit increase..."'''
**You have downloaded up to your daily limit via H@H downloader; you must wait 24 hours.
**This limit can be reset at your [[My Home]] area or increased by purchasing the "More Pages" [[Hath Perks]].

*'''"Server reported expired key; attempting to refresh time from server and retrying."'''
**Ignore this unless it persists.

*'''My client has been revoked!'''
**Your client has been banned for failing to adhere to the [[Hentai@Home#Signing_Up|uptime requirements]] by a significant margin, or having an unreasonably high cache/ranges reset count.
***Revoked clients can sometimes be reactivated by sending an unblock request to [https://forums.e-hentai.org/index.php?showuser=6 Tenboro]. This will be decided on a case-by-case basis, and can only happen when there is a very strong justification for your case.
***Note that claiming ignorance of the H@H uptime requirements or the automated warnings on your excessive cache/ranges resets is '''NOT''' considered an acceptable justification.
**This can also occur if any of your cache files were deleted and your cache database was not updated to reflect this. Do '''NOT''' manually delete files from your cache.
***If you need to reduce your cache size simply reduce the value in the client's setting. The client will automatically remove excess cache files.

*'''"Critical Error: java.sql.SQLException: disk I/O error"'''
*'''"java.lang.NullPointerException - [ERR] at org.hath.base.CacheHandler.initializeCacheHandler(CacheHandler.java:214)"'''
*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)} at org.sqlite.Conn.setAutoCommit(Conn.java:336)"'''
*'''"[ERR] java.sql.SQLException: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed)"'''
**Delete hath.db and rename hath.db.bak to hath.db, then restart the client.
***If this fails delete both files and restart the client.
**Make sure that the user you're running H@H as has write access to the directory from which you run it.
**If all else fails run [https://en.wikipedia.org/wiki/CHKDSK chkdsk] on the drive that stores H@H.

*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)} java.lang.InternalError: HTHEME is null"'''
**This is an aesthetic issue. [[Image:WindowsOS.png]] If the Themes service is disabled on a Windows OS and a client is running in the H@H GUI this error will happen whenever it is given focus as it fails to parse themes.
**Use the command-line client or enable the Themes service.

*'''"Cache Handler: cannot meet space constraints: Disk free space limit reached."'''
**Your free disk space was detected as too low. The client will stop getting new files until this is remedied.
**Change your disk space setting ("Minimum space to leave on disk") (minimum 100 MB even if not set) or remove non-H@H files from the drive that H@H uses.

*'''I'm having high memory usage running H@H under OpenVZ!'''
**Because of how OpenVZ calculates resident memory size H@H can appear to use as much as 1 GB of RAM even though its actual resident memory size is usually 50-100 MB.
**There is no known workaround at this time.

*'''My client's country on the H@H status page is shown in <span style="color:#ff0000">red</span>!'''
**Your client has been moved from its first-time startup location ("''home region''") to a different region. e.g., the client started in the United States, then moved to Japan at a later point.
**When the system detects that a client is operating outside of its ''home region'', this will have multiple effects<sup>[https://forums.e-hentai.org/index.php?s=&showtopic=234458&view=findpost&p=6376141]</sup>:
***Clients outside the ''home region'' will no longer be assigned new [[Hentai@Home#Static_Ranges|ranges]] or be considered for range priority promotions.
***If there are multiple clients with the same range/priority in the region, clients outside its ''home region'' will always be demoted first, and the client in the ''home region'' will be preferred for routing traffic.
***No [[Hath]] will be awarded for clients located outside of its ''home region''.
**To resolve this, you will need to contact [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] directly. Note that in most cases, resetting the ''home region'' of an H@H client will result in the demotion of all of the client's P1 ranges to P2 to allow the system to optimally rebalance range priority.
**This may also happen if the auto-detected country is simply wrong. In this case, a geolocation override may be applied without the demotion of [[Hentai@Home#Priority_Ranges|priority ranges]].

*'''My country is incorrect on my H@H page!'''
**This does not matter for clients in Canada/United States.
**If the indicated country is geographically very far away from what it should be an override for the client ID may be necessary. Please contact [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] directly.

*'''My client key is "Not Set"!'''
**You must enter all the configuration details (speed, disk size, etc.) before the key is given.

*'''The SSL handshake times out!'''
**This happens on some routers where the WAN is through PPPoE, although rare.
**If you have access to your router configuration you can change this with iptables:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -t mangle -A FORWARD -p tcp -i pppoe-wan -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu</pre>

For an ISP provided router you may need to switch the router into modem mode and append second router in front of it.

===Startup Errors===
*'''"Startup notification failed."'''
**(This is a generic message, but if no other message accompanies it then this section may apply).
**Your speed was measured as too low. Turn off any bandwidth-consuming applications and try again.
**Java may be binding an IPv6 port. Try launching H@H with <tt>java -Djava.net.preferIPv4Stack=true -jar HentaiAtHome.jar</tt>.
**You failed to contact the main server. Try again later.
**Turn off any anti-DDoS settings on your router which prevent multiple connections from occurring simultaneously.

*'''"The client has failed the external connection test."'''
**Your port for H@H was not detected as open. You may test it [https://canyouseeme.org/ here].
**Make sure that the port you are opening matches the one set in your H@H settings.
**Read a [https://portforward.com/ guide] to help with the opening of ports.
**Make sure you have a public IP address. ISPs may use [https://en.wikipedia.org/wiki/Carrier-grade_NAT CG-NAT], preventing others on the internet from seeing your computer.
**Check the IP of your router/modem. If it is [https://en.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces within a private range], you may have to ask your ISP to grant you a public address.

*'''My entire cache is being verified when I start the client!'''
**This happens whenever there was a bad shutdown. This is to ensure the integrity of your cache is still in good standing.
**The client should run normally after the checking is complete. Please be patient.

*'''"The database could not be loaded."'''
*'''"Critical Error: Failed to buffer requested data for cache list write."'''
**Delete hath.db, rename hath.db.bak to hath.db, then re-launch the client.
***If this fails, delete both files and re-launch the client.
**Make sure you have ownership of the files and folders that H@H uses.

*'''"Rejecting connection request during startup."'''
**If this doesn't happen very often just ignore it. Other users are simply contacting your client too soon.
**Check if your firewall or other software is blocking Java connections.

*'''"Required library file sqlitejdbc-v056.jar could not be found."'''
**The file is missing, re-download H@H.
**It you run H@H through a command line, make sure to <tt>cd</tt> to the same directory as the HentaiAtHome.jar file before running. You may also add that <tt>cd</tt> command to the batch file.

*'''"[WARN] Unknown host rpc.hentaiathome.net, aborting.."'''
*'''"[ERR] java.net.UnknownHostException: e-hentai.org"'''
**This may be a DNS issue. Try [https://documentation.cpanel.net/display/CKB/How+To+Clear+Your+DNS+Cache flushing your DNS cache] and restarting the client.
**Try switching to [https://developers.google.com/speed/public-dns/docs/using Google's public DNS].

*'''"[ERR] {java.lang.Throwable$WrappedPrintStream.println(Unknown Source)}"'''
*'''"Could not start the internal HTTP server."'''
**Something besides H@H is already using the port that it was assigned. Try closing any program that may be doing this or set H@H to use a different port.
<div id="ports"></div><div id="Ports"></div><div id="port"></div><div id="Port"></div>

*'''It doesn't allow me to use a specific port!'''
**The following ports aren't available due to browser blocking and other compatibility issues: 80, 2049, 3659, 4045, 6000, 6665, 6666, 6667, 6668, 6669.

==[[E-Hentai Forums]]==
*'''"Sorry, you are not permitted to use this board."'''
**Your IP address may be banned. Try to change it.
**[https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro] with your IP if this continues or if you cannot change it.
**[[Image:Opera.png]] You are using the Opera Mini browser/network. Try an alternate browser.
<div id="NoURLs"></div>

<div id="Attachment"></div>
*'''I can't post URLs or attachments!'''
**New users may not do so until they have made at least '''2''' posts.
**Some subforums and threads disallow attachments.
***If there is a serious need to post an image in such a thread simply upload to and link to a filehost.

*'''My post count is not going up!'''
**Posts made in certain subforums do not increase post counts.
**[[Forums#Rewards|There is no benefit to inflating one's post count anyway]].

<div id="TenboroPM"></div><div id="PMTenboro"></div>
*'''My PMs to [https://forums.e-hentai.org/index.php?showuser=6 Tenboro] are not being answered!'''
**He receives a lot of them, please be patient.

*'''I accidentally deleted a private message!'''
**Unfortunately it is too difficult to restore individual PMs from the site's backups.
**It is best to maintain [https://forums.e-hentai.org/index.php?act=Msg&CODE=14 archives] of important PMs on your own.

*'''My sent PMs are not showing up in my 'Sent' folder!'''
**You must check off "Add a copy of this message to my sent items folder" when you send messages.

*'''My post / thread disappeared!'''
**They were likely deleted by a moderator due to rule violations.
**Do '''not''' repost the offending content.

*'''I don't receive notification e-mails for private messages!
**Email notifications have been disabled. [https://forums.e-hentai.org/index.php?showtopic=239754&st=0&p=5717185&#entry5717185]
***Username/Password recovery emails, and PM archives requested to be sent to the registered email, are still enabled.
***Registration emails are not sent. A valid email address is not required to register an account, albeit a valid email is recommended for recovery purposes.

*'''I receive a warning e-mail from the forum!'''
**The forum will send a warning to your original e-mail address whenever the password or e-mail associated with the account is changed.

*'''I cannot see the CAPTCHA for posting.'''
**Disable any software that blocks ads or scripts.
**Try with a different browser.

*'''I made a [[donation]] recently but don't see the corresponding [[awards]]!'''
*'''I'm missing a [[award|confectionery]]!'''
*'''I don't get the corresponding [[Dawn]] rewards!'''
**Refresh your account by performing an action such as changing [[HentaiVerse]], [[Gallery]], or [[My Home]] settings, custom forum title, or buying/selling from the [[GP Exchange]] or [[Hath Exchange]].

*'''"Sorry, your posting rights have been temporarily suspended. The suspension is due to end on {date}."'''
**You have been blocked from submitting new threads or replies temporarily. This restriction will automatically expire eventually. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).
**<span style="color:red">'''Further violation of the [[forum rules]] will lead to a permanent [[Bans|ban]].'''</span>

*'''"Your posting permissions have been removed"'''
**You have been banned from making new threads or replies. This is permanent.

*'''"You are not allowed to use the messenger feature on this board"'''
**You have been banned from sending private messages due to repeated harassment or spam sent to other users.

==[[Bounty]]==
*'''I cannot contribute [[GP]] to a bounty.'''
**You may only use [[Hath]] or [[Credits]]. Use the [[GP Exchange]] to convert your gallery points to credits.

*'''I cannot claim a bounty!'''
**Check if you have met the [[bounty#Hunter_Ranks|Hunter Ranks]]. Note that Unranked is above Rank D.
**The bounty may be closed (a [https://e-hentai.org/bounty.php?s=c pending claim] already exists or [https://e-hentai.org/bounty.php?s=r the bounty is reserved]). Check its status.

*'''I claimed a bounty but even after 7 days, the claim was not accepted.'''
**Working as intended (see above). The bounty poster may no longer dispute the claim but you should PM/contact them to remind them as accepts are manual to prevent abuse.

*'''I cannot rescind a reward!'''
**Rewards can only be rescinded within 15 minutes of posting, after 30 days or by cancelling the bounty if it is yours. They also cannot be rescinded if the bounty enters a closed status (Closed/Claimed or Closed/Reserved).

*'''Bounties do not properly value Hath.'''
**Hath to Credit conversion uses the [[Hath Exchange]] average over 24 hours<sup>verification needed</sup>, not a static amount of 5,000 credits per Hath - the minimal amount is intended as a guideline.

*'''I cannot set bounty restrictions above rank A.'''
**Working as intended. If you notice users of rank A or above claiming bounties in bad faith, PM them politely or report them in the relevant thread to let other users know.
**If accounts reach rank A unusually fast and then immediately start claiming bounties in bad faith, you should contact Tenboro to have him investigate and, if applicable, ban all involved accounts. Please be patient.

*'''The requested bounty was not found.'''
**If you get this message when clicking on a link from the [[forums]], the [https://e-hentai.org/logs.php?t=credits credit log] or a private message, the bounty does not exist or was deleted by the bounty poster or Tenboro.
**Bounties you contributed to will be immediately refunded when deleted.

*'''"You have been banned from posting bounties."'''
*'''"You have been banned from claiming bounties."'''
**You are no longer allowed to use certain function(s) of the [[bounty]] system. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

==[[EHTracker]]==
*'''My stats are not being tracked!'''
**Make sure you are using the personalized torrent and not the public one.
**You may have reset your personal key. Any torrents with older personal keys need to be re-downloaded.
***Seedmins only count towards torrents you created yourself.

*'''My stats stopped updating even though I'm seeding properly!'''
**This generally happens if you are disconnected while seeding and have a dynamic IP address.
**Stop all torrents, then resume them in order to force a tracker announce check.

*'''I'm seeding but not gaining any GP!'''
**This only occurs [[EHTracker#Rewards|if you are the torrent's or gallery's uploader]].

*'''"Torrent not found"'''
**All torrents for the gallery have been expunged.

*'''"Upload Error: Failed uploading file (code=4)."'''
**The server didn't receive any file. Try uploading with another browser.

*'''"Invalid auth"'''
**Refresh the page and try to upload the torrent again.

*'''"Torrent Error: This torrent is already uploaded for this gallery."'''
**You are trying to upload an exact duplicate of a torrent that already exists for that gallery.

*'''"Upload Error: You have too many recently uploaded torrents with no completions. Make sure your torrents are seeded before adding more."'''
**You have uploaded [https://ehwiki.org/wiki/EHTracker#Limits too many torrents with 0 completes].

*'''"You have been banned from uploading torrents."'''
**You are no longer allowed to upload any torrent to the tracker. This is permanent. Check your [https://forums.e-hentai.org/index.php?act=Msg&CODE=01&VID=in forums PM inbox] for any moderator's notice(s).

==[[EHWiki]]==
*'''I'm not receiving a verification e-mail!'''
**You may change the e-mail address for the account and revalidate.

*'''I can't edit/create anything!'''
**You need to be in the 'Creator' group in order to edit/create pages. Please contact a [[E-Hentai Janitor|wiki admin]].

*'''I can't edit certain articles!'''
**Some articles are protected due to their importance or past abuse and thus cannot be edited by non-admins. Please [[E-Hentai Janitor|contact one of them]] if you have information to add/edit.

*'''I can't create an account!'''
**If your IP may be listed on the wiki's DNSBL.
**Change your IP and try again.

==See also==
*[https://forums.e-hentai.org/index.php?showforum=7 Forum - Site Discussion, Help & Feedback]

[[Category:Site Features]][[Category:E-Hentai Forums]][[Category:EHwiki]][[Category:HentaiVerse]][[Category:E-Hentai Galleries]]

Hentai@Home

2026-08-05T00:07:11Z

Kagoraphobia: /* H@H Downloader */

Hentai@Home (H@H) is an open-source Peer-2-Peer gallery distribution system which reduces the load on the [[E-Hentai Galleries]]. The current version can be found in the [https://forums.e-hentai.org/index.php?showtopic=234458 update announcement thread].

[[Image:H@H Client.png|thumb|The client UI (maximized)]]
[[Image:H@H Client Screen.png|thumb|The client list UI]]

==General Information==
H@H is a project that can be compared to a cross between the [https://setiathome.ssl.berkeley.edu/ SETI@home] project and [https://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent].

All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the [[E-Hentai Galleries]]. This allows E-Hentai to serve many more images using less server bandwidth.

==Signing Up==
[[Image:H@H Application.png|thumb|The H@H application form.]]
<div id="Requirements"></div><div id="requirements"></div><div id="Requirement"></div><div id="requirement"></div>
===Minimum Requirements For New Clients===
{|class="wikitable"
|-
!Requirement
!Notes
|-
|[https://www.java.com/en/download/ Java Runtime Environment]
|
*Version 8 or newer
*The JDKs are also usable.
|-
|80+ Mbit/s measured speed
|
*At least 2500KB/s must be dedicated to H@H
*This applies to both upload and download.
|-
|500 GB/month data transfer
|Users may limit how much data is used per month. Note that this limit is approximate.
|-
|10+ GiB of '''dedicated''' hard drive space
|
*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
*Please ensure the client can sustain both speed and disk I/O in the long run.
|-
|[https://portforward.com/ An open TCP port]
|
*443 recommended; otherwise must be between 1024-65534.
*[https://en.wikipedia.org/wiki/Ephemeral_port Unregistered IANA ports or UNIX kernel ports] are recommended as private ports. Check [https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers this list] for potential port conflicts.
*[[Technical_Issues#Ports|Some ports are not permitted]].
|-
|A unique IPv4 IP address
|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
|-
|Uptime
|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
|}

===Obtaining Client Keys===
Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

<div id="Installation"></div>

==Installation Guides==
*[https://forums.e-hentai.org/index.php?showtopic=19795 Windows]
*[https://forums.e-hentai.org/index.php?showtopic=100453 FreeBSD with Jails]
*[https://forums.e-hentai.org/index.php?showtopic=214602 Daemonizing H@H on BSD]
*[https://forums.e-hentai.org/index.php?s=&showtopic=19795&view=findpost&p=797807 Linux]
**[[Installing H@H on Ubuntu|Ubuntu]]
**[[Installing H@H on Debian|Debian]]
**[https://forums.e-hentai.org/index.php?showtopic=69880 Debian on Raspberry Pi]
**[https://forums.e-hentai.org/index.php?showtopic=69887 Solaris]
*[https://forums.e-hentai.org/index.php?showtopic=97809 Rented Server]
*[https://forums.e-hentai.org/index.php?showtopic=132751 Python Client]

==Limits==
A client's maximum burst speed (in KB/s) will determine the maximum number of connections that can be had simultaneously (up to 500 at 4800 KB/s or more).

Simultaneous connections are determined by a client's hitrate and burst speed (during speed tests, the packet size is adjusted to match the client's burst speed).
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

The disk cache size (in GB) must be enough to maintain static ranges. Clients must be able to store 10 GB or 250 MB per static range at any given time, whichever is higher:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Minimum cache size''' = max(10, static_ranges * 250 / 1024)</pre>

===Speed Test===
When the H@H client starts, it contacts one of the H@H control servers which tests the connection of the client in order to check if it can upload data at the configured maximum burst speed. If it cannot, the maximum burst speed is reduced internally to the measured upload speed in order to prevent the connection from being overloaded.

==Activity==
<div id="healthy"></div>A client is considered to be "healthy" if '''all''' of the following apply:
* The client '''must be running and not suspended'''.
* The client's '''[[#Trust|trust]] value must be above 0'''.
* The client must maintain a '''[[#Quality|quality]] of more than 2000'''.
* The client's tested speed must '''exceed 400 KB/s (for Asia clients) or 800 KB/s (for non-Asia clients)'''.
Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.

==Data Transfer Cap==
With each client, you may define a <i>Monthly Data Transfer Target</i> from the client's settings page (under the "Advanced Settings" section). This will help to prevent H@H from using more data than the monthly cap set by your ISP.
*If the system detects that you are likely to exceed this target, it will reduce the [[Hentai@Home#Priority_Ranges|priority]] of ranges on your client to reduce the load, but it is not guaranteed to stay below this value.
*The value must be at least 500 GB if set.
*If a limit is set, '''the [[static range]] allocation of that client will be limited to 1 per 5 GB.'''
**<span style="color:#ff0000">'''If set below 5000 GB/month, the client will not be assigned any [[Hentai@Home#High-Capacity_Ranges|high-capacity ranges]], and all previously assigned high-capacity ranges will be removed ''immediately''.'''</span>

==Software==
A few command line switches may be given to the H@H application in order to change some of its behaviors:
:<tt>--disable_bwm</tt>
::(''Can also be set from the client's settings page'')
::Disables the bandwidth monitor, which prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the <u>mean</u> upload speed of the client won't exceed that value. However, the client might use as much upload speed as its connection provides in order to send files, which generally results in upload peaks.
::In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the client's upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the client to give better performance.
:<tt>--disable_logging</tt>
::(''Can also be set from the client's settings page'')
::Disables the opening, creation, and writing to the ''log_out'' file. This will significantly reduce I/O for HDD but make network troubleshooting harder. Java errors will still be logged to ''log_err''.
:<tt>--flush-logs</tt>
::Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
:<tt>--max_connections=''conn''</tt>
::Sets the maximum number of connections the application can handle to ''conn''. The default maximum number of connections depends on the max burst speed parameter, as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value too high might have severe consequences on a client's performance and impact the whole H@H network badly. '''DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!'''
:<tt>--port</tt>
::Overrides the port set in the client's settings. For example, one may use this option and the following iptables rules to allow running H@H on one port officially (in the [https://e-hentai.org/hentaiathome.php settings page]) whilst binding or tunneling a completely different port. One potential use case cloud be: configure H@H in the setting to start on port <tt>443</tt> (HTTPS), then use <tt>--port=7777</tt> with the following iptables rules:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 7777 -j ACCEPT
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 7777</pre>
:<tt>--rescan-cache</tt>
::Checks the cache for errors.
:<tt>--silentstart</tt>
::Starts the UI in minimized mode / tray icon.
:<tt>--skip_free_space_check</tt>
::Disables the free space check so that the application won't err if the space left on the partition that contains the ''cache'' folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
:<tt>--verify_cache</tt>
::(''Can also be requested from the client's settings page'')
::Forces a check of the entire cache. This is the same as <tt>--rescan-cache</tt> with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
:<tt>--disable-ip-origin-check</tt>
::Disables the requirement that RPC server requests come from a whitelisted IP. Using this is discouraged as it reduces security, but may allow the client to work in some common non-transparent proxy configurations.
:<tt>--disable-flood-control</tt>
::Disables the rate limit on connections per IP address. May be necessary to use with the above trigger.

===Directories===
:<tt>--cache-dir</tt>
:<tt>--data-dir</tt>
:<tt>--download-dir</tt>
:<tt>--log-dir</tt>
:<tt>--temp-dir</tt>

These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only ''log'' and ''temp'' may share a directory.

Examples:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Windows''': --download-dir="c:\some download dir with spaces\"
'''Linux''': --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath</pre>

==Cache==
The system fills a client's cache exclusively with [[#Static Ranges|static ranges]] of files. Users should '''not''' tamper with any of these files; this will cause major [[#Trust|trust]] and cache database issues for the client. Corrupted files will be deleted and replaced if requested.

===Static Ranges===
Static ranges each correspond to 1/65536th of the site's content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use.

The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example if the client if offline for an extended period of time.

To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

====High-Capacity Ranges====
Static ranges can also be promoted into High-Capacity (HC) ranges, in which the client will be used to serve large and original quality files of that range.

To receive any HC ranges assignment, clients must meet more stringent requirements:
*Must be located in one of the three major regions with surplus capacity. i.e., Europe, North America, or Asia (excluding mainland China)
*Must have at least 10000 KB/s throttle and 8000 KB/s tested speed
*Must have the [[Hentai@Home#Data_Transfer_Cap|monthly bandwidth limit]] set to either unlimited (0) or at least 10000 GB/month
*Must have at least 100 GB of disk space assigned

The maximum number of HC ranges that a client can have is limited to 1 per 1 GiB of reserved disk space. <span style="color:#ff0000">'''You will lose all of your assigned HC ranges if you set a [[Hentai@Home#Data_Transfer_Cap | data transfer cap]] below 5000 GB/month or reduce the maximum upload rate below 10000 KB/s.'''</span> The traffic estimates for calculating Hathrate will also be reset.

Due to their surplus cache capacity, clients with a low ratio of P1 ranges will be preferred for HC range promotions. '''Do NOT attempt to avoid P1 assignments for the sake of gaining HC ranges''', as they are still preferable over HC ranges.

Note that HC ranges are set independently of priority, meaning a static range can both have a priority of P1 and be set as an HC range.

==Trust==
Trust indicates how well the client is performing according to other clients.
*Trust caps at +1000 and gradually rises by 1-4 per minute if the client is behaving normally, even if it is not serving files.
*Negative trust often occurs from improper shutdowns, bad connections, or having a higher than expected number of cache misses.

==Quality==
Quality measures the long-term overall stability and reliability of a client, calculated by comparing the client's average failure rate to the average failure rate of the region. It influences the assignment/promotion of [[static range]]s, as well as the allocation of traffic.
*If the client's average failure rate is the same as the regional average, the quality metric will be at 9000. To achieve maximum quality (i.e., 10000), the client would need to have less than half the failure rate compared to the average.
*If the quality drops below 2000, the client will stop receiving traffic until it recovers.
*New clients with minimal traffic may experience some fluctuations in the value, but this will stabilize over time.
*Due to the quirkiness of the region, clients located within the Chinese Dominion region (i.e., mainland China) do not use the quality metric. The value output is locked at 10000 on the user end.

==[[Rewards]]==
Users receive 1 [[GP]] for each hit on their client and may compete for a position on the [[Toplists#Hentai.40Home_Toplists|H@H toplist]]. While running [[Hentai@Home#healthy|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

The daily [[Hath]] earned per client is based on the following formula:
<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">'''Hathrate/day''' = 1 + 0.15 * max(hits_per_minute, KB_served_per_minute / 420) + 0.025 * active_rangecount + 0.05 * hicap_rangecount</pre>
*The contribution from assigned ranges is capped by the client's tested speed. The cap is set to <tt>tested_speed / 100 KB/s</tt>.
*The [[Hath]] is made available roughly every 4 hours the client has been running.
*Only [[Hentai@Home#healthy|healthy]] clients which current or previous session '''lasted for at least 24 hours straight''' will generate [[Hath]].
*Clients will not receive any [[Hath]] if the [[Hentai@Home#Quality|quality]] drops below 2000.

===H@H Downloader===
''For more information, please check [https://forums.e-hentai.org/index.php?showtopic=196195 this thread].''

An H@H client can be used to download [[archive]]s (instead of via HTTPS).
* Resolution options include 800x, 1280x, 1920x, 2560x, or original (availability may differ).
**2560x resamples cannot be downloaded for galleries older than 1 year. The maximum available resolution will be 1920x.
**If they were already created, the 2560x option can still be used on older galleries.
* Once queued there is no way to prevent the client from downloading the gallery.
* A ''galleryinfo.txt'' file is generated upon completed unlike [[archive]] downloading.
* [[Archives#Filenames|Filename changes]] still occur.
* These downloads still cost [[GP]]/[[credits]] ([[#Free_Archives|see below for exceptions]]).
* The download queue is server-side and as such is not affected by client-side interruptions. It will resume if the client is restarted. Queued downloads aren't pruned unless the client fails to download them for a full week. The client will verify that the downloaded file has the expected hash at completion.

====Free [[Archives]]====
[[Hentai@Home#healthy|Healthy]] clients with its current or previous session '''lasted for at least 24 hours straight''' earn a quota of 1,000 MB/day in free [[archive]] downloads. An additional 10 MB/day is earned per adjusted average hit.
* This quota is measured over a 7-day sliding window.
* [[Archives#Costs|Recreated archives]] do NOT qualify.
* Extra clients do NOT earn another 1,000 MB.
* The amount a user has earned can be found on their H@H client list page at the bottom of the "Your Active Clients" section.

==Revocations==
Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.

Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

If your client is revoked, you will not be able to re-apply to H@H in the future.

==See also==
*[[Hentai@Home FAQ|FAQ - Hentai@Home]]
*[[Technical_Issues#H.40H|Technical Issues - H@H]]
*[[Hath]]
*[[Downloading]]
*[[Renting A Seedbox]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=19795 H@H FAQ topic]
*[https://forums.e-hentai.org/index.php?s=&showtopic=101296&view=findpost&p=2336526 Running H@H as a Service]
*[https://forums.e-hentai.org/index.php?showtopic=238973&st=0&p=5695501&#entry5695501 Tenboro's post detailing the limitations regarding the allocation of static ranges]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]][[Category:Site Features]]

Gallery Tagging

2026-08-03T22:18:41Z

Kagoraphobia: /* Good Tags */ nice wiki editing there shanky

Tagging is a system of the [[E-Hentai Galleries]] to assist users in identifying the major contents and properties of a gallery.

<i>Additional rulings and clarifications can be found on the [[Talk:Gallery_Tagging | talk page]].</i>

[[File:Tagging_Guidelines.png|frame|567px|right|The Tagging Guidelines pop-up appears the first time a user attempts to tag a gallery. Users agree to having fully read and acknowledged these rules.]]

<div id="Rules"></div><div id="Rule"></div><div id="Guidelines"></div>
==General Usage Guidelines ==
<div id="Presence"></div><div id="Rule1"></div>
{| class="wikitable" width="100%"
!Rule
!Details
!Examples / Exceptions
|-
|'''Presence'''||[[Image:Point.png]] <font size="5">In general do '''<span style="color:#ff0000">NOT</span>''' tag something unless it has a fair amount of presence in a gallery. In general, do not tag content that is only featured in a few images.</font>
||<u>Example</u>: The following presence examples always qualifies a normal presence tag:
*25% of any sized gallery.
*10 or more sequential images in an 80 or less pages gallery.
*20 or more sequential images on any sized gallery.

<u>Notes</u>: The no. of minimal required images does not always scale up/down with the gallery size 1:1. Although a 10 sequential in 80 pages gallery is acceptable, 5 in 40 is not.
*A presence-passing count in a large gallery also generally holds in the smaller galleries. Therefore, since 10/80 (sequential) is ok, sequential 10/40 or 10/60 would be as well.

See the [[Talk:Gallery_Tagging#Presence_Notes|talk page]] for further details.

<u>Exceptions</u>: [[Talk:Gallery_Tagging#1-Image_Only_Tags|1-Image Only Tags]].<div id="Definition">
|-
|'''Definition'''||The meanings of various tags on this site may not match those of other sites. Please read the definition of each tag before using it.
||<u>Example</u>: [[brother]] is only used in cases of [[yaoi]] [[incest]].<div id="Formatting">
|-
| rowspan="2" |'''Formatting'''||Tags only allow for alphanumeric characters, spaces, periods, and hyphens. Tags must be at least 3 characters long.
||<u>Exceptions</u>: [[3d]] or anything with a [[namespace]] (e.g. a:23).
|-
|Due to the aforementioned limitation certain terms are tagged differently than how they are normally written.||<u>Example</u>: The circle "#define" is tagged as "g:sharp define", and artist "hhh_hudiki" as "a:hhh-hudiki".
<div id="Namespace"></div>
|-
|'''Namespace'''||[[Fetish]] tags use a female, male, or mixed namespace to indicate which gender(s) is applicable. For these purposes [[futanari]] and [[shemale]] are considered female.
||<u>Example</u>: m:[[glasses]] if a male is wearing them, f:[[glasses]] for a female.
<div id="Conflicting"></div><div id="Conflicts"></div><div id="Conflict"></div>
|-
|'''Conflicting'''|| Tags such as [[dark skin]] and [[tanlines]], or [[swimsuit]] and [[school swimsuit]] do not go together as they are mutually exclusive; they can only be tagged if they both occur separately.
||<u>Example</u>: A participant with tanlines having sex followed by a dark skinned one in another instance would suffice for both tags.<div id="newtag"></div>
|-
|'''New'''||
*Artist, Group, Cosplayer, Parody and Character tags may be requested with citations.
*Entering temp: followed by the desired tag will prompt you to provide a source for the tag. See [[Tag Creation]] for detailed instructions.
*Users will also be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
*'''Hitting the "OK" button will also bring up the New Tag Justification window if the user has at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
||<u>Warning</u>: The creation of new fetish/content tags is highly restricted. Please use the [[forums]] to discuss new tag possibilities of this nature.
*[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence, or repeated misuse of the tag creation tool including repeated creation of fetish tags may lead to a [[Bans|ban]].'''</span>
|}

==Presence Recognition Types==
<div id="Visual"><div id="Visuals">
{| class="wikitable" width="100%"
!Rule
! Details
!Examples / Exceptions
|-
|'''Visual'''||Nearly all fetish tags are based on visuals, not text (''see the next rule''). If there is any conflict between what is being said and what is shown the visual wins.||<u>Example</u>: A young-looking girl saying she is old does not qualify for the [[milf]] / [[old lady]] tags.
<div id="Context"></div><div id="Contextual"></div>
|-
|'''Contextual'''||[[Fetish_Listing#Contextual|Contextual tags]] do not require visual presence but must have dialogue/story presence. These should '''NOT''' be tagged unless they are fairly obvious to a casual reader.
||<u>Example</u>: A woman saying the man with whom she's having sex is not her husband counts as [[cheating]].
</div>
|}

==Special Tag Types==
<div id="Gallery-Wide">
{| class="wikitable" width="100%"
!Rule
!Details
! Examples / Exceptions
|-
|'''Gallery-Wide'''||Gallery-Wide tags apply to an entire gallery. They have single page requirements to tag, but do not qualify if a single conflicting image is present.
||<u>Note</u>:

* 1 image is enough to qualify or disqualify most of these tags. Omake/covers/credits/colophons are ignored.
*Gallery-Wide tags that indicate the gender of the participants, for example [[sole female]], [[males only]], etc. allow for minimal amounts (no more than a single page) of conflicting content so long as the depicted actors are not vividly displaying sexual activity beyond nudity, and are not real or in-universe participants, e.g. being depicted in a magazine.<div id="Costume"></div><div id="Clothing"></div><div id="Clothes"></div><div id="Costumes">
|-
|'''Clothing'''||Costume tags such as [[schoolgirl uniform]] only apply if they are kept on (at least partially) during sexual activities. If they are absent or removed beforehand they should '''NOT''' be tagged.
||<u>Exceptions</u>: For non-pornographic galleries the clothing does not need to be removed in any way.<div id="Locations"></div><div id="Location"></div>
|-
|-
|'''Location'''||Location tags only apply if relevant during sexual activities. If the location is used without any sexual activity/nudity they should '''NOT''' be tagged.
||<u>Note</u>:
*For non-pornographic galleries the location tags are not applicable.<div id="Visual"></div><div id="Change"></div>
*There needs to be a sufficient amount of visual indications to confirm that the scenes take place in a certain location, before the tag in question is applicable. For example, merely wearing a swimsuit outdoors on a sunny day is '''NOT''' sufficient for the [[beach]] tag.
|-
|'''Change'''||For all (but four) change tags only the images involving the change itself are counted towards presence.||<u>Exceptions</u>:
*For [[gender change]] / [[gender morph]] the duration of the individual being a different gender also qualifies.
*For [[futanarization]], the duration of the character being a dickgirl also counts.
*For [[body swap]], post-swap images also count for presence.<div id="Animal"></div><div id="Animals">
|-
|'''Animal'''
|All animal tags require that an animal be explicitly involved in sex or nudity (e.g. [[animal on animal]], [[bestiality]]).
|<u>Example</u>: Two canines mating allows for the [[dog]] tag; a [[furry]] [[dog girl]] having sex with a human does not.<div id="Format"></div><div id="Format">
|-
|'''Format'''
|Format tags work similarly to the [[category|gallery categorization]] system. The work must overall fulfill the gallery format as specified in the respective definition for it to be applicable.
|<u>Examples</u>:
*A loose 200-pages [[western imageset]] containing 20 sequential [[comic]] pages should '''NOT''' be tagged with [[comic]].
*Some CG images within a published western release that is still predominantly utilizing panels to convey their story should still be tagged with [[comic]], but '''NOT''' [[western cg]].
|}

==[[Tagging Mechanics]]==
Tags are voted on by the users of the site as such they are subject to potential errors. Tags with <span style="border:thin solid green;">solid</span> borders have a cumulative [[mod power]] that is equal to or higher than 100 (i.e., been upvoted by many users, or by a handful of individuals with high [[mod power]]). Tags with <span style="border:thin dashed green;">dashed</span> borders mean that their cumulative [[power]] is between 10 to 99, while <span style="border:thin dotted green;">dotted</span> tags have a cumulative [[power]] between 1 to 9. <span style="color:#ff0000">'''It is important to note that the cumulative [[power]] of a tag does NOT necessarily indicate its validity.'''</span> '''Precaution must always be exercised when judging whether a tag is correct or not.''' See the [[#Forum Links|forum links]] below to report any tag misuse. Tags do not indicate to which images and to which participants they are applicable within a gallery; this information can be provided by gallery [[comments]].

==Good Tags==
;Contents/Fetishes
:As long as they are relevant sexually and pass presence. Whenever in doubt it is better not to tag them.

;Languages
:Tagged in their English equivalent (e.g. ''<span style="color:green">Spanish</span>'' not ''<span style="color:red">Espanol</span>'').

;Circles
:Names of the circles/groups that published the work. Should '''NOT''' be added when they are not officially credited (e.g. most [[Manga]]).

;Artists
:Names of the artists who drew portions of or all of the work; must be officially credited as such. Japanese artists should be written using [https://en.wikipedia.org/wiki/Hepburn_romanization Hepburn romanization]; some exceptions exist for artists that consistently spell their names otherwise.

;Cosplayers
:If the cosplayer consistently uses a name order, use that. Otherwise, follow the name order of the cosplayer's country.
<div id="originalseries"></div>
;Original Series
:Names of the series that are being parodied. Should generally be as specific as possible (e.g. ''[[Dragon Quest VIII]]'' instead of just ''[[Dragon Quest]]'') if the sub-series passes presence. A combination of images from different sub-series that passes presence (but no one sub-series passes) uses the generic series tag instead.
*The following apply:
**All canon characters within a parody
**Canon races within the parody (e.g., Khajiit from [[the elder scrolls|The Elder Scrolls]])
**Costumes styled after a parody if that parody is specifically mentioned/has some context in the work.
<div id="Character"></div><div id="Characters"></div>
*The segregation or unification of subseries is based on [[Series_Segregation#Reasoning | a number of factors]].

;Participants
:Names of characters (including [[cosplaying]]) participating in the gallery. Original characters (non-parodies) that do not exist outside of their own works should not be tagged.
*Non-pornographic works may only have the '''most focused''' characters be tagged.
* Character names are preferred in full western order; given name(s) followed by family name. e.g. ''[[hinata hyuga]]''. There are rare exceptions.
*Any character who transforms '''beyond that of a costume change''' (to the point where a casual observer cannot tell they are the same person) is to be tagged with their alias (should they have one). e.g. ''[[peashy]]'' vs. ''[[yellow heart]]''.
* A [[gender change|gender changed]] character is preferred be tagged with their regular name.
*A character with no official name may be tagged based on their relationship with another character. e.g. ''[[dexters mom]]'' from ''[[Dexter's Laboratory]]''.<sup>([https://dexterslab.wikia.com/wiki/Mom#Trivia Ref])</sup>
*Characters that share the exact same name (e.g. ''c:sakura'' from ''[[Urusei Yatsura]]'', ''[[Fire Emblem Fates]]'', etc.) can not be differentiated except by other tags such as parodies or attributes.

<div id="Category"></div><div id="Categories"></div>
===[[Gallery Categories‎|Categories]]===
[https://repo.e-hentai.org/tools/taggroup?show=1 Reclass tags] should only be used to fix an improperly categorized gallery. Once a tag receives 100 [[power]] the category will switch.
*If there are conflicting category tags, the one with the earliest "[[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|lock-in]]" time determines the category.
**To make a new category tag take effect, the pre-existing category tag must be downvoted to at least [[Tagging_Mechanics#Tag_Mod_Power|non-solid border]].
*These tags are automatically pruned from galleries after 30 days of no voting activity.
*Please note that "reclass:asianporn" is no longer functional. See its [[asianporn|definition]] for details.

<div id="Directory"></div>

=== Tag Directory===
{{TagNav}}

== Information Sources==
The information used to tag should always be based solely on the contents of the images in the gallery itself. The gallery's title, comments, or 3rd party sites do NOT qualify as information sources in the majority of cases.

<u>Exceptions:</u>
*[[:Category:Series_Tag|Parodies]] have all of their canon counted as existing information (unless the dialogue indicates otherwise). This precludes informed attributes for visual tags (e.g. [[Lum]] from [[Urusei Yatsura]] can be tagged with [[oni]] but not with [[alien girl]]).
*If an artist's name is not present in the gallery it may be obtained from a verifiable source such as the circle's website or store listing.
*The title may be used as proof of [[incest]] (unless the dialogue indicates otherwise).
*Participants' genders being ''extremely'' vague may use a verifiable source to identify them.

==[[Know The Difference]]==
For tags that are often confused for one another.

==Bad Tags==
;Commissioners / Decensors / Scanners / Translators
:Do not produce the content.
;No Sexual Connection
:(e.g. baseball, celebrity, clouds, exercise, microphone, pillow, red eyes, sword)
;Opinionated / Pejorative
:(e.g. cute, extreme, funny, gross, hot, garbage, nice, sad, scary, terrible, ugly, weird)
;Publishers / Websites
:Do not actually produce the content. Rare exceptions apply if nothing else can be used to identify a work's creator.
;Software
:The tools the artist used to created the content are irrelevant.
;Too Common
: (e.g. anime, nymphomaniac, semen, sex, skirt, softcore, straight, upskirt, vaginal)
;Too Vague
: (e.g. areola, ass, fetish, nipples, pussy, shaved, wet)
;Writers
:Not to be confused with the artists.

== Do Not==
*Use category exclusive tags outside of their category (e.g. [[non-nude]] is only for [[Cosplay]], [[comic]] is only for [[Western]] or [[Misc]]).
*Use [[:Category:Language Tag|language tags]] for anything other than indicating a gallery's text.
*Use a language tag on [[imageset]]-style galleries unless a majority of it (50%+) contains text in that language.
*Tag [[mother]] when not in conjunction with [[incest]]. This includes women giving [[birth]], women who happen to have children, or [[milf]]s.
*Use the [[cosplay]] tag when characters in drawn works are dressed as other recognizable characters; use [[cosplaying]] instead.
*Downvote any "redundant" reclass tags (i.e. being the same as the gallery's current category).
*Downvote any tag(s) that becomes "invalid" due to the uploader attempting to remove valid content. The said gallery should be reported for a [[Expunging#Reverting_and_Splitting|reversion/spilt]] action.
**If the tag(s) remains invalid after the revert/split, they may be downvoted accordingly.
*Downvote [[Fetish_Listing#Expunging|expunging tags]] purely because an [[Expunging|expunge petition]] has not been created. The system will automatically prune them from an active gallery if they remain for longer than 30 days.
**If the expunge type is definitely not valid for the gallery, then it may be downvoted.

==== Temporary Tags ====
Upvoting these tags is generally unnecessary. Galleries may be fixed / updated which would render such tags invalid.
*[[incomplete]]
*[[missing cover]]
*[[out of order]]
*[[Expunging]] tags
<div id="Why Should I Tag?"></div>

==[[Rewards]]==
Tagging earns points towards the [[toplists]].

[[Image:Point.png]] Poor tagging will result in the user '''losing''' [[power]]. Any attempts at farming points, accuracy spoofing, or heavy misuse WILL result in a permanent [[ban]].

==Exact Tag Searching==
Searches for certain tags can return results from more tags than intended. This happens to tags that appear as partial strings inside longer tags.

<u>Example</u>: The tag ''f:wolf'' will match both [[wolf]] and [[wolf girl]]. This also impacts [[slave tag]]s; a search for ''f:anal'' may return a gallery tagged with [[sex toys]]. This happens because the search for ''anal'' matches "anal beads" which is slaved to [[sex toys]].

To avoid this users may search with a dollar sign at the end of the tag to search only for that string (e.g. ''f:wolf$'', ''f:anal$'', etc.)

==Tagging Hotkeys==
The following hotkeys can be used when a tag is selected.

{| class="wikitable" style="text-align: center;"
! rowspan="2" |Function
! colspan="4" |Hotkeys
|-
!Numpad!!Other
|-
|Show All Tagged Galleries||{{Keypress|4}}||{{Keypress|A}}
|-
|Show Tag Definition||{{Keypress|6}}||{{Keypress|D}}
|-
|Vote Up||{{Keypress|8}}||{{Keypress|W}}
|-
|Vote Down||{{Keypress|2}}||{{Keypress|S}}
|-
|Clear Selection||{{Keypress|5}}||{{Keypress|Spacebar}}
|}

==Tag Tracker==
Users may see recently added tags across all public galleries via https://repo.e-hentai.org/tools/tagtrack
*This tool is primarily for tag cleanup, including removing invalid tags and making strong valid ones.
*Tags are displayed per gallery, and show that that are:
**<span style="opacity:0.3">weak</span> (with 1-9 [[Mod Power|MP]])
**<span style="opacity:0.7">active</span> (with 10-99 MP)
**<span style="color:#0000a4">SOLID</span> (with ≥100 MP)
**<span style="color:#009b00">ENFORCED</span> (tags that were added, and were [[Tagging_Mechanics#Tag_Veto|hard enforced]])
**<span style="text-decoration:line-through; opacity:0.3">downed</span> (tags that were added, but reduced to 0 MP)
**<span style="text-decoration:line-through; opacity:0.3;color:#f00">vetoed</span> (tags that were added, but were [[Tagging_Mechanics#Tag_Veto|hard vetoed]]).
*The results may be filtered in the following ways:
**'''downed''' - Displays tags that were created and have been reduced to 0 MP without being vetoed.
**'''weak''' - Displays tags that were created and have between 1-9 MP inclusive.
**'''active''' - Displays tags that were created and have between 10-99 MP inclusive.
**'''solid''' - Displays tags that were created and have 100 MP or higher.
**'''aged galleries''' - Displays galleries that have been tagged after they are no longer considered new.
**'''revived tags''' - Displays tags that were killed, and have been revived.
**'''exclude expunged''' - Filters out expunged galleries from the list.
**'''exclude autotags''' - Filters out tags added by the system, e.g. p:[[original]], or tags added due to a [[Namespace|slaving action]], etc.
**'''Tag/NS''': Filters out all but the chosen tags, with the following formats:
***''tag'', with no namespace, e.g. [[hairy]], will search for tags in all namespaces that match it.
***''namespace:tag'', e.g. f:hairy, will search for all tags that match both the tag and namespace.
***''tagid'', will return results for only the tag that has the chosen tagid.
***''special:namespace'', e.g., special:female, will search for all tags with the chosen namespace.

==Tag History==
Users can check their own tag history (up to actions made within the last 60 days), accuracy ratings, and overall usage via this tool:

<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">https://repo.e-hentai.org/tools/taglist?uid={USERID}</pre>
*Replace {USERID} with a userID (can be found by going to a user's profile in the [[forums]]) then checking the URL.
**Example: [https://forums.e-hentai.org/index.php?showuser=5 Snowflake] (UID: 5) would use the URL https://repo.e-hentai.org/tools/taglist?uid=5
*A &from={UNIXTIME} string may be added at the end of the above-mentioned URL. This can be used to allow users to quickly review their tagging actions made on or before the specified time.
**The date and time provided in the string must be in the Unix time format.
**Example: If Snowflake wants to review their tag actions made on or before July 2, 2026, 15:34:17 UTC, they would use the URL https://repo.e-hentai.org/tools/taglist?uid=5&from=1783016057
**A "'''Show Older >'''" button is also available at the end of the page, allowing users to continue reviewing their tagging histories dating even further back in time.
*Votes are organized by gallery. The value next to each tag indicates the amount of [[power]] utilized for that action at the time.
**A <span style="color:#008000">green</span> positive value (e.g., <span style="color:#008000">'''+69'''</span>) indicates that the user upvoted that tag in the gallery.
**Meanwhile, a <span style="color:#ff0000">red</span> negative value (e.g., <span style="color:#ff0000">'''-69'''</span>) indicates a downvote on the tag from the user.
**An <em>italicized</em> entry (e.g., ''female:nakadashi'') indicates that the user started the said tag.
*Accuracy score calculations are delayed by 3 days. Further accuracy checks take place to ensure a tag vote remains correct. '''Accuracy values are not foolproof; users should always manually review their tags.'''
**Vote entries that are highlighted in <span style="color:#ff0000">red</span> (e.g., <span style="color:#ff0000">female:nakadashi</span>) either indicate a started/upvoted tag was killed, or a downvoted tag is still alive.
**Started/Upvoted tag killed will be assessed as a "bad" vote (e.g., <span style="color:#008000">'''+69'''</span> <span style="color:#ff0000">female:nakadashi</span>) and negatively affects your accuracy.
**A downvote on tag will also be assessed as "bad" (e.g., <span style="color:#ff0000">'''-69'''</span> <span style="color:#ff0000">female:nakadashi</span>) if another user upvotes it after your downvote. Your accuracy will also be negatively impacted.
***Should the tag becomes fully downvoted later, it will be retallied and no longer classed as a "bad" vote on your record.
***For this reason, users are encouraged to use the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread to ensure that the identified invalid tags are fully downvoted.
**Users may use the "Filter galleries with assessed bad tagvotes" toggle to quickly review their tag votes that were assed as "bad" by the system.
*Accuracy scores are split by month, year, and overall total. The metrics are further separated into "Started" and "Voted" accuracies.
**Only the most recent seven monthly accuracies will be shown to the user. Yearly accuracies reflect the user's average tagging performance over the last 12 months.
**"Started" indicates accuracy for tags the user added themselves. "Voted" indicates accuracy for votes on tags already on a gallery.
**Values of less than 100 tags will only show the number of tags voted in gray without an accuracy calculation.
**"-" indicates 0 tags were voted by the user during that time period.

*[[Janitor|Tag checkers]] may check the history of any user.
**[[Image:Point.png]] Having an accuracy metric highlighted in red puts the user at high risk for a [[ban]].

==Limitations==
Users with < 2 [[power]] are unable to start tags or downvote tags.

==See also==
*[[Fetish Listing]] - A categorized list of all official fetish tags.
*[[Technical_Issues#Gallery_Tagging|Technical Issues - Gallery Tagging]]
*[[Toplists#Tagging_Toplists|Toplists - Tagging]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] - Please report any bad tagging here.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]
[[Category:Rules]]

Gallery Tagging

2026-08-02T19:36:24Z

Kagoraphobia: /* Do Not */

Tagging is a system of the [[E-Hentai Galleries]] to assist users in identifying the major contents and properties of a gallery.

<i>Additional rulings and clarifications can be found on the [[Talk:Gallery_Tagging | talk page]].</i>

[[File:Tagging_Guidelines.png|frame|567px|right|The Tagging Guidelines pop-up appears the first time a user attempts to tag a gallery. Users agree to having fully read and acknowledged these rules.]]

<div id="Rules"></div><div id="Rule"></div><div id="Guidelines"></div>
==General Usage Guidelines ==
<div id="Presence"></div><div id="Rule1"></div>
{| class="wikitable" width="100%"
!Rule
!Details
!Examples / Exceptions
|-
|'''Presence'''||[[Image:Point.png]] <font size="5">In general do '''<span style="color:#ff0000">NOT</span>''' tag something unless it has a fair amount of presence in a gallery. In general, do not tag content that is only featured in a few images.</font>
||<u>Example</u>: The following presence examples always qualifies a normal presence tag:
*25% of any sized gallery.
*10 or more sequential images in an 80 or less pages gallery.
*20 or more sequential images on any sized gallery.

<u>Notes</u>: The no. of minimal required images does not always scale up/down with the gallery size 1:1. Although a 10 sequential in 80 pages gallery is acceptable, 5 in 40 is not.
*A presence-passing count in a large gallery also generally holds in the smaller galleries. Therefore, since 10/80 (sequential) is ok, sequential 10/40 or 10/60 would be as well.

See the [[Talk:Gallery_Tagging#Presence_Notes|talk page]] for further details.

<u>Exceptions</u>: [[Talk:Gallery_Tagging#1-Image_Only_Tags|1-Image Only Tags]].<div id="Definition">
|-
|'''Definition'''||The meanings of various tags on this site may not match those of other sites. Please read the definition of each tag before using it.
||<u>Example</u>: [[brother]] is only used in cases of [[yaoi]] [[incest]].<div id="Formatting">
|-
| rowspan="2" |'''Formatting'''||Tags only allow for alphanumeric characters, spaces, periods, and hyphens. Tags must be at least 3 characters long.
||<u>Exceptions</u>: [[3d]] or anything with a [[namespace]] (e.g. a:23).
|-
|Due to the aforementioned limitation certain terms are tagged differently than how they are normally written.||<u>Example</u>: The circle "#define" is tagged as "g:sharp define", and artist "hhh_hudiki" as "a:hhh-hudiki".
<div id="Namespace"></div>
|-
|'''Namespace'''||[[Fetish]] tags use a female, male, or mixed namespace to indicate which gender(s) is applicable. For these purposes [[futanari]] and [[shemale]] are considered female.
||<u>Example</u>: m:[[glasses]] if a male is wearing them, f:[[glasses]] for a female.
<div id="Conflicting"></div><div id="Conflicts"></div><div id="Conflict"></div>
|-
|'''Conflicting'''|| Tags such as [[dark skin]] and [[tanlines]], or [[swimsuit]] and [[school swimsuit]] do not go together as they are mutually exclusive; they can only be tagged if they both occur separately.
||<u>Example</u>: A participant with tanlines having sex followed by a dark skinned one in another instance would suffice for both tags.<div id="newtag"></div>
|-
|'''New'''||
*Artist, Group, Cosplayer, Parody and Character tags may be requested with citations.
*Entering temp: followed by the desired tag will prompt you to provide a source for the tag. See [[Tag Creation]] for detailed instructions.
*Users will also be presented with a [[Technical Issues#temp tag pop-up warning|pop-up message]] when upvoting an existing temp tag that does not already have an active entry on the [[Tag_Creation#Tag_Approval_Tracker|approval tracker]].
*'''Hitting the "OK" button will also bring up the New Tag Justification window if the user has at least 15 [[mod power]] and no active tag creation [[Bans|ban]].'''
||<u>Warning</u>: The creation of new fetish/content tags is highly restricted. Please use the [[forums]] to discuss new tag possibilities of this nature.
*[[Image:Point.png]] <span style="color:red">'''Repeatedly creating an entry on the [[Tag_Creation#Tag_Approval_Tracker|tag approval tracker]] without providing any supporting evidence, or repeated misuse of the tag creation tool including repeated creation of fetish tags may lead to a [[Bans|ban]].'''</span>
|}

==Presence Recognition Types==
<div id="Visual"><div id="Visuals">
{| class="wikitable" width="100%"
!Rule
! Details
!Examples / Exceptions
|-
|'''Visual'''||Nearly all fetish tags are based on visuals, not text (''see the next rule''). If there is any conflict between what is being said and what is shown the visual wins.||<u>Example</u>: A young-looking girl saying she is old does not qualify for the [[milf]] / [[old lady]] tags.
<div id="Context"></div><div id="Contextual"></div>
|-
|'''Contextual'''||[[Fetish_Listing#Contextual|Contextual tags]] do not require visual presence but must have dialogue/story presence. These should '''NOT''' be tagged unless they are fairly obvious to a casual reader.
||<u>Example</u>: A woman saying the man with whom she's having sex is not her husband counts as [[cheating]].
</div>
|}

==Special Tag Types==
<div id="Gallery-Wide">
{| class="wikitable" width="100%"
!Rule
!Details
! Examples / Exceptions
|-
|'''Gallery-Wide'''||Gallery-Wide tags apply to an entire gallery. They have single page requirements to tag, but do not qualify if a single conflicting image is present.
||<u>Note</u>:

* 1 image is enough to qualify or disqualify most of these tags. Omake/covers/credits/colophons are ignored.
*Gallery-Wide tags that indicate the gender of the participants, for example [[sole female]], [[males only]], etc. allow for minimal amounts (no more than a single page) of conflicting content so long as the depicted actors are not vividly displaying sexual activity beyond nudity, and are not real or in-universe participants, e.g. being depicted in a magazine.<div id="Costume"></div><div id="Clothing"></div><div id="Clothes"></div><div id="Costumes">
|-
|'''Clothing'''||Costume tags such as [[schoolgirl uniform]] only apply if they are kept on (at least partially) during sexual activities. If they are absent or removed beforehand they should '''NOT''' be tagged.
||<u>Exceptions</u>: For non-pornographic galleries the clothing does not need to be removed in any way.<div id="Locations"></div><div id="Location"></div>
|-
|-
|'''Location'''||Location tags only apply if relevant during sexual activities. If the location is used without any sexual activity/nudity they should '''NOT''' be tagged.
||<u>Note</u>:
*For non-pornographic galleries the location tags are not applicable.<div id="Visual"></div><div id="Change"></div>
*There needs to be a sufficient amount of visual indications to confirm that the scenes take place in a certain location, before the tag in question is applicable. For example, merely wearing a swimsuit outdoors on a sunny day is '''NOT''' sufficient for the [[beach]] tag.
|-
|'''Change'''||For all (but four) change tags only the images involving the change itself are counted towards presence.||<u>Exceptions</u>:
*For [[gender change]] / [[gender morph]] the duration of the individual being a different gender also qualifies.
*For [[futanarization]], the duration of the character being a dickgirl also counts.
*For [[body swap]], post-swap images also count for presence.<div id="Animal"></div><div id="Animals">
|-
|'''Animal'''
|All animal tags require that an animal be explicitly involved in sex or nudity (e.g. [[animal on animal]], [[bestiality]]).
|<u>Example</u>: Two canines mating allows for the [[dog]] tag; a [[furry]] [[dog girl]] having sex with a human does not.<div id="Format"></div><div id="Format">
|-
|'''Format'''
|Format tags work similarly to the [[category|gallery categorization]] system. The work must overall fulfill the gallery format as specified in the respective definition for it to be applicable.
|<u>Examples</u>:
*A loose 200-pages [[western imageset]] containing 20 sequential [[comic]] pages should '''NOT''' be tagged with [[comic]].
*Some CG images within a published western release that is still predominantly utilizing panels to convey their story should still be tagged with [[comic]], but '''NOT''' [[western cg]].
|}

==[[Tagging Mechanics]]==
Tags are voted on by the users of the site as such they are subject to potential errors. Tags with <span style="border:thin solid green;">solid</span> borders have a cumulative [[mod power]] that is equal to or higher than 100 (i.e., been upvoted by many users, or by a handful of individuals with high [[mod power]]). Tags with <span style="border:thin dashed green;">dashed</span> borders mean that their cumulative [[power]] is between 10 to 99, while <span style="border:thin dotted green;">dotted</span> tags have a cumulative [[power]] between 1 to 9. <span style="color:#ff0000">'''It is important to note that the cumulative [[power]] of a tag does NOT necessarily indicate its validity.'''</span> '''Precaution must always be exercised when judging whether a tag is correct or not.''' See the [[#Forum Links|forum links]] below to report any tag misuse. Tags do not indicate to which images and to which participants they are applicable within a gallery; this information can be provided by gallery [[comments]].

==Good Tags==
;Contents/Fetishes
:As long as they are relevant sexually and pass presence. Whenever in doubt it is better not to tag them.

;Languages
:Tagged in their English equivalent (e.g. ''<span style="color:green">Spanish</span>'' not ''<span style="color:red">Espanol</span>'').

;Circles
:Names of the circles/groups that published the work. Should '''NOT''' be added when they are not officially credited (e.g. most [[Manga]]).

;Artists
:Names of the artists who drew portions of or all of the work; must be officially credited as such. Japanese artists should be written using [https://en.wikipedia.org/wiki/Hepburn_romanization Hepburn romanization]; some exceptions exist for artists that consistently spell their names otherwise.

;Cosplayers
:If the cosplayer consistently uses a name order, use that. Otherwise, follow the name order of the cosplayer's country.
<div id="originalseries"></div>
;Original Series
:Names of the series that are being parodied. Should generally be as specific as possible (e.g. ''[[Dragon Quest VIII]]'' instead of just ''[[Dragon Quest]]'') if the sub-series passes presence. A combination of images from different sub-series that passes presence (but no one sub-series passes) uses the generic series tag instead.
*The following apply:
**All canon characters within a parody
**Canon races within the parody (e.g., Khajiit from [[the elder scrolls|The Elder Scrolls]]
**Costumes styled after a parody if that parody is specifically mentioned/has some context in the work.
<div id="Character"></div><div id="Characters"></div>
*The segregation or unification of subseries is based on [[Series_Segregation#Reasoning | a number of factors]].

;Participants
:Names of characters (including [[cosplaying]]) participating in the gallery. Original characters (non-parodies) that do not exist outside of their own works should not be tagged.
*Non-pornographic works may only have the '''most focused''' characters be tagged.
* Character names are preferred in full western order; given name(s) followed by family name. e.g. ''[[hinata hyuga]]''. There are rare exceptions.
*Any character who transforms '''beyond that of a costume change''' (to the point where a casual observer cannot tell they are the same person) is to be tagged with their alias (should they have one). e.g. ''[[peashy]]'' vs. ''[[yellow heart]]''.
* A [[gender change|gender changed]] character is preferred be tagged with their regular name.
*A character with no official name may be tagged based on their relationship with another character. e.g. ''[[dexters mom]]'' from ''[[Dexter's Laboratory]]''.<sup>([https://dexterslab.wikia.com/wiki/Mom#Trivia Ref])</sup>
*Characters that share the exact same name (e.g. ''c:sakura'' from ''[[Urusei Yatsura]]'', ''[[Fire Emblem Fates]]'', etc.) can not be differentiated except by other tags such as parodies or attributes.

<div id="Category"></div><div id="Categories"></div>
===[[Gallery Categories‎|Categories]]===
[https://repo.e-hentai.org/tools/taggroup?show=1 Reclass tags] should only be used to fix an improperly categorized gallery. Once a tag receives 100 [[power]] the category will switch.
*If there are conflicting category tags, the one with the earliest "[[Tagging_Mechanics#Tag_Soft_Veto.2FEnforcement|lock-in]]" time determines the category.
**To make a new category tag take effect, the pre-existing category tag must be downvoted to at least [[Tagging_Mechanics#Tag_Mod_Power|non-solid border]].
*These tags are automatically pruned from galleries after 30 days of no voting activity.
*Please note that "reclass:asianporn" is no longer functional. See its [[asianporn|definition]] for details.

<div id="Directory"></div>

=== Tag Directory===
{{TagNav}}

== Information Sources==
The information used to tag should always be based solely on the contents of the images in the gallery itself. The gallery's title, comments, or 3rd party sites do NOT qualify as information sources in the majority of cases.

<u>Exceptions:</u>
*[[:Category:Series_Tag|Parodies]] have all of their canon counted as existing information (unless the dialogue indicates otherwise). This precludes informed attributes for visual tags (e.g. [[Lum]] from [[Urusei Yatsura]] can be tagged with [[oni]] but not with [[alien girl]]).
*If an artist's name is not present in the gallery it may be obtained from a verifiable source such as the circle's website or store listing.
*The title may be used as proof of [[incest]] (unless the dialogue indicates otherwise).
*Participants' genders being ''extremely'' vague may use a verifiable source to identify them.

==[[Know The Difference]]==
For tags that are often confused for one another.

==Bad Tags==
;Commissioners / Decensors / Scanners / Translators
:Do not produce the content.
;No Sexual Connection
:(e.g. baseball, celebrity, clouds, exercise, microphone, pillow, red eyes, sword)
;Opinionated / Pejorative
:(e.g. cute, extreme, funny, gross, hot, garbage, nice, sad, scary, terrible, ugly, weird)
;Publishers / Websites
:Do not actually produce the content. Rare exceptions apply if nothing else can be used to identify a work's creator.
;Software
:The tools the artist used to created the content are irrelevant.
;Too Common
: (e.g. anime, nymphomaniac, semen, sex, skirt, softcore, straight, upskirt, vaginal)
;Too Vague
: (e.g. areola, ass, fetish, nipples, pussy, shaved, wet)
;Writers
:Not to be confused with the artists.

== Do Not==
*Use category exclusive tags outside of their category (e.g. [[non-nude]] is only for [[Cosplay]], [[comic]] is only for [[Western]] or [[Misc]]).
*Use [[:Category:Language Tag|language tags]] for anything other than indicating a gallery's text.
*Use a language tag on [[imageset]]-style galleries unless a majority of it (50%+) contains text in that language.
*Tag [[mother]] when not in conjunction with [[incest]]. This includes women giving [[birth]], women who happen to have children, or [[milf]]s.
*Use the [[cosplay]] tag when characters in drawn works are dressed as other recognizable characters; use [[cosplaying]] instead.
*Downvote any "redundant" reclass tags (i.e. being the same as the gallery's current category).
*Downvote any tag(s) that becomes "invalid" due to the uploader attempting to remove valid content. The said gallery should be reported for a [[Expunging#Reverting_and_Splitting|reversion/spilt]] action.
**If the tag(s) remains invalid after the revert/split, they may be downvoted accordingly.
*Downvote [[Fetish_Listing#Expunging|expunging tags]] purely because an [[Expunging|expunge petition]] has not been created. The system will automatically prune them from an active gallery if they remain for longer than 30 days.
**If the expunge type is definitely not valid for the gallery, then it may be downvoted.

==== Temporary Tags ====
Upvoting these tags is generally unnecessary. Galleries may be fixed / updated which would render such tags invalid.
*[[incomplete]]
*[[missing cover]]
*[[out of order]]
*[[Expunging]] tags
<div id="Why Should I Tag?"></div>

==[[Rewards]]==
Tagging earns points towards the [[toplists]].

[[Image:Point.png]] Poor tagging will result in the user '''losing''' [[power]]. Any attempts at farming points, accuracy spoofing, or heavy misuse WILL result in a permanent [[ban]].

==Exact Tag Searching==
Searches for certain tags can return results from more tags than intended. This happens to tags that appear as partial strings inside longer tags.

<u>Example</u>: The tag ''f:wolf'' will match both [[wolf]] and [[wolf girl]]. This also impacts [[slave tag]]s; a search for ''f:anal'' may return a gallery tagged with [[sex toys]]. This happens because the search for ''anal'' matches "anal beads" which is slaved to [[sex toys]].

To avoid this users may search with a dollar sign at the end of the tag to search only for that string (e.g. ''f:wolf$'', ''f:anal$'', etc.)

==Tagging Hotkeys==
The following hotkeys can be used when a tag is selected.

{| class="wikitable" style="text-align: center;"
! rowspan="2" |Function
! colspan="4" |Hotkeys
|-
!Numpad!!Other
|-
|Show All Tagged Galleries||{{Keypress|4}}||{{Keypress|A}}
|-
|Show Tag Definition||{{Keypress|6}}||{{Keypress|D}}
|-
|Vote Up||{{Keypress|8}}||{{Keypress|W}}
|-
|Vote Down||{{Keypress|2}}||{{Keypress|S}}
|-
|Clear Selection||{{Keypress|5}}||{{Keypress|Spacebar}}
|}

==Tag Tracker==
Users may see recently added tags across all public galleries via https://repo.e-hentai.org/tools/tagtrack
*This tool is primarily for tag cleanup, including removing invalid tags and making strong valid ones.
*Tags are displayed per gallery, and show that that are:
**<span style="opacity:0.3">weak</span> (with 1-9 [[Mod Power|MP]])
**<span style="opacity:0.7">active</span> (with 10-99 MP)
**<span style="color:#0000a4">SOLID</span> (with ≥100 MP)
**<span style="color:#009b00">ENFORCED</span> (tags that were added, and were [[Tagging_Mechanics#Tag_Veto|hard enforced]])
**<span style="text-decoration:line-through; opacity:0.3">downed</span> (tags that were added, but reduced to 0 MP)
**<span style="text-decoration:line-through; opacity:0.3;color:#f00">vetoed</span> (tags that were added, but were [[Tagging_Mechanics#Tag_Veto|hard vetoed]]).
*The results may be filtered in the following ways:
**'''downed''' - Displays tags that were created and have been reduced to 0 MP without being vetoed.
**'''weak''' - Displays tags that were created and have between 1-9 MP inclusive.
**'''active''' - Displays tags that were created and have between 10-99 MP inclusive.
**'''solid''' - Displays tags that were created and have 100 MP or higher.
**'''aged galleries''' - Displays galleries that have been tagged after they are no longer considered new.
**'''revived tags''' - Displays tags that were killed, and have been revived.
**'''exclude expunged''' - Filters out expunged galleries from the list.
**'''exclude autotags''' - Filters out tags added by the system, e.g. p:[[original]], or tags added due to a [[Namespace|slaving action]], etc.
**'''Tag/NS''': Filters out all but the chosen tags, with the following formats:
***''tag'', with no namespace, e.g. [[hairy]], will search for tags in all namespaces that match it.
***''namespace:tag'', e.g. f:hairy, will search for all tags that match both the tag and namespace.
***''tagid'', will return results for only the tag that has the chosen tagid.
***''special:namespace'', e.g., special:female, will search for all tags with the chosen namespace.

==Tag History==
Users can check their own tag history (up to actions made within the last 60 days), accuracy ratings, and overall usage via this tool:

<pre<includeonly></includeonly> style="overflow: auto;{{{style|}}}">https://repo.e-hentai.org/tools/taglist?uid={USERID}</pre>
*Replace {USERID} with a userID (can be found by going to a user's profile in the [[forums]]) then checking the URL.
**Example: [https://forums.e-hentai.org/index.php?showuser=5 Snowflake] (UID: 5) would use the URL https://repo.e-hentai.org/tools/taglist?uid=5
*A &from={UNIXTIME} string may be added at the end of the above-mentioned URL. This can be used to allow users to quickly review their tagging actions made on or before the specified time.
**The date and time provided in the string must be in the Unix time format.
**Example: If Snowflake wants to review their tag actions made on or before July 2, 2026, 15:34:17 UTC, they would use the URL https://repo.e-hentai.org/tools/taglist?uid=5&from=1783016057
**A "'''Show Older >'''" button is also available at the end of the page, allowing users to continue reviewing their tagging histories dating even further back in time.
*Votes are organized by gallery. The value next to each tag indicates the amount of [[power]] utilized for that action at the time.
**A <span style="color:#008000">green</span> positive value (e.g., <span style="color:#008000">'''+69'''</span>) indicates that the user upvoted that tag in the gallery.
**Meanwhile, a <span style="color:#ff0000">red</span> negative value (e.g., <span style="color:#ff0000">'''-69'''</span>) indicates a downvote on the tag from the user.
**An <em>italicized</em> entry (e.g., ''female:nakadashi'') indicates that the user started the said tag.
*Accuracy score calculations are delayed by 3 days. Further accuracy checks take place to ensure a tag vote remains correct. '''Accuracy values are not foolproof; users should always manually review their tags.'''
**Vote entries that are highlighted in <span style="color:#ff0000">red</span> (e.g., <span style="color:#ff0000">female:nakadashi</span>) either indicate a started/upvoted tag was killed, or a downvoted tag is still alive.
**Started/Upvoted tag killed will be assessed as a "bad" vote (e.g., <span style="color:#008000">'''+69'''</span> <span style="color:#ff0000">female:nakadashi</span>) and negatively affects your accuracy.
**A downvote on tag will also be assessed as "bad" (e.g., <span style="color:#ff0000">'''-69'''</span> <span style="color:#ff0000">female:nakadashi</span>) if another user upvotes it after your downvote. Your accuracy will also be negatively impacted.
***Should the tag becomes fully downvoted later, it will be retallied and no longer classed as a "bad" vote on your record.
***For this reason, users are encouraged to use the [https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] thread to ensure that the identified invalid tags are fully downvoted.
**Users may use the "Filter galleries with assessed bad tagvotes" toggle to quickly review their tag votes that were assed as "bad" by the system.
*Accuracy scores are split by month, year, and overall total. The metrics are further separated into "Started" and "Voted" accuracies.
**Only the most recent seven monthly accuracies will be shown to the user. Yearly accuracies reflect the user's average tagging performance over the last 12 months.
**"Started" indicates accuracy for tags the user added themselves. "Voted" indicates accuracy for votes on tags already on a gallery.
**Values of less than 100 tags will only show the number of tags voted in gray without an accuracy calculation.
**"-" indicates 0 tags were voted by the user during that time period.

*[[Janitor|Tag checkers]] may check the history of any user.
**[[Image:Point.png]] Having an accuracy metric highlighted in red puts the user at high risk for a [[ban]].

==Limitations==
Users with < 2 [[power]] are unable to start tags or downvote tags.

==See also==
*[[Fetish Listing]] - A categorized list of all official fetish tags.
*[[Technical_Issues#Gallery_Tagging|Technical Issues - Gallery Tagging]]
*[[Toplists#Tagging_Toplists|Toplists - Tagging]]

==Forum Links==
*[https://forums.e-hentai.org/index.php?showtopic=274004 Tagging and Mistagging Assistance] - Please report any bad tagging here.
*[https://forums.e-hentai.org/index.php?showtopic=295953 General Tag Discussion]

{{Template:EHGNav}}

[[Category:E-Hentai Galleries]]
[[Category:Rules]]

Talk:rough translation

2026-08-02T13:06:35Z

Kagoraphobia: /* Alternate Tagging Criteria */ already is a thing for a while but just never got codified

==Whitelist==
To be added to the whitelist for "rough translation" a user needs at least:
*A mod [[power]] of 10.
*Three existing gallery [[comments]] that fulfill the tag requirements.

To be added, a user must make a post in [https://forums.e-hentai.org/index.php?showtopic=254539 this thread] linking to the comments they made. Existing whitelisted users and/or moderators will then validate that their posts are valid and constructive before they are approved. A history of non-constructive or discourteous posts beyond the submitted three may also disqualify the user from the whitelist.

The second post in the thread can be edited by a Global or Vigilante [[Janitor|Moderator]] to change the whitelist.

A user may be removed from the whitelist if they use the tag beyond its stated purpose, provide supporting comments that are not constructive or are discourteous, or tag languages not listed with their entry.

Tag [[Janitor|vetoers]] are automatically whitelisted.

==Alternate Tagging Criteria==
Rough translation may be added through the [[Making_Galleries|upload manager]] by the uploader, in such cases a comment is not required.
*The Uploader not adding the tag themselves, but indicating within the work that it is machine translated, may be tagged without a detailed comment. A comment along the lines of "Uploader marked as machine translation" will suffice for this.
**Works indicating that machine translation was used to initially translate the work, but was proofread and corrected by a proficient translator, does not qualify without the ordinary tagging criteria.
*The following methods of uploader indication apply:
**Gallery title, such as the non-standard special indicator [MTL], set by either the upload manager or through a rename petition '''started by the uploader'''.
***[[Image:Point.png]] <span style="color:red">'''[MTL] should not be added through renaming except by the uploader.'''</span> In cases where the gallery was renamed by the non-uploader to include this, rough translation would '''NOT''' qualify without a detailed comment unless any of the below also qualify. The rename attempt should also be reverted.
***Further details on the renaming process can be found [[Talk:Renaming#mtl|here]].
**Within the work, for example on a credits page.
**Uploader comment.
**For English translations, the translator clearly indicating it is a rough translation.

'''Note:''' Translators are not considered as proficient if they have regularly been proven to not be able to translate proficiently.

Rough translation may also be added when not indicated by the uploader based on the criteria below. These '''must''' have a detailed comment.
*Machine Translation/AI software being provably used without being revised by a proficient translator. This is proven by the raw image being used in said software producing the '''exact''' same result. Steps must be detailed in the comment and reproducible by anyone who would add the tag. All comments must be verified and reproduced before tagging.

Gallery Mods (i.e., [[Janitors]] with the Galleries '''Moderating''' privilege) have the discretion to add the tag when the translated work clearly appears to them as a machine/AI translation.
*Gallery mods may skip detailed comments if the justification was deemed too effortful to write, or out of concern for providing hints on potential circumventions of the tag. A brief comment, such as "tagging obviously rtl", may instead be substituted.
*Whitelisted users or tag vetoers are '''NOT''' given the discretion to enforce the tag in such a manner.
*For inquiries about a specific judgment call, users may contact the said gallery moderator directly or ask in the [https://forums.e-hentai.org/index.php?showtopic=254552 Translations Evaluation] thread.

E-Hentai Janitor

2026-08-02T13:05:52Z

Kagoraphobia: /* Explanations */

Certain members have been given special abilities or access to restricted tools due to their expertise and/or historic diligence and willingness to help make E-Hentai a better place.

Tag vetoers will be classed as "inactive" under [[Talk:E-Hentai Janitor| certain conditions]]. These users are indicated with a gray <span style="opacity:0.3">✔</span>.

Removal of janitor role(s) is generally done due to extended inactivity or by own request. Re-assignment is possible should the user return from inactivity.

{| class="wikitable sortable" width="100%" style="text-align: center"
! rowspan="2" |Name
! rowspan="2" width="12%" |[[Forum]] Mod
! rowspan="2" |[[IRC]] Op
! rowspan="2" |[[EHWiki]] Admin
! colspan="3" |[[Tagging]]
! colspan="2" |[[namespace|Namespacer]]
! colspan="4" |[[Galleries]]
! rowspan="2" |Additional
|-
! width="6.5%" |Cleaning!!Vetoing!!Checking
! width="6.5%" |Approving!!Grouping
! width="6.5%" |Expunging!!Locking!!Moderating!!Banning
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4791588 -Lumina-]|| || || ||✔|| || || ✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=243587 Binglo]|| || ||✔||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔ ||✔||✔ || ||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3201420 Byza]||<span title="The Vigilante" style="border-bottom:1px dotted">Section</span>|| || ||✔||✔||✔||✔||✔
| ✔||✔||✔ || ||ES-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=359756 chriseras]|| || ✔|| || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1207129 Cipher-kun]|| || || ||✔ ||✔|| ✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1908893 Dnkz]|| || || ||✔||✔||✔||✔||
|✔||✔||✔|| ||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2115725 Eboshi]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔ ||✔|| ||KR-EN<br>JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2790 elgringo]|| ||✔|| ||✔||<span style="opacity:0.3">✔</span>||✔|| ✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=367313 ericeric91]||<span title="General Chat" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| || || || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=384226 EsotericSatire]||<span title="Discussion Forums (Hobbies)" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=6011981 Feftak]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3737344 Glovelove.]|| || || ||✔|| || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4850902 Kagoraphobia]||Global||✔||✔||✔|| ✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge<br>CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7508384 krvn64]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=5313759 lurphysmaw]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=560909 Mags_]|| || || || || || || ||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=589675 Maximum_Joe]|| || || || || || || ||
| || || || ||''<span title="Thank you for everything you have done for the site. Rest in peace, Joe." style="border-bottom:1px dotted">Retired</span>''
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=204246 meow_pao]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1898816 Mrsuperhappy]||Global|| || ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3655031 Muffinlemon]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3169265 nasu]||<span title="The Vigilante, Site Discussion & Helpdesk" style="border-bottom:1px dotted">Section</span>
| || ||✔||✔||✔||✔||✔
|✔||✔||✔|| ||Rename Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=867559 Nezu]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2977124 Noni]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>||✔|| || || ||✔||✔||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=600260 noones]|| || || || || || ||✔||
|✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=892479 peterson123]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3139892 poiuytrewqazx]|| || || ||✔|| || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=958849 rinruririn]||<span title="The Vigilante, Site Discussion & Helpdesk, Requests and Bounties" style="border-bottom:1px dotted">Section</span>
| || ||✔|| || || ||
| || || || || JP-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=242621 rizelbr]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1913944 Rogabute]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=989173 Shank]||Global||✔||✔||✔||✔||✔||✔||✔
|✔||✔||✔||✔||Tag Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2714686 shiluo]|| || || ||✔ || || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1732804 simplesimon32]|| ||✔|| ||✔|| || || ||
| ||✔|| || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=352564 SIRIUSs]||<span title="The HentaiVerse" style="border-bottom:1px dotted">Section</span>|| || || || || || ||
| || || || ||CN-EN
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=825505 somerandomdude33]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=2203 Spectre]||Global|| ✔|| ||✔||<span style="opacity:0.3">✔</span>||✔|| ||
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=976341 svines85]|| || || ||✔||✔|| || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=4842635 terry]||Global|| || ||✔||✔||✔||✔||✔
|✔||✔||✔||✔||QC Judge
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=582527 TheGreyPanther]|| || || ||✔||<span style="opacity:0.3">✔</span>||✔||✔||✔
|✔||✔||✔|| ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=1194701 tobeunforgiven2]|| || || ||✔|| || || ||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=3172187 Waitugreat]|| || || || || || || ||
| ✔|| || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=7752125 流萤啾啾]|| || || || || || ||✔||
| || || || ||
|-
| align="left" |[https://forums.e-hentai.org/index.php?showuser=374857 海想列車]|| || || ||✔|| || || ||
| || || || ||
|}

==Explanations==
Some janitor roles come with implicit permission(s), which may be seen [[Talk:E-Hentai_Janitor|here]].
{| class="wikitable"
!Position
!Capabilities
|-
|Forum Mod||Edit or delete [[forum]] posts. Global Mods can impose posting restrictions on accounts with severe [[forum rules]] violations.
|-
|IRC Op ||Kick or ban users from the [[IRC]] channel.
|-
|EHWiki Admin ||Manage wiki editing permissions. Can also edit pages that are marked as protected.
|-
|Tag '''Cleaning'''||Users with this privilege are able to:
*Downvote tags at full [[power]].
* Bypass the minimum MP requirement for downvoting locked-in solid tags.
*Cancel out implied language tags from the uploader [[Making_Galleries#Uploading|language setting]] with a -100 [[power]] downvote.
*Have elevated voting power (3 votes) in [https://forums.e-hentai.org/index.php?showforum=89 tag suggestions].
|-
|Tag '''Vetoing'''||These users are given additional tagging privileges:
*[[Tagging_Mechanics#Tag_Veto|Veto/Enforce]] tags on a gallery, preventing them from being resurrected or killed respectively.
* Bypass the minimum MP requirement for reviving downvoted tags.
*Vote against incorrectly vetoed/enforced tags.
*Bypass the MP requirement of [[:Category:Power_Restricted|power-restricted]] tags.
*Bypass whitelists for certain special tags (e.g., [[rough translation]]).
*Instantly remove [[rough translation]] tags added by autotagger.
*Create temp tags even without meeting the [[power|power requirement]] (i.e., 25).
*Participate in the [https://forums.e-hentai.org/index.php?showtopic=136551 community veto] process presuming the user is an [[Talk:E-Hentai_Janitor| active tag vetoer]].
|-
|Tag '''Checking'''||View any user's or gallery's [[Gallery_Tagging#Tag_History|tag histories]].
|-
|Namespacer - '''Approving'''||Approve, rename, and set [[namespace]]s on the pending tags from the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Namespacer - '''Grouping'''||[[slave tag|Group tags]], as well as set blocks, [[namespace]]s, and aliases on any existing tags. Can also reject pending tags on the [[Tag Creation#Tag Approval Tracker|tag approval tracker]].
|-
|Galleries '''Expunging'''
|Start an [[expunge]] on a gallery that has previously been de-expunged by the community or administration. Can also file an [[Expunging#Appeal_an_Incorrect_Expunge|appeal]] on aged expunges.
|-
|Galleries '''Locking'''|| Lock galleries with any depictions of real children, or other illicit content (e.g., real-life snuff and gore).
|-
|Galleries '''Moderating'''||Moderators with the following gallery privileges:
*Receive a base [[power]] boost of +10.
* Block further [[Making_Galleries#Updating|updates]] on galleries that are excessively bumped.
* Delete malicious [[EHTracker#Expunges|torrents]].
*Both [[comment]] and vote on other comments in the same gallery.
*Permanently hide gallery comments with a downvote, assuming they have reached -100 [[power]].
*Review recently posted comments that have been [[Gallery_Commenting#Perma-Hidden_Comments|permanently hidden]].
*Check the original ownership of a [[disowned]] gallery.
*Enforce the [[AI Generated]] indicator when it is falsely denied by the uploader.
*Add [[rough translation]] without a detailed comment when the work is [[Talk:rough translation|clearly a machine/AI translation]].
|-
|Galleries '''Banning'''||Restrict users from performing certain gallery activities due to major site rule violations (e.g., spamming). All [[Bans|ban]] actions will be reviewed by the administration.
|-
|Tag Judge ||Make judgement calls on [[Fetish_Listing|fetish/content tags]].
|-
|<span title="Quality Control" style="border-bottom:1px dotted">QC</span> Judge||Make judgement calls on [[Expunging#Superior_Versions|gallery superiority]].
|-
|Rename Judge||Make judgement calls on [[renaming]].
|-
|JP-EN||Heightened trust in Japanese-English translations/transliterations.<br>Similar positions exist for other languages (CN-EN, ES-EN, KR-EN).
|}

[[Category:Users]]

Talk:Renaming

2026-08-01T22:23:50Z

Kagoraphobia: /* Bottom Priority */ missed this one, no longer allowed at all

==Notes==
*For re-printings of [[tankoubon]]s use the printing number as an indicator at the end; e.g. [8han] / [8版].
*For re-printings of [[doujinshi]] without a convention use the date as an indicator at the end; e.g. [2009-10-19] / [2009年10月19日].
*Multiple titled stories (e.g. as released by a translator) and multiple translators are connected via a plus sign; e.g. [Team Koinaka + CrowKarasu].
*Always use titles provided by translators even if they are wrong.
*The [[ai generated | [AI Generated] / [AI生成]]] special indicator should only be added on galleries which are clearly AI generated, where the AI images are present in at least half of the gallery, unless specifically denied by the uploader in the title, uploader comment, within the work, or on the credits page of the uploader/group. Specific cases may be discussed [https://forums.e-hentai.org/index.php?showtopic=265497 here].
*<div id="mtl"></div>The [MTL] indicator may be added by the uploader (or by a rename petition started by the uploader) when they wish to mark their work as a machine translation and should not be removed. This is primarily used as supporting evidence for the [[rough translation]] tag.
**It should be placed after the translator name/group if applicable, and before any official special indicators. e.g. [English] [Translators] [MTL] [Digital]
**If the machine translation status was declared in the title, but the uploader used a different wording from the suggested [MTL] format, the uploader's wording should remain intact.
***Example: "(C69) guyacircle, drawn by guya, Haachama Hot Tits!!! digit release (GuyaMachineTL)" should only be standardized to "[guyacircle (guya)] Haachama Hot Tits!!! [Chinese] [GuyaMachineTL] [Digital]"
***If the MTL wording in the R and J fields conflicts, and both clearly indicate that the work was machine-translated, use the wording provided by the uploader in the J field.
**[[Image:Point.png]] <span style="color:red"> '''[MTL] or equivalent should NOT be added when not present unless it is started by a vote from the gallery uploader.'''</span>

==Conventions==
*COMITIA is a convention for original, non-parody [[doujinshi]] only.
*Fancy Frontier is a predominantly [[Chinese]] original convention; [中国翻訳] should generally not be used therein unless the work can be confirmed to be [[translated]] from a non-Chinese version.

==Parodies==
*Popular stylizations of parody names are permitted if they are a slave [[tag]]; e.g. [https://repo.e-hentai.org/tools/taggroup?mastertag=12857 The Idolm@ster], [https://repo.e-hentai.org/tools/taggroup?mastertag=18411 Super Mario Bros.]
* The (Various) indicator does not require the parodies pass [[presence]] but does ignore minor instances such as omake.

==Common Symbols==
、「」・ ☆★♥♡❤！？。．ー～【】…♂♀

==Magazine vs. Anthology==
Stand-alone publishings should have the anthology indicator in their name while serial magazines should not. The [[anthology]] [[tag]] is used in all cases because of simplicity.

A '''serial magazine''' is a collection of works from multiple authors that follow a regular release schedule (monthly, bimonthly, or quarterly). Schedule changes are announced in advance. It is usually possible to subscribe to serial magazines and have them delivered directly home. A '''stand-alone magazine''' is a collection of works from multiple authors that are usually published without a regular release schedule, although some publications may also be regular for a time. A stand-alone magazine publishing is essentially just another manga publishing, containing the works of different authors.

To properly identify a magazine or an anthology can be done via its Japanese Article Number (JAN). The JAN contains a magazine code (雑誌コード) which uniquely identifies what type of publication it is followed by a publication number or date. This code should be located on the lower left corner of the magazine's cover. It either looks like '''雑誌 xxxxx-xx/xx''' or '''雑誌 xxxxx-x'''. Stand-alone publishings do not have this magazine code but may still have a regular ISBN or 2-column JAN.

The magazine code can be read as "ABBBC":
*A - Issue form code
**0, 1: Monthly, bimonthly or quarterly publication.
**2, 3: Weekly, every 10 days or biweekly publication.
**4, 5: Comic magazine (tankoubon).
**6: Mook (similar to magazines, but intended for a longer release cycle).
**7-9: Not relevant.
*B - Magazine name code
**Uniquely identifies the magazine.
*C - Identifier for extraordinary issues
**When the issue form code is 0 or 1 (monthly magazine)
***1: Regular issue.
***0: Extraordinary issue.
**When the issue form code is 2 or 3 (weekly magazine)
***1-5: Issued week.
***6-9: Extraordinary issue.

Longer versions may appear as 13-digit ''Common Magazine Codes'' (publications between 1986-2004), also known as T-codes for its leading T, or 18-digit ''Periodical Publication Codes'' (publications after 1 June 2004).
*Common Magazine Codes before December 1991 follow the pattern "AAABBBBBCCDDE" and after December 1991 "AABBBBBCCDDDE". B refers to the magazine code above.
*Periodical Publication Codes follow the pattern "AAABCCCCCDDEF - GHHHH". C refers to the magazine code above.

These codes are often omitted with old scans and the advent of digital publishing. Research will then have to be done to classify a magazine properly. Some publishings may even switch from being a serial magazine to stand-alone and vice-versa, making it harder to generalize a whole series as one or the other.

'''If you can't be sure, ask or leave it to the experts.'''

==Priority==
In general it is recommended to maximize the use of a rename petition as much as possible. Re-renaming takes increasing amounts of [[mod power]] and communication.

===High Priority===
''These are always accepted even if only 1 is being made.''

*Adding missing information such as translators, conventions, special indicators, etc.
**Adding whatever was censored by a maru in the '''R''' field
*Fixing/removing incorrect information
**Fixing misspellings (not counting spacing and punctuation)
**Fixing chapter count
**Removing convention indicators for digital releases
*Fixing full-width or Unicode variants of Latin characters to their ASCII representations of said characters in the '''R''' field; Ｎｕｄｅ -> Nude or 𝐅𝐮𝐞 > Fue.
*Changing a [[rewrite]] to its unique formatting; [Touma Ran] Bust Jack [English] [Fraction] -> Bust Jack [English] [Rewrite] [Fraction]

===Low Priority===
''These are not needed but are welcomed if done during more than 1 change.''

*Fixing J conventions; (CR30) -> (Cレヴォ30)
*Fixing multiple spaces or punctuation
*Fixing parodies to match the [[tag]] or full romanized name; (Evangelion) -> (Neon Genesis Evangelion)
**(Touhou) -> (Touhou Project) / (東方) -> (東方Project)
*Adding the [Incomplete] indicator if the [[tag]] is already present
*Removing extraneous information; (Complete) / (同人誌) / (エロ) / (Non-H) / (Original) / (Japanese) / etc.
*Changing 4+ creator names into (Various)
*Fixing the romanization of kanji representing numbers; 六 = Six -> Roku
*Replacing an individual translator's name with the group's name

===Bottom Priority===
''These should not be done unless done alongside a higher priority change.''

*'''Any other change that does not impact the [[search]] engine.'''
*Removing leading zeroes; COMIC1☆04 -> COMIC1☆4
*Fixing capitalization; ch. 2 -> Ch. 2
*Fixing spacing or punctuation on any non-title portion; Vol.2 -> Vol. 2
**Changing commas or curly braces
*Expanding truncated language indicators; [ENG] -> [English]
*Removing languages not in their English name; [German/Deutsch] -> [German]
*Changing a '''J''' chapter indication from 章 to 話
*Adding missing symbols to the '''J''' field
*Changing Roman numerals to Hindu–Arabic or vice-versa; VIII <-> 8
*Changing the convention indicator コミトレ -> こみトレ
*Adding a redundant name when the sole artist and sole circle match; [Kaishaku] -> [Kaishaku (Kaishaku)]
*Changing any existing を romanizations from wo -> o
*Adding spaces in the '''J''' field ; タイトル。[DL版] -> タイトル。 [DL版]

===Never Change===
''These should never be done as they have no impact or merit.''

*Changing a [[parody]] to beyond its [[tag]]; (Sailor Moon) -> (Bishoujo Senshi Sailor Moon)
**(Infinite Stratos) -> (IS <Infinite Stratos>)
**(とらぶる) -> (To LOVEる -とらぶる-)
**(ナルト) -> (NARUTO -ナルト-)
**(咲) -> (咲-Saki-)
*Changing a '''J''' [[parody]] name to stylized English; (フェイト/ステイナイト) -> (Fate/stay night)
*Adding information to [[rewrite]]s beyond the unique formatting
**Adding/fixing the Japanese field for a [[rewrite]] (unless it erroneously indicated a translation)
*Adding [Out of Order] or other non-standard special indicators
*Changing the order of parodies/artists/circles

==Chinese Groups==
*(枫色汉化) or [枫色汉化组] or NERV logo = [Maplecolor]
*Snowman logo = [YUKI飛雪之城] = 飞雪汉化组
*烏龍派出所
*[moesola 萌の空漢化社合集]
*bbs.dmacgn.com [冥月汉化组]
*moe.hk [萌會漢化組]
*[Genesis漢化]
*[sa768019]
*[moeheart 萌の羽翼汉化组]
*[绯色汉化组]
*[52H里漫画组]
*[天月NTR汉化组]
*[L.S.同漫汉化组]
*[萌文化研究会汉化] Galnote
*[XW舞舞]
*[2DJGAME汉化]
*[破缩卵同好会] hins
*[指○奶茶步兵團]
*[sos117]
*[沒人漢化] nobodykkk
*[JJ.Club] old: [JJ動漫社]
*[Cheria~☆汉化]
*[darkstarrd汉化]
*[FS@IE]
*[天狼星汉化]
*[UB-001汉化]
*[萌の空漢化社]
*[final個人漢化]
*[SUN汉化]
*[屑月星辰汉化组] SHK
*[K3漢化] * logo 3 Kings (poker)
*[著色中文版]
*[清純突破漢化] Innocent Breakout
*[嗒呢小姐汉化] tani
*[final個人漢化]
*[星咏汉化]
*[RS漢化]
*[次元汉化组]
*[lzmcsa個人漢化]
*[lostmoon 神风汉化组]
*[午後茶会] Cosplay Swimsuit Waitress
*[萌の羽翼漢化組]
*[悠月工房]

==Korean Groups==
'''Editing''': 역식자, 식자
<br>'''Translating''': 역자, 역, 번역

*볼켄
*체리펀치
*달려있어
*에보커
*개인번역본
*고갤롬
*거인
*이비의
*후코코모리
*이스카 (ISUKA)
*정상인
*중심구멍
*꽂}
*KOREAN-LIBRARY
*LIMITE
*미쿠다요
*모에로나
*무코우
*나키우사기
*닐게미
*누구게
*Project H
*포르노키위 (Porno Kiwi)
*푸리매
*푸슈치
*소로타
*써무손잡고와
*팀 ALONE
*Team 아키바
*팀 하누
*Team Human Trash
*팀 에찌
*Team LTG
*팀 면갤
*팀 남성부
*여우별

Template:NewTags

2026-07-30T23:31:58Z

Kagoraphobia:

*[[textless narrative]]<small><sup>'''C'''</sup></small> (tag rename; was called [[speechless]])
*[[gender change]]/[[gender morph]]<small><sup>'''C'''</sup></small> (Clarification)
*[[focus handjob]]<small><sup>'''N'''</sup></small>
*[[hippo boy]]/[[hippo girl]]<small><sup>'''N'''</sup></small>
*[[animated]]<small><sup>'''C'''</sup></small>
*[[mushroom girl]]/[[mushroom boy]]<small><sup>'''N'''</sup></small>
*[[hanging]]<small><sup>'''C'''</sup></small>
*[[suspended]]<small><sup>'''N'''</sup></small>
*[[hidden toy]]<small><sup>'''N'''</sup></small>
*[[sauna]]<small><sup>'''N'''</sup></small>
[[Category:E-Hentai Galleries]]