ComfyStream turns any ComfyUI workflow into a real-time video pipeline. Phase 4 hardened it for production: multimodal output, dynamic warm-up, BYOC packaging.
ComfyStream is a Livepeer-maintained extension of ComfyUI that swaps batch image generation for a real-time video loop. A ComfyUI workflow that takes an image and returns an image becomes a live-video-to-video pipeline when run through ComfyStream: video frames flow in over WebRTC, the workflow processes each frame, transformed frames flow back out at sub-second latency.Phase 4 (January 2026) hardened ComfyStream for production. The runtime added audio processing, data-channel output, dynamic workflow warm-up, and PyTrickle-based BYOC packaging. Daydream and Embody both run on ComfyStream infrastructure.The canonical install reference is docs.comfystream.org. The repository is livepeer/comfystream. The current Docker image is livepeer/comfystream, with livepeer/comfyui-base:stable as the BYOC base.
ComfyStream workflows produce one of four output types. Every workflow declares its output mode through the nodes it composes.
Mode
Input
Output
Representative node
Image-to-image (live)
Live video frames
Transformed video frames
StreamDiffusionSampler
Video-to-video
Video segment
Processed video
StreamDiffusion V2
Audio processing
Audio track from stream
Audio (pass-through or transformed)
LoadAudioTensor
Data-channel output
Audio or video frames
Structured text alongside video
AudioTranscription + data output node
A single ComfyStream container can host multiple pipelines (Phase 4 addition). Dynamic warm-up loads new workflows mid-stream without restarting the server, which lets one Orchestrator advertise multiple capabilities from one image.
SuperResolution. Real-time video upscaling. Input: standard-resolution frame. Output: upscaled frame.
AudioTranscription. Whisper-based real-time speech transcription. Two output modes: SRT subtitles burned into video, or text delivered to the application via WebRTC data channel.
ComfyStream requires workflows in ComfyUI API format, not the default save format. The default ComfyUI export includes layout metadata that ComfyStream does not parse.To export a workflow in API format:
Enable Developer Mode in ComfyUI settings.
Use Save (API Format) to produce the JSON file.
Workflows saved in the default format will not load correctly. API format is the only supported input.Place the workflow file in your ComfyStream workspace’s workflows/ directory. For Docker deployments, mount this directory as a volume. The canonical workspace layout is in docs.comfystream.org.When the workflow loads in the ComfyStream UI, the server compiles TensorRT engines for the relevant nodes. First run takes between two and ten minutes depending on the model and the GPU. Subsequent loads skip compilation.
Phase 4 added a structured-text output path that runs alongside video. The ComfyStream WebRTC connection extends with a data channel; workflows containing a data output node emit text to the browser or application that connects to the server.Use cases:
Real-time audio transcription delivered as text to a downstream application
Frame-level metadata (object labels, confidence scores) delivered to an overlay UI
Any workflow where the output is data, not video
To receive data-channel output from a browser client, use , which handles WebRTC video streaming and the data channel from the same connection.
ComfyStream requires an NVIDIA GPU. The server component runs on Linux only; Windows and macOS are not supported for the server, though the browser client runs anywhere.
Workload
Minimum VRAM
Recommended
Real-time AI (ComfyStream)
12 GB
16 GB+
VRAM headroom matters for stability. A workflow that runs at 12 GB may stutter under load that 16 GB absorbs cleanly. Source: the .CUDA 12.0+ is required. Current ComfyStream releases target CUDA 12.8 with NVIDIA driver 570.124.06 or later.
ComfyStream is itself BYOC-compatible. Phase 4 integrated ComfyStream with PyTrickle, which means the livepeer/comfystream Docker image can register directly as a BYOC capability on an Orchestrator without rewriting the workflow as a custom container.
If you want to
Use
Run a ComfyUI workflow as a real-time pipeline
ComfyStream directly
Run a custom Python model that isn’t a ComfyUI workflow
Run multiple ComfyStream workflows from one Orchestrator
ComfyStream’s multi-pipeline mode (Phase 4)
Earn fees from your ComfyStream instance
Register as a BYOC capability on go-livepeer
The ComfyStream quickstart gets you to a working pipeline in under 30 minutes. Start there.