Lossless by default
Remux — never re-encode. A two-hour movie processes in under a minute. Pixels and audio samples are bit-identical to the source.
A free macOS app that tags, organises, and transcodes your video files for Apple TV and Plex. Drop a folder in, walk away, library ready.
🚀 Early-adopter phase. Install today, free of charge with no obligation, and lock in founders' pricing when paid plans arrive.
Remux — never re-encode. A two-hour movie processes in under a minute. Pixels and audio samples are bit-identical to the source.
Embeds iTunes-style metadata + artwork. Proper .m4v with full atoms for
TV.app. Clean filenames and folder layout for Plex.
Drop a messy release-group filename. FlicksForge figures out the title, year, and episode, pulls the poster, writes the atoms. Review only the uncertain ones.
Source chapters preserved automatically. Or auto-detect chapters from scene changes — no external service required. Manual editor for when you want to polish.
VideoToolbox HEVC → H.264 for older Apple TVs. 8× realtime on Apple Silicon. Software fallback on older Intel Macs happens automatically when needed.
Browse every TMDb poster variant, filter by language, paste a custom image from the clipboard, or drag-drop your own JPEG in.
Already MP4 or M4V? Skip the remux entirely. Five seconds on any file size. Forty-gigabyte Blu-ray rip or four-hundred-megabyte web rip — same time to tag.
Tell FlicksForge to watch a download folder. New files get matched and filed away automatically. Uncertain matches wait for your review.
Got an MP4 from a sketchy source with malformed atoms? FlicksForge transparently re-remuxes through ffmpeg to produce a clean file before tagging.
Drop your .rule files in — they run unchanged. NSPredicate
parser, template tokens, conditional actions including AppleScript hooks.
Visual editor with dry-run preview. 15 community-curated rules ship as
defaults.
iFlicks has been a beloved tool for years. Its last major release was in 2021, and if you've been looking for an actively-developed alternative, FlicksForge picks up where it left off — same fast MP4 tagging, plus chapter markers, hardware transcoding, universal Intel + Apple Silicon support, and a proper artwork picker. Free today, and early adopters get permanent founders' pricing when paid plans arrive.
.rule files across — drop them in, they run unchanged in FlicksForge's rules engine.preset files — distribute processing settings to friends or other machines
One download. Installs in seconds. Auto-updates quietly after that.
Download FlicksForgeUniversal macOS build · ~300 MB · signed & Apple-notarized
Requires macOS 11 Big Sur or later. Intel and Apple Silicon both supported.
✓ You're on the list.
We'll email you once, when paid plans launch. That's it.
Yes — FlicksForge. iFlicks has been the go-to MP4 tagger on macOS for years,
but its last major release was in 2021. FlicksForge is an actively-developed,
free alternative that covers the same core workflow (auto-match on TMDb, embed
iTunes-style metadata + artwork, tag MP4 and M4V for Apple TV and Plex)
and runs your existing iFlicks .rule files unchanged
via a hand-rolled NSPredicate-subset parser.
It also adds things iFlicks didn't have: chapter markers from scene-change
detection, AppleScript action types for the rules engine, shareable
.preset files, a universal Intel + Apple Silicon build, a
Quick Tag path for in-place metadata updates, and auto-repair for
malformed source files.
Yes — drop your .rule files into the Rules page (or use the
Import .rule files… button) and they run unchanged.
FlicksForge ships with a hand-rolled NSPredicate-subset parser that handles
the same predicate syntax iFlicks does, the same template tokens
({title}, {year}, {showName}, etc.),
and the same conditional action types — set tag, set value, set filename,
set creation date, plus a new AppleScript hook.
15 community-curated rules ship in the app as defaults, so you can see how the engine works before importing your own. A visual row-based editor and a dry-run preview let you see exactly what a rule will do to a file before committing.
FlicksForge is free for everyone today — we're in our early-adopter phase while the product finds its audience. This isn't VC- funded; it's a sustainable indie project, and paid plans will arrive at some point (targeting 2027) to keep it viable long-term.
When that happens, users who installed during the early-adopter phase get permanent founders' pricing — a generous discount that won't be available to new users afterwards. Our way of saying thanks for being here first. Join the founders' list below if you'd like a heads-up before anyone else.
When paid plans launch, everyone who installed FlicksForge during the early-adopter phase (that includes you, if you download today) is entitled to a permanent discounted tier that new users after that point won't get. We haven't finalised the exact amount yet — but the intent is clear: early adopters took a chance on us, and that matters.
We'll announce the paid plans 6+ months before they go live, with generous transition terms for existing users. No "sorry, subscription starts tomorrow" emails. Optionally drop your email in the founders' list and we'll let you know directly when the time comes.
Drop the file onto FlicksForge's Dashboard, click Auto-Match, pick an output folder in Settings, and click Start Processing. FlicksForge looks the title up on TMDb, downloads artwork, writes iTunes atoms (title, description, genre, year, cast, director, content rating, HD flag), and files the tagged output into your chosen folder. Apple TV and Plex both read the resulting file out-of-the-box. For existing MP4s that just need metadata updated, the Quick Tag button tags in-place in a few seconds regardless of file size.
Three built-in ways. Source chapters are preserved automatically — MakeMKV Blu-ray rips and most decent sources already carry chapter atoms, and FlicksForge passes them through unchanged. For sources without chapters, open the file in the Metadata Editor and either auto-detect from scene changes (offline, takes a minute or two on a feature-length movie) or add them manually. You can also generate evenly-spaced markers for a quick structural pass, or paste a YouTube-style chapter list or OGM chapter file directly in.
For the tag-and-organize workflow, yes. FlicksForge covers what those tools do (iTunes-atom writing via AtomicParsley, TMDb-driven metadata, artwork embedding) and adds a modern UI, auto-matching, watch folders, chapter markers, and hardware-accelerated HEVC→H.264 transcoding. Subler remains strong for hand-editing individual iTunes atoms at a fine-grained level; FlicksForge is more opinionated about the "just do the right thing for Apple TV and Plex" use case.
Yes. The DMG is a universal binary that runs native on both Apple Silicon and Intel Macs. Minimum is macOS 11 Big Sur. Pre-T2 Intel Macs (2013–2017) fall back to software encoding for HEVC output automatically — slower, but works without user intervention.
No telemetry, no analytics, no account. The only network calls are to TMDb (to look up metadata), OpenSubtitles (when you click "Search"), and our own server to check for app updates. Your video files never leave your Mac.
No. FlicksForge writes tagged output into the output folder you choose; your source files are left completely untouched. The one exception is Quick Tag, which explicitly tags an existing MP4/M4V in place — only when you click that specific button.
Not yet as a standalone CLI, but the flicksforge:// URL scheme
lets you trigger file opens from Terminal, Apple Shortcuts, Automator, or
Keyboard Maestro. FlicksForge also registers as a Finder "Open With" handler
for common video formats, so right-click → Open With → FlicksForge is an
option on every `.mkv` and `.mp4` on your Mac.
macOS only for now. Windows 10+ support is on the roadmap — Electron makes porting technically feasible, but native tagging and hardware encoders need platform-specific code we haven't written yet. Linux isn't currently on the plan but could follow Windows if there's demand.
Email support@flicksforge.com, or post on r/FlicksForge. Include the raw error text from the "Show details" link on any failed job — it tells us exactly what went wrong.