Free tool · works now

Filename Rename Planner

Plan, preview, and validate batch file renames with casing presets, collision guards, and reversible shell scripts.

Runs 100% in your browser. Standardize vault naming conventions, resolve target collisions, and generate non-destructive shell rename scripts safely.

8Total files
6Renamed
0Unchanged
2Target collisions
Vault file paths listOne relative path per line

Paste outputs from terminal utilities. Supports standard relative paths, directory prefixes, and Markdown bullet lists.

Rename staging plan8 files evaluated
RENAMEDQ4 Product Launch Notes.md→q4-product-launch-notes.md
RENAMEDDatabase Migration Architecture.md→database-migration-architecture.md
RENAMED20261013 Executive Sync.md→20261013-executive-sync.md
RENAMED20261014 Board Review.md→20261014-board-review.md
COLLISIONmy_draft_ideas.md→my-draft-ideas.md
⚠️Target path 'notes/my-draft-ideas.md' is claimed by multiple source files.
COLLISIONmy-draft-ideas.md→my-draft-ideas.md
⚠️Target path 'notes/my-draft-ideas.md' is claimed by multiple source files.
RENAMEDLegacy Summary 2025.md→legacy-summary-2025.md
RENAMEDAPI Specification v2.md→api-specification-v2.md

Click "Copy bash rename script" to review the non-destructive commands in your local terminal.

The Architecture of Batch Renaming in Personal Knowledge Vaults

As Markdown vaults grow to hundreds or thousands of interconnected notes, naming conventions inevitably drift. What began as a neat system of kebab-case titles frequently absorbs mixed conventions: Title Case notes created in desktop interfaces, snake_case files exported from code repositories, and irregular date prefixes imported from mobile capture apps.

Why Blind Renaming Breaks Vault Integrity

In traditional file management, renaming files is considered a trivial operating system operation. In a linked Markdown knowledge graph, however, every file basename serves as an explicit foreign key. Bidirectional wikilinks such as [[Q4 Product Launch Notes]], image embeds like ![[architecture-diagram.png]], and heading anchors depend strictly on exact filename strings.

Running naive command-line renames or bulk renaming utilities without preflight planning creates broken references across your entire vault. A reliable rename pipeline requires three essential guarantees:

  1. Target collision prevention: Ensuring that two distinct source notes do not transform into the same target destination.
  2. Preservation of file extensions: Keeping syntax and media extensions intact without accidental truncation or case degradation.
  3. Wikilink traceability: Producing an auditable before-and-after mapping so you can safely orchestrate search-and-replace updates across your note library.

The Destination Collision Hazard

A subtle yet dangerous hazard of case and separator normalization is the target collision. Consider a vault containing two notes in the same folder:

When transforming these files with a kebab-case rule, both basenames evaluate to my-draft-ideas.md. A naive renaming script would overwrite the first file with the second, permanently destroying document history. This planner proactively detects all target collisions before any shell commands are generated, halting the operation and warning you to disambiguate the source files.

ISO Date Prefix Standardization

Daily notes and meeting records frequently employ diverse date formats: compact 8-digit strings (20261013-standup.md), spaced notations (2026 10 13 Meeting.md), or unformatted titles. The ISO 8601 standard (YYYY-MM-DD) is the universally recommended format for vault organization because it sorts chronologically in all filesystem views and terminal tools regardless of locale.

The ISO date normalization preset identifies existing date strings and cleans them into clean YYYY-MM-DD- prefixes while preserving the rest of the descriptive note title.

Non-Destructive Shell Script Safety

The generated bash shell script enforces zero-data-loss execution:

Step-by-Step Vault Normalization Protocol

  1. Extract file inventory: In your vault root, run git ls-files or find . -name "*.md" to generate a complete list of file paths.
  2. Select your naming preset: Paste your list into the planner above and select your target convention (such as kebab-case or ISO date prefix).
  3. Verify collision status: Review the staging plan. If any items display the COLLISION tag, adjust your rules or disambiguate the source note titles.
  4. Copy the bash rename script: Copy the generated script and run it in your terminal. The script will safely execute the renames while skipping any potential clobbers.
  5. Export the CSV mapping: Download the CSV plan to update your wikilinks across the vault using global search-and-replace or your editor's link-refactoring tools.

Questions

How does the Filename Rename Planner prevent target file overwrites?

Before outputting any script commands, the engine indexes every proposed target destination. If two different source files transform into the exact same target path (for example, if both my_notes.md and my-notes.md map to my-notes.md), both files are immediately flagged with a collision warning, and the generated shell script refuses to stage either operation.

What naming presets are supported for batch normalization?

The tool provides presets for kebab-case (hyphen-separated lowercase), snake_case (underscore-separated lowercase), Title Case (spaced capitalized words), and ISO date standardization (converting legacy dates like 20261013 to YYYY-MM-DD-). It also supports custom regex or literal search-and-replace with configurable prefix and suffix additions.

How does this tool help me update internal wikilinks after renaming?

Every row in the audit matrix displays the corresponding wikilink transformation ([[Old Title]] to [[New Title]]). You can export this mapping as a spreadsheet CSV to orchestrate automated global search-and-replace passes across your Markdown notes.

Why are file extensions protected during transformations?

Transformations operate strictly on the file basename preceding the final dot delimiter. This guarantees that file extensions such as .md, .canvas, .png, and .pdf remain intact and functional.

Does the generated rename script execute automatically on my computer?

No. The planner runs entirely in your browser and produces a reviewable bash shell script. You copy the script and inspect every command in your local terminal before running it with full administrative transparency.

Is my note data uploaded to external servers or cloud services?

No. All path parsing, string manipulation, collision detection, and script generation run 100% in local browser memory. Zero network requests are initiated.

Keep your Markdown vault structured and durable

Private on-device text intelligence and native Markdown editing in Oyma. Keep your file names organized with zero cloud lock-in.

tools filename rename planner downloadDownload for Mac

No account needed. Intel Mac build