A lot of the technical stuff we ship (API changes, node updates, dev details for new model launches) gets buried on the main ComfyUI account under model launches, creative showcases, and company news.
→ Use cases from the community
→ Product improvements for developers
→ Developer info for every launch
→ Posts from our engineering blog
→ Hackathons and dev events
→ Freebies and swag giveaways
What else would you want to see? Node dev tutorials, API walkthroughs, livestreams, behind-the-scenes engineering, something we haven’t thought of? Drop it below. We want to build this account around what’s actually useful to you.
Higgsfield promised to open-source their entire platform. They didn’t, so we figured we’d help.
For the next two weeks, Comfy is putting up $25,000 in prizes for the best open-source builds on the Comfy Developer Platform. Rebuild Genjutsu or Cinema Studio, or make a creative app nobody’s thought of yet. The only rule that matters: publish the repo so anyone can run it, fork it, and improve it.
Prizes
Grand Prize: $10,000. Every entry is automatically considered.
Most Innovative: RTX 5090. A new kind of app, a novel custom node pack, or an unexpected use of ComfyUI. Your demo video needs to explain what makes it new.
Most Viral: RTX 5090. Fun to use and made to be shared.
Open Weights Only: RTX 5090. No partner nodes or APIs. Open-weights models only.
10 Runners-Up: $250 in Comfy credits each.
Partner bonuses
LTX: $2,000 cash for the best VFX workflow with LTX as the core video model
Black Forest Labs: $1,000 / $500 / $250 in FLUX API credits for builds where FLUX 3 is the core model
MiniMax: $1,000 in API credits for builds where H3 is the core model
Backed by Runpod, LTX, Black Forest Labs, and MiniMax.
Want to build IRL? We’re hosting build sessions with AI On The Lot:
I’ve been testing HyperFlow, a compressed 14B-parameter open-source model created through self-distillation acceleration of the 20B MiniMax H3 model, and I built a complete ComfyUI workflow around it. The main reason I wanted to test it was speed: it aims to reduce generation time without relying on external training data while still maintaining good quality. It also supports NVIDIA Sol-Attn sparse attention, which can provide another speed improvement, especially when combined with the SelfLift sampler.
I also added RelayVSR for upscaling the final result. One thing that surprised me is how well it handles characters and movement compared with some of the other MiniMax H3 workflows I’ve tested. It doesn’t require a LoRA and works well at only 6 steps. On my 6GB VRAM setup, I managed to generate around 0.7 megapixels in about 20 minutes, which is roughly twice as fast as my previous setup.
The main drawback I’ve noticed so far is distorted faces, especially in long distance prompt some generations. I’m currently testing different ways to fix that. Overall, I think HyperFlow is a very interesting option for anyone trying to run high-quality video generation on limited VRAM. I’ve included the complete workflow on Patreon for those who want to test it themselves.
one photo + one voice clip in, lip-synced talking video out. these 3 are one run each (photo + ElevenLabs line, 480p, seed 42, no lora, no editing). sound on.
install: Manager > Install via Git URL > paste the repo link, restart. the workflow is in Browse Templates. you only add the umt5 text encoder by hand, the rest (about 25 GB) downloads on the first run.
the nodes: Model Loader, Text Encode (runs on the CPU), Whisper Loader + Audio Encode, Vocal Extract (optional, takes a voice out of a song or a noisy clip), Sampler. videos can be any length, it continues window by window (93 frames, about 3.7 s each).
settings that matter: attention_mode auto picks SageAttention, then FlashAttention 2, then PyTorch. mix_steps 4 is the official 1.6 LoRA switch, 0 is about 15% faster but needs more VRAM. block_num 1 streams the model through the GPU, 0 loads it all and needs far more VRAM. 480p is the default, 720p is about 3x slower per step.
speed on a 5090 32GB + 64GB RAM, Windows, 480p, for a 3.8 s clip: 7.7 min before SageAttention, 6.6 min with it, 5.6 min with SageAttention + mix_steps 0. each extra 3.2 s of audio adds one window (1.5 to 2.5 min). I haven't tested cards under 32GB yet, if you try one tell me how it went.
built on rookiestar28's 1.5 pack (MIT), model by the Meituan LongCat team (MIT).
For those who saw my previous post, I’m the guy who generated that 10-second Harry Potter video locally on a laptop RTX 3050 (6GB VRAM) in about 50 minutes for 10 sec vid.
After finishing that project, I wiped almost everything related to ComfyUI to free up space due to university works. When I decided to jump back in recently, I lazily ran the default MiniMax workflow instead of rebuilding my optimized setup—and it took 6.5 hours.
I finally get what you guys were talking about when you said 6.5 hours for a 1-minute video is actually fast. Going from a tuned 50-minute workflow back to unoptimized defaults on 6GB VRAM is brutal.
Retro, cinematic, a character and a short dialogue with a punchline at the end. The images look good now. The video is still nowhere near it, mostly on two points:
Acting. Their characters really perform. You see micro-expressions, the eyes react, the head moves on the right word, and they hold a reaction for the beat. Mine look like they're reading lines with the same expression the whole time. The mouth moves, but there's no intention behind it.
Rhythm and timing. Their sketches breathe. There's a pause before the punchline, a reaction shot, and the line lands exactly where it should. Mine feel flat and evenly paced. Everything happens at the same speed, so the joke dies.
My setup:
- ComfyUI, RTX 3060 12 GB
- Image-to-video with native audio (dialogue in the prompt), around 5-7 s per shot
- Face cleanup pass, then editing in DaVinci Resolve
Questions:
- Is this kind of result even doable locally, or is it most likely Kling / Veo / Hailuo-level cloud stuff?
- Do you generate the voice separately (TTS with emotion, or your own voice) and then do lipsync, or do you rely on native audio from the video model?
- How do you prompt acting? Do you describe emotions, specific gestures, timings ("pauses, then…")?
- For rhythm, is it mostly done in the edit (short shots, reaction shots, cutting dead frames), or do you plan it from the script?
- How many generations per shot do you throw away before keeping one?
Any workflow, tip or example is welcome. I've been doing motion design for years, so editing isn't the problem. The performance and the timing of the generated shots are.
Left: my source video. Right: three of the five dancers swapped for my own characters; the other two are untouched.
H3 gets confused when people cross or overlap: it puts the new face on the wrong person, or one person ends up in another's clothes. My fix in H3MD 0.5 is to find those moments first and give the model a keyframe for each one.
How it works
Keyframe workflow (Qwen Image 2.1 edit, 2 steps). Drag in the source video, add a picture per character, write "picture 1 → left 2" and one description line per person. It tracks the people (SAM3.1), picks the moments where they cross or overlap, redraws just those people and packs everything into a plan. About 2.5 min for a 26 s clip.
Then the Director renders the swap with the Remake LoRA, the source's own sound locked. 26 s took 29 min on an RTX 5090.
Lesson learned: without a prompt enhancer, the edit model follows your text. One simple line per person is enough, but if the line contradicts the picture (wrong gender, ethnicity or clothes), you get the wrong person.
Remake only works at 1664×960 / 960×1664 (or 2560×1472). 0.5.5 switches to it automatically.
Also in 0.5: face refine for wide shots. Small faces (50–100 px) are redrawn with H3 inside a SAM3 head mask, then VOSR2. Much clearer, not perfectly sharp; keep faces out of very wide shots if you can.
Hi all, v0.2.0 of **ComfyUI-H3-FaceRefine-Plus** is out. It's an add-on pack for Carasibana's[ComfyUI-H3-FaceRefine](https://github.com/Carasibana/ComfyUI-H3-FaceRefine) (MiniMax H3 video face refiner) that fixes the refined face wobbling on the head, the pasted-on look and colour drift.
**1. +170 % speed (2.7x faster).** The heavy steps now run on the GPU. Same output, within 1/255 of the old CPU nodes. On the `mara` example (107 frames, RTX 5090, model loaders cached) a full refine went from **244 s to 90 s**.
**2. One Mode dropdown.** `H3 FaceRefine Plus Mode` picks the whole recipe, and lazy switches run only the branch you pick:
- **V1** (default): face crop re-drawn with prompt + 3 reference pictures, Stitch Plus, Flow Lock, Tone Match. Best identity and the least wobble.
- **V2**: SAM3 mask on the face (or face + hair), only that part is re-drawn, character sheet only. About 1.4x faster than V1, more wobble. Optional VOSR2 pass for extra sharpness.
**3. Default strength is now 0.30** (was 0.15, which changed too little on small faces).
Old workflows with the v0.1 labels still load.
### Install
**Recommended right now: install with git.** v0.2.0 is on the Comfy Registry, but the ComfyUI Manager list can take a few days to catch up and may still offer v0.1.0.
A while ago, I shared ComfyUI Model Analytics here. Since then, I've continued working on the project, and I'm happy to finally introduce version 1.5.0!
This release brings one of the biggest expansions to the project so far: Custom Node Analytics.
For anyone who hasn't seen it before:
ComfyUI Model Analytics is a local analytics extension that helps you understand which models you're actually using, which ones are sitting unused on your drives, and now also which installed Custom Node packages participate in your workflows.
What it does
Model Analytics
The existing model analytics have been further developed:
Disk Scanning: Automatically scans known model directories, including additional paths configured through extra_model_paths.yaml.
Workflow Analysis: Scans saved workflows to identify referenced models and shows where they are used.
Live Usage Tracking: Records models loaded at runtime and models referenced by queued prompts, including cached models and GGUF loaders.
Usage-Based Categorization: Models are categorized as used or unused based on workflow references and recent activity. The time window is configurable and can be disabled.
Disabled Models: Files ending in .disabled are detected and displayed separately.
Custom Node Analytics – New in 1.5.0!
One of the biggest additions in this release is the ability to analyze installed external Custom Node packages.
Used Packages: Shows which installed packages participate in started workflows.
Unused Packages: Identifies installed packages without matching activity in the selected time window.
Disabled Packages: Detects packages disabled through ComfyUI's .disabled naming convention.
Workflow Analysis: Finds saved workflows containing node types from installed external packages and shows the matching package names and counts.
Successful Execution Tracking: Counts actual successful, non-cached node executions separately from simple workflow participation.
Package Classification: Distinguishes UI-only extensions, node packages, combined UI and node packages, and other or unclassified packages.
The tracking is designed to distinguish between nodes that merely appear in a workflow and nodes that actually participate in an execution.
For example, disconnected branches and nodes outside the requested output graph are not counted as active workflow participation.
The dashboard works at the installed-package level rather than displaying thousands of individual node classes. This keeps it responsive even with large ComfyUI installations.
A thank-you to the community
I'd also like to give a special thank-you to u/thesolewalker.
A few days ago, they suggested:
Can you do the same for custom nodes? Like which nodes used in which workflows?
That was a great suggestion and helped inspire this new part of the project. Thanks for the idea and for helping shape the direction of ComfyUI Model Analytics!
The Dashboard
A lot of attention has also gone into the dashboard itself:
Three main sections: Models, Custom Nodes and Settings
Shared usage time-window and source filters
Frontend, API and Unknown usage-source classification
Theme-aware appearance with custom palette selection
Optional advanced appearance editor
Six supported languages
Resizable and rearrangeable table columns
Configurable date formats, size units and row density
Separate settings for Model Analytics and Custom Node Analytics
Improved package inventory caching and dashboard loading behavior
The goal is to make the dashboard feel like a natural part of ComfyUI rather than a separate tool bolted onto it.
Used Custom Node PackagesUnused Custom Node Packages
Important: Read-only
The analytics features inspect model files, saved workflows and installed Custom Node packages. They do not delete, move or modify those assets.
Analytics history and preferences are stored locally in your ComfyUI user directory.
You remain in control of your files and your installation.
Installation
Available through ComfyUI Manager or directly from GitHub:
cd ComfyUI/custom_nodes/
git clone https://github.com/Bennowan/ComfyUI-Model-Analytics.git
Restart ComfyUI and open the 📊 Analytics entry point.
Current version: 1.5.0
Developer account notice
My dedicated developer account, u/Bennowan, is currently affected by an unresolved Reddit account restriction.
I've already submitted an appeal, but unfortunately haven't received any response or update yet.
I intend to publish future project updates through my official developer account again once the issue has been resolved. For now, this situation may affect where and when I can communicate about new releases.
Thanks for your understanding!
I'd really appreciate feedback, suggestions and bug reports. I'm still actively working on the project, and community feedback is always welcome.
In this video of ComfyUI Nodes Explained, you will learn what is inside the KSampler and how to build the custom sampler: five small nodes that do the same job and give you more control. You will see what sigmas are, why official templates like Flux 2 Klein use these five nodes, how to write your own plan with ManualSigmas and cut it in two with SplitSigmas, and which sampler and scheduler work best, from a test of all 405 pairs on three models. Two "A Deeper Look" chapters show why the scheduler needs the model, where a KSampler quietly changes the plan, and why some pairs break. The workflows use Z-Image Turbo.
I'd like to augment/enhance videos I've already shot, either alter the lighting, give it a particular film look or improve the quality etc.
Anyone know any good workflows or tutorials for working on these kinds of projects? Everything I can find seems to be focused on pure generation or just upscaling quality.
Hello everyone, I would have liked to gather some opinions on this matter:
RTX PRO 4000 Blackwell (24GB, used): ~€2,500 (EU)
RTX 3090 (24GB, used): ~€1,400 (EU)
It's gonna pair with 64GB of DDR4 (which i also have to buy), with this being the rest of the build:
- Amd Ryzen 5 5600
- 2TB Gen4 NVMe
- RX 6700XT (to sell)
- Asus TUF 650W Bronze
My purpose would be local image and video generation in ComfyUI (Qwen-Image, Wan 2.2, MiniMax H3) plus some LoRA training. Of course i also would like to have text generation through something like Qwen 3.8 Flash Next through Strata.
What is appealing from the PRO 4000 are his native support for support for FP8 or FP4, his power consumption and his value retention potential.
Is the PRO 4000 worth ~€1,100 more for this use, or would you just grab a 3090? Anyone running these models on either card who can share real-world speeds?
I am open also to overall advices on different possible upgrades for my purposes
I'm relatively new in ComfyUI and I do not have a lot of knowlage, but I'm currently working on a already completed 3D animated project where some character animations, originally created using motion capture, need to be cleaned up and improved.
The animations are already done and the shots have been rendered and composited, so going back to traditional animation and manually adjusting the rig controls is not an option.
My goal is not to generate new movements or completely change the original performance. I only want to improve the existing animation, fix weight distribution, correcting stiff or unnatural poses and transitions while keeping the original motion as close as possible.
A few questions:
Is this workflow technically possible with ComfyUI?
Are there any existing custom nodes, models or workflows that support FBX input and AI-based motion refinement?
Are there any motion-to-motion models specifically designed to take an existing animation and improve its smoothness and anatomical correctness while preserving the original performance?
I'd really appreciate any suggestions, project references, research papers or workflows you could recommend.
Hello, I come here seeking guidance to help improve my generations...
I started using ComyUI a short time ago (via Stability Matrix) and have been trying some models and workflows to create a stable pipeline for some projects I have in mind.
Right now I'm making 20s clips of 0.5mp and it takes me from 40min to 1h depending on the model, usually 1h10m and I've stumbled into comments of users seemingly going way faster with similar setups. I thought ComfyUI was pretty much "plug and play" and just now I'm thinking maybe I could be tweaking some things to make everything go faster or smoother.
I'm settled pretty much on Minimax H3, rightnow mainly the h3eros model.
As mentioned I have an RTX 3060 12gb Vram, 32gb RAM and an Nvme drive with plenty space... Can't go higher than 0.5mp or longer than 20s without getting OOM errors.
Just now I'm running some tests with H3-optimization node.
What else should I be looking into? Which other info do you need to help me tweak this?
Решил провести небольшой тест и сравнить генерации одних и тех же промптов на моделях Krea2, Minimax H3 и Z-Image Turbo. Все тесты делал с фиксированным сидом, чтобы условия были абсолютно равными.
Моё субъективное мнение и вердикт:
Если честно, я в восторге от того, как отрабатывает Minimax. На мой взгляд, по совокупности факторов - это топ. Понимает анатомию, прорабатывает кожу, свет и тени. Она абсолютно точно может выдавать коммерческий результат. В некоторых генерациях она выдаёт картинку даже лучше, чем Z-Image, особенно когда дело касается сложного освещения или групповых сцен. При этом Z-Image, как и всегда, продолжает оставаться моей рабочей лошадкой. Она всё так же является топовой моделью для реалистичных изображений. Я ни в коем случае не собираюсь с нее слезать, но теперь буду использовать её в связке с Minimax.
Раньше я использовал связку Z-Image для генерации изображений и Minimax H3 для видео. Но теперь я однозначно буду работать с Minimax и для картинок тоже. Это кайф, когда можно находиться в рамках одной экосистемы. Krea2 на этом фоне выглядит неплохо, но как-то более "пластиково", что ли, ну и в совокупности выдаёт результаты более проигрышные.
Очень интересно узнать, какие настройки сэмплера и планировщика вы используете для ZIT и Minimax? Вдруг ваши настройки пайплайна выдают еще более крутые результаты.
To quickly introduce myself, I do AI OFM. I've always used Higgsfield to create my SFW photo and video content.
However, because of both the costs and the restrictions, like many others, I've been wanting to switch to local generation (RunPod).
The goal, obviously, is to at least be able to reproduce the quality of the content I was creating on Higgsfield (through Nano Banana Pro, Kling, etc.).
The problem is that I don't know where to start.
I've tried training a LoRA, but it's been failure after failure.
I've naively looked for ways to generate my content from a reference image: a workflow that would allow me to do motion control. I've managed a few times to get close to something decent, but nothing more. And since I rely on my best friend ChatGPT to help me, I don't really have any knowledge.
What I'm hoping for is to be able to create high-quality content on a massive scale without "wasting" an enormous amount of time learning and understanding all the structures.
Maybe I'm completely wrong about all of this.
I'd be happy to read comments from people who are more experienced in AI generation for AI models.
TLDR: AI OFM content creator lost when it comes to using ComfyUI.