Version: 2.2.15 (2020-12-05)
Windows 32-bit or 64-bit supported




Version: 2.2.15 (2020-12-05)

Added option to auto-relaunch if streaming/encoding pipeline stalls

Added real-time buffering checkbox to "URL" input options

Fragmented MP4 flag changed to "-movflags frag_keyframe+empty_moov" to conform to latest guidance

Added option to write FFmpeg output to weekly rotating logfile

Added menu option to save currently open preset without prompting for filename (i.e. File > Save)

Fixed minor cosmetic bug on main page

Version: 2.2.11 (2019-12-05)

Fixed minor cosmetic bug on Encoding Status page

Fixed error with duplicate DirectShow devices

Fixed bug with non-ASCII DirectShow device names

Version: 2.2.10 (2019-08-16)

Added textbox to provide custom input commands

Added input decoder read buffer option

Added NVENC presets list

Status display expanded with restart & kill commands

File output selection now includes filename prompt

Improved bitness checking allowing for smaller install footprint

Miscellaneous minor changes

Version: 2.2.7 (2019-02-11)

Original release


Input Sources

FFmpegGUI currently supports File, DirectShow, Blackmagic Decklink, NewTek NDI or URL inputs.

Drag & Drop

Drag and drop your file(s) from your system to be processed quickly.

Auto Renaming

Prompting to rename any input file(s) with non-ASCII filenames to be compatible with command-line processor.

Output Support

You can easily export your clip(s) to a file, NewTek NDI destination, RTMP server or any other custom output supported by FFmpeg.

H/W Encoding

The included FFmpeg is built with hardware encoding support for NVENC. GUI support is experimental at this time, feedback is welcome.

32 and 64 bit

32-bit and 64-bit Windows binaries of FFmpeg included. Current binaries are based on version 3.4.5.


Save your encoding settings as file to be recalled later. Settings are formatted as an XML document.

Free license

GUI project is developed by ffmpeg fans and distributed for any usage. Non-free codecs in the included FFmpeg build may have further restrictions.


Why was this tool built? Can I request new features?

While this tool was built for personal use of the original developers, it is being shared with the public in hopes it makes FFmpeg easier to use and allow media jobs to be processed faster. The software developers work on it in their spare time, but if a particuarly useful feature is missing, let us know and we will try to add it.

Is the source code available?

The developer team decided not to publish the project on any public open-source platforms to avoid it becoming a huge time-suck for them dealing with issue reports, but if you want to volunteer development efforts to the project please contact us. If you notice a problem, please contact us and we will do our best to fix it in a timely manner.

Is this program safe? What information is sent when using it?

This program is ad-free and contains no code designed to do anything other than fulfill the obvious purpose. The only network access performed by this program is to check if the latest version is installed, this communication is unencrypted and sends no information about the user. Auto-update checks are optional, and a prompt appears on first-run asking for your permission.

What is strm.one?

The developer team just wanted a quick & easy random domain to use for personal pet-projects.