How to Set Up FileBot Watch Folders for Auto-Tagging

Setting up FileBot watch folders lets you skip the tedious part of managing a media library: manually renaming files, sorting episodes, and fetching artwork every time something finishes downloading. This guide walks you through building a reliable watch folder setup, whether you run FileBot on a desktop machine, a Synology or QNAP NAS, or inside a Docker container. It is aimed at anyone who wants new TV shows and movies to be automatically identified, renamed, and moved into a tidy library structure without lifting a finger.

What you’ll need

• FileBot installed on the machine or NAS that will do the processing
• A download client (torrent client, Usenet client, or similar) that saves completed files somewhere on that same system
• A separate folder for incoming downloads and a destination folder for your sorted library
• Basic comfort with folder permissions and, if you’re on a NAS, Docker or a task scheduler
• An active internet connection, since FileBot matches files against online metadata databases

Understand how FileBot watch folders actually work

FileBot’s core renaming logic lives in what’s called the AMC (Automated Media Center) script. A watch folder setup simply means something triggers that script automatically whenever new files appear, instead of you opening FileBot and dragging files in yourself.

There are two common ways to trigger it: watching a folder for filesystem changes, or having your download client call the script the moment a download finishes. The FileBot developer behind the project has been fairly direct about this: pure filesystem watching using tools like inotify is not fully reliable, because it can fire while a large file is still mid-copy, especially over a slow network link. If FileBot tries to process a half-written file, you can end up with failed matches or incomplete renames.

The more dependable approach is to let your download client trigger the AMC script only once a file or folder is completely finished downloading. If you do need to rely on folder watching (for example with a Docker-based setup on a NAS), it helps to build in a short settlement period before processing starts, so FileBot doesn’t jump on files too early.

Set up the folder structure

1. Create a dedicated incoming or staging folder that your download client writes to. This folder should not be the one FileBot watches directly.
2. Create a separate destination folder that will hold your finished, renamed library (commonly split into TV and Movies subfolders).
3. Configure your download client to move or copy completed downloads out of the staging folder and into the watched folder as a single, complete operation, rather than writing files directly into the watched folder piece by piece.
4. Confirm that FileBot, your download client, and the watched folder all have the correct read and write permissions, particularly important on a NAS where different services can run under different user accounts.

Configure FileBot to process the watched folder

1. Get the AMC script within FileBot, since this is the script responsible for matching, renaming, and moving files.
2. Set the input path to your watched folder and the output path to your library destination folder.
3. Choose the action you want FileBot to take on matched files, such as moving or copying them into the destination structure, rather than leaving duplicates behind in the watch folder.
4. If you’re running FileBot through a download client’s post-processing hook, point that hook at the AMC script so it only runs after a download is verified complete. This avoids the timing problems that come with pure folder watching.
5. If you are instead using a scheduled or container-based watcher (such as the official filebot-watcher setup used on Synology, QNAP, and other embedded Linux systems), configure a settlement delay so files are left untouched for a period after their last modification before FileBot attempts to process them. A couple of minutes is a reasonable starting point for small files, but larger video files copied over a slow connection may need a longer buffer.
6. Run a manual test first with a couple of sample files before switching everything over to fully automatic processing, so you can confirm naming and folder placement look right.
7. Once you’re happy with the results, enable the watcher or scheduled task so it runs continuously or on your chosen schedule.

Tips and troubleshooting

• If files are being processed while still downloading, increase the settlement delay rather than reducing it. It’s far safer to wait a little longer than to risk FileBot matching a partial file.
• Avoid pointing your download client’s write path and FileBot’s watched folder at the exact same location if you can help it. A staging folder plus a single atomic move into the watched folder avoids most timing issues entirely.
• Where possible, trigger the AMC script from your download client’s own “download complete” event instead of relying on filesystem watching. This sidesteps the reliability issues altogether.
• Double-check permissions if files appear in the watched folder but nothing happens. Mismatched user accounts between the download client and FileBot are a common cause on NAS systems.
• Keep an eye on FileBot’s logs when troubleshooting a container or scheduled setup, since they will usually show whether a file was skipped, matched incorrectly, or simply not detected yet.

Frequently asked questions

Is watching a folder the best way to automate FileBot?

Not necessarily. It works, but it’s considered a fallback rather than the ideal method. Triggering the AMC script directly from your download client once a file finishes is generally more reliable, since it avoids the risk of FileBot processing a file that hasn’t finished writing yet.

Why does FileBot sometimes rename files incorrectly when using a watch folder?

This usually happens when FileBot starts processing a file before it has fully finished copying or downloading. Adding a longer settlement delay before processing, or switching to a completion-triggered setup, generally fixes it.

Can I run FileBot watch folders on a NAS like Synology or QNAP?

Yes. Many users run FileBot in a Docker container on their NAS specifically for this purpose, watching a designated folder and moving matched files into a library share. The same reliability considerations apply, so a staging folder and a sensible settlement period are recommended.

Do I need an internet connection for FileBot to auto-tag files?

Yes. FileBot matches your files against online metadata sources to identify the correct show, season, episode, or movie title, so an active connection is required for accurate renaming and tagging.