!日本語の説明は下部にあります!
This model detects NSFW areas (segments) in anime images. One model supports multiple types of detection.
Detectable Regions: nipples, pussy, anus, penis, testicles, x-ray, cross-section
Recommended Threshold: 0.5 ~ 0.8
Base Model: yolov11s-seg.pt
🗂️Install Location
Stable Diffusion WebUI/reForge -> models/adetailer
ComfyUI -> models/ultralytics/segm
❓FAQ
How to Deal with the Issue of Detected Areas Being Replaced by Another Object
If the detailer prompt is empty, enter the target prompt.
For example, if a nipples is being replaced with pussy, enter "nipples" in the prompt.
Lower the denoise value.
Expand the inpainting region.
WebUI (ADetailer): Increase "Mask erosion (-) / dilation (+)"
If "Inpaint only masked" is enabled, increase "Inpaint only masked padding, pixels"
ComfyUI (SEGS): Increase "crop_factor"
Troubleshooting “UltralyticsDetectorProvider Weights only load failed…” in ComfyUI
⚠️This workaround is required for v4 and earlier
Install the latest ComfyUI-Impact-Subpack and restart ComfyUI.
Open the file
<COMFYUI_INSTALL_PATH>\user\default\ComfyUI-Impact-Subpack\model-whitelist.txtin a text editor (e.g. Notepad).Add the following line to the end of the file, then save:
ntd11_anime_nsfw_segm_v4_all.pt
ntd11_anime_nsfw_segm_v4_anus.pt
ntd11_anime_nsfw_segm_v4_cross-section.pt
ntd11_anime_nsfw_segm_v4_nipples.pt
ntd11_anime_nsfw_segm_v4_penis.pt
ntd11_anime_nsfw_segm_v4_pussy.pt
ntd11_anime_nsfw_segm_v4_testicles.pt
ntd11_anime_nsfw_segm_v4_x-ray.ptRestart ComfyUI.
References
ComfyUI-Impact-Subpack README, Pull request
📄Note
ComfyUI allows you to filter detection class while using the "All" model.
Trained on images generated by Illustrious/noob derived models such as WAI-NSFW-illustrious-SDXL, Hassaku XL (Illustrious), Raehoshi illust XL, paruparu
Cannot be detected in monochrome images or comics
Cannot be detected in realistic images
⚙Training Settings (v5)
task="segment"
epochs=200
lr0=0.02
lrf=0.05
seed=0
imgsz=1024
batch=-1
close_mosaic=0
mosaic=0.0
erasing=0.0
scale=0.0For description of each setting, see: https://docs.ultralytics.com/modes/train/#train-settings
📢Past Announcements
Announcement for Stable Diffusion WebUI / reForge Users (2025/06/27)
I have an announcement for those using Stable Diffusion WebUI or reForge.
If you’re interested, please check out the details below—and I’d really appreciate any feedback or bug reports you may have!
When using my detection model with Stable Diffusion WebUI or reForge, the typical approach is to use it with the ADetailer extension.
While ADetailer offers many features, a few key functions were missing for making full use of my model.
To address that, I forked the original ADetailer and added the following features:
Class name filter: You can now filter detection results by specific class names
Class-specific prompts support: You can assign different prompts for each detected class using the
[CLASS=name]syntaxBounding box mask option: You can choose to use the bounding box as the mask for segmentation models, instead of the segmentation mask itself
You can find the repository here: https://github.com/newtextdoc1111/adetailer
Please see the README for installation instructions and more details on the new features.
My hope is that with class filtering, there will be no need to use anything other than the “ALL” model, and that the [CLASS=name] syntax will help reduce cases where unintended objects are drawn during inpainting.
Honestly, not having to train individual models for each release in the future would be a huge relief—this is one of the main reasons I implemented these changes 😂
If you’re someone who would still prefer to have individual models in future releases, feel free to share your specific use case. I may be able to offer an alternative solution (ComfyUI users are welcome too!).
アニメ画像のNSFW領域(セグメント)を検出するモデルです。一つのモデルで複数種類の検出に対応しています。
検出可能な領域: nipples, pussy, anus, penis, testicles, x-ray, cross-section
推奨閾値: 0.5 ~ 0.8
ベースモデル: yolov11s-seg.pt
🗂️インストール場所
Stable Diffusion WebUI/reForge -> models/adetailer
ComfyUI -> models/ultralytics/segm
❓FAQ
検出された領域が別のオブジェクトに描き換えられてしまう問題の対処法について
Detailer用プロンプトが空の場合、対象のプロンプトを入力する
nipplesがpussyに描き変わる場合、プロンプトに"nipples"と入力する
Denoseを下げる
インペイント領域を拡張する
WebUI (ADetailer): "Mask erosion (-) / dilation (+)" を増やす
ComfyUI (SEGS): "crop_factor" を増やす
ComfyUIで生成実行時に「UltralyticsDetectorProvider Weights only load failed. ...」と表示される問題の対処法について
⚠️v4以前のモデルで必要な対処法です
最新の ComfyUI-Impact-Subpack をインストールし、ComfyUIを再起動
<COMFYUIインストールパス>\user\default\ComfyUI-Impact-Subpack\model-whitelist.txtが作成されているので、メモ帳などで開く以下のテキストを追記して保存する
ntd11_anime_nsfw_segm_v4_all.pt
ntd11_anime_nsfw_segm_v4_anus.pt
ntd11_anime_nsfw_segm_v4_cross-section.pt
ntd11_anime_nsfw_segm_v4_nipples.pt
ntd11_anime_nsfw_segm_v4_penis.pt
ntd11_anime_nsfw_segm_v4_pussy.pt
ntd11_anime_nsfw_segm_v4_testicles.pt
ntd11_anime_nsfw_segm_v4_x-ray.ptComfyUIを再起動する
参考資料
📄メモ
ComfyUIの場合、"All" モデルを使いつつ検出したい種類をフィルタリング可能です
WAI-NSFW-illustrious-SDXL, Hassaku XL (Illustrious), Raehoshi illust XL, paruparu等のIllustrious/noob派生モデルで生成した画像で学習しています
モノクロ画像やコミックでは検出できません
リアル調の画像では検出できません
⚙学習設定 (v5)
task="segment"
epochs=200
lr0=0.02
lrf=0.05
seed=0
imgsz=1024
batch=-1
close_mosaic=0
mosaic=0.0
erasing=0.0
scale=0.0各設定の説明についてはこちら: https://docs.ultralytics.com/modes/train/#train-settings
📢過去のお知らせ
Stable Diffusion WebUI / reForge をお使いの方へのお知らせ(2025/06/27)
Stable Diffusion WebUI / reForge をお使いの方にお知らせがあります。
気になった方は以下の内容を確認し、感想や不具合の報告を頂けると嬉しいです!
Stable Diffusion WebUI / reForge (以下WebUIに統一)で私の検出モデルを利用する場合、ADetailerの拡張機能を使う方法が一般的です。
ADetailerは多くの機能がありますが、私の検出モデルを便利に活用するための機能がいくつか不足していました。
そこで、元のADetailerをフォークし以下の機能を追加しました。
クラスフィルター:検出したい対象をクラス名でフィルタリングする機能
クラス毎のプロンプト指定:
[CLASS=name]の構文で検出したクラス毎に個別のプロンプトを指定する機能バウンディングマスクオプション:セグメント検出モデルでもバウディングボックス形状でマスクを生成するためのオプション
リポジトリは https://github.com/newtextdoc1111/adetailer にあります。追加機能の詳細とインストール方法はREADMEを確認してください。
私の想定では、クラスフィルターがあれば「ALL」モデル以外不要になり、 [CLASS=name] 構文で適切なプロンプトを与えればインペイント後に別のオブジェクトが描画される事故も減るはずです。
特に、今後のリリースで複数のモデルファイルを学習しなくて済むと本当に助かります。このために実装したと言っても過言ではありません😂
今後のリリースでも個別モデルを残してもらいたい、と考えている方は具体的なユースケースを教えてもらえれば別の解決策を提案できるかもしれません。(ComfyUIユーザーの方からでも大丈夫です)。
Description
Detection rate of penis and testicles during foreplay has improved.
Notes:
Added 200 images mainly of foreplay scenes for training (900 images in total!).
Regarding detection rates for other regions, I think increasing the dataset will slightly reduce false positives.
If you have the v3.0beta model installed, it will be overwritten. Newer versions offer improved detection accuracy, but if you're concerned, please rename or move the existing model to a different folder beforehand.
---
前戯中の陰茎と睾丸検出率が向上しました
メモ:
前戯中のシーンをメインに200枚の画像を追加して学習しました(全画像数は900枚!)
それ以外の項目の検出率について、データセットを増やした事で誤検出が若干減ると思います
v3.0betaのモデルをインストールしている場合は上書きされます。新しいバージョンは検出率が向上していますが、気になる方は事前にリネームか別フォルダーに移動させてください
FAQ
Comments (30)
Havent tried v3 because v2 is working for my needs more than enough. But if you are going to make more my one request would be to combine testicle and penis models together in an individual version if possible. Either seperate detection in a single model just for those 2 or one trained in both of those 2 together whole package that detects both areas as "penis". Thanks for the updates regardless, this is gold o7
Thank you for your feedback and thoughts! I always welcome positive and constructive comments like yours.
That said, I’m sorry but I don’t have plans to create models with combinations other than the “ALL” version.
The reason is that having too many combinations would increase the release workload and make future updates and management more difficult.
I’ll continue working on improving detection accuracy, so feel free to let me know if you have any other questions.
@newtextdoc11996 Other than this no, didnt encounter many issues personally. sometimes pussy detection is hit and miss from side angles but i have the detection pretty high to be safe and prevent false positives so thats probably on me. this one has the best penis detection among adetailers on the site good stuff.
Oh maybe anus detection. It only detects upper quarter in anal pictures. idk if even worth mentioning but thats all i can think of
@Wizzi Thank you for your reply.
The next update is planned to improve the detection rates for cross-section and x-ray, but I will also try to increase dataset for the compositions you suggested.
@newtextdoc11996 played around more with v3. thanks for the update a lot of stuff is better now. Only thing i want to ask is if it is intentional for nipple detection to detect see-through or not. Personally i would prefer if it didnt detect see-through nipples AT ALL but currently it is almost always half detecting one while not detecting the other in even relatively low detection rate like 0.5. One thing that might be good to keep in mind if there will be any future updates.
@Wizzi Glad to hear it's working better for you!
> Only thing I want to ask is if it is intentional for nipple detection to detect see-through or not.
Yes, the detection is intentional. The low detection rate is due to the limited number of see-through samples in the dataset.
Also, improving the detection rate for see-through nipples was planned for a future update.
If you don’t mind, could you share why you prefer not to detect them?
@newtextdoc11996 i am using a nipple LORA and i dont want to erase it everytime for see-through, that LORA ruins the see-through look when it detects it. idk if you can seperate it on comfyui but you cant on A1111 and forge.its a personal thing tho would understand if that doesnt matter for your use and purposes.
@Wizzi I see, thank you for your reply.
It's interesting to hear that you're using a dedicated LoRA for specific body parts—that's very helpful to know.
Currently, my approach is focused on improving the overall detection rate, including see-through cases. So I hope you can understand that some extra adjustments might be necessary for your specific use case.
From a technical standpoint, it's always possible to exclude see-through detection, so depending on feedback from other users, I may reconsider the direction in the future. If that happens, I’ll be sure to let you know.
@newtextdoc11996 i think biggest benefit to adetailers is ability to use specific style prompts and loras for body parts. for nipples there are lots of good LORAs on the site i would recommend you to try. Difference in quality is insane. Same with penis, a lot of models are not good at making good looking ones so loras help there too.
This nipple LORA is amazing, would rec you to try:
https://civitai.com/models/827482/illustrious-xl-nipple-lora-for-adetailer-adetailerlora
@newtextdoc11996hi its me again. v4 feedback here. Did 100~ tries with v4 so far and only problem i noticed is nipple recognition from above angle. its become better with sideboob angle and underboob angle but in poses woman is kneeling when looked at from above or when she is for instance on all fours with breasts hanging, recognition is pretty inconsistent.
@Wizzi Hi! Thanks for the quick review—your feedback is always helpful.
> but in poses woman is kneeling when looked at from above or when she is for instance on all fours with breasts hanging, recognition is pretty inconsistent.
I didn’t include many images with that kind of composition in the dataset.
To confirm, are you referring to a composition like the one you posted on Civitai about 10 days ago?
I downloaded the image and checked it, and you're right—the model didn’t detect it properly.
By the way, I also tested with an image using the following prompt, and it was able to detect nipples as long as they weren't heavily obscured by arms or other elements.
The model I used was WAI-NSFW-Illu v14:
1girl, from above, all fours, nude, large breasts, sagging breasts, nipples
@newtextdoc11996
>To confirm, are you referring to a composition like the one you posted on Civitai about 10 days ago?
yes that kind of pose. I think there is a % threshold for poses like that where you do not see the bottom half of the nipples and if you do not see enough of that percentage it doesnt recognize. Because noticed similar issue with poses where girl is lifting breasts thus blocking some part of the nipple/areola even if angle is different. Idk if adding more stuff to the dataset where nipples interact with fingers or from different angles is enough to solve or not but thats that.
This nipple adetailer for instance is pretty good at those angles but its much worse at side angles and false detections instead:
https://civitai.com/models/490259/adetailer-nipples-model
@Wizzi I see, thank you for the detailed information.
Adding around 10 to 20 images with similar compositions and actions to the dataset should improve detection rates.
Since the images I generate myself tend to have some bias, your feedback on detection performance is extremely helpful.
I'm planning to increase the variation in the dataset for the next release, so if you notice anything else, feel free to leave a comment.
@newtextdoc11996 have you tried penis adetailer with curved penis? i've done around 5 with curved penis so far and it kinda didnt detect the middle part of the penis in 2 of those, didnt detect the shaft in 1. But yes for nipple model, if a finger or something else touches areola a little bit it completely ruins the detection.
@newtextdoc11996 heeeey its me again.......today i noticed another thing. when bouncing breasts in motion it doesnt detect parts of it, usually the middle of the nipple.....Posting it as a picture, will delete once you see to not clog up example pics
@Wizzi Thanks a lot for the enthusiastic feedback!
Curved penises, partially covered areolas, and bouncing breasts in motion are either not included in the dataset or only appear in very small numbers 😓
I'll try generating some sample images myself when I have time, so if you're willing, it would be really helpful if you could share the specific prompts and (publicly available) models you used.
> Posting it as a picture, will delete once you see to not clog up example pics.
I checked both the model gallery and your profile, but I couldn’t find any images that match the description. Is it unpublished or maybe still in draft?
If possible, please send me a direct link.
Feel free to leave comments anytime if you notice anything else. I keep notes of all feedback and make sure to test them properly when I have the time.
@newtextdoc11996 posted it under this page.Idk if specific examples will help you much really. Since it is not 100% guaranteed to not work. Sometimes if registers sometimes it doesnt. Tags i noticed these issues with are "Curved Penis,huge penis " "bouncing breasts,unaligned breasts,motion lines,motion blur", "breast lift,grabbing own breast,deep skin,breasts squeezed together" and sometimes if lactation is too severe with "excessive lactation" prompt.
@Wizzi Hmm, it looks like I still can't see the image.
I double-checked my visibility filters, but everything is set to show all content.
In any case, thank you for the tag information. Most of the tags you mentioned weren't really included in the dataset.
Up until now, the datasets I’ve added were mostly focused on foreplay and intercourse, so I think I’ll need to add more compositions that focus specifically on breasts or genitals going forward.
If you’re open to it, I’d love to show you some sample images when I start preparing the next version—just to check if they resemble the ones that weren’t detected properly.
That said, I haven’t decided exactly when I’ll start the next round of work.
Lastly, thank you again for taking the time to provide such detailed feedback!
yeah idk why but seems like civitai is blocking the pictures cuz it doesnt think they are AI generated lol. But yeah i think you just need more pictures where something is interacting with areola and nipples in the dataset. poking nipples with fingers and penis, covering half/quarter of the nipples from below with hands or clothes and penis or nipples in motion or in different shapes/states(i think there are issues with flaccid penises too depending on the size)
Made a seperate stanalone gradio with these models (V2) working great but missing some close or small area , i will try v3 . thanks for these models
Also i was wondering how these models can be trained ? Any tutorial ref link?
@MeloChan Glad to hear you're enjoying the models!
> these models (V2) working great but missing some close or small area
Could you let me know which specific areas you're referring to? If you don’t mind sharing an example image or the model and prompt you used, that might help identify the cause.
> Also i was wondering how these models can be trained? Any tutorial ref link?
I've been asked about that by a couple of people before, so I’ll drop the links to those comment threads here:
- English: https://civitai.com/models/1313556?dialog=commentThread&commentId=737373&highlight=737762
- Japanese: https://civitai.com/models/1313556?dialog=commentThread&commentId=768265&highlight=798196
For both CVAT and Ultralytics, I referred to the official manuals and Github issues.
Feel free to ask if you have questions—I can try to answer based on what I know.
@newtextdoc11996 yea i tried v3 too and yes its still missing couple of close area like say for example, the pose hugging and on top and kissing each other , with penetration it misses the penis area, or if theres too many penises like foursome it misses to mark testicle even though i used penis and testicle and pussy model together, or for lets say a upside down pressed penetration it misses the penis completely .
@MeloChan Thanks for the detailed info. I’ll try to include the poses you mentioned when preparing future datasets.
Just to double-check, I’ve written out the poses and actions as Danbooru-style tags. Let me know if any of them seem off:
hug, upright_straddle, girl_on_top, kiss, sex, vaginal, group_sex, piledriver_(sex), upside-down
@newtextdoc11996 yea the tags are on point
Is it difficult to detect the shape of the entire breast, not just the nipple? It is possible with other SEGs, but I believe yours will be of higher quality.
To put it simply, it's definitely possible, but it would take quite a bit of effort.
Specifically, it would require annotating the breast areas (using polygons) in all 900 images, and the same would need to be done for any future additions to the dataset.
That said, I'm currently prioritizing improving the detection accuracy of this model, so I can't say when or if I'll get around to adding that.
testicles detection often fails—what threshold parameter settings would work best?
If detection is low, try lowering the threshold as much as possible.
While lowering it too much can increase false positives, in my local tests it seemed to work fine even at 0.01.
If you're still not getting detections at 0.01, it might be due to an style or pose that wasn’t included in the training dataset.
If possible, feel free to share the image, or the model and prompt you used—it might help identify the cause more accurately.
Thank you for your reply.
Originally, I had the threshold parameter set around 0.3 to 0.5.
After lowering the threshold parameter to 0.05, everything worked normally and detection was successful.



