ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality
Join our community

Actions11

Overview

This node provides functionality to add filters and effects to media files (video or audio) using ffmpeg capabilities. It is useful in scenarios where you want to programmatically apply transformations such as scaling, grayscale, or other filter chains to media content within an n8n workflow.

Practical examples include:

  • Adding visual effects like resizing or color adjustments to videos.
  • Applying audio filters such as volume normalization or equalization.
  • Automating media processing pipelines that require consistent filter application.

Properties

Name Meaning
Media File Input A valid media URL or the name of the input binary field containing the media file.
Media File Output The name of the output binary field that will contain the processed media file.
Media File Selects the type of media to process: Video or Audio.
Filter and Effects (videoF) For video media only: a comma-separated list of filters and effects to apply (e.g., "scale=640:480, grayscale").
Filter and Effects (audioF) For audio media only: a comma-separated list of filters and effects to apply.

Output

The node outputs the processed media file in a binary field named as specified by the "Media File Output" property. The output contains the media data after applying the requested filters and effects.

  • The json output field typically includes metadata about the operation or the processed file.
  • The binary output field contains the actual transformed media file (video or audio).

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on an external ffmpeg processing backend accessible via this API.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common issues:

    • Invalid media input URL or missing binary input field can cause failures.
    • Incorrect filter syntax or unsupported filter names may result in errors from ffmpeg.
    • Mismatched media type selection (e.g., applying video filters to audio) can cause unexpected behavior.

  • Error messages:

    • Errors related to "invalid filter" usually indicate syntax problems in the filter string; verify filter names and parameters.
    • "Input file not found" suggests the input media reference is incorrect or inaccessible.
    • Authentication errors imply missing or invalid API credentials.

  • Resolutions:

    • Double-check the input media source and ensure it is correctly referenced.
    • Validate filter strings against ffmpeg documentation.
    • Confirm API credentials are properly configured in n8n.

Links and References

Discussion