FLUX Kontext PuLID: Hosted Editor or ComfyUI Workflow?

You cannot load PuLID in the Kontext editor on flux-3image. As of October 2026, its Kontext [pro] and [max] controls offer reference editing, with no PuLID adapter or identity-strength setting. Search results for “FLUX Kontext PuLID” include ComfyUI workflows that combine model and adapter components. For PuLID controls, you need a compatible workflow; for a simple scene change, Kontext can use a portrait and a written instruction.

Which FLUX models does PuLID support?

PuLID uses a face reference to guide identity without training a new model for each person. The maintainers' PuLID-FLUX documentation names FLUX.1-dev and FLUX.1-Krea-dev. It also describes a setting for when identity conditioning begins: earlier conditioning favors likeness, while later conditioning gives the model more freedom to follow the edit.

That documented support does not establish compatibility with hosted Kontext [pro] or [max]. BFL's Kontext editing documentation describes an image-plus-prompt request, and fal's Kontext [pro] input schema has no PuLID adapter input. Typing “PuLID” in flux-3image's prompt box cannot load its weights or set its conditioning strength.

How do ComfyUI “Kontext PuLID” workflows differ?

RunComfy's Kontext PuLID workflow page describes PuLID weight and start/end controls in its sampling groups. We read that description but did not run the workflow, so its results are not part of the example below.

ComfyUI can run on your machine or in the cloud. What matters is the workflow's connections: identify the base model receiving PuLID conditioning and check whether Kontext is a separate editing stage. The workflow's name alone does not answer those questions.

For a concrete PuLID starting point, Nunchaku's FLUX PuLID documentation links a downloadable workflow using Nunchaku FLUX.1-dev. It lists the PuLID weights, EVA-CLIP, AntelopeV2, and FaceXLib dependencies. That is a documented FLUX.1-dev route; it does not establish PuLID support in flux-3image's Kontext editor.

How much does Kontext preserve without PuLID?

We generated a fictional adult portrait with FLUX.2 [pro], then submitted it once to Kontext [pro] through fal using flux-3image's request settings. No PuLID adapter was used. The exact edit instruction was:

Place this person in a sunlit pottery studio. Keep his face shape, eyes, hairline, freckles, expression and charcoal shirt unchanged.

Left: fictional reference generated with FLUX.2 [pro] through fal, 880 × 1168 pixels. Right: FLUX.1 Kontext [pro] through fal using flux-3image settings, one reference, automatic aspect ratio, 880 × 1184 pixels. The edit prompt was sent as typed, with prompt enhancement disabled.

The result adds sunlit windows and pottery. The forehead curl, hazel eye color, and overall facial appearance remain recognizable. The close crops make the skin-detail differences easier to inspect:

Each crop uses the same 500 × 570-pixel rectangle from its full image, without retouching or resizing; the face shifts slightly within that rectangle.

The edited face is softer, the neck gains many dark speckles, and the shirt gains a chest pocket. Kontext preserved a recognizable character here, but it did not keep the requested skin and clothing details unchanged.

Which route fits your character edit?

For a scene change like this one, upload a clear portrait, select Kontext [pro], and state what should change and what should stay. Compare the output with the reference before accepting it. As of October 2026, the live flux-3image Kontext page lists [pro] at 4 credits per image.

For several reference views, the consistent-character tool uses FLUX 3 Image with up to ten references. It has no PuLID adapter control either. If you need PuLID weight or timing settings, follow a workflow that names its compatible base model and dependencies.

The Kontext quality guide has more face-detail examples. The Kontext ControlNet guide explains how a hosted reference slot differs from a separate structural input.