automation

Automatically move files from one folder to another

You keep dragging the same files from the same place to the same destination. Every PDF from Downloads to Documents/PDFs. Every invoice to its folder. It’s mechanical, it’s daily, and it’s exactly the kind of thing a computer should do for you. So you search “automatically move files from one folder to another windows” — and the classic answer is a script you have to write, schedule, and then babysit forever. There’s a calmer way: a watched folder. You describe the move once, and from then on the file gets sorted the instant it lands — no button, no script, no you.

This post is deliberately narrow. It’s not a tour of everything rules can do — that’s the anatomy of a perfect file rule. It’s the single most-asked task, done end to end: one folder → one condition → move to another folder, running on its own in real time.

The idea: a folder that acts the moment a file arrives#

Windows has no built-in way to keep watching a folder and quietly move whatever shows up. That’s the gap. A watched-folder rule fills it: you point at the folder where the mess is born (usually Downloads), say which files you care about, and say where they should go. After that, the folder watches itself. A file lands, gets recognized, and moves — while you’re still doing something else.

File arrivesRule recognizes itSimulateMoveUndo

That chain is the whole life of the feature. The first four happen without you; the last one is always there if you want it. Let’s build it.

Build the one rule, step by step#

Open Automation and click “+ New rule”. The wizard has a handful of numbered steps, and none of them asks you to write a single line of anything.

  1. Rule name — call it something you’ll recognize later, like PDFs to their folder.
  2. Monitored folders — click “+ Add folder” and pick your Downloads. Leave “Include subfolders” off for now; you want the top of Downloads, not everything under it.
  3. When to run — this is the switch that makes it automatic. Choose “Automatically, when a file arrives (real time)”. That’s the trigger that turns a folder into a watched folder.
  4. Which files (conditions) — keep it to one condition: Extension ispdf. One condition, one file type. Nothing fancy — that’s the point.
  5. What to do (actions) — add Move to, and in the “Destination or pattern” box type Documents/PDFs. Done.

That’s the entire rule: watch Downloads, and the moment a PDF arrives, move it to Documents/PDFs. Source, condition, destination. If you later want dated subfolders like Documents/PDFs/{year}, the placeholders are covered in the placeholders guide — but you don’t need them to get the move working.

Automation rule wizard: rule name, the Downloads folder as monitored, the real-time trigger, an Extension-is condition, and a Move-to action Automation rule wizard: rule name, the Downloads folder as monitored, the real-time trigger, an Extension-is condition, and a Move-to action
One folder, one condition, one destination — the whole rule fits on a single screen.

Rehearse before you trust it#

Before saving, click “Simulate effect”. The app scans the folder, applies your one condition, works out every destination, and shows you the exact list of what would move — under a fixed banner that reads “Preview — nothing is actually changed”. Not one file moves during this. If the destination came out wrong, or the condition grabbed more than you meant, you see it here, on screen, where fixing it costs nothing. The full trust cycle behind that button is its own story — we tell it in preview before organizing, then undo.

For a real-time rule this matters extra, because after you save it, the move happens on its own. Simulating once is how you earn the confidence to let it fly.

What happens when a hundred files arrive at once#

Here’s the reassuring part people don’t expect. Real time is built for the normal trickle — one file arrives, one file gets sorted. It is not built to silently shovel a huge pile. So if you suddenly dump a hundred old PDFs into Downloads, the watched folder doesn’t quietly move them all behind your back. A large batch like that waits for you — it stays put and lets you run and review it by hand, instead of acting on a mountain of files without you watching.

So the everyday flow (“a file just arrived”) is handled the instant it happens, and the occasional avalanche is left for your review. You get automation for the common case and a speed bump for the rare, risky one — without configuring anything. If you’d rather promote a rule to real time slowly, earning trust one step at a time, that journey is from manual to autopilot.

And if it moves something you didn’t mean to — undo#

Every automatic move can be undone. When the watched folder acts on its own, a small “🤖 Autopilot acted” notice appears in the corner with an “Undo” button beside it; one click returns each file to exactly where it came from. And it isn’t only that toast — the Run history in the Automation manager keeps every run, each with its own “Undo”, so you can reverse a move from days ago. Moving files is fully reversible here, which is why letting a folder move them on its own stops feeling like a gamble.

The same rule, other folders#

The recipe generalizes without any new skills. Point the same one condition → Move to shape at whatever pattern you repeat by hand:

  • Screenshots piling on the Desktop → Name contains ScreenshotMove to Pictures/Screenshots.
  • Installers cluttering Downloads → Extension is exeMove to Downloads/Installers.
  • Spreadsheets you always file → Extension is xlsxMove to Documents/Sheets.

Each is one folder, one condition, one destination — the exact same rule you just built, aimed somewhere new. Start with a single one, watch it work for a few days, then add the next. That’s how a couple of watched folders quietly take over the dragging you used to do all day.

Frequently asked questions

Can Windows move files between folders automatically on its own?

Not on its own — there’s no built-in watched-folder feature, which is why the usual online answer is a script you have to write and schedule. A watched-folder rule gives you the behavior directly: pick the source, one condition, and a Move to destination, set the trigger to “Automatically, when a file arrives (real time)”, and the folder sorts itself from then on.

Do I have to keep the app open for the automatic move to happen?

Yes. Real-time watching runs while the app is running; nothing moves when it’s closed. When you open it again, it picks up watching where it left off.

What if the wrong file gets moved?

You’ll usually catch it in the simulation before it ever runs. If a move does slip through, the “🤖 Autopilot acted” toast has an “Undo” right there, and the Run history keeps every run with its own undo. Moves are fully reversible.

Will it move a file that's still downloading?

No. The watcher waits until a file has finished and is no longer being written before it touches it — a half-finished download is never moved.

Can I move files to a subfolder by date automatically?

Yes. In the “Destination or pattern” box, add placeholders like Documents/PDFs/{year}/{month-name}, and each file lands in the right dated folder. The placeholders guide lists them all.

Available now on the Microsoft Store.

Read next