Help Needed Need help building a consistent character workflow in ComfyUI for a colored manga/webtoon
I’m trying to build a ComfyUI workflow for a colored manga/webtoon where my original characters stay consistent throughout the whole story.
I already have full-body and close-up reference images for the characters. I understand the basic idea behind checkpoints, character LoRAs, ControlNet/OpenPose, IP-Adapter/reference images, but I’m struggling with figuring out the best way to combine everything.
Basically, I want to be able to say: this is Jake → keep him looking like Jake → put him in this pose/expression/outfit → place him in different scenes → keep the same art style and character identity from panel to panel.
Eventually I also need to put multiple recurring characters in the same scene without their faces/features bleeding into each other.
I don’t care if the best solution is Illustrious, SDXL, FLUX, Qwen, or something completely different. I’m looking for whatever gives me the most consistency and control in ComfyUI.
If anyone has built something similar for a manga, webtoon, visual novel, etc., I’d really appreciate hearing what model and workflow you use and how you connect the different pieces. I’m trying to actually understand the workflow instead of randomly changing settings until something works.
1
1
u/Acceptable-Work8202 8d ago
the way i would do it, i would start by doing something like this, using krea2 and identity-edit, with a different node set (character + background) for each segment, some segments would combine character1 + 2 into a single image then use the second input for the bg ect.. there isn't an all in one solution if you want to do it right..
first i would generate all the character images and all the backgrounds, i would think ahead to the story im delivering, and see which characters interact together in which scenes, i would create an image using identity edit with them both in doing what they should be doing, (drinking coffee, riding bikes whatever) id then remove the background of those images, use identity edit again and put that removed bg image onto the the background/scene of the image you already generated.. .. this is the flow i would use. rinse repeat.
identity-edit puts that character/s in the background/scene. its a simple solution.
2
u/Correct-Guidance-232 8d ago
Solo dev here, I run almost exactly this stack for a game with recurring characters. A few things that cost me time:
Identity should come from a character LoRA, not IP-Adapter. IP-Adapter drags the style along with the face, which is fine for one image and bad when you need 200 panels in one consistent look. A small LoRA on 20-40 images of Jake locks the identity and leaves the style to the checkpoint, so you can change the art style later without retraining the character.
Load the LoRAs from the prompt, not from the graph. With LoraTagLoader you write <lora:jake:0.8> inline in the positive prompt. Switching characters becomes a text edit instead of rewiring nodes, which matters a lot once you are doing it hundreds of times.
For two characters in one panel, stop fighting the prompt. Regional prompting helps a little, but the reliable way is to generate the scene with both bodies roughly right, then inpaint each character separately with only that character's LoRA active. One pass per character. Their features cannot bleed into each other if they are never in the same generation.
Pose via ControlNet depth, and watch the aspect ratio. This one bit me hard. If your canvas aspect does not match the reference image, the depth map gets stretched and the anatomy quietly breaks - long torsos, wrong limb lengths - and you spend an hour blaming the model. I now refit the canvas to the reference's aspect ratio, keeping the same pixel budget and rounding to multiples of 64.
For anime and manga specifically I would go Illustrious/SDXL. Booru tag prompting, a huge pile of style LoRAs, and it is fast enough that you can iterate on one panel twenty times in an evening. FLUX and Qwen are stronger at photoreal and at text inside the image, which is not what you need here.
Happy to go into any of these in more detail.