ダウンロードフォルダの整理 alternatives: what you can drop

Searching for ダウンロードフォルダの整理 daitai usually means a rules app has been recommended, the price or the setup effort gave you pause, and now the question is whether there is a substitute. There is more than one, and they are not interchangeable. Each replaces a different slice of the job, and each gives up something specific. The more useful question is not which tool is cheapest but which parts of the job you can drop entirely, because the folder is the symptom and not the problem.

The folder is an inbox with no owner

A Downloads folder fills up for a structural reason. Every app writes into it, no app is responsible for it, and nothing in the system decides when an item there stops being current. A file arrives, gets used once, and stays. Multiply that by a browser, a chat client, a mail app, and a few tools that quietly expand archives, and a folder with four thousand items is the predictable outcome rather than a personal failing.

That structure tells you what any substitute has to provide. There are exactly three jobs in play. Reducing arrivals, so fewer things land there at all. Finding an item later, without reading four thousand file names. Deciding what can go, which is the one that stalls, because most items are neither clearly needed nor clearly disposable.

A rules app addresses all three at once, which is why it gets recommended. It also asks for a permanent process, a set of conditions you have to maintain, and in most cases a licence. If only one of the three jobs is actually hurting, paying for all three is the wrong shape of solution. Working out which one is yours takes about ten minutes and changes the answer more than any feature comparison does.

Five substitutes, and what each one gives up

These are the options that are genuinely available on a Mac without buying anything, plus the paid option for reference. The last column is the part people discover after committing.

Approach	Replaces	What it gives up
Sort by Date Added, sweep by hand weekly	Deciding what can go	Nothing is automatic, so it survives only as a habit
Saved search across the whole disk	Finding an item later	Files stay where they are, so the count never drops
Grouping in the Finder window	Scanning a long list	Cosmetic only, items are not moved or removed
Folder Actions with a script	Acting when a file lands	AppleScript or Automator, and errors are close to silent
Shell script plus a scheduled agent	Sorting and cleanup on a timer	Written and debugged by you, with no preview and no undo
Rules app such as Hazel, $42	All three jobs	A licence, a background process, and rules to maintain

Two of these deserve a note. Grouping in a Finder window changes how the list is drawn and nothing else, which is useful for a quick scan and useless for a folder that keeps growing. Stacks are the related feature on the Desktop, where files are gathered into piles by kind, date, or tag, and they do not apply to a Downloads folder window at all. People often try Stacks first because it is the most visible option, and conclude that macOS cannot help, which is the wrong conclusion drawn from the wrong feature.

Folder Actions, the built-in watcher nobody uses

The one substitute in that table that genuinely duplicates a paid app is Folder Actions. It has shipped with macOS for years, it attaches a script to a folder so the script runs whenever items are added, and it is set up by right-clicking the folder and choosing Folder Actions Setup. Automator provides a Folder Action workflow type for people who would rather not write AppleScript directly.

It is also the option with the highest abandonment rate, for one reason that has nothing to do with capability. When a Folder Action fails, it tends to fail without telling you. There is no status window listing what matched and what did not, so a rule that has quietly stopped working looks identical to a folder where nothing needed doing. That is survivable if you check the destination folder occasionally, and it is the reason many people who are perfectly comfortable in a terminal still end up preferring a script on a timer, where the output goes somewhere they can read.

What you can drop: reacting the moment a file lands

The headline capability of a rules app is that it acts immediately. A PDF arrives and is filed before you have looked at it. This feels like the essential part. For most people it is the part that can be dropped first.

Immediate action is only worth its cost when the delay itself causes harm. Two cases qualify. One is a shared destination where something else picks up the file next, such as a folder an import job watches. The other is high volume from a single reliable source, like a scanner writing two hundred documents a day with predictable names. Both are real. Neither describes a browser Downloads folder, where arrivals are irregular and the file's value is usually decided by whether you open it in the next ten minutes.

The substitute is a sweep on a schedule. A shell script that moves anything older than a set number of days into a dated archive folder, run by a launch agent once a day, covers the same ground with one difference: the file sits in Downloads for up to twenty four hours before it moves. If that is acceptable, and it usually is, the entire event-driven layer disappears along with the permanent background process it needs.

What you give up is worth naming. A script has no preview mode, so the first run is the test. It has no undo, so a bad pattern moves everything before you notice. Run it once with the move replaced by an echo, read the output, then run it for real. That one step replaces most of what a preview feature would have given you.

What you can drop: tags as the filing system

Tagging is the other feature that sells the idea and then quietly stops being used. A rules app can add coloured tags automatically, and tags are searchable across the whole disk regardless of folder.

The catch is not technical. It is that a tag has to be interpreted the same way in six months as it was on the day the rule was written, and nobody documents their tag vocabulary. Red meant urgent in March and important in July. A tag applied automatically by a rule is worse in this respect than one applied by hand, because the meaning was fixed by a condition you no longer remember writing.

The substitute for most cases is the file name plus a saved search. A name that begins with a date in year-month-day order sorts correctly, survives being copied to any other system, and carries its meaning without a legend. A saved search that collects, say, every PDF added in the last thirty days gives the same one-click view that a tag would, and needs no rule to keep it accurate because it reads what is already there. Saved searches live in the Finder sidebar and are built from File then New Smart Folder.

Where tags still earn their place is state rather than category. A single tag meaning "not yet dealt with", applied by hand and removed by hand, holds up because it has one meaning and a short life. That is a habit, not an automation, and it costs nothing to try.

What you can drop: a folder tree that mirrors your projects

The most expensive substitute is the one nobody counts: building a destination hierarchy for the rules to file into. Clients, then years, then document types. Ten minutes of design, and then a maintenance obligation forever, because every new client needs a folder and every rule needs updating to know about it.

Search has made most of this unnecessary. Spotlight indexes content, not just names, and the same index is reachable from the terminal through mdfind, which means a query can be part of a script rather than a thing you type into a window. If a file can be found in two seconds by searching, the folder it sits in is storage, not organisation.

A flatter structure holds up better. One archive folder per year, with dated file names inside it, needs no maintenance and no rule updates. It loses the ability to browse by project, which matters if browsing is how you actually work, and does not matter at all if you always arrive at files by searching. That is a question about your habits, not about the tools, and it is answered by noticing whether you reach for the search field or the sidebar.

What does not substitute: moving files to another volume

One trap sits underneath every option above. When the destination is on a different volume, whether that is an external drive or a network share, the operation is no longer a rename within a filesystem. It becomes a copy followed by a delete of the original.

Three consequences follow. Time scales with file size rather than being instant, so a sweep that moves a folder of video files is a long job rather than a quick one. An interruption can leave the copy partially done, with some files at the destination and some still in place. And the Date Added attribute that the Finder shows, the one most sweeps rely on for their age condition, is a property of the item in its current location rather than something that travels with the file, so files arrive at the archive looking newly added.

This affects every approach equally. A rules app, a shell script, and dragging a selection in the Finder all hit the same behaviour, because it is the filesystem doing it. The practical response is the same in all three cases: sweep to a folder on the same volume first, and move that archive folder to external storage as a separate, deliberate step. It also means that any age condition should read the created or modified date rather than Date Added, if you want it to keep working after the first archive move.

What to change first

Spend ten minutes sorting the folder by Date Added and scrolling to the bottom. If the oldest items are things you could delete without checking, the job you have is deciding, and a weekly manual sweep solves it for free. If instead you find items you need but could not have found by name, the job is finding, and a saved search solves that one without moving anything. Only if arrivals are outpacing both is a rules app the right shape of answer, and it is worth checking what a file manager with the terminal in the same window changes about the sweep itself before comparing licence prices, since a comparison of the alternatives tends to assume the sorting is the whole task. Atriens publishes its pricing alongside that comparison.