MediaFX icon

MediaFX

Process videos, audio, and media files with FFmpeg

Actions13

Overview

This node provides media processing capabilities focused on videos, audio, images, subtitles, and fonts using FFmpeg. Specifically for the Font - List operation, it retrieves a list of available fonts filtered by type. This is useful when you want to dynamically select or display fonts in workflows that involve adding text or subtitles to media files.

Common scenarios include:

  • Listing all fonts available for overlaying text on videos.
  • Filtering fonts by categories such as Korean fonts, global fonts, user-uploaded fonts, or fallback fonts.
  • Including detailed font information to help users choose appropriate fonts for their media projects.

Example: You might use this node to fetch all user-uploaded fonts and then pass the font keys to another node that adds subtitles with those fonts.

Properties

Name Meaning
Filter Options Collection of filters to narrow down the font list:
  Font Type Select font category to list: All Fonts, Korean Fonts, Global Fonts, User Fonts, Fallback Fonts
  Include Details Boolean flag to include detailed font information (true/false)

Output

The output JSON contains:

  • success: Boolean indicating if the operation succeeded.
  • operation: The operation performed, here always "list".
  • data: An object mapping font keys to font metadata objects. Each font metadata includes properties like name, type, and description depending on the filter applied.

No binary data is output for this operation.

Example output structure:

{
  "success": true,
  "operation": "list",
  "data": {
    "noto-sans": {
      "name": "Noto Sans",
      "type": "global",
      "description": "A global sans-serif font"
    },
    "user-font1": {
      "name": "My Custom Font",
      "type": "user",
      "description": "User uploaded font"
    }
  }
}

Dependencies

  • Requires access to the local environment where fonts are stored or registered.
  • Uses internal utility functions to retrieve available fonts and their details.
  • No external API keys or credentials are needed for listing fonts.

Troubleshooting

  • No fonts returned: Ensure fonts are installed or user fonts have been uploaded correctly.
  • Invalid filter option: If an unsupported font type is specified, the node defaults to listing all fonts.
  • Permission errors: The node reads font files from disk; ensure the n8n process has read permissions for font directories.
  • Empty data field: Could indicate no fonts match the selected filter; try changing the filter or verifying font availability.

Links and References

Discussion