Save Frames:
PaintAPlate_SaveFrames, displayed as Save Frames, saves a batch of images as a numbered image sequence in ComfyUI’s output directory. It is designed for exporting generated shots and composited frames efficiently, using parallel file writing rather than saving every frame one after another. It supports standard 8-bit PNG, higher-precision 16-bit PNG, and half-float EXR with lossless PIZ compression. Standard PNG follows core Save Image’s pixel conversion, while 16-bit PNG provides finer tonal precision and EXR preserves values above 1.0 for high-dynamic-range work. File naming follows ComfyUI’s Save Image conventions, making the sequence easy to organize alongside other workflow exports. Parallel writing uses up to 16 workers, depending on available CPU cores; actual speed depends on your hardware, storage, image dimensions, and chosen format. This is an image-sequence exporter, not a movie encoder or a replacement for a plate-saving workflow that needs to preserve original file metadata and additional layers.
Save Frames Input Parameters:
images
Required IMAGE input containing the frame or batch of frames you want to save. Each frame becomes a separate numbered file, and the batch order determines the sequence order. The implementation expects ComfyUI’s usual image tensor layout: a batch of frames, each with height, width, and color channels. Frames are converted to floating-point CPU arrays before writing, so large batches and high resolutions can increase memory use and transfer time. The selected file format determines how pixel values are stored: PNG formats restrict values to the 0–1 range before conversion, while EXR uses half-float storage and preserves values above 1.0. No default image, minimum or maximum frame count, or image-dimension limits are declared in this node’s schema.
filename_prefix
Required STRING input that controls the destination subfolder and the beginning of each saved filename. The default is paintaplate/frames/f, which places files inside the paintaplate/frames subfolder of ComfyUI’s output directory with f as the filename prefix. The node uses ComfyUI’s save-path helper to determine the destination and starting counter, then assigns consecutive five-digit numbers followed by an underscore and the file extension. For example, if the returned starting counter is 1, the default prefix produces names such as f_00001_.png and f_00002_.png. Enter a folder and filename prefix rather than a complete numbered filename; the node adds the counter and extension itself. No minimum or maximum string length is specified in the schema.
format
Optional COMBO input selecting the file format and pixel precision, with options png, png16, and exr; the default is png. Choose png for standard 8-bit PNG files: values are multiplied by 255, clipped to the supported range, and converted to unsigned 8-bit integers without rounding, matching the conversion used by core Save Image. Choose png16 for 16-bit PNG files: values are clipped to 0–1, multiplied by 65535, rounded, and stored as unsigned 16-bit integers, providing finer tonal steps when your incoming images contain that precision. Both PNG options use the .png extension, and neither preserves values outside 0–1. Choose exr for half-float EXR files with lossless PIZ compression, preserving values above 1.0 for HDR and compositing work; half-float storage still has its own numerical precision limits, so lossless compression does not mean full 32-bit floating-point precision is retained. This setting controls file encoding, not color-space conversion.
Save Frames Output Parameters:
(none)
This node has no output sockets and does not return an IMAGE or other connectable value to downstream nodes. It is an output node whose purpose is to write files to disk. After saving, it supplies ComfyUI’s interface with an entry for each file containing its filename, output subfolder, and output-file type. These interface entries identify the saved files but are not workflow outputs you can connect elsewhere. If you also need to continue processing the same images, connect their upstream source to both this node and the next processing node.
Save Frames Usage Tips:
- Use
format = pngfor ordinary previews and deliveries that need standard 8-bit PNG compatibility. Its pixel conversion matches core Save Image, but this does not imply that every aspect of the saved files, such as metadata, is identical. - Use
format = png16when your images contain meaningful precision beyond 8 bits and you need smoother tonal steps for later grading or compositing. Saving an already quantized 8-bit image as 16-bit does not restore missing detail. - Use
format = exrwhen highlights exceed 1.0 or you need floating-point files for a compositing pipeline. PNG export clips those highlights, so select EXR before saving HDR material. - Set descriptive prefixes such as
project/shot010/relight/fto separate shots and versions. Let the node append frame numbers and extensions rather than adding them yourself. - Prepare the intended color space upstream. This node does not apply an OCIO conversion, display transform, or automatic HDR-to-display mapping, so select the appropriate conversion before saving files intended for viewing or delivery.
- For faster exports, use fast local storage with sufficient free space. The node already selects its parallel worker count automatically, up to 16 workers; there is no worker-count setting on this node.
- Test a short batch before exporting a long shot, especially for 16-bit PNG or EXR. Check the files in your intended application to confirm their precision, color appearance, dimensions, and sequence naming.
- If a large export causes memory pressure, save smaller batches. When splitting a shot across separate executions, verify the resulting frame numbering before assembling the complete sequence.
Save Frames Common Errors and Solutions:
Required input missing: images
- Explanation: The node needs an IMAGE connection to know which frames to save. ComfyUI may report a missing required input during workflow validation; the exact wording can vary.
- Solution: Connect an image-producing node to
images. For an animation, confirm that the upstream node supplies the full frame batch rather than only a single preview frame.
Invalid format selection
- Explanation: The supported choices are
png,png16, andexr. An edited workflow or API request containing another value may fail input validation. The node itself does not define a custom error message for this situation. - Solution: Select one of the three listed options. Use
png16, notpng16bitor16-bit PNG, when submitting the value through an API.
PermissionError: [Errno 13] Permission denied
- Explanation: This is a possible operating-system error if ComfyUI cannot create the destination directory or write the files. It can result from restricted folder permissions or a read-only output location.
- Solution: Use a writable subfolder inside ComfyUI’s output directory and check that the account running ComfyUI has write access. If the output directory is on a mounted drive, confirm that it is mounted with writing enabled.
OSError: [Errno 28] No space left on device
- Explanation: The destination storage may be full. Long sequences, high-resolution frames, and higher-precision formats can consume substantial disk space. Some image-writing backends may report a more general write failure instead.
- Solution: Free space on the drive containing ComfyUI’s output directory, choose another properly configured output location, or export fewer frames at a time. Check for partially written files before retrying.
EXR or PNG writing fails with a backend-specific error
- Explanation: File creation is delegated to the package’s image-writing helpers. Missing or incompatible dependencies, unsupported image data, or an encoder failure may produce an error whose exact text comes from those helpers or their libraries; their implementation is not included in the supplied source.
- Solution: Read the full ComfyUI console traceback to identify the failing library, verify the custom node’s documented dependencies, and test a single standard RGB frame. If only EXR fails, test PNG to help isolate the problem, but do not use PNG as an HDR replacement because it clips values above 1.0.
MemoryError or an out-of-memory message during export
- Explanation: The node converts frames to CPU arrays and writes several frames concurrently. A large image batch can therefore require substantial memory in addition to the memory already occupied by the incoming images.
- Solution: Reduce the number of frames per export, close memory-heavy applications, or reduce image dimensions if appropriate for your delivery. There is no exposed setting for reducing this node’s worker count.
Saved highlights are clipped or bright areas lose detail
- Explanation: This may happen without an error message. Both PNG modes clip incoming values to 0–1, so switching from 8-bit PNG to 16-bit PNG does not preserve brighter-than-1.0 HDR values.
- Solution: Choose
exrto retain HDR values. If you need a display-ready PNG, apply an appropriate tone-mapping or color-management step upstream before saving.
Saved images look too dark, too bright, or different in another application
- Explanation: This is not necessarily a write failure. The node saves the supplied pixel values without performing a color-space conversion, and different applications may interpret or display those values differently.
- Solution: Confirm the color space of the incoming images and configure the viewing application accordingly. If the delivery requires a different color space, apply the appropriate conversion before this node rather than expecting the format setting to change the image’s color interpretation.
