Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is FileBot?
FileBot is a media file organizer and renamer. It matches your movie, TV and anime files against online databases, then renames and moves them into a clean folder structure that media servers can read — the kind of structure Plex, Kodi, Jellyfin and Emby expect. It also fetches subtitles and artwork alongside the rename.
What it actually does
- Batch renaming: drop in hundreds of files and rename them in one pass, rather than fixing episode titles one by one.
- Database matching: pulls episode and movie information from TheMovieDB, TheTVDB or AniDB, so names follow real release data instead of whatever your downloader produced.
- Naming schemes: use the built-in
{plex}standard for a no-decisions setup, or write a custom format string if you have strong opinions about folder layout and file names. - Subtitles: searches OpenSubtitles, can match by file hash for a precise fit, and includes a subtitle viewer for previewing and fixing encoding issues.
- Beyond video: music via ID3 tags or AcoustID fingerprints, photos via Exif metadata, and arbitrary files via custom patterns.
- Automation: a command-line interface for scripted runs and a scripting engine for more involved workflows, including unattended setups that watch folders and process new files as they arrive.
- Undo: rename operations are recorded in an internal history, so a bad batch can be reverted.
Who it suits
| You are… | FileBot fits if… |
|---|---|
| Running a home media server | You want files named and sorted for Plex, Kodi or Jellyfin without manual work |
| Managing a large backlog | You have hundreds of inconsistently named files to clean up at once |
| Comfortable with a terminal | You want scheduled, unattended processing via CLI or scripts |
| A casual viewer with a tidy library | You may find the setup and naming-scheme options more than you need |
A concrete next step
Take one season of a show with messy file names and run it through FileBot using the {plex} scheme first. Check the resulting folder structure against what your media server expects before committing to a custom format — that tells you quickly whether the default is good enough or whether you need to learn the format syntax. If you later want it hands-off, move the same workflow to the command line so new files are processed automatically.
FileBot is a paid tool; the site lists a one-year license and a lifetime license, with purchase handled through Paddle.
How do I rename and organize my TV shows and movies with FileBot?
FileBot is built for exactly this job: it matches your media files against online databases, then renames and moves them into a consistent folder structure. The basic loop is drag in files, confirm the matched names, and hit Rename.
The manual workflow
- Drag your movie or episode files into the Original Files list.
- Right-click the New Names list and pick your datasource — TheMovieDB, TheTVDB or AniDB, depending on whether you're cataloguing films, Western TV or anime.
- Check the proposed names. FileBot queries the database and proposes matches automatically; you only intervene where a file is ambiguous (a badly named rip, a double episode, a remake with the same title).
- Hit Rename.
The default {plex} naming scheme produces a structure that Plex, Kodi, Jellyfin and Emby all read without further configuration. If you have strong opinions, the naming scheme is customizable and can pull technical details from MediaInfo, so you can embed resolution, codec or audio channels in filenames or folder names.
Subtitles in the same pass
Subtitles are handled separately but just as simply: drop the video files onto the drop area, hit Download, and FileBot fetches matching subtitles from OpenSubtitles. Hash-based matching is the useful part here — it finds subtitles that correspond to your exact release rather than a version with different timing. There's also a built-in viewer for previewing and fixing encoding issues, and you can upload subtitles by hash.
When to stop clicking and start scripting
The manual interface is fine for a one-off backlog. For anything recurring — a download folder that fills up weekly, or a media server you want to keep tidy without thinking about it — the command-line interface is the better fit. A single filebot -rename command handles a folder of files, and the amc script goes further: extract archives, identify and organize media, fetch artwork and metadata, and trigger a Plex update in one command. That's the point at which FileBot stops being a renaming tool and becomes part of an unattended pipeline, which you can run remotely on a server or NAS.
A practical decision rule
- Under a few hundred files, one time: use the GUI, accept
{plex}naming, spot-check the New Names column before renaming. - Ongoing library maintenance: invest an hour in the CLI and the
amcscript; the upfront cost pays back quickly. - Mixed content types: FileBot also renames music via ID3 tags or AcoustID fingerprints, photos via Exif metadata, and arbitrary files via custom patterns or AI prompts, so it can cover more than video if you'd rather not run several tools.
Two things worth knowing before you commit: renames can be reverted using the internal history, which makes experimentation low-risk, and FileBot is a paid application with a one-year or lifetime license option. If you're weighing it against alternatives, Plex and Kodi handle library display but not file organization, so the comparison is really against other renamers rather than against your media server.
A sensible first step: point FileBot at a copy of one season of a show, rename it, and inspect the resulting folder tree. If it matches how your media server expects things, apply the same scheme to the rest of your library.
How can I automate media file organization for Plex or Kodi using FileBot?
Automating media organization for Plex or Kodi with FileBot means letting a script do the matching, renaming, moving, and metadata fetching that you would otherwise do by hand. The page describes a built-in scripting engine and a command-line interface for exactly this, plus an amc script that extracts archives, identifies and organizes media, fetches artwork and metadata, and updates Plex in one command.
The two automation paths
| Approach | Best for | Trade-off |
|---|---|---|
Command-line filebot -rename |
Simple, repeatable batches of files you point at manually | You supply the file list or folder each run; less logic for mixed content |
Built-in scripting engine / amc script |
Unattended pipelines that watch a folder and process whatever arrives | More setup and testing; mistakes can rename many files at once |
A practical middle ground is to start with the simple CLI on a small test folder, confirm the naming scheme produces what Plex or Kodi expects, then move to the scripted workflow once you trust the output.
A concrete walkthrough
- Put a few sample files in a separate test folder, not your live library.
- Run a basic rename against that folder and inspect the results before touching real media.
- Check the naming scheme. The page notes you can customize it or keep the
{plex}standard, which is the low-effort option if you use Plex. - Confirm the datasource. FileBot can match against TheMovieDB, TheTVDB, or AniDB, so anime and standard TV may need different sources.
- Once the test output is correct, point the script at your download or staging folder and let it run on a schedule.
- Keep the internal history in mind: the page mentions reverting rename operations, which is your safety net if a batch goes wrong.
Automation beyond renaming
The same workflow can fetch subtitles from OpenSubtitles, including hash-based matching, and pull artwork and cover images. For a media center, that means one pass can leave a file correctly named, placed in the right folder, and accompanied by its poster and subtitles.
Where to go next
If you want to see how others structure these scripts, the FileBot forums linked from the site are the natural first stop. For the target library, check the official conventions of Plex or Kodi so your naming scheme matches what the server expects. If you also run Jellyfin, the same standard file structure generally works across all three.
What is the difference between the 1-year and lifetime license for FileBot?
The 1-year license covers FileBot for twelve months; the lifetime license covers the same application permanently. Both are described as universal licenses, so the difference is duration of access, not which features you get. In practice, both unlock the full application during their term, including the command-line interface and scripting engine used for automation.
What that means in practice
- 1-year license: best if you have a short-term project, a one-off library cleanup, or want to test whether FileBot fits your workflow before committing further. When the year ends, you would need to renew to keep using licensed functionality.
- Lifetime license: best if FileBot is part of an ongoing media setup. If you run automated renaming on a schedule, or manage a library that keeps growing, a one-time purchase avoids renewal decisions later.
A useful way to decide
Estimate how long you will keep using FileBot. If your media library is a long-term hobby or you run unattended workflows, the lifetime option usually makes more sense. If you only need it for a bounded task, the annual option limits your upfront commitment.
Practical next step
Before buying either, install the current version and try a small batch: drag a few episodes into the Original Files list, right-click the New Names area to pick a datasource, and confirm the proposed names look right. That test tells you whether the naming scheme and database matching suit your library. If it does, choose the term that matches how long you expect to keep using it.
How does FileBot fetch subtitles and artwork for my media files?
FileBot treats subtitles and artwork as two separate jobs that run alongside renaming.
Subtitles
Subtitles come from OpenSubtitles, and FileBot's main advantage is that it can match by file hash rather than by filename alone. A hash match means the subtitle file was made for that exact video release, so timing stays in sync instead of drifting a few seconds off.
In practice: drop your episode or movie files into the drop area, hit Download, and FileBot looks up and saves matching subtitle files next to the video. You can also search manually, preview a subtitle before keeping it, and fix encoding problems (useful for older files with non-UTF-8 character sets). Uploading subtitles back, also by hash, is supported.
Artwork and metadata
Artwork is fetched as part of the same lookup that renames your files. FileBot matches each file against an online database — TheMovieDB, TheTVDB or AniDB — then pulls episode or movie information plus cover images and artwork, and writes everything into a folder structure that Plex, Kodi, Jellyfin and similar media servers read correctly.
What this means for you
The realistic workflow is: drag files in, right-click the New Names area to pick your datasource, then Rename. Subtitles are a second, separate pass. If you run a server, the amc script bundles the whole chain — extract archives, identify and organize files, fetch artwork and metadata, and refresh Plex — into one command, which is the part that matters if you'd rather not click through a GUI every week.
Two trade-offs worth knowing. Hash-based subtitle matching is accurate but only works when OpenSubtitles already has a subtitle for your exact release; obscure encodes may fall back to name-based results. And automatic artwork/metadata depends on your files being matched correctly in the first place, so a wrong match produces wrong art as well as a wrong filename — check the New Names list before confirming if you're processing a large batch.
Next step: test on 5–10 files from one show before running a full library, so you can confirm the datasource and naming scheme produce the folder layout your media server expects.
Can FileBot rename music and photos, and how does it work?
Yes. FileBot handles music and photos alongside video, though the matching logic differs by media type.
Music
FileBot can rename audio files using embedded ID3 tags (artist, album, track number, title) or by AcoustID acoustic fingerprinting when tags are missing or wrong. AcoustID works by analyzing the audio itself and matching it against a fingerprint database, which helps with untagged rips or files with garbled metadata. You then apply a naming scheme — for example, an artist/album/track structure — and FileBot moves and renames in one pass.
Practical scenario: you rip a stack of CDs and end up with files named track01.mp3, track02.mp3. If tags exist, FileBot sorts them into a clean library layout immediately. If tags are absent, AcoustID identification is the fallback, but it depends on a match existing in the fingerprint database, so obscure or live recordings may not resolve.
Photos
Photos are renamed from Exif metadata — capture date, camera model, and similar fields. A common use is turning IMG_4821.jpg into a date-based name like 2024-06-14_15-32-08.jpg, which makes chronological sorting reliable across cameras and phones.
What ties them together
All three media types share the same workflow: load files into the Original Files list, choose a datasource or metadata source, define a naming scheme, then rename. The naming scheme is customizable and supports MediaInfo for video; for music and photos the drivers are tags and Exif rather than online databases.
| Media type | Primary matching source | Typical use |
|---|---|---|
| Video | TheMovieDB, TheTVDB, AniDB | Plex/Kodi/Jellyfin library structure |
| Music | ID3 tags, AcoustID | Album/artist folder trees |
| Photos | Exif metadata | Date-based filenames |
Trade-offs to weigh
Music and photo renaming is metadata-driven, not database-driven, so results are only as good as the tags or Exif data present. Video renaming benefits from online lookup that can correct bad filenames; music and photos generally cannot be "corrected" the same way unless AcoustID finds a fingerprint match. If your library has inconsistent tags, budget time for a test run on a small batch first.
A sensible next step: copy 20–30 representative files into a scratch folder, run your intended naming scheme there, and inspect the output before applying it to the full library. FileBot's rename history also lets you revert operations if a scheme produces unwanted results.
User reviews (0)