<h2 id="overview">Overview</h2>A general-purpose, mask-driven Detailer workflow for ComfyUI.Unlike detailer workflows tied to a predefined target, this workflow allows the region being detailed to be selected independently from the generation pipeline.The supplied implementation uses Ultralytics + SAM for target detection and segmentation. By changing the Ultralytics detection model, the same workflow can be used to detail eyes, faces, heads, hands, characters, body regions, objects, or other detectable targets without restructuring the pipeline.The selected region can also be inverted, allowing the detected subject to remain protected while the surrounding region is regenerated.Generic architecture:Select → Mask → Crop → Detail → StitchThe selection mechanism and detailing engine remain independent, allowing each stage to be configured and experimented with separately.<hr /><h2 id="pipeline">Pipeline</h2>The included implementation uses:Detect → Segment → Crop → Detail → StitchDetect — Ultralytics identifies the target region using the selected detection model.Segment — SAM refines the detected region into a more accurate mask.Crop — Inpaint Crop extracts the localized region while retaining the information required to place it back into the source image.Detail — The cropped region is regenerated through a standard VAE → KSampler → VAE pipeline.Stitch — The detailed crop is composited back into the original image.The Detailer Diagnostics section exposes intermediate results for inspection and troubleshooting.<hr /><h2 id="why-a-modular-detailer">Why a Modular Detailer?</h2>The objective is not to replace FaceDetailer. FaceDetailer remains an excellent all-in-one solution for conventional detailing workflows.This workflow instead exposes the individual stages of the detailing process and removes the assumption that the target must always be a face.The modular architecture provides:<ul><li>Transparent detection and sampling stages</li><li>Selectable detailing targets</li><li>Independent control over the generation model and LoRAs</li><li>Independent prompt and sampling configuration</li><li>Easy inspection of intermediate results</li><li>Reusable mask-driven detailing architecture</li><li>Simple experimentation with detection and segmentation</li><li>Target switching without rebuilding the pipeline</li><li>Support for both detailing the selected region and preserving it</li></ul>The key difference is simple:FaceDetailer selects the face. This workflow allows you to select what gets detailed.<hr /><h2 id="target-selection">Target Selection</h2>The included workflow uses an Ultralytics detector to determine the target region.The selected detector model effectively defines what the Detailer operates on.For example:Eye detector → Eye DetailerFace detector → Face DetailerHead detector → Head DetailerHand detector → Hand DetailerPerson detector → Person / Character DetailerOther suitable detection models can be used for other targets.Changing the target only requires changing the appropriate detector model.The downstream:Segment → Crop → Detail → Stitchpipeline remains unchanged.No pipeline restructuring is required when switching detection targets.<hr /><h2 id="segmentation">Segmentation</h2>Detection determines the approximate target location, while SAM refines the detected region into the mask used by the detailing pipeline.This separation allows the detector and segmentation stages to be tuned independently.Detection quality is therefore important: SAM can refine a successfully detected region, but the detector must first provide a suitable target for segmentation.The exposed mask preview makes it easy to verify the selected region before evaluating the detailing result.<hr /><h2 id="detailing-engine">Detailing Engine</h2>The included example uses ZiT Redcraft, but the detailing engine is intentionally independent of the detection and segmentation stages.Other compatible image-generation models can be substituted by replacing the appropriate:Model / CLIP / VAE / Conditioningcomponents and configuring any model-specific sampling requirements.The exposed sampling stage also provides direct control over:<ul><li>Prompt</li><li>LoRAs</li><li>Sampler</li><li>Scheduler</li><li>Steps</li><li>CFG</li><li>Denoise</li><li>Model-specific sampling configuration</li></ul>This makes the generation stage independently configurable without changing how the target region is detected, segmented, cropped or stitched.<hr /><h2 id="lora-support">LoRA Support</h2>Because the detailing sampler is exposed as a standard generation pipeline, LoRAs can be applied directly to the detailing model.This allows the workflow to perform more than conventional restoration or enhancement.Depending on the model, LoRA and prompt, the selected region can be refined, restyled or substantially regenerated while the surrounding image remains preserved.Multiple LoRAs may also be combined as supported by the selected generation model.LoRAs are optional and are not required for the detection, segmentation or stitching stages.<hr /><h2 id="mask-inversion">Mask Inversion</h2>The same target selection can be used in two different ways.<h3 id="standard-mask">Standard Mask</h3>The detected region becomes the detailing target:Detect Target → Detail Target → Preserve SurroundingsFor example:Person detector → regenerate/detail the person while preserving the background<h3 id="inverted-mask">Inverted Mask</h3>By enabling mask inversion in Inpaint Crop, the detected region instead becomes the protected region:Detect Target → Preserve Target → Detail SurroundingsFor example:Person detector → preserve the character while regenerating the backgroundThis allows the same detection and detailing pipeline to operate either inside or outside the selected region without restructuring the workflow.<hr /><h2 id="detailer-diagnostics">Detailer Diagnostics</h2>The workflow exposes several intermediate stages through the Detailer Diagnostics section.These previews allow the user to inspect:<ul><li>Detected / segmented mask</li><li>Source crop</li><li>Active detailing region</li><li>Detailed crop</li><li>Final stitched result</li></ul>This makes it easier to identify where an unexpected result originates.For example:Incorrect target → inspect detectionPoor mask → inspect segmentationIncorrect crop/context → inspect Inpaint CropWeak or excessive modification → inspect prompt, LoRA, denoise and samplingStitching artifacts → inspect mask and stitch configurationThe diagnostic nodes are provided for visibility and troubleshooting and do not define the detailing target themselves.<hr /><h2 id="modular-architecture">Modular Architecture</h2>The workflow can be understood as three independent layers.<h3 id="1.-selection-layer">1. Selection Layer</h3>What should be detailed?Ultralytics or another compatible selection mechanism identifies the target.<h3 id="2.-mask-layer">2. Mask Layer</h3>Where is regeneration allowed?SAM and the crop/mask configuration determine the active region.Mask inversion can reverse this relationship so that the selected target is protected instead.<h3 id="3.-generation-layer">3. Generation Layer</h3>How should the region be regenerated?The model, LoRAs, prompt and sampling configuration determine the resulting detail.Because these layers are separated, each can be modified without unnecessarily changing the others.<hr /><h2 id="extending-the-workflow">Extending the Workflow</h2>The exposed crop and generation stages also provide convenient entry and exit points for additional processing.The cropped region can be processed before sampling, and the generated crop can be processed again before stitching.This allows additional processing stages to be inserted or chained while retaining the original detection, mask and stitch information.The generation stage can therefore be expanded, replaced or chained depending on the intended detailing task.<hr /><h2 id="important">Important</h2>The workflow is only as reliable as the target selection used for a particular image.Different detector models may perform differently depending on:<ul><li>Image resolution</li><li>Target size</li><li>Viewing angle</li><li>Occlusion</li><li>Stylization</li><li>Unusual or heavily modified anatomy</li></ul>If the intended region is not detected correctly, first inspect the Detailer Diagnostics and adjust the detector, detection settings or preprocessing resolution before changing the generation stage.Once the intended region is correctly detected and segmented, the downstream detailing pipeline can remain unchanged.<hr /><h2 id="summary">Summary</h2>This workflow generalizes the familiar Detailer pattern by separating what gets detailed from how it gets detailed.Select → Mask → Crop → Detail → StitchChange the detector to change the target.Change the mask polarity to detail or preserve that target.Change the model, prompt, LoRAs or sampling configuration to change how it is regenerated.The result is a reusable general-purpose Detailer architecture that can be adapted to different targets without rebuilding the workflow.

Files with SHA256: 4542b3a18c911f6bc64b85f04a9a15210273ea26b215b4aba80636fa113780ac