Nodes/ComfyUI-CryptIO/Save Video ๐Ÿ”’
ComfyUI Node

Save Video ๐Ÿ”’

Writing finished clips to disk encrypted

By Suzu008ยทCreated 8 months agoยทUpdated 2 months agoยท 0
Save Video ๐Ÿ”’
  • video
    โ—„filename_prefixComfyUIโ–บ
    โ—„auto_downloadfalseโ–บ

    The video counterpart to SaveImageCryptIO: it writes your finished clip into ComfyUI's output directory the way the stock save-video path does, except the file that actually lands on disk is RSA-encrypted. Your browser handles decryption when it plays the result back or when you download it; anyone or anything reading the output folder directly just gets ciphertext.

    It's one of the eight nodes in the CryptIO pack, all built around the same idea: the server auto-generates a keypair at startup, your browser auto-fetches the public key, and encryption of data moving between the two happens without you managing any keys by hand.

    The inputs

    • video (VIDEO, required) - the clip to save, from upstream in your graph.
    • filename_prefix (STRING, default "ComfyUI") - same idea as the stock save-video node's prefix field, applied to the encrypted file's name.
    • auto_download (BOOLEAN, default false) - flip it on and the node triggers a browser download of the decrypted clip automatically, instead of you having to fetch it from the output folder yourself.

    There's no format or quality field here - unlike the image version, this node doesn't expose those knobs. No outputs either; is_output_node is true, so this is a terminal node in the graph.

    What this is actually protecting against

    Same honest caveat as SaveImageCryptIO: the server that saves this file also holds the private key it generated for itself, so this isn't hiding anything from whoever runs the machine. What it does close off is the network hop and the file-serving surface - ComfyUI's API has no authentication by default, and community PSAs about securing an exposed instance exist precisely because of that. If your ComfyUI is reachable over a network and someone hits the file-serving path directly instead of going through your browser session, encrypting the saved clip means they get ciphertext instead of your actual video.

    Installing it

    Comes with the rest of the CryptIO pack in one repo. Via ComfyUI Manager: search "ComfyUI-CryptIO," install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/Suzu008/ComfyUI-CryptIO, restart ComfyUI. No models - it's Python plus a bit of frontend JavaScript, so nothing heavy to download.

    Troubleshooting

    Video files are bigger and the encrypt step has more bytes to churn through than a still image does, so expect the save to take longer than it would with the stock node - that's normal overhead for this pack's approach, not a stall, though on very long clips it's worth giving it real time before assuming something's stuck. If you go looking in the output/ directory directly (say, over SSH on a remote box) expecting a normal, playable video file, you'll find an encrypted blob instead - that's expected behavior, not a bug; get the real file through the browser (preview playback or auto_download) instead.

    This is a small, early-stage pack - the README still has the untouched boilerplate from ComfyUI's official cookiecutter extension template - so there isn't a deep community troubleshooting history to draw from beyond the README and the node's own tooltips. If something behaves unexpectedly, the repo's issue tracker is the most useful next stop.

    CategoryCryptIO๐Ÿ”’

    Inputs (3)

    NameTypeDefaultDescription
    videoVIDEOThe video to encrypt and save
    filename_prefixSTRINGComfyUIPrefix for the saved encrypted file
    auto_downloadBOOLEANfalseAutomatically download decrypted video in browser

    Outputs (0)

    No outputs