ComfyUI Detailer/ADetailer Workflow

Heya @CplGreedz,

first i wouldn't try to manually bypass the parts, that might destroy some of the functions and switches that are required for switching between the outputs. So only use the switches to activate/deactivate functions 🫡

Do you have any messages in the console where comfy is running?
Could you provide me with a screenshot through imgur or google drive or something?

When initially loading the workflow the only things that are required to be filled out by you, should be the checkpoint, vae and upscale model. From then on out you should be able to run the workflow.

There might be 1 or 2 nodes shown as "running" inside the inpaint part, but these are lazy switches that switch the output based on the switches you have activated. They just serve to forward the image for the previews and do not actually mean that the inpaint area is currently active.

hey @CplGreedz,

noo need to put yourself down - we all start somewhere and Comfy is sadly not the easiest tool to get into ^^

The two errors i can see come from 2 things and are really easy to fix.
The first: "Checkpoint failure" comes from the seconds row -> second group called "Refiner".
When executing the workflow it tries to check for the checkpoint and cant find it in your list.
Just change it to any of your checkpoints like the prefectIllustriousXL_v10 for example - no need to activate or use it, you just need to have an existing checkpoint here.
This is where you have to change it.

The second: "Output images will be put here" means that the "Load last image from output"-Node cannot find any images in your output directory - most likely because you have not yet created any images and therefore your directory is empty.
You can just click on the "choose file to upload"-Button in the Inpainting area to select any picture - no matter where, to fix this issue. Once you have generated 1 image this won't appear again :)
This is where you have to change it.

Let me know if everything works now or if you still need help 🫡♥️

PS: The second image shows warnings from comfyui, the newest frontend version now has something called workflow validation which is not really functional yet and still in the beta phase of it. You can safely ignore them since it's just comfy being stupid 🫣😂

hey @CplGreedz,

Glad that it's working now!
It should only be slower if you're using a lot of resources on your computer, if you're having a black image instead of a generated one it's most likely something with the workflow itself :o

Let me know if you get black images again and if there are any errors in the console.
If you're using the detailers and you're getting black images in the previews it's most likely just that the ultralytics model couldn't find what it's trained to find in an image. But if you're getting a black image in one of the two preview fields let me know!

@xCraftyx this workflow is meant to be run locally via comfyui only.

I have gotten invites for tensor.art in the past but because it‘s such a closed off system i don‘t like to have my workflow published there since i have virtually no way to debug if anything breaks :/

@RussianMan_BRUTAL that sounds unlikely unless you're on a very old comfy version or you're missing custom nodes.
If you copy and paste your errors i might be able to help you figure out what the issue is 🫡🙏

i‘ll gladly help @RussianMan_BRUTAL :D

Just send me the full error log of your console when executing the workflow and i‘ll help you as good as i can! 🫶🏽

Hey @RussianMan_BRUTAL,

i don't really give tutorials on what IPAdapter or ControlNet are since there are a lot of good tutorials out there that probably explain it way better than i do.

You can however find brief explanations in my IMG2IMG guide about what these are.
Here for IPAdapter and here for ControlNet.
There you can also find an explanation on how to use the IPAdapter, Otherwise there are explanations on how to use the IPAdapter and the ControlNet inside the Explanation node to the left called "How to use".

I tried to make the process as streamlined as possible and the workflow is mostly meant for people who already know what all these things are and only want to use them. It's probably not a good workflow for someone trying to learn some additional things.
Don't use/activate the Manual Inpainting part of the workflow if you don't actually want to inpaint anything, for normal text generation you will not need this area.
I can only recommend reading the notes inside the workflow again for ONLY the functions you want to use and only activating the functions you want to use and know what they do.
If you wildly activate a lot of options and don't know how they work or don't provide images for the process it's normal that some things might not work.

I hope that helps 🫡

@RussianMan_BRUTAL sometimes your pc doesn't have the permissions to access the file from outside the comfy folder. You can then just open the .csv file with editor, copy all the content and paste it into the field in the settings instead of setting the file path.

You can then click save and it should work! 🥰

@RussianMan_BRUTAL If you have a question about the functionality of the workflow you can always ask and i'll always try to help :D

If it's more about general stuff like what controlnet, ipadapter, inpainting, refiner etc. is, it's probably better to google or ask chatgpt since it'll solve your issues faster :D

@RussianMan_BRUTAL both of these models are ultralytics segment (seg/segm) models.
So they both belong into the ultralytics/segm folder.

They are NOT loras, i think you don't quite understand what they are doing or what they are there for. They are detection models only there to recognize and mask areas it is trained on, in this example the face.

So all it does is mask the face area so that the actual detailer can then re-paint them at a higher resolution.

You can also find that information in the Guide where it says that:
"Detailer (ADetailer)

The Detailer (often called ADetailer) is used to refine specific parts of an image after the initial generation. It detects body parts or facial features—like eyes, hands, or mouth—using object detection (usually with Ultralytics), and then re-renders those areas at higher quality using targeted prompts and LoRAs. It’s great for fixing anatomy issues or enhancing details like eye color or hand shape."

Please always check the guide or notes inside the workflow first, this way you don't have to wait hours or days for an answer and can help yourself.

In the Files section you can also see an explanation of where they're supposed to go.

hey @rivverswimmer2572,

yeah this problem is listed in the FAQ in the description ^^
It's sadly not possible for me to create a workaround anymore since comfyui changed some things and now the invasive RES4LYF custom_node just messes up things with other nodes like the detailers :/

Thank you! ♥️🥰 really appreciate it

Hey @xenith617,

this sounds weird - normally the controlnet pose should never even end up anywhere close to the output/preview nodes apart from the preview in the debug section.
Are you maybe using the Image feed to check for results? The image feed will show every single preview as a "generated image" unless you change the settings of comfy accordingly so that they only show saved images. Or is the ControlNet Pose actually ending up in the Output folder?

Can you tell me if you have any errors in the console of your comfy? Maybe there is one file missing.
Usually upon loading you'd only have to change a few models for the workflow to run.
The Checkpoint, VAE, Upscale Model and the Checkpoint selected in the Refiner(even if you don't use it, comfy requires a valid checkpoint here).
Let me know if you have filled all of these out and what your console is saying when trying to generate and image 🫡♥️
And don't ever be shy to ask! I'd rather have someone enjoy my workflow than despair because i didn't make something as clear or convenient as intended ^^

@xenith617 yeah sadly there is nothing i can do to fix that :/
Previously in comfy i was able to use some converters to convert present to expected schedulers, but due to some recent changes on Comfy this is no longer possible.
This issue sadly happens a lot and is also listed in my FAQ section.

I hope one day comfy will either allow us to do non-strict passing of values or the custom_node developer of RES4LYF will do a different implementation.

Hey @last27683599,

The image is only ever saved after appearing in the final preview.
If there is no image appearing in the preview then there is also non saved and if it's not appearing in the preview that means that there was an error during generation.

It's good you're not using node 2.0 since they won't work due to incompatibility with rgthree-nodes, but you should have an error in your console that could give us an idea on what's broken.

hey @last27683599,

that error report is already really helpful!
First of all you're getting some warnings like "[ComfyUI-Manager] Skipped fixing the 'comfyui-frontend-package' dependency because the ComfyUI is outdated." and later on the "comfyui-frontend-package not found in requirements.txt" which most likely means that your frontend package is (very) outdated. That means while your comfy(backend) does have most of the functionality, your frontend cant display nor pass the correct values to the actual technical part of the image generation.

Sadly i saw that in your error log:
"### ComfyUI Revision: UNKNOWN (The currently installed ComfyUI is not a Git repository)"
Which means you can't just simply pull the new frontend because you most likely downloaded comfy as a zip file and then unpacked it somewhere on your PC instead of "pulling" it with something called "git" which serves to keep version control of some you download via git and enables you to update it through commands.

From the looks of it you also probably installed all comfy dependencys globally, which can be a hassle since globally installed packages might end up conflicting with other software on your computer which might result in incompatibilities with other software that might also use and/or update it.
The best practice is to start comfy in a venv which means a virtual environment, that helps to keep everything installed necessary for comfy to ONLY be installed inside the comfy directory. So that nothing is really globally installed on your computer and only comfy uses these dependencys. With this you can easily manage the versions of everything installed and it's also what comfy suggests you should do in their installation guide.

The last error comes from you not having a "example.png" file in your input folder inside comfy.
Usually comfy always comes with one image inside the input folder as somewhat of an example.
This image is also visible in my workflow images and it's the little drawing of this one figure with the big yellow hair/ears.
If that image isn't present the workflow will fail since it has to have an image to display in the default "Load image node" from Comfy. So you can either select a new image in every "load image"-node inside the workflow OR you place one image into your /comfyui/input folder and call it "example.png".
Note: you also have to upload at least 1 Image in the Inpaint Area into the "Load last generated image"-Node. But only if you have never generated an image with comfy before and there is no preview of another image in that node.

I know this is all a lot and i hope i explained everything as good as possible :D
But sadly your comfyui installation is a little bit fucked/corrupted by the way you've downloaded and installed it. If you don't want to do all these steps and want to be future-proof with your comfy installation you could use the install script that i use myself to re-install my comfy installation including all dependencys/custom_nodes needed for this workflow.
I use it myself whenever i test a new version before release and a few others have also already used it to install comfy correctly.

You can find it here:
https://huggingface.co/vslinx/ComfyUIDetailerWorkflow-vslinx/tree/main

You can also open the file and check what it does to make sure nothing fishy is going on, it basically just downloads the newest comfy+frontend version and then installs all dependencys only in the comfy directory and gives you the option to also download the controlnet models etc.
At the end it lets you create a desktop shortcut which will ALWAYS start comfy in it's own venv so that it never installs anything outside of it's own directory.
You can try it if you want to - but no pressure, the other steps above will probably already fix your issue unless the frontend is not updateable at all.
If you want to use the script just download the "windows-nvidia.bat" from the link above and put it where you want comfy installed and then just execute it. It'll install comfy correctly right then and there.

@last27683599 nice i'm glad it worked! ♥️
Yeah the portable version would also be wrong ^^ it's best to pull the actual directory via git, but if comfy updated just fine from the unpacked zip, it's also fine - glad it's working now! 🥰

Hope you'll enjoy the workflow and let me know if something's not working!

Hey @RussianMan_BRUTAL,

you can also find that Information in the notes of the workflow itself:
"ControlNet (Optional)

You can either provide a full image in the "Pre-Process image to Pose" image selector or a ControlNet pose image in the "Load ControlNet Pose" image selector at the bottom.
The ControlNet image has to match the ControlNet model in the node inside of the "ControlNet Model"-Node at the top.
If you want to imitate the pose of an image and have selected a image in the "Pre-Process image to Pose"-Node inside the "ControlNet"-Group you have to enable the "Use Pre-Processor"-Node in the "IPAdapter / ControlNet"-Group.
After selecting a pre-processing model at the bottom of the "Model Backend"-Group you can see a preview of the generated/used pose in the "ControlNet Pose Preview"-Node inside the "Debug"-Group.

You can find an in-depth guide about what ControlNet is, what it does and how each model works in this guide. (It's for A1111WebUI but you'll understand)"

I recommend reading the guide that i linked there to understand what ControlNet even does.

In short you can either upload a controlnet pose image, where the image is already pre-processed like these - OR you just provide an Image that you want to copy the pose from (Pre-Process Image) and activate the pre-processing in the controlnet group.

hey @whateverr,

You don't always get an error thrown from comfy, is there something in the console?
There should be an error in your console where comfy is running if something fails and the workflow just stops without generating anything.

hey @tise4ka406,

yeah that is sadly an issue with a comfy update that broke some things with some custom nodes :/
it really really sucks and i have already brought to their attention here:
https://github.com/Comfy-Org/ComfyUI_frontend/issues/6633

This issue has been fixed with this merge-request thanks to a fellow developer in github:
https://github.com/Comfy-Org/ComfyUI_frontend/pull/7154

It's already merged so the fix is already approved, it's just now waiting to be bundles into the next release and will most likely be included in the next comfy update! 🫡♥️

hey @Rvage,

yeah that's what i meant with bundled into the next (frontend) release :D my bad for badly wording it ^^
Thanks a lot for your fix in the github repo! ♥️

Hey @SugoiDess,

if there is no image saved to the output folder it‘d mean that the process didn‘t fully finish. The output images will have all the metadata including used loras.

Can you tell me what errors you have in your console when running the workflow?

Hey @SugoiDess,
these are a lot of errors upon startup for a new installation - damn!
But they are mostly from the GGUF-FantasyTalking node so it should be fine.

The workflow can't run because you're missing a lot of the models required for it or rather don't have them in your models folder.

This error:
* SAMLoader 9:
- Value not in list: model_name: 'sam_vit_b_01ec64.pth' not in []
Can be fixed with this here.

All the other errors are from you not having selected a Checkpoint/VAE/Detection Model.
The workflow you currently have open already has some models selected but it seems that your checkpoint folder does not have the "betterDaysIllustriousXL_illuXLV0341BKEDVAE.safetensors" checkpoint (it seems to be empty in fact).
You don't have a vae selected, the default sdxl one is not in your folder - the only one in your vae folder is the pixel_space vae.
You're also missing a face detection model while having the face detailer activated, you've selected the "segm/Anzhc Face seg 1024 v2 y8n.pt"-File but there are no files in your ultralytics folder.

In general i wouldn't recommend using portable versions, the sam_vit_b model for example should already be included in the default comfy installation.
The Tavriv1's install script also seems to also be based on the portable comfy version.
If you want to do a clean full "install" of comfyui in it's own virtual environment i could recommend my install script that installs everything automatically that is required for this workflow (except the models of course). It'd install comfy in it's base version wherever you execute it and will run in it's own venv so nothing get's installed globally which helps a lot with dependencies for custom nodes.
You can find the windows-nvidia.bat here if you're interested. But i'd also understand if you don't want to do a new comfy installation again, so the suggestions above should already fix your problems.

@SugoiDess you are trying to install a new comfyui where the old one already is.
So the install script is basically skipping everything.
That's why it's saying this everywhere:
Cloning custom nodes...
- ComfyUI-Impact-Pack already exists. Skipping.
Installing requirements for ComfyUI-Impact-Pack...

I assume the desktop shortcut couldn't be created because of some file permission issues with your computer.
You should install it with the script somewhere else than your current comfy installation, you can just rename the old ComfyUI folder to something else like ComfyUI2 to make the actual script run without issues.

After that you shouldn't have any issues.
It's also always important to refresh the page once after updating/installing anything, because comfyui keeps all old things in it's cache. Make sure to refresh the page and then load the downloaded workflow again, not your old edited version.

Lastly since it didn't generate a desktop shortcut for you because of file permission issues i recommend creating a new one where you start ComfyUI in a venv instead of just normally.
So create a shortcut on your desktop that does this:
@echo off

cd /d "G:\\AI\ComfyUI\"

call "G:\\AI\ComfyUI\venv\Scripts\activate.bat"

python main.py

pause

@SugoiDess Yeeeey! :D

Yeah for the last generated image node there always has to be at least 1 image in the output folder or at least 1 selected ^^ it‘s a bit annoying and i hope comfy will change the behaviour of the node soon!

Hope you‘ll enjoy the workflow ❤️

Hey @Unhing3d,
well that can be or good or bad thing! :D but i'll take it as a compliment for now 😎
This problem is relatively easy to fix, you can read the FAQ entry for that here.

Just a little mention - if you replace the lora loaders, the image saver will not save the metadata information for that ^^ So if you upload the images to civitai the loras wont be automatically added as meta info

@Unhing3d was just waiting for your question 😈😂
Glad it works now! (Hopefully) Enjoy the workflow! ♥️

Hey @amemiyaharuka5391,
this problem is definitely caused by res4lyf being installed :/
Maybe your comfy manager just isn't showing the custom node anymore.
Make sure you go into your comfyui folder -> custom_nodes and then check if there is a RES4LYF folder still in your custom_nodes folder.

If that is the case you can simply delete it, restart comfy and then (very important) refresh your browser window where you have comfy open. Comfy persists a lot of things in the cache until you refresh the browser with comfy open manuall once.

@amemiyaharuka5391 aaaaaaaah!
I'm glad you managed to fix it. I have not heard of another custom_node yet that adds the scheduler to the list and causes this issue. If you ever find out which node it was, feel free to let me know and i'll add it to the FAQ part about this problem 🫡

I hope you'll enjoy the workflow! ♥️

@jess_aitrash that issue is "sadly" already well known. The image saver and the detailers don't do well with the RES4LYF node since there's a mismatch between the schedulers/samplers.

The RES4LYF node overwriting the default dialog but no subnodes is bad design and has to sadly be solved by the developer :/

hey @moddimourad,
this looks like a common out of memory error during vae decoding.
The active node you see during in-paint is most likely just something called a lazy node that is only active for branching and basically does nothing but expect an image and then forward it once it get's it. It's required to do a seamless forwarding of the image.

If you ran out of memory during VAE decoding it most likely means that the image had too big dimensions for your GPU during the decoding.
What GPU do you have?

If you provide me a full error log i might be able to see where the problem is coming from.
Does this only happen when you're running a detailer? Or also when ur trying a normal txt2img process?

hey @moddimourad,
sadly there has to be an image inside the output folder for comfyui to correctly execute all steps of the workflow. If you haven't generated an image yet or have it inside a subfolder in the output folder you'll have to click "choose file to upload" inside the "Load last generated image"-Node.

This is imo an oversight from the default comfy node and i might write my own node with better value handling for these cases in the future to avoid this until comfy fixes that behaviour.

When you have added a picture to the inpainting "Load last generated image"-Node, does this fix your issue and an image actually gets saved? If yes you could also just bypass that node for the time being until you'd like to use the inpainting part.

@moddimourad all right, thank you for the feedback! ♥️
I hope you'll enjoy the workflow and i'll see what i can do to fix this issue in a future v5.1 where i'll remove the comfy-core node and implement my own.

hey @emdomenic,
if you don't have a final image in the "Preview after Detailing"-Node it means that the workflow had an error at some point during execution.
Please check your comfy console and let me know what error is being thrown there.

You can also check the FAQ section to see if the error you have might be listed there already.

And no worries, once the final preview actually appears(when the error is fixed), the image will be saved with all metadata information.

Hey @willshawn2519,

implementing faceid is currently not intended as it is a little bit too niche for my workflow and since you can mostly do it already (without using faceid).
You could either use a face detailer and activate the prompt and prompt which face you want it replace by OR you could use the manual inpainting part and mark the area you want to change and then prompt the character you want it to be replaced by.
It might not be as convenient as faceid but it works really well and i've done it frequently before ^^

Sadly faceid is not on my to-do list currently as there are some things i'd like to fix and implement first, but maybe along the way i'll add it!

Hey @timsatyr981,

it seems that your comfy installation is a little bit broken.
Your main issue seems to come from a Image Preview node receiving a "CLIP" instead of an "Image". Usually comfy doesn't even allow such a connection to begin with, so it's very likely that your installation is broken and upon loading the workflow your comfy started re-wiring node connections wrongfully.

The node in question is the "Eyes"-Node in the Debug section. You could try removing/bypassing it to see if that'd make the workflow run normally.

But there are some other things that are throwing failures in your Comfy Setup, i'll mark the things you can change, in order to probably make it work, fat:

You have two nodes that fail during import, maybe update them through Comfy Manager or remove them:
- ComfyUI-GGUF-FantasyTalking
- comfyui-reactor

You have not selected a Checkpoint in the "Refiner"-Section. While you don't have to use the refiner and i usually would not use it, Comfy still expects a valid value in the Node. So just go down to the "Refiner"-Group next to the model selection and choose 1 of your models, doesn't really matter which one unless you actually want to use the Refiner functionality.

You do not have a example.png in your input folder. This image usually comes with every comfy installation and provides one common image for everyone to share workflows with. You might have deleted it from your ComfyUI/input folder. Your options are to either load an image into all of the "Load image"-Nodes (ControlNet, IPAdapter & "Load last generated Image" in the Inpainting section) or simply copy any .png file into your ComfyUI/input folder and rename it to example.png.

Fixing these Problems SHOULD make the workflow run. Make sure that you update all your custom nodes beforehand and then re-load the downloaded workflow and then refresh your Comfy Page to make sure the cache is cleared.

If this does not fix your issue your Comfy Installation might be too corrupted. In that case i can recommend to install Comfy through git instead of the installer, as it is way better at keeping dependencys local to the comfy installation instead of globally inside your AppData folder.
This makes things way easier for you and your comfy. If you don't know how to do it you could download my Installer from here by downloading the "nvidia-windows.bat" and executing it where you want comfy to be installed. It installs the newest Comfy via git including all the dependencys required for this workflow and the workflow itself. It also lets you choose if you want to download the controlnet models etc.
I frequently have people with the comfy installer or the portable comfy since they are more prone to running into errors and quite a few have switched to the git installation through my script.

I hope that helps, if you need anything more let me know :)

@timsatyr981 No problem! Let me know how it goes 🥰

hey @Darkbiology,

there is currently no option to just upscale the latent instead of upscaling the decoded img with an upscale model.
This feature is currently also not planned to not overload the workflow even more since most people rather use an upscale model instead of upscaling the latent :/

If you're concerned about colors washing out i can recommend the color fix option with a small strength like 0.1