ComfyUI 0.44 adds ProRes export and more video finishing options

ComfyUI 0.44 expands options for finishing and exporting generated video.

**Dek:** The November 4 release adds a video-saving option in ComfyUI itself alongside updates to separately supplied upscale nodes. That split matters when a workflow must run locally or be reproduced by another editor.

ComfyUI 0.44.0 adds support for saving ProRes and choosing different chroma subsampling settings in its video-saving path. The November 4 tag also introduces a Pruna video upscale partner node and gives the Flux Video Upscale V2 partner node output targets of 1080p, 2K and 4K. The release notes list the Seedance 1.x video partner nodes as deprecated. Together, these changes affect the last steps of a video graph as well as the maintenance of older graphs that still depend on specific providers. [ComfyUI 0.44.0 release](https://github.com/Comfy-Org/ComfyUI/releases/tag/v0.44.0)

Generating a clip and delivering it are separate steps

A generative workflow often begins with a clip created for iteration. An editor may then enlarge it, correct a visible issue or put it into an editing timeline. The video saver controls how an output is encoded, while an upscaler changes the resolution of the image data feeding the saver. This distinction helps explain why a ProRes option and a 4K upscale target are different additions. A clip can be encoded as ProRes at its original resolution. A 4K file produced by an upscale step can still have temporal artifacts, flicker or fine details that vary from frame to frame. [ComfyUI release notes](https://github.com/Comfy-Org/ComfyUI/releases/tag/v0.44.0)

Chroma subsampling describes how much color detail is represented relative to brightness detail. An editor moving a generated clip into a graphics-heavy or compositing workflow may care about the edges of saturated shapes or small colored lettering. A producer delivering a simple preview may instead care more about file size and compatibility. The release gives workflows more control over that export decision. The tagged notes do not establish what combination is best for a specific editing application or codec profile.

What to test when updating an existing graph

The upscale entries are listed as partner nodes, whereas the video-saving change is listed as a ComfyUI change. Teams should check provider access, pricing and input handling separately from their local encoding setup. For a workflow that contains sensitive reference footage, knowing which node sends assets outside the machine is as important as checking the output resolution. A graph that still uses the older Seedance nodes also merits a trial run on a representative project before an upgrade is rolled out to every editor. The deprecation label establishes a change in support status without saying that every existing workflow immediately stops. [ComfyUI release notes](https://github.com/Comfy-Org/ComfyUI/releases/tag/v0.44.0)

A useful test keeps the same input clip and compares file metadata, duration, audio alignment and visible changes in several frames after export. Running the result through the actual downstream editing application can reveal a mismatch that a standalone player misses. The November update gives editors a larger set of delivery options, with the right choice still determined by where the clip goes next.