Open-sourced AI filmmaking tool Inline Studio built on ComfyUI

A developer in our community just shipped a feature that makes AI video worse on purpose. u/nomadoor built a video stabilizer node for ComfyUI. This week they added the opposite: artificial camera shake presets, walking, action, with optional motion blur layered in. Their reasoning, in their own words: AI-generated videos can be a bit too smooth sometimes. Real cameras sit on human shoulders. They drift, they breathe, they overshoot a pan. Take that away and something in the viewer stops believing. My favorite part is what happened in the comments. Someone pointed out that a real camera operator's handheld shot never rolls on the lens axis, so believable shake needs a level horizon. A day later the node had a Lock Horizon option. That's a filmmaker's eye correcting an engineer's model of imperfection, in public, in a day. Every model race is running toward cleaner motion, higher fidelity, fewer artifacts. And here's the craft pointing the other way: past a certain point, perfect motion is what gives it away. No metric catches that. A human does, which is exactly why we build Comfy as a graph you direct instead of a button you press. Go show love here: https://lnkd.in/g8FVqzeF

A solo developer just built a search engine for ComfyUI workflows because he had 1,300 and couldn't find any of them. Greg Ohlsen posted the tool to r/comfyui last week, where it picked up 119 upvotes and 34K views in a few days. It runs as a standalone desktop app, indexes your local workflow library, and lets you search by what a workflow does, not what its filename happens to be. Type "generate video from an image" and it finds the workflow. It also previews the node graph without opening ComfyUI, scans YouTube, CivitAI, GitHub, and Reddit in real time for new workflows, and filters by the custom node packs you have installed. The thread is the part I keep watching. A commenter asked for node-pack filtering on launch day. Greg shipped it the same afternoon and posted the update under the same thread. That's the loop you don't get to design. Someone builds the thing they need, the community asks for a feature, and a working version ships before the day is over. ComfyUI ended up with 60,000 community nodes for exactly this reason. The platform grows on what the community ships: https://lnkd.in/gWg-Uq2a

Most video models give you one image to lock a character. HappyHorse 1.1 takes nine. The Reference-to-Video node maps characters and scenes to separate reference images, then lets you direct them through a timestamped storyboard with per-character dialogue. Multiple characters stay visually distinct, and the backgrounds can change without bleeding into the character references. For anyone doing narrative or brand work, that's a different class of control than picking one frame and hoping. Then there's the audio. It's a single unified Transformer, so text, image, video, and audio tokens all run through the same attention pass, and the output comes out with audio already timed to the visual instead of stitched on after. 1.1 ships as three nodes in ComfyUI: Text-to-Video, Image-to-Video, and Reference-to-Video. All three output up to 1080p with audio included. They're in the Node Library now, or load a template to see how it's wired. I'm so hyped to see what people do once a single shot can hold this many characters.

One user was struggling to figure out his laggy workflow last week. Instead of going to Google, he went straight to our subreddit. Within minutes, our community was writing him a tutorial. Zaphielll's screenshot showed a workflow that had become a wall of identical nodes, each generating a different pose with a different LoRA. His UI was lagging hard. The post asked one question: "Is there a trick for repetitive task?" What came back was a real engineering tutorial, written by people he'd never met. The thread filled with suggestions for loop nodes, subgraphs, the Comfy API, wildcards, custom Python nodes. One commenter pasted a working multiplex node example with full code. The running argument was that writing your own custom node has become genuinely easy now that AI can help. Soon after, Zaphielll came back with an update. He'd condensed the workflow into a few nodes by writing two of his own. This is what makes ComfyUI work. There was no support ticket queue. The community gave him a tutorial on their own time, for free, because that's how this group shows up when one of them needs help. This is the part of running ComfyUI I'm most proud of. Anyone can fork the code, but no one can fork the community we've built around it.

Upscaling is the AI video problem the studios I talk to flag most. ComfyUI now has a community-shipped fix. The bottleneck for production work is upscaling that holds consistency across hundreds of frames and dozens of styles. The paid tools handle some of it and break on enough cases that studios have been waiting for a better answer. A few weeks ago a creator with the handle Zlikwid published an open-source LTX 2.3 upscale IC-LoRA. It's free, the weights are open, and it runs inside any LTX 2.3 ComfyUI workflow. The pattern matters more than this one release. The gaps commercial AI tools leave open keep getting closed by someone in the community within months, sometimes weeks. The studios picking up ComfyUI are betting on the layer underneath, not on a single vendor. That's why open keeps winning in production. https://lnkd.in/gnUarrVG

The main reason we have four million active users on ComfyUI is because we’re open source. Here’s why that was the plan from day one. ComfyUI started as a tool one of our cofounders built because existing AI tools didn’t give enough control. At the time, platforms were moving toward closed systems. You could generate results, but you couldn’t really see what was happening under the hood. So if something didn’t work the way you wanted, you were stuck. We didn’t want to build another black box. We believed creative tools should belong to the people using them. You should be able to run them locally, inspect the workflow, modify the pipeline, and push them as far as you want. So we ended up making it open source and that turned out to be the best business decision we ever made. Being open source meant the community had stake, and as our community grew, so did ComfyUI. Today there are 160K people in the ComfyUI subreddit and 51K in Discord. Developers are shipping custom nodes. Artists publicly sharing workflows. People debugging things at midnight with strangers on the internet. We didn’t spend a single dollar on marketing to grow to four million users. We let people build, and that scaled faster than any campaign could.

One of our users spent a month and a half building a video tool full-time, then gave it away for free. They go by WhatDreamsCost, the tool is LTX Director, and version 2.0 turns it into a real video editor inside ComfyUI: trim and extend clips on a timeline, regenerate any single segment that comes out wrong, inpaint audio, drag in IC-LoRAs. Another community member, nghtdrp, contributed the IC-LoRA implementation, which WhatDreamsCost cleaned up and shipped to everyone. We didn't build any of this. That's the part closed platforms can't copy. When the tool belongs to the people using it, they build what no company would prioritize, then hand it back to everyone for free. 532 upvotes, and a thread full of people asking the LTX team to hire them. So much of what people build on ComfyUI comes from outside our team, from people like WhatDreamsCost working in the open and a lot of it is work we'd never have gotten to.

A community member shipped a tool in 9 hours that would cost a $10M startup weeks of meetings to approve. Here's how it happened. One of our ComfyUI users was running into a problem with cloud GPU services. Most of them don't give you terminal access, which meant he couldn't use AI coding assistants with his workflows. So he built a tool that embeds an AI assistant directly into the ComfyUI browser interface with full access to edit, connect nodes, and run previews in real time. He posted his work to ComfyUI’s subreddit at midnight. By morning there were: 333 upvotes Dozens of people testing it and offering ways to secure the feature Others already asking how to adapt it for local models instead of cloud APIs Nine hours from post to active iteration with real user feedback A single person with a specific problem shipped a solution, got it in front of thousands of builders, and had meaningful feedback before most funded teams finish their standup meeting. 160,000 people in our subreddit, and we're incredibly grateful for every individual in this community that continuously builds alongside us.

A new ComfyUI user just built the best onboarding tool we've ever seen and gave it away to 160K people for free. ComfyUI is a complex tool. Beginners often get stuck trying to figure out what each node does and which ones they actually need. This user was stuck too. So they built the "ComfyUI Beginner Bible", a searchable guide that explains every core node in simple English, right inside the interface. They posted it to our subreddit 2 days ago and received the much deserved praise. 193 upvotes. Comments calling it "essential" and raving about how it should be a part of our official guide. This is why we're so grateful for our community. We've been focused on making ComfyUI powerful for professionals, and our users step in to make it accessible for everyone else. Someone brand new to the platform just shipped a feature that made ComfyUI better for thousands of people. That's what a community of 160K builders in an looks like. They don't wait for us to fix what's missing, they just build it. Shoutout to Yedp, link to the Github here: https://lnkd.in/gbHzhEzH

Zafer Söğütcü took something that usually needs more than 20 nodes in ComfyUI and got it down to two. If you've ever built a text-to-video workflow, you know how fragile it gets. You wire up the checkpoint loader, the CLIP encoder, the latent setup, the sampler chain, the VAE decoder, and then the whole reference-image side on top of that. It runs fine on your machine, but the moment you share it, a few nodes are named differently or missing and the whole thing falls over. Zafer's answer is a project called ComfyUI-ZFRNodes, and it folds most of that wiring into two custom nodes. The first one, the Simple Image Generator, packs the entire text-to-image and reference-based image-to-image pipeline into a single node, so you're not hand-wiring the loader, encoder, and sampler chain anymore. The second, the Story Frame Generator, takes plain text and spits out per-frame JSON that routes through the chain on its own. It all runs locally, and if you want, you can hook it up to Ollama to have the model write your prompts. What I like is that he didn't pile on new features, he just took the messy parts everyone keeps rebuilding and tucked them behind something cleaner. The complexity is still under there, you just don't have to deal with it anymore. https://lnkd.in/gsH76pmv