Hazel alternatives: what you can drop

Searches for a Hazel replacement rarely begin with a feature that is missing. They begin with a Downloads folder that is full again after months of being empty, or with a rule set that has grown past the point where anyone can say what it does. Nothing failed loudly. A condition stopped matching, and files quietly stayed where they landed. That is a maintenance problem wearing the costume of a software problem, and swapping applications does not solve it by itself.

The useful question is narrower. One window is doing several unrelated jobs at once. Some of those jobs can be handed to parts of macOS that are already installed, some cannot, and the split is not where most comparison articles put it.

Read the log before reading a feature list

Before any of this, there is a measurement worth taking. Hazel writes a log of what it did to each file, reachable from Help > View Logs or from View Log in the status menu, and the search field narrows it to a single filename. Open it and count two things: how many distinct rules fired in the last month, and how many folders those rules belong to.

There is a second number in the same place that is worth writing down: how many of the fired rules touched files that were already where they should be. Rules that move a file into a folder it would have been dragged to anyway are doing real work. Rules that rename a file nobody opens again are not, and they still carry the cost of being read and reasoned about every time the set is reviewed.

The result decides most of what follows. A rule set that looked like thirty rules often turns out to be four that fire daily, three that fire monthly, and a long tail that has not matched anything since the naming convention of some export changed. The tail is not doing work. It is doing the opposite, because it makes the active rules harder to find. Counting first also protects against the most common outcome of a replacement, which is carrying all thirty rules into a new tool and arriving at the same confusion a year later.

What one window is actually doing

Split the application into jobs rather than features, and there are five:

• Watching folders and reacting when their contents change
• Matching on attributes: name, date, kind, size, where a download came from
• Matching on content: text inside a document, including text that has to be recognised first
• Acting: move, copy, rename, tag, archive, upload, run a script
• Keeping the Trash in check, including finding support files left behind by deleted applications

The fifth is easy to forget because it runs without being asked. App Sweep watches for an application going into the Trash, then offers the support files that came with it. Automatic deletion clears the Trash by age or by size.

The third job changed shape recently. Hazel 6 added on-the-fly text recognition, so a PDF that was never put through OCR, or a plain image, can still be matched on the words inside it. The same release reads encrypted PDFs when a password is supplied, storing that password in the keychain, and added a Revert command in the Finder context menu that returns a file to its original location and name and restores properties such as tags and comments.

Which jobs hand off, and to what

Set the five jobs against what macOS already includes and the picture separates cleanly.

Job	What can take it over	What is given up
Watching folders	Folder Actions, or a launch agent watching a path	Any record of what fired and what did not
Attribute matching	Smart Folders, find, mdfind	Conditions and actions living in one place
Content matching	Text recognition in Preview, done by hand	Using the recognised text as a condition
Acting	Finder's multiple-item rename, shell commands	Automatic application without being asked
Trash hygiene	Finder's option to remove items after 30 days	Clearing by size, and support file detection

The top four rows are genuinely transferable if the price in effort is acceptable. Folder Actions have shipped with macOS for two decades and run an AppleScript when a folder's contents change. A launch agent can start a script when a specific path is modified. Finder's rename sheet handles find and replace, numbering, and adding text across a selection, which covers a surprising share of what people write rules for.

The bottom row does not transfer. macOS can empty the Trash on a schedule measured in days, but not when it crosses a size, and nothing built in goes looking for the preference files and caches that a deleted application leaves in the Library folder.

The scope is narrower than it looks

Two behaviours are worth checking before concluding that a replacement is needed, because both are frequently read as faults.

Subfolders are not monitored by default. A rule watching Downloads does not see a file that lands inside a folder within Downloads. Extending rules downward takes a separate rule that matches any folder and carries the action "Run rules on folder contents," which changes how the other rules apply rather than doing anything itself.

The Sync action is one way only. Files deleted from the watched folder are not removed from the destination, because a rule matches things that exist, and a file that is gone is not something a condition can match. The manual states this directly and points to dedicated sync software for two-way work with conflict handling. Someone who wanted two-way sync was never going to get it here, and no replacement file manager will supply it either.

A rule engine and a file manager are not the same purchase

A large share of replacement lists mix two categories that do different work, which is why they read as inconsistent. A rule engine acts on files when nobody is looking. A file manager shows files and waits for an instruction. Both put folders on screen, so the lists blur them, but they fail in opposite ways.

Automation that runs unattended is cheap while its assumptions hold and expensive the moment they stop, because the failure is invisible. A bank changes the filename of its monthly statement and a rule that has run for three years matches nothing, with no notification, until the folder is inspected. Manual work is the reverse. It costs attention every time, and it never surprises anyone, because nothing happens without someone asking for it.

The practical split follows from that. Files that arrive on a schedule in a predictable shape, statements, invoices, camera imports, receipts from the same handful of vendors, belong to automation. Files that arrive irregularly and have to be judged, project material, screenshots, downloads from a dozen unrelated places, belong to whichever window makes judging fast. Most people need both, and the mistake is buying one and expecting it to cover the other. Deciding which pile is larger is more useful than deciding which application is better.

Demo mode measures your own scale for free

There is a shortcut to knowing whether the built-in route is realistic. Without registration, Hazel runs for 14 days with everything except rule export available. After that it drops into Demo mode, which monitors one folder and allows two active rules.

Read those limits as a ruler rather than a restriction. An automation that fits inside one folder and two rules is an automation that a Folder Action or a short script can carry, and the maintenance burden of moving it is small. An automation spread across six folders with rules that read document text is a different proposition, and rewriting it as scripts moves work rather than removing it.

What a script costs that a rule does not

The part of the trade that gets underestimated is not the writing. It is the watching.

A rule engine ships three layers of observation. A preview shows what a rule would do while it is still being edited. A status window lists the files in a folder and which rule each one matches. A log records what happened per file, with a debug mode that makes the output far more detailed. The vendor's own troubleshooting page walks through them in that order, which is a reasonable definition of what "supported" means for automation.

A script started by launchd has none of that. It produces no output unless output is arranged, it fails silently by default, and the discovery that it stopped working typically arrives weeks later in the form of a folder that filled up. Reproducing even a thin version of those three layers, redirecting output to a file and reading that file on a schedule, is more work than porting the rules themselves. Anyone moving to scripts should budget for it deliberately rather than discovering it later.

The money side of staying

Replacement costs are easier to weigh against the cost of not moving, and that number is public. A single user licence is $42. A family pack covering up to five members of one household is $65, and the store page is explicit that it is for private households. Upgrading from any previous version is $20, the same price for either licence type, and the type carries over.

The FAQ states that this is not a subscription: a licence brings free updates within the major version it unlocks, and it keeps unlocking that version after a newer one ships. Purchases made during 2024 were eligible for a free upgrade to the current major version.

Four supply questions are worth asking about any tool before deciding to leave it, and they apply here with clear answers. Sales are open, direct from the developer, with licences delivered by download and email. No version has been withdrawn. Ownership has not changed: Noodlesoft has been a one-person company since 2006, based in New York, and the developer blog marked twenty years since the first release in September 2026 with a weekend discount. Pricing has not been restructured into a subscription. A replacement search driven by worry about any of those four can stop there.

What to change first

Count the rules that fired in the last month and the folders they belong to. If the answer is one folder and a couple of rules, the built-in pieces are enough and the licence is optional. If the answer spans several folders and any rule reads the inside of a document, the thing worth changing is not the automation but the window it is managed from: a file list, a terminal, and a place to describe the rule in words, sitting together rather than in three applications. Atriens is built around that arrangement, the overlap with rule based tools is laid out in Compared with other file managers, and the free and paid boundary is on Pricing.