Nodes/ComfyUI-PixArt_XL/PixArtAlpha Generation
ComfyUI Node

PixArtAlpha Generation

PixArt, the prompt-follower Flux forgot — one node to generate with it

By ShmuelRonen·Created about a year ago·Updated about a year ago· 3
PixArtAlpha Generation
  • model
  • IMAGE
positive
negative
width1024
height1024
steps20
guidance_scale4.50
schedule
seed0

PixArt-Alpha was the underdog that almost made it. Back in early 2024, this 0.6B diffusion transformer with a T5 text encoder was the closest thing to complete prompt adherence you could run locally - a fraction of SDXL's size, better at following what you actually wrote. Then Flux landed in August 2024, PixArt's team joined Nvidia, and the model became a footnote. This node is one of the few places you can still casually generate with it inside ComfyUI.

It's the second half of a two-node pack. The pack's ModelLoader hands you a PAMODEL, you type a prompt into PixArtAlpha Generation, and out comes an IMAGE you can wire straight into a SaveImage or PreviewImage like any other ComfyUI image. The whole thing runs through Hugging Face's diffusers PixArtAlphaPipeline under the hood, which matters more than you'd think: it means this is a self-contained island, not a native ComfyUI model node.

What it actually does

The node takes the already-loaded pipeline and configures it on the fly. It swaps in whichever scheduler you picked, runs the sampler with your prompt and settings, and - this is the pack's whole selling point - babysits your VRAM while it works. From the source: it enables CPU offloading, attention slicing, VAE slicing and tiling, clears the CUDA cache every few steps, and if generation still dies with an out-of-memory error it silently re-runs at half resolution with a few extra steps, then Lanczos-upscales back to your target size. That fallback is janky but genuinely useful - on a cramped card you get an image instead of a crash.

One honest caveat before you get excited: ComfyUI ships its own native PixArt support, and those native nodes load a local .safetensors checkpoint and sample with ComfyUI's normal machinery. This pack doesn't touch any of that. Its PAMODEL type is a walled garden - only this pack's loader feeds it, and only its own sampler consumes it.

The inputs that matter

Three inputs do the actual work; the rest are standard text-to-image knobs:

  • positive and negative - your prompt text. Both are forceInput, so they can be wired from a text node rather than typed in, handy for reusing a prompt across runs.
  • width / height - defaults to 1024×1024, which is the resolution the Alpha model was trained at and where it behaves best. Range is 512 to 3072 in steps of 32.
  • steps (default 20) and guidance_scale (default 4.5) - PixArt likes low guidance, so 4.5 is a sane place to start. Crank guidance toward 7-8 and you get oversaturated, over-sharpened mush.
  • schedule - pick DPM-Solver or SA-Solver. SA-Solver is the snappier of the two and only shows up if its scheduler imported cleanly at load; if you don't see it, DPM-Solver does the job fine.
  • seed - set it to reproduce a run; leave 0 for variety.

Installing it

Same story as the pack's other node. In ComfyUI Manager, search "ComfyUI-PixArt_XL", or from the terminal:

cd ComfyUI/custom_nodes
git clone https://github.com/ShmuelRonen/ComfyUI-PixArt_XL.git
pip install sentencepiece

Then restart ComfyUI. The node sits under the PixArtAlpha category in the menu. The pack's requirements.txt pulls in diffusers and transformers too, and it needs sentencepiece for the T5 tokenizer - that one's easy to miss and is the classic "why won't it load" cause. Fair warning about the first run: it downloads the model from Hugging Face, several gigabytes, so it will look frozen for a while.

Where people get burned

  • The walled-garden surprise. This node's PAMODEL input only accepts the pack's own loader output, and you can't feed it a PixArt checkpoint you already have downloaded for ComfyUI's native nodes. If your goal is native PixArt, this pack isn't it.
  • Everything runs at float32. The loader forces full precision for stability, so you're paying roughly double the memory of an fp16 run on a model that's already light. It usually fits, but don't blame the node if a 3K-tall image OOMs - that's the precision tax.
  • Low-VRAM fallback quality. The half-res-then-upscale path gets you a picture, not a masterpiece. If you're on a genuinely tiny card, generate at the native 1024 first and upscale outside the pack.

None of this makes it a bad toy. It's the easiest route to a model that was, for a few shining months, the best prompt-follower in local land - and if you're nostalgia-tripping or testing an old comparison, it gets you there in one node.

CategoryPixArtAlpha

Inputs (9)

NameTypeDefaultDescription
modelPAMODEL
positiveSTRING
negativeSTRING
widthINT1024512–3072
heightINT1024512–3072
stepsINT201–100
guidance_scaleFLOAT4.500–20
scheduleCOMBO2 options: DPM-Solver, SA-Solver
seedINT00–18446744073709550000

Outputs (1)

NameTypeDescription
IMAGEIMAGE