ComfyUI Node

qwen

Qwen-Image LoRA training on the cloud, with a version picker

By civitai·Created 2 months ago·Updated about a month ago· 42
qwen
  • continue_from
  • api_config
  • moderation_status
  • epochs
  • workflow_id
  • raw_json
training_data_json
storage_buzz_per_epoch0.00
default_steps0
uses_step_pricingfalse
max_batch_size0
samples_json
epochs1
steps1
batch_size1
lr0.00
text_encoder_lr0.00
train_text_encoderfalse
lr_scheduler
optimizer_type
network_dim1
network_alpha1
noise_offset0.00
flip_augmentationfalse
shuffle_tokensfalse
keep_tokens0
trigger_word
versionlatest

Qwen-Image is one of the strongest open image models around, and its LoRA training used to mean a serious VRAM ask locally. CivitaiTrainingAiToolkitQwen moves that to Civitai's cloud: Ostris's AI Toolkit trains a Qwen-Image LoRA from your zip of images, and you get a downloadable model per epoch. The one thing this node adds over the other training nodes is a version dropdown - latest, 2509, or 2512 - so you can pin exactly which Qwen-Image checkpoint you're training on.

It sits in Civitai/Training/qwen, part of Civitai's official ComfyUI pack. The version picker matters because Qwen-Image's releases differ meaningfully in capability; latest is the safe default (and the API's default too), while the dated versions let you reproduce against a known checkpoint. A welcome bit of control you don't get on most of these nodes.

How it works

The node submits a training workflow (engine: ai-toolkit, ecosystem: qwen) to Civitai's Orchestration API. Your training images go up as a hosted zip, the cloud runs AI Toolkit, and each epoch delivers a downloadable LoRA. One quirk worth knowing: Qwen-Image training is batch_size 1 only - the API clamps it, so you can't trade memory for speed the way you can elsewhere. That's baked in, not a bug in your settings.

The core input is training_data_json, a JSON object:

{"type": "zip", "sourceUrl": "urn:air:qwen:dataset:civitai:222@1", "count": 30}

sourceUrl is an AIR URN to the zip of training images; count is the number of images, which is how the run is priced.

The inputs that matter

  • training_data_json (required) - the zip + count object.
  • version - latest (default), 2509, or 2512. Pin a dated version to keep results reproducible.
  • epochs / steps - epochs = saved checkpoints (each a downloadable model), steps = total training length and the pricing driver.
  • trigger_word - the token that activates your LoRA in prompts.
  • network_dim / network_alpha, lr, train_text_encoder, noise_offset - standard trainer dials, all optional.

The required-looking storage_buzz_per_epoch, default_steps, uses_step_pricing, max_batch_size fields are generated plumbing - leave them.

Outputs: moderation_status, epochs, plus the standard workflow_id and raw_json.

Installing it

This is one of ~160 nodes in Civitai Comfy Nodes, Civitai's official pack for their Orchestration API:

  • ComfyUI Manager: Manager → Custom Nodes Manager → search Civitai Comfy Nodes → Install, then restart.
  • CLI: comfy node registry-install civitai-comfy-nodes
  • Source: cd ComfyUI/custom_nodes && git clone https://github.com/civitai/civitai-comfy-nodes.git && pip install -r civitai-comfy-nodes/requirements.txt (just requests).

You need a Civitai account with Buzz and credentials - a Civitai Auth node, CIVITAI_API_TOKEN for headless, or a stored key via the Civitai sidebar.

Where people get burned

  • training_data_json must be valid JSON with type, sourceUrl, and count - malformed input fails locally before it submits.
  • Batch size is locked to 1. Don't fight the batch_size field; the API clamps it for this ecosystem and the tooltip says so.
  • Pricing adds up. Steps are metered and each epoch carries a storage surcharge; check the node's cost report after a run.
  • Moderation gates the model. moderation_status reports whether your LoRA passed Civitai's content review.
  • Early preview. The README warns of breaking changes without notice; early community reports include bugs and slow jobs. Long trainings can hit the default 30-minute timeout - raise it via the Auth node or CIVITAI_COMFY_TIMEOUT.

Qwen-Image LoRAs are worth having, and the version pinning makes this the most reproducible training node in the pack. Feed it clean data and a trigger_word, and let the cloud burn the GPU-hours you'd rather keep.

CategoryCivitai/Training/qwen

Inputs (24)

NameTypeDefaultDescription
training_data_jsonSTRINGRepresents training data in various formats
storage_buzz_per_epochFLOAT0.000–2147483647Per-epoch surcharge (buzz). Each epoch is a delivered checkpoint plus its preview samples, billed on top of the per-step training cost — so raising the epoch count raises the price by this much each. Override per ecosystem where per-epoch samples are expensive to compute (e.g. video).
default_stepsINT00–2147483647Default total step budget when neither Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Steps nor Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Epochs is supplied. Override per ecosystem where the default training length differs (e.g. video needs more steps, quickly-overtrained models need fewer).
uses_step_pricingBOOLEANfalseTrue when billing uses the per-step model. This is the default; the only exception is the legacy path where the caller supplied Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Epochs but no Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Steps (existing consumers), which keeps the historical flat per-epoch price.
max_batch_sizeINT00–2147483647Ecosystem-specific maximum training batch size — the upper bound the user's Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.BatchSize is clamped to. Most ecosystems cap at 1.
samples_jsonoptSTRINGSample generation configuration for training workflows
epochsoptINT11–200Number of training epochs — the number of saved checkpoints produced (each epoch yields one downloadable model). When omitted it is derived from Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Steps; when both are supplied, both are honored (epochs = checkpoint count, steps = total).
stepsoptINT11–10000Total number of training steps. This is the primary control over training length and determines pricing. When supplied, Civitai.Orchestration.Grains.Workflows.Steps.Training.AIToolkit.AIToolkitTrainingInput.Epochs (the number of saved checkpoints) is derived from it; when omitted, steps are derived from epochs.
batch_sizeoptINT11–4Training batch size. Defaults to 1; raise it (up to the ecosystem's maximum) to train faster at the cost of more GPU memory. A larger batch sees more images per step, so fewer steps are needed for a comparable result. Values above the ecosystem maximum are clamped down.
lroptFLOAT0.000–1Sets the learning rate for the model. This is the learning rate when performing additional learning on each attention block (and other blocks depending on the setting).
text_encoder_lroptFLOAT0.000–1Sets the learning rate for the text encoder. Only used when TrainTextEncoder is true. For models with multiple text encoders, this applies to all of them.
train_text_encoderoptBOOLEANfalseWhether to train the text encoder(s) alongside the model. Enabling this can improve prompt understanding but increases training time and memory usage.
lr_scheduleroptCOMBOYou can change the learning rate in the middle of learning. A scheduler is a setting for how to change the learning rate.
optimizer_typeoptCOMBOThe optimizer determines how to update the neural net weights during training. Various methods have been proposed for smart learning, but the most commonly used in LoRA learning is "adamw8bit".
network_dimoptINT11–256The larger the Dim setting, the more learning information can be stored, but the possibility of learning unnecessary information other than the learning target increases. A larger Dim also increases LoRA file size.
network_alphaoptINT11–256The smaller the Network alpha value, the larger the stored LoRA neural net weights. For example, with an Alpha of 16 and a Dim of 32, the strength of the weight used is 16/32 = 0.5, meaning that the learning rate is only half as powerful as the Learning Rate setting. If Alpha and Dim are the same number, the strength used will be 1 and will have no effect on the learning rate.
noise_offsetoptFLOAT0.000–1Adds noise to training images. 0 adds no noise at all. A value of 1 adds strong noise.
flip_augmentationoptBOOLEANfalseIf this option is turned on, the image will be horizontally flipped randomly. It can learn left and right angles, which is useful when you want to learn symmetrical people and objects.
shuffle_tokensoptBOOLEANfalseRandomly changes the order of your tags during training. The intent of shuffling is to improve learning. If you are using captions (sentences), this option has no meaning.
keep_tokensoptINT00–10If your training images have tags, you can randomly shuffle them. However, if you have words that you want to keep at the beginning, you can use this option to specify "Keep the first 0 words at the beginning". This option does nothing if the Shuffle Tokens option is off.
trigger_wordoptSTRINGA trigger word that activates the trained LoRA when used in prompts. Only applicable to certain ecosystems (sd1, sdxl, flux1, chroma, zimagebase, zimageturbo, flux2klein).
continue_fromoptCIVITAI_AIROptional previously-trained LoRA to continue training from ("train further"). When set, the first epoch resumes from this model instead of the base model, and the new epochs build on top of it.
versionoptCOMBOlatest3 options: latest, 2509, 2512
api_configoptCIVITAI_CONFIGOptional Civitai Auth connection; defaults to CIVITAI_API_TOKEN or stored OAuth login.

Outputs (4)

NameTypeDescription
moderation_statusSTRING
epochsSTRING
workflow_idSTRING
raw_jsonSTRING