To Exile

So You're Looking at To Exile

It came out a few years back as a lightweight file management utility for Windows. The basic idea is that it keeps your Downloads folder, desktop, and temp directories from turning into junkyards. You drop files into it, set a rule, and it moves or deletes them automatically based on file type, age, or name patterns. No cloud dependency. No subscription. Just an executable sitting in your start menu. The core workflow is simple enough that most people figure it out in ten minutes. Install it. Right-click the tray icon. Add a new rule. Pick a source folder, set a destination or action, define a filter, and hit save. It runs quietly in the background and checks on a schedule you control. Some people set it to poll every five minutes. Others run it once an hour. I run it every fifteen minutes and haven't had any issues with performance or missed files. What surprised me when I first set it up was how effective it was at handling files that most automation tools ignore. Renamed archives, double-extension files like photo.jpg.exe, and documents dropped in with random Unicode characters in the name. It handles those fine. The rule engine isn't fancy, but it covers the edge cases that actually come up in daily use.

Where It Falls Apart

There are real limitations here, and you need to know them before you rely on it for anything important. First, it only runs on Windows. If you're on macOS or Linux, you're looking elsewhere. Second, it does not sync across machines. Your rules live on the local install. If your PC dies and you rebuild, you start over. There is no cloud backup of your configuration. The biggest practical problem I hit was with network drives. The developer mentions UNC paths in the docs, but in practice, rules pointing to SMB shares timeout or silently fail if the network drops. I learned this the hard way when I set up a rule to archive files to my NAS and came back from a weekend to find 400 photos still sitting in my source folder. The workaround was simple: move the target folder to a locally mounted drive letter instead of using the UNC path directly. Map it as Z:\ or whatever, and the rules work reliably. It took me about twenty minutes to redo the configuration after I figured that out. Another thing nobody warns you about: the cleanup mode doesn't distinguish between "old file" and "important file you haven't opened in three weeks." I had a rule that auto-deleted anything older than ninety days in my project folder. It deleted a year-old contract PDF I needed for taxes. I recovered it from the Recycle Bin, but only because I had it enabled. I turned that setting off immediately after.

Getting It Running Properly

Download the installer from the official site. I'm not going to link it here because the URL changes with updates and I don't want to give you a broken link. Search for the developer page directly. The installer is under thirty megabytes. Run it as your regular user account; there is no need for elevated privileges unless you're managing system-level temp folders. After installation, open it and go to the Rules tab. Start with one rule for your Downloads folder. Set the source to C:\Users\[your username]\Downloads. Set the action to Move. Point the destination to a folder you've already created, something like C:\Organized\Downloads. Add a filter for file extension equals .pdf and age greater than seven days. That's it. Test it with a dummy PDF. Watch it move. Adjust the polling interval in Settings if you want it faster or slower. For advanced users, there is a batch processing option hidden in the tools menu. It lets you run all rules at once instead of waiting for the scheduled check. Useful when you come back from being away and have a week's worth of loose files to clean up. Takes about three seconds to process a few thousand files on my machine.

The Verdict

It works for what it is. A straightforward, no-nonsense automation tool for people who don't want to script their own file cleanup. If you need cross-platform support or network drive reliability without workarounds, it's not the right call. Pair it with a proper backup solution and you won't lose anything when the auto-delete fires. That's the only way I'd recommend running the aggressive rules. Keep a recent backup, test every new rule with a copy folder first, and you'll be fine.