Source-aware
Source-Aware Folders
Group downloads by where they came from, even when Chrome gives incomplete metadata or the file type itself is not special.
Path 1
ChatGPT / Documents
Path 2
GitHub / Archives
Path 3
Yahoo / Documents
The problem
A folder named Documents is useful. A folder named Documents / ChatGPT is often better. Source context gives files a memory of where they came from.
How Downloads Butler handles it
- Downloads Butler reads Chrome download metadata such as final URL and referrer when available.
- When Chrome gives weak metadata, the extension can use active-tab context as a fallback.
- The source label is cleaned for humans, so common hosts can become names like ChatGPT, GitHub, LinkedIn, PayPal, or Yahoo instead of raw URL soup.
- The goal is not to guess wildly. It is to use stronger clues before settling for Unknown.
What you control
- Choose source-first or group-first sorting.
- Use source context with broad groups or exact file types.
- Keep source-aware routing even for files that do not have a special type rule.
- Let rules override defaults when a site deserves special treatment.
Practical examples
- Research PDFs from one site can stay together.
- GitHub archives can go to a developer folder without hand-sorting.
- Documents from webmail or cloud services can keep their source context.
Local note
Source detection is used locally to build folders and names. Downloads Butler does not create a hosted browsing or download history.
Related
Other tidy drawers to open.
Sorting
Download Sorting
Choose where Chrome downloads should land by group, exact type, website/source, or your preferred order, with source detection kept separate from file type.
Renaming
Smart Renaming
Build readable filenames from Date, Website, and Name, then choose the order that makes sense for how you search later.
Local-first
Local-First Download Manager
Downloads Butler works locally in Chrome with no account, no cloud dashboard, no hosted download history, and exportable local settings.