Rename Scanned PDFs by What Is on the Page
A scanner names a file by the order it came off the glass. Scan_0043.pdf tells you it was the forty-third thing scanned, which is the one fact about it you will never need.
The short answer
Renaming a scanned PDF properly means reading the page, because the name assigned by the scanner carries no information about the document. A workflow watching the folder your scans land in uses the Read Details from File step to pull the date, the document type and the party off the page, then the Rename step writes that into the filename — in place, in the folder the scan is already in. The Move step can then file it. Scans that arrive as email attachments need the Save a Copy step first, because an attachment has no home until something gives it one.
Steps this uses
Before and after
What actually changes
As they arrive
- Scan_0043.pdf
- Scan_0044.pdf
- Scan_0045.pdf
After the workflow
- 2026-08-02-invoice-northwind-4821.pdf
- 2026-08-04-signed-contract-acme.pdf
- 2026-08-04-receipt-dataflow.pdf
Three consecutive scans of three unrelated documents.
Setting it up
Described once, then it runs
Send scans to one folder
Whatever your scanner already does is fine, as long as the output lands somewhere consistent — a Google Drive, OneDrive or Dropbox folder.
Describe the name you want
The date on the document, what kind of document it is, who it is from. In plain English, once.
The workflow reads the page
The Read Details from File step works from what is printed on the document, which is why it succeeds where the scanner filename fails entirely.
Renamed, then filed
The Rename step names it and the Move step puts it in the right folder. Both happen in place in your existing cloud storage.
Why scanner filenames are always wrong
A scanner knows two things: the order it processed pages and the time it did so. It cannot know that page forty-three was an invoice from Northwind dated the second of August, because it never read it. Every scanner naming scheme is therefore a counter, and every counter produces filenames that are unique and useless in equal measure.
Scans that arrive by email
Plenty of scanned documents never touch a scanner you own — they arrive as attachments from a client, an accountant, or a scanning service. An attachment has no home until something gives it one, so the Save a Copy step files it into cloud storage first, and the Rename and Move steps then treat it exactly like a scan from your own machine.
Multi-document scans
If you fed a stack through the sheet feeder and got one PDF containing eleven separate invoices, renaming is the second problem. The Split Document step separates them first, and each resulting document is then renamed on its own terms.
FAQ
Common questions
How do I rename scanned PDF files automatically?
Point a workflow at the folder your scans land in. The Read Details from File step reads the date, document type and party off the page, and the Rename step writes them into the filename. The file is renamed in place in your existing cloud storage.
Why does my scanner name files Scan_0043.pdf?
Because a scanner names files by the order it processed them and nothing else. It does not read the page, so it has no information about what the document is. Every scanner naming scheme is a counter for this reason.
Can I rename a scanned PDF that contains several documents?
Split it first. The Split Document step separates a multi-document scan into individual files, and each one is then renamed from its own contents.
Does this work on scans that arrive as email attachments?
Yes. The Save a Copy step gives the attachment a home in cloud storage first — an attachment has no folder of its own until something files it — and renaming proceeds from there.
Let the page name the file.
The date, the type and the party, taken off the document instead of the scanner.
Try The Drive AI Free5 GB free · No credit card required