automation

Is there a Hazel for Windows? Rule-based automation

If you landed here searching for a Hazel for Windows, the short answer is: Hazel itself doesn’t run on Windows — it’s a macOS-only app. The useful answer is that its idea — rules that watch folders and organize files on their own — does exist on Windows, and today it even comes with two safety nets Hazel never had: a preview before, and an undo after. This guide explains what Hazel does, why Windows went so long without a proper equivalent, and what a modern automation tool needs — with a full example built from scratch, using the real on-screen labels.

What Hazel is, and why people love it#

Hazel is a Mac utility (from Noodlesoft, a one-time license around US$42) that runs in the background and watches the folders you point it at — usually Downloads and the Desktop. You write rules: “if the file is a PDF and has ‘invoice’ in its name, move it to Documents/Invoices and rename it with the date.” From then on, every new file that lands in the folder gets evaluated and filed on the spot, with no effort from you.

The love for Hazel has a simple explanation: it turns a boring, never-ending chore — keeping Downloads tidy — into something that happens by itself. You teach the rule once and it works forever. It’s deterministic automation: same input, same result, every day, no surprises.

The historical gap on Windows#

On Windows, anyone who wanted this had basically two options for years, and it’s worth being honest about each:

  • File Juggler. A solid, paid rule engine, well-loved by the people who use it. It watches folders, matches on name, type, size and even content, and moves/renames automatically. For a long time it was the closest thing Windows had to Hazel. If it already covers your case, it’s a respectable choice.
  • DropIt. A lightweight, free classic. You drag files onto a floating target and it distributes them by “associations” (patterns). It proved Windows users want pattern-based automation — but its development slowed, and it never gained things like OCR content matching.

Neither is bad. What was missing was a modern package that paired the rule engine with a real safety net and a complete file manager around it. That’s the gap Elegant File Explorer fills — and our Hazel for Windows page shows the whole product. Here, the focus is on teaching the concept.

What a modern automation tool needs#

After building hundreds of rules, what matters boils down to five pillars. All of them come straight from how the engine actually behaves.

1. Three triggers — the “when”

The trigger answers when the rule kicks in, and you pick one per rule in the “When to run” card of the wizard:

  • Real time“Automatically, when a file arrives (real time)”. Acts the instant a file lands in the folder. This is what makes Downloads organize itself while you download.
  • Periodic“Every so often (periodic)”. Runs every N minutes (default 15) and also when the app opens. Great for unhurried cleanups.
  • Manual“Only when I say (manual)”. Runs only when you click “Run now”. Every new rule is born Manual — the safe way to start.

2. Combinable conditions — the “which files”

In the “Which files (conditions)” step you stack conditions and combine them with AND/OR — and, in Advanced mode, with groups within groups. You can match on Name contains, Extension is, Size greater than (KB), Older than (days), Downloaded from site (domain), and even Content contains (PDF, DOCX, TXT) — that last one reading the text inside the file, including scanned PDFs via OCR. No scripting.

3. Simulate BEFORE

This is the first thing Hazel never had. The “Simulate effect” button runs a full rehearsal: it scans the files, applies the conditions, resolves destinations and conflicts, and shows the exact list of what would happen — “Preview — nothing is actually changed”. Nothing is written to disk. If a destination came out wrong, you catch it here, not after the damage.

4. Undo AFTER

The second thing Hazel lacked. Every automatic run shows a toast — “Autopilot acted” — with an “Undo” button beside it; one click returns each file to where it came from. It works for move, copy, rename, organize by type and zip. And deletes are never permanent: they go to the Windows Recycle Bin, recoverable there.

5. It never trips over itself

Picture a Copy rule whose destination sits inside the very folder it watches. A careless tool would copy a file, notice the copy, copy that, and fill your disk in a runaway loop. This simply doesn’t happen here: the app knows the difference between the files it should act on and the ones it already filed, and leaves what’s already in place alone. You get the automation without the runaway. The snake never bites its own tail.

A full example, built step by step#

Let’s file the PDF invoices that land in Downloads. In the automation manager, click “+ New rule” and follow the 5-step wizard:

  1. Rule name. Type something like Invoices to the right folder.
  2. Monitored folders. Click “+ Add folder” and point to Downloads. Set “Include subfolders” however you like.
  3. When to run. To test calmly, start on “Only when I say (manual)”. You’ll promote it to real time later.
  4. Which files (conditions). Under “Match All (AND) of these conditions”, add Extension ispdf and Content contains (PDF, DOCX, TXT)invoice. That way only PDFs that actually mention an invoice get in.
  5. What to do (actions). Add Move to and, in the “Destination or pattern” box, type Documents/Invoices/{year}/{month-name}. The placeholders become values on the spot: a file from March 2026 goes to Documents/Invoices/2026/March.

Before saving, click “Simulate effect” and check the list: each line shows the file, the action and the final destination. Looks right? Click “Save rule”, then “Run now” to apply. Once you trust it, edit the rule and switch the trigger to real time — Downloads starts tidying itself.

Rule wizard in a Hazel-for-Windows alternative — monitored folders, when to run, conditions, and the Simulate effect button Rule wizard in a Hazel-for-Windows alternative — monitored folders, when to run, conditions, and the Simulate effect button
The same example in the wizard: numbered steps, and Simulate effect before you save.

An honest comparison#

Feature Hazel File Juggler DropIt Modern automation (EFE)
Runs on Windows No (Mac only) Yes Yes Yes, native
Watches folders in real time Yes Yes Yes Yes
Simulate before applying No No No Yes, every run
Undo the run No No No Yes, one click
Reads inside PDFs (OCR) No Partial No Yes
Ready-made recipes No Few Templates 100+
100% local Yes Yes Yes Yes

Hazel is still excellent — on the Mac. On Windows, its idea finally has a home, with the two pieces it was missing to automate without fear.

FAQ

Does Hazel run on Windows at all?

No. Hazel is macOS-only, with no Windows version and no practical way to run it under emulation. The path is to use a native Windows rule-based automation that does the same conceptual work.

Do I need to know how to code to build rules?

No. Everything is built in a visual wizard by picking conditions and actions from ready-made lists. For advanced cases, the name and content fields also accept custom patterns — but you’ll never need to touch them for everyday organizing.

Can the rules read the text inside a PDF?

Yes. The “Content contains (PDF, DOCX, TXT)” condition reads the file’s text, including scanned PDFs via built-in OCR that runs entirely on your PC. So the rule decides by what the document says, not just by its name.

Is it safe to leave it running on its own?

Yes, and that’s exactly where modern automation stands apart: it holds off on unusually large batches so you can look first, shows a preview before, gives you an undo after, never trips over its own files, and never deletes for good — everything goes to the Recycle Bin.

Do my files go to the cloud?

No. It’s 100% local: no account, no cloud, no telemetry. Your rules and files never leave your PC. You can see the details on the Hazel for Windows page.

Available now on the Microsoft Store.

Read next