// autoshelf
Every file you download carries metadata: where it came from. AutoShelf reads that metadata and routes files based on their source. GitHub repos to Developer. Slack files to Work. Figma exports to Design. All automatic.
Download from App Store// the problem
// how it works
Tell AutoShelf which download URLs or apps to watch for. GitHub, Slack, Figma, Gmail, or any source you specify.
Route files from each source to the right folder. GitHub goes to Developer, Slack goes to Work, Figma goes to Design.
Every file from every source gets routed to its destination automatically. No manual sorting, no thinking.
// built-in templates
The Sort by Source template routes files from common sources to the right folders.
// features
Route files by their download URL. Files from github.com go to Developer. Files from slack.com go to Work. Files from figma.com go to Design.
Route files by the app that downloaded them. Safari downloads to one folder, Chrome to another, Arc to a third.
Create rules for any source URL pattern. Use wildcards to match domains or specific download pages.
Source sorting works with file type rules. Route GitHub downloads to Developer, but only if they are .zip or source code files.
// faq
AutoShelf reads the download URL metadata that macOS attaches to every file. Create rules to route files from specific URLs to specific folders automatically.
Yes. AutoShelf knows which app downloaded each file. Route Safari downloads to one folder, Chrome downloads to another.
Yes. Create rules for any URL pattern. For example, route files from yourcompany.slack.com to a Work folder or files from github.com/my-repo to a specific project folder.
Files without download metadata (e.g., files created locally) are not affected by source-based rules. You can create type-based rules as a fallback.