ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Overview

This node provides video processing capabilities specifically for adding subtitles to videos. It supports two subtitle embedding methods: softcoded (subtitles can be toggled on/off) and hardcoded (subtitles are permanently burned into the video). This functionality is useful in scenarios such as:

  • Adding accessibility features by embedding subtitles into videos.
  • Preparing videos for platforms that require hardcoded subtitles.
  • Combining external subtitle files with video content dynamically.

For example, a user might input a video file and an SRT subtitle file, then choose to hardcode the subtitles into the video output for sharing on social media platforms that do not support separate subtitle tracks.

Properties

Name Meaning
Video Input A valid video URL or the name of the input binary field containing the video file.
Subtitle Input A valid subtitle file URL or the name of the input binary field containing the subtitle file.
Video Output Name The name of the output binary field where the processed video file with subtitles will be stored.
Add Method Method to add subtitles: "Softcoded" (subtitles can be toggled) or "Hardcoded" (subtitles burned in).
Video Processing Options Collection of optional video settings including:
- Video Bitrate (number)
- Frame Rate (fps) (number)
- Resolution (string, e.g., "640x480")

Output

The node outputs a binary video file with the subtitles added according to the selected method. The output binary data is stored under the specified output field name. The JSON output typically contains metadata about the processed video, but the main result is the binary video file ready for further use or download.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • Relies on ffmpeg functionality exposed via an API endpoint configured in n8n credentials.
  • The node expects either URLs or binary fields for both video and subtitle inputs.

Troubleshooting

  • Invalid Input URLs or Binary Fields: Ensure that the video and subtitle inputs are correctly specified as accessible URLs or valid binary fields within the workflow.
  • Unsupported Subtitle Formats: The subtitle file must be in a supported format (commonly SRT). Unsupported formats may cause errors.
  • API Authentication Errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data.
  • Video Processing Failures: Check video options like bitrate, frame rate, and resolution for valid values; invalid parameters may cause processing to fail.

Links and References

Discussion