Free tool · works now

Case-Collision Checker

Detect file and directory case sensitivity collisions across macOS, Windows, and Linux filesystems.

Runs 100% in your browser. Surface direct filename collisions, directory casing conflicts, and cross-platform Git checkout hazards before they corrupt your vault.

Filesystem Case Collision Auditor
9Files scanned
3Clean files
6Colliding files
2Direct file clashes
1Directory clashes
Vault file paths listOne relative path per line

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

Case collision audit findings9 paths analyzed
DIRECT FILEdocs/Readme.mdRENAME NEEDED
Collides with:docs/README.md
Safe resolved path:docs/Readme-case-alt.md
DIRECT FILEdocs/README.mdCANONICAL
Collides with:docs/Readme.md
DIRECTORY SEGMENTDaily/2026-10-12.mdRENAME NEEDED
Collides with:daily/2026-10-13.md
Safe resolved path:daily/2026-10-12.md
DIRECTORY SEGMENTdaily/2026-10-13.mdCANONICAL
Collides with:Daily/2026-10-12.md
DIRECT FILEprojects/app-launch.mdCANONICAL
Collides with:projects/App-Launch.md
DIRECT FILEprojects/App-Launch.mdRENAME NEEDED
Collides with:projects/app-launch.md
Safe resolved path:projects/App-Launch-case-alt.md
CLEANnotes/architecture.md
CLEANnotes/database-schema.md
CLEANarchive/2025-retrospective.md

Click "Copy bash rename script" to copy an idempotent two-step temporary rename script.

The Operating System Case-Sensitivity Dilemma in Note Vaults

Modern personal knowledge repositories operate across a diverse ecosystem of platforms: desktop computers running macOS or Windows, servers running Linux, mobile devices on iOS and Android, and version-control hosts such as GitHub and GitLab. However, the filesystems underlying these systems harbor a fundamental architectural disagreement regarding letter casing.

Case-Insensitive versus Case-Sensitive Filesystems

Default filesystems on macOS (Apple File System or APFS, and legacy HFS+) and Windows (NTFS and FAT32) are case-preserving but case-insensitive. When you create a file named Meeting.md, the filesystem remembers the capital "M" for display purposes. However, if any application attempts to open or reference meeting.md, the operating system treats both strings as pointing to the identical file. It is physically impossible for both files to coexist within the same folder on these operating systems.

In contrast, Linux filesystems (such as ext4, btrfs, and ZFS) and Git repositories natively treat file paths as strictly case-sensitive byte sequences. To Linux and Git, docs/Readme.md and docs/README.md are two distinct files with unique inode entries.

The Git Checkout and Cloud Sync Trap

When a vault is created on Linux or populated by automated scripts, multiple case variations of a file can easily be committed to Git. When a developer or researcher later checks out the repository on macOS or Windows, Git encounters an insoluble collision: it attempts to write two separate files to the same filesystem address.

The result is notorious Git error states:

error: The following untracked working tree files would be overwritten by checkout:
    docs/Readme.md
Please move or remove them before you switch branches.

Even in non-developer workflows utilizing iCloud Drive, Dropbox, OneDrive, or Syncthing, case collisions generate silent file overwrite bugs or create endless duplicate sync conflict files (e.g. Meeting (Case Conflict).md).

Directory Segment Collisions

Case collisions are not confined to file basenames; they frequently manifest across directory segments. For example, a daily journaling habit might produce paths like:

On Linux, these files reside in two completely different folders. On macOS and Windows, the OS merges them into a single visual folder, but command-line tools and relative wikilink path resolvers become inconsistent. If one note links to [[daily/2026-10-12]] and another links to [[Daily/2026-10-12]], link graph integrity degrades.

The In-Place Rename Paradox on APFS and NTFS

A common mistake when resolving case collisions on macOS or Windows is attempting a direct rename in the terminal:

mv Readme.md README.md

On APFS and NTFS, this command frequently fails or silently no-ops. Because the operating system considers Readme.md and README.md to be the exact same file, it sees the operation as renaming a file onto itself.

To safely change the letter case of a file on a case-insensitive filesystem, you must execute a two-step intermediate rename:

  1. Step 1: Move the file to a temporary, non-colliding intermediate name: mv Readme.md Readme.md.tmp_case_step
  2. Step 2: Move the temporary file to the desired target case: mv Readme.md.tmp_case_step README.md

The script generated by this tool automatically structures all remediation commands using this two-step intermediate protocol, complete with collision preflight checks.

Step-by-Step Vault Remediation Protocol

  1. Inventory your vault paths: Generate an inventory of your vault files by running git ls-files or find . -name "*.md" in your terminal.
  2. Audit in the browser: Paste the list into the checker above to instantly detect direct file collisions and directory segment mismatches.
  3. Inspect canonical elections: Verify the elected canonical paths. The engine retains standard uppercase filenames (like README.md) and standard lowercase note conventions while preparing safe alternative paths for secondary files.
  4. Execute the two-step rename script: Copy the generated bash script and run it in your terminal. The script uses safe intermediate files and mv -n (no-clobber) flags to prevent accidental data loss.
  5. Update wikilinks and commit: Re-index your vault link graph and commit the normalized files to Git to ensure seamless cross-platform synchronization.

Questions

Why do case collisions happen when syncing Markdown vaults?

macOS APFS and Windows NTFS default to case-preserving, case-insensitive filesystems, meaning Readme.md and README.md refer to the exact same file on disk. In contrast, Linux filesystems (ext4) and Git internal storage are strictly case-sensitive, treating them as two independent documents. When syncing across operating systems or checking out Git repositories, files overwrite each other silently or trigger perpetual merge conflicts.

What is a directory segment case collision?

A directory collision occurs when notes exist in folders with matching names that differ solely by capitalization—such as Daily/2026-10-12.md and daily/2026-10-13.md. On Linux, these exist in two separate physical directories, whereas on macOS and Windows, the OS merges them into a single folder, confusing wikilink targets and file tree indexing.

Why does direct renaming (mv Readme.md README.md) fail on macOS and Windows?

Because APFS and NTFS are case-insensitive, the operating system sees the destination name as identical to the source name. Attempting a direct rename either throws an error that the destination already exists or silently exits without changing the casing. A safe rename requires a two-step temporary rename using an intermediate staging filename.

How does the checker elect which file is the canonical version?

The engine applies heuristic scoring: well-known documentation standards (such as README.md or LICENSE.md) are prioritized in uppercase, while general vault notes are scored by standard lowercase conventions, shortest path depth, and absence of temporary backup markers.

Does this tool transmit my note paths across the internet?

No. All case folding, collision group indexing, canonical election, and shell script generation execute 100% within your local browser tab memory. Zero data leaves your machine.

Does the generated rename script overwrite my existing notes?

No. The generated bash script uses mv -n (no-clobber) and incorporates explicit target existence guards. It renames secondary colliding files to disambiguated names like note-case-alt.md rather than overwriting canonical files.

Keep your Markdown vault durable and cross-platform

Private on-device text intelligence and native Markdown editing in Oyma. Keep your vault free of filesystem sync collisions.

tools case collision checker downloadDownload for Mac

No account needed. Intel Mac build