Can Dinky replace FFmpeg?

Not for every use case. FFmpeg can express arbitrary filters, piping, and server-side automation. Dinky targets interactive shrink workflows on macOS with presets, batch UI, and PDF plus still-image pipelines FFmpeg does not address in one app.

Who should use FFmpeg instead?

Developers and video engineers who live in the terminal, need scripting, or require flags Dinky does not expose should use FFmpeg or tools built on top of it.

Does Dinky use FFmpeg internally?

Dinky uses Apple’s AVFoundation export path for video, not a bundled FFmpeg binary. For FFmpeg-specific behavior, run FFmpeg directly.

Dinky vs FFmpeg

FFmpeg is infinite control in the terminal. Dinky is presets, batches, and watch folders on the Mac—plus PDFs and stills, no flags to memorize.

Choose FFmpeg for scripts and maximum control

When you need custom filters, piping, server automation, or encode settings only the CLI can express.

Choose Dinky for GUI batch work on a Mac

When you want H.264/HEVC presets, drag-and-drop, Finder integration, and PDF compression without maintaining ffmpeg invocations.

	Dinky	FFmpeg
Interface	SwiftUI / AppKit app	Command line
Flexibility	Curated presets	Full encoder surface (expertise required)
Still images / PDF	Yes	Possible via CLI; not one unified Mac app
Batch	In-app queue, watch folders	Shell loops, makefiles, servers
Price	Free (MIT)	Free (LGPL/GPL components; see FFmpeg license)
Processing	Local on your Mac	Local or anywhere FFmpeg runs

Dinky drop zone window compressing files

GUI when you want it

Presets, not flags to memorize

Keep FFmpeg for bespoke invocations—use Dinky for everyday shrink jobs, visible queues, and still images plus PDFs beside your video presets.

Download for macOS Learn more

33 MB · v2.7.12 · Requires macOS 15 Sequoia

More comparisons

Images

Video

PDF

All-in-one

Presets, not flags to memorize