CIVITAI / Workflows

FLUX.1 Dev PiD Direct 4K Image Generation Workflow

Watch the full video first if you want to understand how this FLUX.1 Dev + PiD workflow works in practice. The video shows how a 1024 base image can be generated and then pushed into a PiD-based 4K enhancement lane, how the native baseline compares with the enhanced result, and how to launch the workflow online without building a local ComfyUI setup. This ComfyUI workflow is designed for FLUX.1 Dev 4K image generation using PiD as the high-resolution enhancement stage. Its main purpose is to create a strong FLUX.1 Dev base image first, capture the correct intermediate latent state, and then send it into a PiD 2K-to-4K refinement pipeline for sharper, richer, and more detailed final output. The workflow is built around flux1-dev-fp8.safetensors as the main checkpoint. It uses a 1024×1024 base latent, CLIP text encoding, FluxGuidance, PiDTextPrompt, PiDKSamplerCapture, PiDPrepare, PiDSample, PiDFinalize, VAEDecode, and SaveImage. The graph also includes a native FLUX output lane and a PiD enhanced output lane, making it useful for direct comparison between the standard generation result and the 4K-enhanced version. The first part of the workflow is the FLUX.1 Dev base generation. The prompt is written into PiDTextPrompt and then passed into the positive prompt encoder. FluxGuidance is set to 3.5, while CFG is set to 1.0, which is important because FLUX Dev does not use the negative prompt in the same way as older CFG-heavy models. The workflow note also makes this clear: for FLUX Dev and Schnell, CFG should stay at 1.0 because negative prompting is ignored when CFG is 1.0. The sampling stage uses PiDKSamplerCapture instead of a normal KSampler. This node generates the native FLUX latent while also capturing a PiD-ready latent at the selected capture step. In this workflow, the setup uses 28 steps, Euler sampler, simple scheduler, denoise 1.0, and capture_step 26. This is a practical setting because it allows the base image to develop enough structure before the PiD stage receives the captured latent. After the base latent is captured, PiDPrepare converts it into a PiD-compatible preparation object. The workflow is configured for the FLUX backbone, 2kto4k PiD checkpoint type, scale 4, auto download enabled, and cleanup after prepare enabled. Then PiDSample runs the high-resolution PiD pass with 4 PiD steps, CFG scale 1.0, fixed seed, aggressive cleanup, an