// autoshelf
Ever wonder where a file came from? Was it Safari, Chrome, Arc, Slack, or Finder? macOS tracks this data, but does not show it. AutoShelf reads the downloading app metadata and uses it to organize your files.
// the problem
// how it works
Every file downloaded on macOS carries metadata about which app downloaded it. AutoShelf reads this automatically.
Create rules that route files based on the downloading app. Safari files to Review, Chrome files to Downloads, Slack files to Work.
New files are sorted by their downloading app instantly. No metadata digging, no manual sorting.
// features
Route Safari downloads to a separate folder for review. Safari downloads tend to be intentional and important.
Browser downloads are often temporary. Route them to Downloads or a Browser Downloads folder for easy access.
File attachments from messaging apps belong in a Work or Chat Attachments folder, not mixed with other downloads.
Files copied via Finder or received via AirDrop are locally sourced. Route them to an Inbox folder for review.
// faq
AutoShelf reads the downloading app metadata that macOS attaches to every downloaded file. You can see this information in the app interface or set rules based on it.
Yes. Create rules that route files based on the downloading app. Safari files to one folder, Chrome files to another, Slack files to a third.
AutoShelf supports Safari, Chrome, Arc, Edge, Firefox, and most Chromium-based browsers. It also detects Slack, Discord, Finder, and AirDrop.
Files created locally or copied via Finder are tagged as locally sourced. Files without download metadata can be handled by a default rule.