Security & local processing
FFmix is local-first: your media is processed on your own Mac through the bundled, open-source ffmpeg engine. Files are never uploaded. The only thing that can leave your device is the text sentence you type into the AI box — and only when you ask it to parse a compound request.
Where your data goes
The AI request boundary
FFmix tries to understand a request locally first. A single, simple intent (“compress”, “make a GIF”, “extract audio”) is matched on-device by built-in rules — instant, free, and nothing is sent anywhere. Only a compound sentence (several steps in one instruction) is sent to the cloud parser, and even then only the text you typed crosses the network — never a file. The parser returns a step-by-step plan, which FFmix shows you for review; nothing runs until you confirm.
Usage is counted against an anonymous device identifier so the monthly free allowance can be enforced. What is stored is limited to that device id, the month, and the length of your sentence — never its contents. High-value endpoints are additionally protected by Apple’s App Attest, so quota can’t be spoofed by forging a device id.
The engine
Processing runs on the open-source ffmpeg engine, built into the app. Hardware encoding uses Apple’s VideoToolbox where it makes sense, so exports are fast and battery-friendly. Local subtitle transcription uses an on-device Whisper model. None of these phone home with your media.
The command you see is the command that runs
There’s no hidden behaviour: expand Advanced on any task to read the exact ffmpeg command before it runs, copy it, or edit it in manual mode. Output is written next to your original file and never overwrites it.
Interviews, internal footage, client work — it all stays on your Mac.
More
Local video processing · Full privacy policy · About FFmix · Guides · Support