Internal S2V Final Video

Spreadsheet2Video Final Video (node class Spreadsheet2VideoFinalVideo) is one of the pack's two internal nodes, and the README's advice for it is the whole article: "Ignore them. Used internally only." The node's own description is even blunter: "internal node, ignore." You're not meant to add it to a workflow by hand - the main Spreadsheet2Video node spawns it automatically at the end of its generated graph.

If you've ever looked at the main node's execution log or the expanded graph and wondered where the final result actually comes together, this is it.

What it does

While the loop runs, each row's output frame is saved to the pack's temp directory (ComfyUI/temp/Spreadsheet2Video_<prompt_id>/) as PNG files. When every row is done, Spreadsheet2VideoFinalVideo walks that folder, loads every saved frame back, and concatenates them into a single image batch - the IMAGE output you see on the main Spreadsheet2Video node. It does the same for audio: every row's saved FLAC gets loaded and stitched end-to-end into one waveform, handed out as the AUDIO output.

That's why the README can promise that raw frames live in ComfyUI/temp for lossless quality - the final node is assembling from those lossless PNGs, not from a compressed re-encode.

The inputs and outputs that matter

Technically it takes a single previous INT input (a chaining signal, not something you'd ever set) and outputs IMAGE and AUDIO. None of it is for you to touch; it's the plumbing behind the main node's outputs.

Where you'll actually meet it: error messages

You don't interact with this node, but you will run into its error handling. It's the place that enforces the "all rows must be the same size" rule: if any row's frame has a different resolution than the first, it raises "All images must be the same size", along with a helpful log hint to put a resize node before the Spreadsheet2Video Output Image node to normalize things. It also tolerates one quirk - if the very first saved frame is a different resolution (a known artifact of some loaders), it quietly drops it and starts from the second.

So: don't add it, don't configure it, just know the name. When a "same size" error pops up mid-loop, this is the node delivering the verdict - and the fix is upstream in your graph, not here.