FFmpegFreeUI (3FUI): a Windows FFmpeg front end that expects you to know your parameters

Who 3FUI is actually for, and who it is not for

The README is unusually direct about this: 3FUI is not a one-click tool for complete beginners, it targets users who already understand basic parameters. Beginners can get started, but there is a learning curve, and the project frames its ceiling as the reason to climb it. If you want software that picks a bitrate for you, this is the wrong download.

The audience is narrower than that in one more way. The interface is Simplified Chinese only, and the README states there are no plans for any multilingual feature; anyone who wants another language is invited to fork and maintain the strings under the MIT licence. So a non-Chinese-speaking editor who wants a Windows ffmpeg shell has to weigh a translation project against the alternatives.

What the project does offer that audience is a parameter surface. The README lists full free transcoding with arbitrary hand-written arguments, presets as the underlying logic so schemes can be shared, parameter names printed next to most fields, batch task queues with no fixed limit, real-time remaining-time and output-size estimates, pausable tasks, colour management options, subtitle-burn-in options, and convenience hooks for AviSynth and VapourSynth. It also bundles simple muxing and merging, performance monitoring, ffprobe and ffplay invocation, and a quality assessment view.

No bundled codecs: 3FUI drives whatever ffmpeg you supply

This is the design decision everything else follows from. 3FUI contains no codecs. You place an ffmpeg binary in the program directory or add it to the system PATH, and 3FUI calls it. The README's argument is that this keeps performance at the current level of ffmpeg and removes the need to update parameters inside the GUI: when ffmpeg updates, you swap the binary and keep working.

The trade-off is real. A user who cannot obtain a working ffmpeg build has nothing to run, and a broken or mismatched binary produces failures that 3FUI cannot diagnose for you. The README's feedback section is blunt about the consequences: ffmpeg output does not always have a specific cause, messages about unsupported features or incorrect parameters are not diagnosable without the command line, and the project asks users to bring the full command line and input file details rather than describing symptoms. It explicitly tells people not to send error messages to general-purpose AI chatbots.

There is also a hardware dependency that has nothing to do with ffmpeg. The interface is rendered by LakeUI, a DirectX-based rendering engine maintained by the same developer, and the README states the renderer requires a graphics card that supports D3D11. That is a low bar for a modern Windows machine, but it is a bar, and it rules out some virtual machines and remote desktop configurations.

Installing 3FUI and running a first ffmpeg command through it

The README states the system requirements plainly: Windows 10 1609 or later, x64 or arm64 only. The runtime is .NET 10, which is not bundled and must be installed on the system, though the README says the updater can download and install it automatically. All data is stored in the current directory as a single file, and the release is distributed as a single file.

The README does not give a step-by-step installation walkthrough, so treat the following as the shape of the process rather than a quoted procedure. Download the release from the repository, then place your ffmpeg binary where 3FUI can find it. The README says ffmpeg must be placed manually or added to the environment variable.

3FUI accepts startup arguments in the same style as ffmpeg, and the README notes these run through the plugin mechanism and require version 5.0 or later. The documented flags are -i for the input media file, -3fui_file for a preset file, -ffmpeg to pass everything after it straight to ffmpeg, -test to pop a beep, and fullscreen for a borderless full-screen mode. The README states -i and -3fui_file must be used together, and that the preset file can be specified by its name in the Preset folder. There are also -3fuiVideoHelperInPointTime and -3fuiVideoHelperOutPointTime for passing clip range values.

The README documents a remote call mode as well: enable it in settings, and 3FUI listens on a specified port. Incoming messages carry the same data as the startup arguments, which the README says lets one 3FUI instance serve a whole LAN as long as it can reach the files.

Hardware encoding limits the README wants you to understand first

The README spends significant space on GPU encoder specifications, and the point is not marketing. For NVIDIA, it links the official video encode and decode support matrix and states that a 3090 equals a 3060, and that for a single task a 5090 equals a 5050, because encoder cores differ only by generation and count rather than by scale. If you are buying a card purely for encoding and decoding, the README's advice is to buy the current generation's lowest model, and it notes that ffmpeg cannot correctly use multiple encoder cores within a single task anyway.

There is a second constraint that matters for batch work. The README states NVIDIA consumer cards limit the number of simultaneous encoder sessions, generally eight, meaning roughly eight ffmpeg processes can call the GPU encoder at once, while professional cards carry no such limit. For anyone planning a large batch queue on a consumer card, that ceiling is the real scheduling constraint, not CPU or disk. The README also links Intel Quick Sync Video and AMD AMF documentation, and remarks that those vendors' tables are less generous than NVIDIA's.

The Agent feature and what it does not replace

Version 6 ships what the README calls 3FUI Agent, a copilot built on the Microsoft.Agents.AI.OpenAI framework. It connects to any endpoint compatible with the OpenAI SDK, so you supply the model. According to the README it can control the entire parameter panel, help manage tasks, access the network, read text files and images, and use a Windows PowerShell terminal, with mid-conversation model switching and local-only storage of conversation data. The rendering is described as fully local rather than a web wrapper.

The honest reading is that this is a convenience layer over a tool that still expects you to understand what you are asking for. The same README that advertises the agent also warns that ffmpeg errors about unsupported features or incorrect parameters cannot be diagnosed without the command line, and that even GPT and Claude cannot reliably guess them. A model that can set parameters is not a model that can tell you why a particular file failed. If your workflow depends on the agent producing correct encoding settings for unfamiliar source material, verify the output before trusting it on a batch.

Where 3FUI sits next to HandBrake and ShanaEncoder

The README places 3FUI at the same table as HandBrake, ShanaEncoder and ShutterEncoder, calling them all regular professional compression and conversion software, while noting that one reviewer rated 3FUI as more professional. The difference in approach is the bundled codec question. HandBrake ships its own encoder libraries and its own update cycle, so a user gets a working pipeline immediately and waits for the project to adopt new encoders. 3FUI ships none and calls whatever ffmpeg you provide, so the pipeline is only as good as the binary you installed and you never wait for the GUI to catch up.

That difference cuts both ways. If you want to hand someone a tool and have them converting files in ten minutes, a bundled-codec application is the safer recommendation. If you already keep a current ffmpeg build and want the GUI to expose its full argument surface without translation, 3FUI's model is the one that does not get in the way. The README's own framing supports this: it describes 3FUI as a complete extensible platform rather than an ordinary encoding program.

Licence, maintenance and what upgrading costs you

3FUI is MIT licensed, and the README says the software can be freely used and distributed. It also states the source is open only on GitHub and that source seen on other platforms is not the author's. The MIT terms cover 3FUI itself, not the assemblies it references, and the README lists those separately: LakeUI under GPL-3.0-only as the main interface framework, WindowsAPICodePack under the Microsoft software licence for folder selection dialogs, LibreHardwareMonitorLib under MPL-2.0 for performance monitoring, and Microsoft.Agents.AI.OpenAI under MIT for the agent framework. If you redistribute a build, those terms travel with it, and the GPL-3.0-only component is the one worth reading closely rather than assuming the MIT label covers the whole binary.

The development pace is visible in the release list: 6.2.23 on 2026-09-18, 6.2.25 the same week, and 6.2.26 on 2026-09-21. The repository is not archived and the last push was on 2026-09-21. Frequent point releases mean the upgrade cost is mostly your own time, since data lives in a single file in the current directory and presets are portable by design. The dependency to watch is .NET 10, which the README says is not bundled; if a future release moves to a newer runtime, the updater's ability to install it is what keeps the upgrade cheap. The README also notes the ffmpegfreeui.top and 3fui.top domains will be retired in 2028, so do not build documentation links around them.

Editorial conclusion

Adopt 3FUI if you already write ffmpeg arguments by hand and want a Windows front end that stores presets as shareable files and never touches the registry. Skip it if you need an English interface, a macOS or Linux build, or a one-click preset that decides bitrate for you; the README states the interface is Simplified Chinese only and that the project is aimed at users who understand basic parameters. Before committing, verify three things: that your GPU supports D3D11, that .NET 10 is installed or that the bundled updater can install it, and that you have a working ffmpeg build placed in the program directory or on PATH.

Frequently asked questions

Official sources

1. Lake1059/FFmpegFreeUI on GitHub
2. License: MIT
3. Project website
4. README
5. Releases