What manual renaming actually costs
Typing is not the expensive part. The expensive part is the chain before it: open the file, scroll to the right spot, find sender and document date, decide whether the invoice date or the service date belongs in the name, switch back to the file manager, rename, verify. Every step is a context switch, and context switches are why ten minutes of filing feel like half an hour. At five documents a day it hardly matters; with Monday morning's inbox it does. Count honestly how many documents pass through your hands each week — that number settles this comparison, not a feature list.
Where renaming by hand is objectively better
There are cases where manual work wins, and we would rather list them ourselves. At a handful of documents per month, no setup time pays off. If the filename has to carry internal logic that is nowhere in the document — a project code, a client number, a caseworker initial — it cannot be derived from the content. And if the material falls under a confidentiality duty that rules out sending anything to an external service, the decision is already made. Anyone who still wants to automate then needs control over their own AI access rather than just any tool.
The real difference: patterns or content
Classic renaming utilities work on the filename: search and replace, add sequence numbers, append timestamps. Scan_001.pdf becomes Scan_001_2024.pdf — tidier, but still meaningless, because the information was never in the name. Manual work solves that because a person reads the document. Filery solves it by reading the file and analysing the text: sender, date, document type, subject. From those fields the app assembles the name according to your pattern. The human stays in the loop, but at the more useful point — confirming rather than transcribing.
Consistency beats speed
The stronger argument is not pace but uniformity. By hand, variants of the same name accumulate over months: “Telekom invoice March”, “Invoice_Telekom_03-2024”, “telekom march invoice”. The files sit in the same folder and still do not sort next to each other. A fixed pattern with a leading ISO date sorts every folder chronologically by itself, and a search for one sender finds all the hits instead of two thirds of them. By hand you only get that uniformity through discipline that holds up for months — and in practice hardly anyone sustains it.
Preview, history and the way back
Automatic does not mean unsupervised. Before every rename, Filery shows the proposed name next to the old one, either per file or for a whole folder at once. You confirm, correct or skip. What has been renamed then appears in a history inside the app, so it stays traceable what a file used to be called. You keep the checkpoint that your own eyes provide when renaming by hand, but hand over the searching and typing. If you distrust the first run, review the first twenty suggestions individually and release the rest afterwards. Scanned PDFs without a text layer are handled by the optional OCR.
What happens to your documents, and what getting started costs
So that nothing is glossed over here: Filery reads the PDF on your machine and sends the extracted content encrypted for AI analysis. What comes back are the recognised metadata — sender, date, type, subject — and the renaming itself runs again on your own device. The files themselves are not stored permanently. If you want the analysis to run through your own provider account, the Custom plan uses your own API keys for 5 € per month. The Starter plan covers 50 documents per month, free and without signup; Business is 30 € per month with 500 documents.
FAQ
Related topics
Download Now
Choose your platform and start with automatic document renaming
Windows
Windows 10 & 11
We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.
System requirements: macOS 10.14+, Windows 10/11
All downloads are transmitted securely via HTTPS.