ComfyUI Image to Video V2 icon

ComfyUI Image to Video V2

Convert images to videos using ComfyUI workflow
Join our community

Overview

This node converts a single input image into a video using a ComfyUI workflow. It uploads the image to a ComfyUI server, runs a user-defined workflow (provided as JSON) that processes the image and generates video output, then retrieves the resulting video file.

Typical use cases include:

  • Creating short videos or animations from static images.
  • Automating video generation workflows with custom ComfyUI pipelines.
  • Integrating ComfyUI's image-to-video capabilities into larger automation scenarios in n8n.

For example, you might provide an image URL or base64 data, specify a ComfyUI workflow JSON that defines how to transform the image into a video, and get back a video file encoded in MP4, GIF, or WebP format.

Properties

Name Meaning
Workflow JSON The ComfyUI workflow definition in JSON format. This JSON must contain a LoadImage node.
Input Type The type of input image provided: URL, Base64 string, or Binary data from previous node.
Input Image The image data as a URL or base64 string (shown only if Input Type is url or base64).
Binary Property The name of the binary property containing the image (shown only if Input Type is binary).
Timeout Maximum time in minutes to wait for the video generation process before timing out (default 30).

Output

The node outputs one item containing:

  • json object with:

    • mimeType: MIME type of the generated media (e.g., video/mp4, image/gif, image/webp).
    • fileName: The filename of the generated video or animation.
    • data: Base64-encoded string of the video/image content.
    • status: Status information returned by ComfyUI about the generation process.

  • binary data under the property data containing:

    • fileName: Filename of the video.
    • data: Base64-encoded video content.
    • fileType: Always "video".
    • fileSize: Approximate size in kilobytes.
    • fileExtension: File extension such as mp4, gif, or webp.
    • mimeType: MIME type matching the video format.

This allows downstream nodes to consume the video either as JSON data or as binary data.

Dependencies

  • Requires access to a ComfyUI API endpoint with an API URL and an API key credential.
  • The node makes HTTP requests to the ComfyUI server to upload images, queue workflows, and poll for results.
  • The ComfyUI workflow JSON must be valid and contain a LoadImage node with an image input.
  • The node depends on n8n helper methods for HTTP requests and binary data handling.

Troubleshooting

  • Invalid workflow JSON: If the workflow JSON is malformed or not a valid object, the node will throw an error. Ensure the JSON syntax is correct and the structure includes a LoadImage node.
  • No LoadImage node found: The workflow must contain a LoadImage node with an image input; otherwise, the node errors out.
  • Binary property not found: When using binary input, if the specified binary property does not exist or no image-type binary data is found, an error is thrown.
  • Unsupported media type: Only image MIME types are supported for input. Providing non-image binary data causes an error.
  • Video generation timeout: If the video is not generated within the specified timeout (default 30 minutes), the node throws a timeout error.
  • API connection issues: Failure to connect to the ComfyUI API or missing/invalid API key will cause errors.
  • No video outputs found: If the workflow completes but no video or animation files are produced, the node reports an error.
  • File not found: If the generated video file cannot be retrieved from the ComfyUI server, an error is raised.

To resolve these issues:

  • Validate your workflow JSON carefully.
  • Confirm the input image is accessible and correctly specified.
  • Check API credentials and network connectivity.
  • Increase the timeout if processing takes longer.
  • Inspect ComfyUI logs or UI for workflow execution details.

Links and References

Discussion