VIDEO RUNTIME

Install FFmpeg for Flixlar

Flixlar uses FFmpeg and FFprobe for MP4 export, burned-in captions and video metadata detection.

About the runtime -FFMPEG Video Processing ToolkitFFPMEG

Flixlar can open and edit some files without the video runtime, but MP4 export, high-quality subtitle rendering and detailed video detection require FFmpeg and FFprobe.

Install options

Automatic install

Recommended for most users. Open Flixlar → DependenciesInstall runtime.

This installs a local Flixlar runtime inside the app data folder and keeps it managed by the app.

Global FFmpeg install

Recommended if you already use other video tools and want one shared FFmpeg installation.

Shared installations can save disk space and be used by multiple apps.

Custom runtime path

Advanced option — use this when FFmpeg/FFprobe are installed in a non-standard location or when automatic detection fails.

Point Flixlar to the runtime bin folder containing the binaries.

Platform: global install

macOS compatiblemacOS (Homebrew)

Install via Homebrew:

brew install ffmpeg

If Homebrew is not detected by Flixlar, use the custom runtime path below.

Windows compatibleWindows

Download the official FFmpeg builds from the FFmpeg website. Make sure you have ffmpeg.exe and ffprobe.exe inside a bin folder and either add that bin folder to your PATH or point Flixlar to it.

Official downloads:ffmpeg.org/download.html

Linux compatibleLinux (example)

Use your distribution package manager. For Debian/Ubuntu:

sudo apt install ffmpeg

On some distros, packaged FFmpeg may be out of date — consider a distro-specific guide if you need newer builds.

Custom runtime path

Flixlar expects a runtime layout like this:

ffmpeg-runtime/
  bin/
    ffmpeg
    ffprobe

Windows:
ffmpeg-runtime/
  bin/
    ffmpeg.exe
    ffprobe.exe

Steps to configure

  1. Open Flixlar
  2. Open Dependencies
  3. Enter or browse to the runtime bin folder
  4. Click Test paths
  5. When both FFmpeg and FFprobe pass, click Use these paths

Troubleshooting

  • Point to the bin folder — not the parent runtime folder.
  • Verify both ffmpeg and ffprobe exist and are executable.
  • Restart Flixlar after changing the runtime setup.
  • On macOS/Linux, ensure binaries have executable permissions: chmod +x ffmpeg ffprobe.
  • If automatic Homebrew detection fails, use the custom runtime path.
  • If you don't want a local runtime, remove the local runtime and use a global installation instead.

Ready to go

Once FFmpeg and FFprobe are available, Flixlar will be able to export MP4s, burn subtitles into video, and detect detailed metadata.

Download FlixlarRead subtitle history guide