Accessories Segment (RMBG)

Accessories Segment is a helper node, and understanding that is the whole trick to it. It doesn't produce an image or a mask on its own. Instead it's a selector that feeds the Fashion Segment node - you use it to say "and also grab the belt, the bag, and the necklace trim," and it hands that choice off. On its own it does nothing visible; wired into Fashion Segment, it extends that node's garment mask to include accessories.

Here's why the pack is built this way. The fashion-parsing model behind Fashion Segment recognizes a lot of classes - not just garments but a long tail of accessories and trim details. Stuffing all of them as checkboxes onto one node would make it unusable, a wall of fifty toggles. So the pack split them: garments live on Fashion Segment, accessories live here, and this node's single output plugs into Fashion Segment's accessories_options input port to merge the two. It's a clean bit of design once you see it - this node is essentially a configuration bundle for accessories.

The inputs are all accessory toggles, and the list is long because the fashion model is detailed: hat, glasses, "headband, head covering, hair accessory", scarf, tie, glove, watch, belt, "leg warmer", "bag, wallet", umbrella, collar, lapel, neckline, epaulette, pocket, buckle, zipper, applique, bow, flower, bead, fringe, ribbon, rivet, ruffle, sequin, and tassel. Tick whichever you want folded into the mask. Notice how granular the tail gets - sequins, rivets, tassels, appliqué - which tells you this model was trained on serious fashion annotation, right down to garment hardware and decoration. There are no other settings; this node is purely the selection. The single output is accessories_options (type ACCESSORIES_OPTIONS), which goes into nothing else in ComfyUI except the Fashion Segment node's matching input.

So the usage is: drop this node, tick your accessories, and drag its accessories_options output into the accessories_options input on Fashion Segment. Set your garments on that node, and the resulting MASK now covers both. That's the entire workflow. Run this node without connecting it and you'll get nothing, which is the number-one point of confusion - it is not a standalone masker.

Install comes with the pack, no separate step: "Comfyui-RMBG" in ComfyUI Manager, or cd ComfyUI/custom_nodes && git clone https://github.com/1038lab/ComfyUI-RMBG, then pip install -r requirements.txt and restart. It shares the same fashion-parsing model as Fashion Segment, which auto-downloads on first use - so if you've already run Fashion Segment, there's nothing new to fetch.

Practical read: you only need this if the thing you're masking is an accessory the garment toggles don't cover - a belt, a bag, a watch, decorative trim. For plain clothing work, just use Fashion Segment (or the simpler Clothes Segment) and leave this out entirely. Where it earns its keep is detailed fashion pipelines where you genuinely need, say, the belt masked separately from the pants, or the necklace isolated for a recolor. It's a niche node by design - the low search interest reflects that - but if you're deep in garment editing, it's the piece that unlocks the accessory half of the fashion parser.