How to set up a file organizing app in ten minutes
A file organizing app is only as good as its first rule. A ten-minute setup that sorts your Downloads folder without moving anything you did not expect.
Written by the team building Quick File Organizer, folders that organize themselves, by your rules.
Choosing a file organizing app is the easy part. The part people get wrong is the first twenty minutes afterwards: they write nine rules, point them at every folder on the machine, and discover a week later that something ended up somewhere strange.
Here is the setup that does not do that. It takes about ten minutes, it starts with one rule, and every step is reversible.
Before you install anything: pick the folder
A file organizing app applied to your whole drive is how people lose files. Applied to one folder that fills passively, it is close to magic.
The right first folder has three properties: things land in it without you
choosing, you rarely open it on purpose, and you have looked for something in
it and failed. On most machines that is Downloads. On some it is
Pictures\Screenshots — the full list of where Windows puts things is in
where screenshots are saved.
Step one: install and point it at that folder
Install from the Store
Skip anything that asks for an account before it will sort a folder. There is no reason a local tool needs one.
Add your chosen folder
Just the one. Resist adding Desktop at the same time — you want to be able to tell which rule did what.
Look at what is already in there
Sort by type. You will usually find four or five real categories and a long tail of things you will never open again. That list is your rule set.
Step two: write one rule
The instinct is to describe your whole filing system at once. Do not.
Pick the single most common thing in that folder — usually PDFs or installers — and write one rule for it. Where should a PDF that lands in Downloads go? Answer that, write it, and stop.
One rule is enough to learn three things: whether the destination folder was the right choice, whether the rule catches what you expected, and whether you actually look in the new location afterwards. All three are commonly wrong on the first attempt, and all three are cheap to fix when only one rule exists.
Step three: preview before anything moves
Any file organizing app worth installing will show you what a rule is about to do before it does it. Use it every time you add a rule, not just the first.
Read the list properly. You are looking for two things: files you expected to match that did not, and files that matched that you did not intend. The second is the dangerous one, and it is almost always a rule that is broader than the sentence you had in your head when you wrote it.
Step four: deal with the backlog separately
Rules are for files that arrive. They are a poor tool for four thousand files that arrived over three years, because your categories have changed since and the old files do not match the way you think now.
Do the backlog by hand, once, and coarsely: sort by date, keep the last month, move everything older into a single dated archive folder. Do not try to categorise it. It is searchable, it is out of the way, and the time you would spend sorting it properly is better spent on the rules that stop it happening again. The same approach applied to a desktop is in how to clean up your desktop.
Step five: run it by hand for a week
This is the step everyone skips, and it is the one that decides whether the setup survives.
Run the rules manually for a week before you let anything run unattended. You are testing a judgement, not a feature: do files land where you expected, and do you find them there later without thinking? If yes, automation is worth having. If no, automating it would only have made the wrong outcome happen faster and more often.
After that week you will know whether you need the thing to watch the folder on its own — which in most file organizer apps, ours included, is the paid tier. What that costs and whether it is worth it is set out in what Pro adds.
The four mistakes that undo all of it
Too many rules on day one. When something lands somewhere odd you cannot tell which rule did it. Add them one at a time, a few days apart.
Destinations on another drive. A rule that files into a folder on a different volume turns every arrival into a full copy instead of an instant index edit, and fails entirely when an external disk is unplugged. The mechanics are in why moving files to another drive is slow.
Rules that overlap. Two rules that both match .pdf will fight, and which
one wins is not something you should have to reason about. Keep each file type
in exactly one rule.
Filing things you should delete. Installers you have already run do not
need a folder. A delete rule for .msi and .exe older than you care about is
usually more useful than a tidy Installers folder nobody opens.
If you have not settled on the app yet, Quick File Organizer vs File Arbor compares the two closest options on the exact things this setup depends on — the preview step and where the free tier stops.
Common questions
How long does setting up a file organizing app actually take?
About ten minutes for the first folder and rule, then a week of using it before you add more. The ten minutes is the easy part; the week is what makes it hold.
How many rules should I end up with?
Three to five per folder covers most cases — documents, images, installers, archives and a catch-all. If you are heading past ten, the folder structure underneath is usually the thing to fix.
What if a rule moves something to the wrong place?
Move it back and narrow the rule. This is why the first week is manual: a mistake you catch immediately is a nuisance, and the same mistake running unattended for a month is a search.
Can I undo a whole run?
Depends on the tool. Ours previews rather than undoes, which is why the preview step is not optional. Check what your tool offers before you point it at anything you care about.
Should the app start with Windows?
Only once you have stopped adjusting rules. Until then you want to run it deliberately so you can connect a change to its effect.
Does this work for a shared or work PC?
The rules do, but check the policy first — moving files on a machine you do not own can cause problems no rule anticipated, especially with synced folders.
Which folders should I never point it at?
Anything an application owns: Program Files, AppData, a game's install folder, and the system drive's root. Those folders are structured the way they are because software depends on it.