AI video guide · ComfyUI · Wan 2.2

Wan 2.2 Remix + PromptRelay in ComfyUI: GGUF workflow guide

Turn The Render Den’s short video into a practical operating procedure: install the shared workflow, choose Wan 2.2 Remix model variants, connect the high-noise and low-noise loaders, optionally use GGUF text encoders on a second GPU, and write segmented PromptRelay prompts for short cinematic clips.

Difficulty: Intermediate Updated: May 17, 2026 Primary source: The Render Den video Output: short AI video clips
1

What you will build

This guide documents a local ComfyUI workflow for Wan 2.2 Remix, using the GGUF-capable shared workflow highlighted in the video. The practical goal is a repeatable image-to-video or text-to-video setup that can generate short cinematic clips with realistic motion, scene consistency, and segmented prompt control.

Use it for

  • Short cinematic experiments.
  • Image-to-video motion tests.
  • Prompt-segmented video timing.
  • Local GPU generation without cloud services.

Core pieces

  • Wan 2.2 Remix high-noise and low-noise models.
  • Text encoder / CLIP models.
  • ComfyUI workflow JSON.
  • Optional PromptRelay node.

Main choices

  • GGUF versus safetensors.
  • Regular text prompt versus PromptRelay.
  • Single GPU versus second-GPU text encoder offload.
  • Optional acceleration LoRAs enabled or bypassed.
Plain-English flow: load the model pair, load the text encoder, provide an image or prompt, set video length and size, describe each segment of motion, then let the high-noise and low-noise samplers refine the final clip.
2

Safety boundary for adult-capable models

Important: the source video discusses adult-content-capable variants. This guide is for lawful, private, fictional, consenting-adult creative experimentation only. Do not generate minors, real people without consent, non-consensual scenarios, harassment, impersonation, extortion material, or illegal/exploitative content.

Keep your model files, outputs, and prompts in a private workspace. If a workflow or model card includes its own license, prohibited uses, or distribution rules, follow those terms. For public or professional demonstrations, use safe, non-explicit prompts and label AI-generated media clearly.

  • Use fictional adult subjects only.
  • Avoid celebrity, coworker, student, or private-person likenesses unless you have explicit permission.
  • Do not upload sensitive source images into public services.
  • Review outputs before sharing; discard anything unsafe or unintended.
3

How the workflow is organized

The tutorial describes the graph in practical zones. Think of it as a left-to-right production line.

Model loaders

  • High-noise Wan 2.2 Remix model.
  • Low-noise Wan 2.2 Remix model.
  • GGUF or safetensors text encoder / CLIP.
  • Optional set-device node for second-GPU offload.

Optional flavor nodes

  • Acceleration LoRA loaders for high and low flow.
  • Custom Script nodes for convenience features.
  • Extra Models nodes if you want additional loader options.

Inputs and controls

  • Image loader for I2V.
  • Resize/preview node for output dimensions.
  • Total steps, split steps, and video length controls.
  • Prompt group switch for regular prompt versus PromptRelay.

Generation path

  • High-noise sampler starts the motion.
  • Low-noise sampler refines structure and consistency.
  • Final video output node saves the generated clip.
4

Prerequisites

Software

  • A working ComfyUI installation.
  • ComfyUI Manager for installing custom nodes from a Git URL.
  • Enough disk space for multiple model files.
  • A browser for Google Drive workflow/model links.

Hardware

  • NVIDIA GPU strongly recommended.
  • Higher VRAM allows larger resolution and longer clips.
  • GGUF variants can help fit hardware constraints.
  • Second GPU offload is optional but can reduce RAM bottlenecks.
Start conservative: first test at a modest resolution and short length. Confirm your loaders, text encoder, and prompt path work before increasing duration, resolution, or steps.
5

Download the workflow and place model files

  1. Download the shared workflow. Use the Google Drive workflow link from the video description, then save the workflow JSON somewhere easy to find.
  2. Choose the Remix model format. The video says Remix variants are available as safetensors and GGUF. GGUF is often the practical choice for constrained systems; safetensors may be preferable when you have enough VRAM and a compatible loader.
  3. Select version 3 for both model stages. For the workflow shown, use the version 3 variant for both the high-noise and low-noise loaders. The transcript notes that FP16 is available for some variants, but v3 FP16 was not available at the time of the video.
  4. Download both high and low models. The graph expects a high-noise model and a low-noise model. If only one is connected, the workflow will fail or produce poor results.
  5. Download the text encoder / CLIP models. The video uses adult-content-capable text encoder links and mentions GGUF variants as direct downloads.
  6. Place text encoders in the ComfyUI model folder. Use your ComfyUI text encoder folder, commonly ComfyUI/models/text_encoders/. If your custom nodes expect a different folder, follow the node documentation.
ComfyUI/
  models/
    diffusion_models/   # common location for video/diffusion model files
    text_encoders/      # place text encoder / CLIP files here when required
    loras/              # optional acceleration/flavor LoRAs
    vae/                # VAEs if the workflow requires them

Folder names can vary by custom node. When a loader dropdown does not show your model, check the node’s expected model directory and restart ComfyUI or refresh model lists.

6

Wire the high/low model loaders correctly

The shared workflow includes color-coded loader groups. The video shows both regular split-file loader nodes and the creator’s preferred loader nodes with more optimization controls.

  1. Open the workflow JSON in ComfyUI. If nodes are red or missing, install the missing custom nodes first, restart, and reload the workflow.
  2. Set the high-noise loader. Choose the high-noise Wan 2.2 Remix v3 model in the loader intended for the high flow.
  3. Set the low-noise loader. Choose the matching low-noise Wan 2.2 Remix v3 model in the low-flow loader.
  4. Reconnect loader outputs if needed. The video demonstrates rewiring by holding Shift and dragging the connection to the target input.
  5. Handle optional LoRAs. If you are not using acceleration or flavor LoRAs, toggle them off or bypass those loader nodes entirely.
  6. Choose text encoder handling. For GGUF CLIP/text encoder, the creator offloads to a secondary GPU. If you do not have a second GPU, disable or delete the set-device node and let the workflow use your normal device path.
Success check: all loader dropdowns show the selected files, there are no missing-node warnings, and the high/low model outputs connect forward into the sampler path.
7

Install and use PromptRelay for segmented motion

PromptRelay lets you describe a clip as timed segments instead of one long prompt. The workflow can switch between regular prompt input and PromptRelay input.

  1. Open ComfyUI Manager.
  2. Choose Install via Git URL.
  3. Paste https://github.com/kijai/ComfyUI-PromptRelay.
  4. Confirm installation and restart ComfyUI.
  5. In the workflow’s prompt switch, set the control to use PromptRelay. The video says false selects the PromptRelay node and true selects the regular prompt node.

Simple pipe syntax

wide cinematic shot, adult character enters a neon hallway |
character turns toward the camera, coat moving naturally |
camera pushes in, lights flicker, character exits frame

Segment length options

  • Leave segment lengths blank for equal distribution.
  • Use comma-separated frame counts if you need exact timing.
  • With the Smart PromptRelay node, weighted ranges such as [0-50] can assign proportions.
PromptRelay rule: use one segmentation style at a time. Do not mix multiple syntaxes in one field unless the node documentation explicitly supports it.
8

Set video length, size, and first-run values

The settings group controls total steps, split steps, and video length. The resize/preview node controls output size for the image-to-video path.

Recommended first test

  • Short clip length.
  • Moderate resolution.
  • No optional LoRAs.
  • PromptRelay equal segment distribution.
  • One clean source image for I2V.

Increase only after success

  • Longer video length.
  • Higher resolution.
  • More steps or split steps.
  • Acceleration or flavor LoRAs.
  • More complex segment timing.
  1. Load a test image for I2V. Use the linked test image or your own safe, appropriate source image.
  2. Check the preview after resizing. Make sure framing still looks correct after the resize node.
  3. Set conservative dimensions. Avoid large resolutions until the workflow runs cleanly.
  4. Set total and split steps. Use the workflow defaults first. Later, adjust quality/speed once you understand runtime and VRAM.
  5. Queue the prompt and watch the console. Missing model, missing node, and CUDA out-of-memory errors are easiest to diagnose from the console output.
9

Prompt patterns that work well

Wan-style video workflows tend to respond best to visual, camera-aware prompts. Segment prompts should describe motion changes, not just static appearance.

Global prompt ingredients

  • Overall style: cinematic, realistic, handheld, studio, macro, etc.
  • Lighting: soft key light, neon rim light, golden hour.
  • Camera: slow push-in, tracking shot, locked tripod.
  • Motion: hair moves, fabric sways, character turns.
  • Quality controls: stable anatomy, consistent scene, smooth motion.

Segment prompt ingredients

  • Segment 1: establish the subject and camera.
  • Segment 2: introduce a clear action.
  • Segment 3: change expression, pose, or camera distance.
  • Final segment: resolve the action instead of continuing endlessly.
Global: cinematic realistic lighting, stable anatomy, consistent outfit, smooth natural motion, detailed environment, safe fictional adult subject

Segments:
subject stands in a softly lit room, camera begins a slow push-in |
subject turns and walks toward the window, fabric moves naturally |
subject pauses, looks outside, warm light crosses the face |
camera settles, subject relaxes, motion resolves cleanly
Avoid prompt overload: too many actions in one short clip can cause jitter, warped limbs, or abrupt transitions. Give each segment one clear job.
10

Troubleshooting

Models do not appear in dropdowns

  • Confirm file location matches the loader node’s expected folder.
  • Refresh model lists or restart ComfyUI.
  • Check whether the node expects GGUF, safetensors, or split model files.

Missing custom nodes

  • Install required nodes through Manager.
  • PromptRelay must be installed by Git URL if not in your Manager list.
  • Custom Script and Extra Models are optional unless your loaded workflow has active nodes that require them.

CUDA out of memory

  • Lower resolution first.
  • Shorten video length.
  • Use GGUF variants if appropriate.
  • Disable optional LoRAs and extra loaders.
  • Use second-GPU text encoder offload only if you actually have the hardware.

PromptRelay timing feels wrong

  • Start with blank segment lengths for equal timing.
  • Make sure pipe-separated segment count matches your intended timing.
  • Use comma-separated frame counts only when you know total frames.
  • Keep each segment visually simple.

Motion is unstable

  • Use a cleaner source image.
  • Reduce how much the subject changes between segments.
  • Describe camera motion and subject motion separately.
  • Lower resolution or steps temporarily to iterate faster.

Second GPU offload fails

  • Disable or delete the Set Device node.
  • Use the safetensors loader path if GGUF offload is not working.
  • Verify the target GPU exists and is visible to your Python/PyTorch environment.
11

Sources and related links

This guide summarizes procedural points from the transcript and description. Model repository links and model license terms may change; always read the model page or repository before downloading or generating.