Bulk File Renamer / File Naming Studio
100% client-side file batch renaming with zero uploads. Preview all changes in real-time, inspect collisions, Windows reserved names, and invalid characters before execution. Apply sequential numbering, text replacement, regex, case conversion, and export via Safe ZIP or Direct In-Place Rename.
- 100% in-browser processing with zero server uploads and zero persistent storage usage
- Full real-time before/after preview with character-level diff visualization
- Rigorous collision detection, Windows reserved name checks, and invalid character validation
- Natural sort (1, 2, 10), sequential numbering (padding, step, direction), and date token expansion
- Find & replace, removal, insertion, ReDoS-protected regex, case conversion, and whitespace normalization
- Direct In-Place Rename (supported browsers) and Safe Export (ZIP) download fallback
Direct Rename is available when the current browser and execution environment provide the required File System Access API capabilities and the user grants read/write permission. Unsupported environments can use Safe Export instead.
No files registered. Click 'Select Files' or 'Load Sample Files' to get started.
About Bulk File Renamer Studio
A powerful, browser-native file naming studio designed to bring desktop-grade batch renaming capabilities to the web with zero installation.
All processing, rule execution, preview rendering, and ZIP generation run 100% locally inside your browser's memory. Zero file contents, filenames, or directory paths are ever uploaded to remote servers or saved in persistent storage.
Preview First & Rigorous Safety Validation
Inspect a side-by-side comparison of current and target filenames in real-time before any disk modifications take place. Distinct character-level diff highlights allow you to immediately recognize changed, unchanged, or conflicting files.
The validation engine proactively detects duplicate target names within the batch, collisions against existing files in your folder, Windows reserved device names (CON, PRN, AUX, NUL, COM1-COM9, LPT1-LPT9), forbidden characters, and configured portability length warning thresholds (255 characters/bytes).
Comprehensive Rule Pipeline & Natural Sorting
Chain multiple renaming rules in any sequence: search and replace, text removal, insertion at specific positions, ReDoS-protected regular expressions, case formatting (Title Case, camelCase, kebab-case, snake_case), and whitespace normalization.
Full support for Natural Sort ensures numbers are ordered intuitively ('photo1, photo2, photo10'). Pad sequential numbers with zero padding (e.g. 001, 002) and expand dynamic tokens like {original}, {n:001}, and {yyyy}.
Dual Execution Modes: Direct Rename & Safe Export
Direct Rename is available when the current browser and execution environment provide the required File System Access API capabilities and the user grants read/write permission. Multi-stage rename plans with temporary names are designed to avoid detected swap and chain collisions.
In unsupported environments or for workflows requiring zero direct disk modification, Safe Export packages renamed files into a ZIP archive generated in memory (note that filesystem-specific metadata like creation dates may not be fully preserved in ZIP archives).
Terminal Script Generators & Absolute Privacy
For power users and system administrators, the studio can generate pre-escaped, ready-to-run PowerShell (.ps1) and POSIX Bash (.sh) automation scripts for terminal execution.
Zero tracking, zero cookies, zero localStorage, and zero file analytics. Your confidential files, sensitive documents, and personal photos remain completely private on your local machine.
Frequently Asked Questions (FAQ)
What is bulk file renaming?
Bulk file renaming allows you to rename multiple files simultaneously using automated rules such as sequential numbering, prefixes, suffixes, search-and-replace, and case formatting.
Can web browsers really rename files locally?
Direct Rename is available when the current browser and execution environment provide the required File System Access API capabilities and the user grants read/write permission. Unsupported environments can use Safe Export instead.
Are files or filenames uploaded to any remote server?
No. Files are processed entirely within your browser and are never uploaded to any remote server. Filenames, directory paths, file contents, hashes, and metadata are never sent across the network or to analytics.
Does the tool read or re-encode file contents?
No. The rename engine strictly operates on filename metadata. Image, video, audio, and document payloads remain byte-for-byte identical.
Can I select an entire folder of files?
Yes. In supporting browsers, click 'Select Folder' to choose a directory. All files within the directory are instantly listed for batch operations.
What is the Preview first principle?
Before any modifications occur on disk, the tool displays a side-by-side comparison of original and target filenames, complete with change highlights and error indicators.
What is Dry Run mode?
Dry Run simulates the entire rename pipeline in memory without touching your filesystem, allowing you to verify numbering, formatting, and collision states safely.
How does Sequential Numbering work?
You can specify start number, step increment, zero-padding (e.g. 001), direction (ascending/descending), and placement (prefix, suffix, replace existing number, or standalone).
What is Natural Sort?
Natural sort orders numeric components by value rather than strict ASCII codes, correctly arranging 'file1, file2, file10' instead of 'file1, file10, file2'.
Can I use regular expressions (Regex)?
Yes. Full regular expression search and replace with capture groups ($1, $2) is supported. The engine includes automated ReDoS detection to protect against exponential backtracking.
What case conversion styles are available?
You can convert filenames to lowercase, UPPERCASE, Title Case, camelCase, snake_case, or kebab-case with a single click.
Can I change file extensions?
Yes, you can standardize extensions to lowercase or replace them. Please note that changing a filename extension does not convert the underlying file format.
How are Windows reserved names and filename length limits handled?
Filename length rules vary across operating systems and filesystems. Solasu warns about names that exceed its configured portability threshold (255 characters/bytes); this threshold should not be interpreted as a universal filesystem limit. Windows reserved device names (CON, PRN, AUX, NUL, COM1-COM9, LPT1-LPT9) and forbidden characters are also flagged beforehand.
Are Unicode and international characters supported?
Yes. Unicode characters across all languages (Japanese, Arabic, Cyrillic, accented Latin, emojis) are fully preserved using NFC normalization.
What is Collision Detection?
Collision detection identifies when two or more files would end up with identical filenames after applying your rules, preventing accidental data overwrites.
Will it overwrite existing files in my directory?
Solasu validates rename targets before execution and uses a multi-stage rename plan to avoid detected name collisions, including common swap and chain scenarios. Filesystem-level atomicity is not guaranteed by Solasu.
What is Safe Export (ZIP fallback)?
Safe Export creates a renamed ZIP archive completely in browser memory without modifying your original files. Please note that filesystem metadata (such as OS creation timestamps and permissions) may differ after ZIP export.
What are the PowerShell and Bash script generators?
They produce shell scripts containing safely escaped rename commands so you can audit the exact filesystem operations before executing them in your local terminal. The generated script has not been executed by Solasu.
Can I save my rename rules for later use?
Yes. Click 'Export Rules JSON' to save your rule configuration to a file. You can import it anytime using 'Import Rules JSON' (hardened against prototype pollution).
Can I undo a Direct Rename operation?
Solasu can generate an undo plan for the rename operation where supported, presenting reverse steps based on the immediate rename plan. However, complete filesystem recovery cannot be guaranteed in every external state (for example, if files were moved or altered externally).
Is any data stored in cookies, localStorage, or IndexedDB?
None. All filenames, rule parameters, and intermediate structures are stored in volatile session memory only and are immediately destroyed when you close the tab.
How does the tool perform with thousands of files?
The engine uses efficient in-memory indices and virtualized list rendering, enabling smooth preview and sorting of 10,000+ files without browser freezing.