A watch folder is a folder that software monitors continuously: when a new video lands in it, the file is automatically converted with a preset you chose in advance and the result is saved somewhere else. It turns video conversion into a drop-and-forget task, which is ideal for regular footage from cameras, screen recorders, capture devices or colleagues.
This guide explains how watch folders work, the problems a good setup has to handle (half-copied files, duplicates, loops and failures), how to build a basic one with a script, and how to choose sensible settings for unattended conversion.
How a watch folder works
The basic cycle is simple:
- The software watches an input folder for new files, either by receiving file system notifications from Windows or by checking the folder at intervals.
- When a matching file appears - for example anything ending in
.movor.mkv- it waits until the file is complete. - It queues an encode using a fixed preset or workflow.
- It writes the output to a separate folder and records whether the job succeeded.
- Optionally, it moves the original to a "done" or "failed" folder.
Typical uses include shrinking screen recordings as soon as they are saved, converting camera MOV files to MP4 for sharing, producing proxy files for editing, normalising audio on podcast video, and preparing files for a media server.
The problems a watch folder has to solve
The concept is easy; doing it reliably is not. These are the issues that cause most home-made setups to misbehave.
Files that are still being copied
Windows notifies software the moment a file is created, not when copying finishes. If conversion starts on a 20 GB file that is only half copied - especially over a network or from a slow card reader - the encoder reads a truncated file and produces a short or broken output. A reliable watcher waits until the file size has stopped changing for a while and the file is no longer locked by the copying process.
Processing its own output
If the output folder sits inside the input folder, or both use the same extension, the watcher can pick up its own converted files and encode them again, endlessly. Keep output outside the watched folder, or use software that recognises and ignores its own output.
Duplicates and restarts
If the watcher restarts, it must not convert every file in the folder again. It needs a record of what it has already processed, ideally based on more than just the file name, since a camera may reuse names like C0001.MP4.
Failures
Some files will be corrupt, use an unsupported codec, or arrive while the disk is full. A good setup retries transient failures a limited number of times, then moves the file aside and tells you, rather than retrying forever or silently skipping it.
Originals
Automatic deletion of originals is risky. If an encode produces a bad file and the original is gone, nothing can be recovered. Moving originals to a processed folder is safer, and deleting them should only ever be a deliberate choice.
Building a simple watch folder with a script
If you are comfortable with scripting, PowerShell can do a basic version. The simplest robust approach is a scheduled task that runs every few minutes and processes any file older than a threshold, which neatly sidesteps the half-copied file problem:
Get-ChildItem C:\Watch\*.mov | Where-Object { $_.LastWriteTime -lt (Get-Date).AddMinutes(-2) } | ForEach-Object { ffmpeg -n -i $_.FullName -c:v libx264 -crf 21 -c:a aac -b:a 160k ("C:\Out\" + $_.BaseName + ".mp4"); if ($LASTEXITCODE -eq 0) { Move-Item $_.FullName C:\Done\ } }
Run it with Windows Task Scheduler on a repeating trigger. This version only moves the original after FFmpeg reports success, writes output to a separate folder, and uses -n so it never overwrites an existing output. What it lacks is proper logging, retry limits, notifications, and protection against an interrupted encode leaving a partial output that later blocks a retry. Those are where scripts tend to grow complicated.
Choosing settings for unattended conversion
Because nobody checks each file, choose settings that behave well across varied input:
- Use constant quality (CRF) rather than a fixed bitrate. It adapts to each clip, so a static screen recording and a fast sports clip both look right. See CRF vs two-pass bitrate.
- Avoid upscaling. If your preset scales to 1080p, make sure smaller sources are left alone.
- Pick a forgiving container. MKV accepts almost any track type; MP4 is more compatible but cannot hold every subtitle format.
- Consider the hardware. GPU encoding keeps up with a busy folder and leaves the CPU free for other work. Our guide to GPU video encoding explains the quality trade-off.
- Set working hours if the PC is in use. Heavy encodes can make a workstation sluggish, so scheduling them overnight is often sensible.
Watch folder or batch queue?
A watch folder suits a steady flow of new files that all need the same treatment. For a one-off pile of existing videos, a batch queue is simpler and gives you more control over each job - see our guide to batch converting videos on Windows. Many people use both: a batch to convert the backlog, then a watch folder for everything new.
Doing it with Movie Encoder
Movie Encoder's watch folders automatically encode new files with a preset or workflow. They wait until files have finished copying, filter by extension, prevent duplicates, retry failures, and can sort files into success and failure folders. You can restrict encoding to working hours and receive Windows notifications, and the app will not re-process its own output.
Originals are never moved or deleted unless you explicitly turn that on. Each encode goes to a temporary file and is only moved into place after it finishes and passes a check, so a partial encode is never treated as complete, and full logs are kept for every job.
Frequently asked questions
What happens if a file is still copying when the watch folder sees it?
A poorly designed watcher will start encoding a truncated file and produce a broken output. Reliable tools wait until the file size stops changing and the file is no longer locked.
Should a watch folder delete the original files?
It is safer to keep originals or move them to a processed folder. Deletion should only be switched on deliberately, once you trust the output.
Can I use Windows Task Scheduler as a watch folder?
Yes. A scheduled PowerShell script that processes files older than a couple of minutes works well for simple cases, though you will need to add your own logging and retry handling.
