Installation
Requirements
Section titled “Requirements”| Platform | Status |
|---|---|
| Windows 10 or 11, 64-bit | Available |
| Linux desktop | Planned |
| macOS | Planned |
| Headless / Docker, driven from a browser | Planned |
You also need disk space for the files you intend to process — a Compress job writes a new file alongside the original before anything is replaced.
Only the Windows build exists today, so these pages describe it, and anything platform-specific is called out where it comes up. What the app actually does — how it reads tracks, decides verdicts, renames and encodes — will be the same everywhere, because it is the same code underneath.
Installing
Section titled “Installing”Download the installer and run it. FileVerdict installs as a normal desktop application and checks for updates shortly after launch, with a manual Check for updates in Settings → General.
What’s included
Section titled “What’s included”Everything FileVerdict needs ships inside the installer: ffmpeg, MKVToolNix,
and Tesseract, the OCR engine that reads image-based subtitles (PGS and
VobSub). You do not need to install any of them, put them on
your PATH, or keep them updated — this is most of why the download is tens of
megabytes rather than 5 MB.
Tesseract comes with English language data, which also reads other languages written in the Latin alphabet. See Subtitles for how image subtitles are read.
Supported files
Section titled “Supported files”Scanning and renaming work with .mkv, .mp4, .m4v, .avi, .mov, .ts
and .webm.
Track edits — renaming a track, changing its flags, removing it — are written
with MKVToolNix for Matroska files (.mkv, .mka, .webm) and with ffmpeg for
everything else. Matroska is the better-supported path: some flags FileVerdict
reads and writes, such as hearing-impaired and commentary, only exist in
Matroska in the first place.
Where your data lives
Section titled “Where your data lives”Settings, presets, encode history and licence activation are stored in your
operating system’s app-data folder — on Windows, %APPDATA%\FileVerdict\ —
not in the installation directory.
Any API keys you enter are the exception. Those are credentials you registered yourself, so they go to the operating system’s credential store — the Credential Manager on Windows — rather than into a settings file where a backup tool would copy them. See Privacy and network access.
Activate your licence, then run your first clean-up.