Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > FunUI > FunUI Save Video

ComfyUI Node: FunUI Save Video

Class Name

FunUISaveVideo

Category
FunUI/Output
Author
digital-garbage (Account age: 1276days)
Extension
FunUI
Latest Updated
2026-11-03
Github Stars
0.02K

How to Install FunUI

Install this extension via the ComfyUI Manager by searching for FunUI
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter FunUI in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

FunUI Save Video Description

Saves image frame sequences as MP4 videos with NVIDIA GPU encoding and automatic CPU fallback.

FunUI Save Video:

FunUISaveVideo saves a sequence of finished image frames as an MP4 video, making it a final export step for your animation or video-generation workflow. It combines video creation and saving in one node rather than requiring separate creation and export stages. When a compatible NVIDIA hardware encoder is available, it can use NVENC, the GPU’s dedicated video-encoding hardware, to encode with H.264 or H.265. If hardware encoding is unavailable or fails, its fallback path uses H.264 encoding on the CPU with all cores, helping protect your finished generation from hardware-encoder problems. H.264 is the more broadly compatible choice, while H.265 can produce smaller files but may not play in some browsers. The node saves to ComfyUI’s output directory and displays a video preview so you can review the result.

FunUI Save Video Input Parameters:

images

Required IMAGE input containing the frames you want to save, in playback order. Connect a decoded animation frame batch, a sequence from a media-loading node, or another compatible image-producing node. ComfyUI images normally contain normalized pixel values between 0 and 1; this node multiplies those values by 255, clamps them to the 0–255 range, and converts them to 8-bit image data before encoding. The frame dimensions determine the saved video’s width and height, while the number of frames and the frame rate determine its nominal duration. For example, 120 frames at 24 fps produce approximately five seconds of video. The frames are copied into CPU memory for encoding preparation, even when GPU encoding is selected. No default image batch, frame-count limits, or resolution limits are specified in the node schema.

fps

Required FLOAT parameter controlling how many frames are played each second. Its default is 24.0, minimum is 1.0, maximum is 240.0, and interface adjustment step is 0.01. Increasing this value plays the same frames faster and shortens the video; decreasing it slows playback and lengthens the video. It does not generate extra frames or add motion between existing frames. To preserve the intended timing of an animation or an imported clip, use its intended frame rate. When including audio, choose this value carefully because changing video duration without changing the audio can affect synchronization.

filename_prefix

Required STRING parameter defining the beginning of the saved filename, with a default of FunUI. The node uses ComfyUI’s output-path helper to resolve the destination and adds a numbered suffix followed by the .mp4 extension. For example, an output may be named FunUI_00001_.mp4. A descriptive prefix helps you distinguish projects, versions, or test exports; a relative subfolder prefix such as project_a/preview can help organize files beneath the output directory. You do not need to add the .mp4 extension yourself. No minimum or maximum string length is specified in the node schema.

audio

Optional AUDIO input supplying a soundtrack to the encoding process. Connect compatible ComfyUI audio data if you want the exported video to include sound; leave it disconnected when you do not need an audio track. The node passes the supplied audio to its encoder rather than generating audio itself. For predictable results, use audio that matches the intended video timing, especially if you have changed the frame rate or frame count. The provided class does not specify how mismatched audio and video lengths are handled, so you should not assume automatic trimming, looping, or stretching. Its execution default is None, and the node schema defines no additional audio settings or limits.

encoder

Optional COMBO parameter choosing the encoding route, with a default of auto. The choices described by the node are auto, gpu, and cpu. Both auto and gpu attempt to use NVENC when it works and fall back to H.264 on the CPU if it does not; choosing gpu therefore does not require the export to fail when hardware encoding is unavailable. The cpu choice uses the libx264 H.264 encoder with all CPU cores. Hardware encoding can reduce export time on a compatible system, while CPU encoding provides an alternative when NVENC is unavailable or troublesome. This setting affects encoding, not the generation of the image frames.

codec

Optional COMBO parameter selecting the compression format for GPU encoding, with a default of h264. The choices described by the node are h264 and h265. H.264 is the safer option when you want straightforward browser playback and sharing. H.265 can produce smaller files, but playback support varies, and the node specifically warns that Firefox may not play it. This setting applies to the GPU encoder: selecting cpu, or reaching the CPU fallback path, results in H.264 encoding through libx264 even if you selected H.265. The saved container remains MP4 in either case; this parameter does not change the file extension.

FunUI Save Video Output Parameters:

None. FunUISaveVideo has no output sockets and does not return an IMAGE, AUDIO, VIDEO, or file-path value for connection to another node. Instead, it acts as a final output node: it writes the MP4 file to ComfyUI’s output directory and supplies a video preview to the interface. The preview is a display result, not a connectable output. Keep any branches that need further frame processing connected before this save step.

FunUI Save Video Usage Tips:

  • Start with encoder=auto and codec=h264 for a convenient export that uses compatible NVIDIA encoding when available and retains broad playback compatibility.
  • Use codec=h265 when smaller files matter and you know your playback software supports H.265. Test a short clip first, particularly if you plan to review it in Firefox.
  • Match fps to your source or intended animation timing. For example, 240 frames at 24 fps last approximately 10 seconds; those same frames at 30 fps last approximately 8 seconds.
  • Use encoder=cpu when troubleshooting hardware-encoding problems. CPU mode uses H.264 on all cores, so it can place a substantial load on your processor during export.
  • Connect an image sequence directly to images rather than connecting a VIDEO object. This node performs the creation-and-saving step itself, so a separate CreateVideo node is not needed.
  • Use descriptive prefixes such as project_a/test_24fps to organize exports. Let the node add the numbered suffix and MP4 extension.
  • Check audio synchronization after changing fps or the number of frames. The node does not expose controls for stretching, looping, or aligning the soundtrack.
  • Watch ComfyUI’s log for the saved filename, frame count, elapsed encoding time, and encoder used. This helps you confirm whether an export used GPU encoding or CPU fallback.
  • Allow enough system memory for the frame batch. The node prepares the entire batch as a CPU NumPy array, so GPU encoding does not eliminate CPU-memory requirements.
  • Workflow metadata is passed to the encoder when metadata saving is enabled and the information is available. If you need an export without that workflow information, use ComfyUI’s global metadata-disable setting; this node has no separate metadata switch.

FunUI Save Video Common Errors and Solutions:

“Saved as H.264 on the CPU instead.”

  • Explanation: This is the documented fallback alert, preceded by the specific reason hardware encoding could not be used. It indicates that the encoder fell back to CPU H.264 rather than abandoning the export; it is not, by itself, a failed-save message.
  • Solution: Check the output directory and preview first. If you want GPU encoding, review the reason before this message and check that your environment provides a compatible NVIDIA GPU, NVENC support, and working drivers. Otherwise, continue with CPU encoding.

Missing or incompatible images input

  • Explanation: This is a troubleshooting description, not an exact error string from the supplied source. The node requires IMAGE data and immediately performs image-array operations on it. A missing connection or an incompatible type, such as a VIDEO object or latent samples, can prevent execution.
  • Solution: Connect a valid IMAGE batch. Decode latent samples into images first, or use the frame output from a compatible media-loading node. Remove an unnecessary CreateVideo step if it prevents you from connecting frames directly.

Empty or incorrectly shaped frame batch

  • Explanation: This is a possible input-data problem rather than a quoted node error. The implementation reads frame dimensions from the image array and passes that array to the encoder. An empty batch or data that does not follow ComfyUI’s usual batch, height, width, and channel layout may fail during preparation or encoding.
  • Solution: Preview the images upstream and confirm that at least one valid frame is present. Use standard ComfyUI IMAGE outputs and ensure your frame batch has consistent dimensions.

Memory allocation failure during frame preparation

  • Explanation: The exact message depends on your system and underlying libraries. The node converts the entire image batch to 8-bit CPU image data before encoding, so a long or high-resolution sequence can exhaust available memory. Choosing GPU encoding does not bypass this preparation.
  • Solution: Reduce the frame count or resolution, close memory-heavy applications, or divide the sequence into shorter exports and combine them afterward with a video editor.

File could not be written

  • Explanation: This is a general troubleshooting description; the supplied class does not define a custom file-writing error message. Insufficient disk space, an unwritable destination, or an invalid path can stop the MP4 from being created. Encoder fallback does not resolve storage problems.
  • Solution: Check free disk space and output-folder permissions. Test again with the default filename_prefix=FunUI to rule out a problematic custom path.

H.265 MP4 does not play in the browser

  • Explanation: This can be a playback-compatibility issue rather than an encoding failure. The node explicitly warns that Firefox may not play H.265, even when the MP4 was saved successfully.
  • Solution: Export again with codec=h264 for broader compatibility, or open the existing file in a player that supports H.265. Check the saved file before assuming the generation was lost.

CPU encoding also fails

  • Explanation: The source provides a fallback for GPU-encoder problems, but it does not guarantee that every export will succeed. Invalid frame data, storage problems, or an unavailable or failing CPU encoder can still prevent saving. The precise error depends on the encoding implementation and environment.
  • Solution: Read the full encoder error in ComfyUI’s log, then test a short, standard-sized image batch with encoder=cpu and the default filename prefix. Check the image data, storage, and your installation’s video-encoding dependencies according to the reported error.

FunUI Save Video Related Nodes

Go back to the extension to check out more related nodes.
FunUI
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.