For the folder full of final_FINAL (2)
Tidy NamesRename a messy folder to one consistent scheme.
Paste the file names. The page renames them by your rules, shows every old name against its new one, catches collisions and lost extensions, and writes a rename script that cannot overwrite anything. One run proposes one scheme for the whole folder and a new name for each file - using only what each name actually says.
1 The files and the rules free
Copy the names from a Drive folder, a Finder window (select all, copy) or ls. Dates like 05.03.2024 are read day-first. Nothing is renamed here - you run the script yourself. Or drop a .txt here.
2 Old name, new name free
To run a script, open a terminal in the folder that holds the files and move the script there. Mac, Linux: bash ./name-of-script.sh. Windows: powershell -ExecutionPolicy Bypass -File .\name-of-script.ps1.
What needs a look
3 One scheme for the folder metered
One run reads the whole list, picks the scheme that fits it - which parts are the date, the client, the kind of document, the version - and proposes a new name for each file, using only the dates, numbers and words that file's name or your description carries. Files it cannot place come back as questions. The page re-checks every name.
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
New names
Questions for you
The page's check
The scripts rename only the files whose new name passed every check, and keep the rest as they are. Run them in the folder that holds the files; keep the undo script next to them.
4 Saved folders
How it works
Each line is split into its folder, its name and its extension (.tar.gz stays together; a name starting with a dot has none). The page finds the first date in the name - 2024-03-05, 20240305, 2024-3-5, 05.03.2024, 5 Mar 2024, March 2024 - and any version tag such as v3, then applies your rules in order: find and replace, copy marks, dates, separator and case, prefix, numbering.
Every new name is checked against the others ignoring case, the way Drive, macOS and Windows compare names, and against what Windows refuses. The scripts first move each file to a temporary name and only then to its new one, so a chain of renames - a to b while b goes to c - cannot overwrite anything.
The run proposes names with judgement - which word is the client, which number is a version - but the page checks that every date, number and word in a new name came from that file's own name or your description.