Google Drive has no bulk rename. You can rename files one at a time, or you can write an Apps Script that does find-and-replace on names that were meaningless to begin with.
The short answer
Renaming files in bulk in Google Drive means one of two different jobs. If the existing names contain the information and just need reformatting, an Apps Script find-and-replace is enough. If the names are meaningless — Scan_0043.pdf, IMG_4471.pdf, Untitled document — then no amount of string manipulation helps, because the information you want is inside the document, not in its name. For that, a workflow reads each file and the Rename step names it from its contents. Point it at a folder and it works through what is already there, renaming in place.
Steps this uses
Before and after
As they arrive
After the workflow
Four consecutively scanned files that share nothing in their names, renamed from four different documents.
Setting it up
Choose the Google Drive folder holding the files. A workflow can run over what is already in it, not only what arrives later.
In plain English: the date on the document, the document type, the party. You are describing the output, not writing a pattern.
The Read Details from File step pulls those details off the document itself. This is why it works on files whose current names say nothing.
The Rename step writes the new name to the file where it sits in Google Drive. Nothing is copied, moved, or re-uploaded, so links and permissions survive.
If every file is named `2026_08_invoice_acme.pdf` and you want dashes instead of underscores, that is string manipulation and a script does it in a few lines, for free. Use the script. The case where scripts cannot help is the common one: names that never contained the information, because the scanner or the camera or the download assigned them.
Most automation only acts on new files, which leaves the backlog untouched — and the backlog is usually the reason you went looking. A workflow can run on a schedule across a folder you point it at, working through existing documents. The same naming applies to both, so the folder converges on one convention rather than splitting into before and after.
It reads one document at a time and names it from what that document says. It does not compare fields across a set of files, and it does not notice that a document is missing from a sequence. If the information you want in the filename is not in the document, no amount of reading will find it.
FAQ
Not with a built-in feature — Google Drive renames one file at a time. Bulk renaming requires either an Apps Script for find-and-replace on existing names, or a workflow that reads each document and renames it from its contents when the existing names carry no information.
Point a workflow at the folder, describe what the names should contain in plain English, and the Rename step applies it to each document in place. For files whose names already contain the right information in the wrong format, a Google Apps Script find-and-replace is simpler and free.
No. Sharing and links are attached to the file ID rather than the name, so a file renamed in place keeps its permissions and its links.
Yes. A workflow running on a schedule works through the folder you point it at, so existing files get the same naming as new ones rather than leaving you with a backlog under the old convention.
Point a workflow at a folder and it works through what is already there.
Try The Drive AI Free5 GB free · No credit card required