How it works
- Watches your Downloads folder, wherever you moved it, or another folder you pick; subfolders only if you ask.
- Filter by name patterns like *.pdf; *.zip, and in the advanced options by the site the file came from, like github.com.
- A file counts as finished once the browser's temporary file is gone, its size has stopped changing and nothing is still writing it, without ever blocking the browser or antivirus.
- The routine gets the file's path, name, extension, size and the web address it came from.
- Files KeyRoutines itself just moved or renamed are ignored, so a sorting routine never sets itself off.
Routines that use it
Archive zip downloads
For *.zip downloads, Move or copy file puts them in Downloads\Archives.
Rename PDFs
When a PDF finishes, Rename file adds today's date to its name.
Handle files from one site
Only for downloads from github.com, Unzip file extracts them and Show banner says where.
Settings
| Setting | What it does |
|---|---|
| Folder | The folder downloads land in (empty = your Downloads folder). |
| Pattern | Only names like these, e.g. *.pdf or *.zip; *.7z (empty = every download). |
| Include subfolders | Also downloads saved into folders inside it. |
| From siteadvanced | Only downloads from this site, e.g. github.com. |
Good to know
- The site filter relies on the web address the browser records with the download.
Questions
- How can I run something automatically after a download completes?
- Create a routine with the Download finished trigger and add your steps. It fires once per finished file, after the browser has fully written it.
- Does it work with Chrome, Edge and Firefox?
- It watches for the temporary files browsers use while downloading, including Firefox's .part files, and waits until they're gone. It doesn't depend on one browser.