Rename It! Tutorial: Automate File Renaming with Simple Scripts
Overview
This tutorial shows how to automate batch file renaming using simple scripts on Windows, macOS, and Linux. It covers common renaming tasks (prefix/suffix, find-and-replace, sequential numbering, date stamps) and provides ready-to-run examples in PowerShell, Bash, and Python.
Why automate
- Saves time for large numbers of files
- Ensures consistency in naming conventions
- Reduces errors from manual renaming
Typical tasks covered
- Add/remove prefix or suffix
- Replace or remove parts of filenames (find-and-replace)
- Add sequential numbers or zero-padded indices
- Insert file timestamps (creation/modified date)
- Change extensions in bulk
- Handle duplicates safely (skip, overwrite, or add suffix)
Example scripts (ready to run)
PowerShell (Windows) — add prefix “Project”:
powershell
Get-ChildItem -File | Rename-Item -NewName { “Project\(</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(54, 172, 170);">\).Name)” }
Bash (macOS/Linux) — replace spaces with underscores:
bash
for f in *; do mv “\(f</span><span class="token" style="color: rgb(163, 21, 21);">"</span><span> </span><span class="token" style="color: rgb(163, 21, 21);">"</span><span class="token" style="color: rgb(54, 172, 170);">\){f// /}” done
Python — zero-pad sequential numbering for .jpg files:
python
import os files = [f for f in os.listdir(’.’) if f.lower().endswith(’.jpg’)] for i, name in enumerate(sorted(files), 1): new = f”image_{i:03d}.jpg” os.rename(name, new)
Safety tips
- Always run a dry-run or print proposed names first.
- Work on a copy or test folder first.
- Handle collisions by checking if target exists before renaming.
- Preserve extensions and hidden files unless intended.
When to use which tool
- Use PowerShell for Windows-native environments and tight OS integration.
- Use Bash for Unix-like systems and quick shell one-liners.
- Use Python for cross-platform needs, complex logic, or metadata-based renaming.
Quick checklist before running a script
- Backup files or work in a copy.
- Confirm the script’s pattern matches only intended files.
- Test on 3–5 files first.
- Verify results and keep a log of changes.
Leave a Reply