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 The type of media being processed; options are "Video" or "Audio".
Filter and Effects (Video) A comma-separated list of video filters and effects to apply (e.g., scale=640:480, grayscale). Only shown if Media File is Video.
Filter and Effects (Audio) A comma-separated list of audio filters and effects to apply. Only shown if Media File is Audio.

Output

The node outputs the processed media file in a binary field named as specified by the "Media File Output" property. The json output field typically contains metadata about the operation or the media, but the main result is the transformed media binary data with the applied filters and effects.

If the media is video, the output binary will be the filtered video file; if audio, the filtered audio file.

Dependencies

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

Troubleshooting

  • Invalid media input: Ensure the input media URL or binary field name is correct and accessible.
  • Filter syntax errors: Filters must be correctly formatted according to ffmpeg filter syntax; invalid filters will cause processing failures.
  • Unsupported media type: Confirm that the media type matches the selected filters (video filters for video, audio filters for audio).
  • API authentication issues: Verify that the API key credential is valid and has necessary permissions.
  • Output binary field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow.

Common error messages may relate to invalid filter strings or inaccessible media inputs. Reviewing the filter syntax and input references usually resolves these.

Links and References

Discussion