Downloads Butler

How it works

The tiny route from incoming file to useful folder.

Downloads Butler does not replace Chrome downloads. It gives Chrome a better filename and folder suggestion at the right moment.

1

Chrome starts a download

A file begins downloading like usual. Downloads Butler listens for Chrome's download filename decision moment, which is exactly when a little organization can prevent a future folder sigh.

2

Downloads Butler builds a candidate

The extension reads available metadata such as original filename, extension, MIME type, source URL, referrer, download time, and browser download id. If Chrome gives weak source clues, it checks safer fallbacks before surrendering to Unknown.

3

Priority decides the behavior

Manual one-time choices, active sessions, saved rules, and general defaults are checked in order. Enabled rules also get conflict checks, because one file should not need to attend a committee meeting.

4

Sorting chooses the folder

The file can be sorted by group, exact type, website/source, or your preferred order. Source-aware sorting stays useful even when the file type itself is not special.

5

Renaming chooses the filename

If Renaming is active, Downloads Butler can build a cleaner name from simple parts like Date, Website, and Name. Because download (12).pdf is not a filing strategy.

6

Chrome gets a safe suggestion

Downloads Butler returns a Chrome-safe relative filename and folder path. The file lands organized before the mess gets a chance to unpack its tiny suitcase.

Safety

The sharp bits have guardrails.

Rules

Contradictory saved rules can exist, but Downloads Butler blocks them from being enabled together.

Sessions

A focused session can pause ordinary rules, then let the previous setup return when the session ends.

Rescue

Subfolders are excluded by default, project-looking folders get caution, and cleanup starts as a preview.

Less magic. More clear rules.

The goal is not to be mysterious. The goal is to make downloads land in places that make sense, then show you what happened in the local log.