Filesystem Portability Auditor
Screen the path names in a source tree before transferring it to Windows, macOS APFS or Linux ext4. Paste slash-separated relative paths, import a UTF-8 list or choose a local folder to collect its names. File contents are never read and no file is renamed. The report preserves original paths, distinguishes file conflicts from directory aliases and offers tentative names to review. It cannot guarantee that an actual copy will succeed on a particular destination.
Key features
- Find sibling files or folders that merge after case or NFC/NFD comparison
- Distinguish file-versus-file loss risks, file-versus-directory conflicts and directory aliases
- Screen Windows device names, forbidden characters, trailing dots/spaces and length thresholds
- Check ext4 filename UTF-8 byte length and a common Linux pathname-call threshold
- Export a review-only JSON or spreadsheet-safe CSV without changing source files
How to use
- Enter one slash-separated relative path per line, import a UTF-8 list, or choose a local folder. End explicit empty directories with /.
- Select the Windows, macOS and Linux profiles and check the destination root paths.
- Run the audit and separate file collisions, directory aliases, reserved names and length risks.
- Use any suggested spelling only as a starting point, change source names separately and rerun the audit.
- Download the full JSON or CSV report and test an actual copy on the destination system.
Use cases
- Review case collisions before cloning a repository on a Windows PC
- Find NFC and NFD path pairs before moving a folder to macOS APFS
- Check nested archive paths and Windows reserved names before extraction
- Review UTF-8 byte lengths of paths intended for a Linux server
Frequently asked questions
Does zero collisions mean this will copy to every computer?
No. This is an approximate name and path screen for three explicit profiles. Actual volume options, permissions, symbolic links, existing files and application-specific rules are outside its scope.
Does the Windows profile include long-path support?
It conservatively screens the destination-root path against 260 UTF-16 units including the NUL terminator for common Win32/Shell compatibility. It does not assume a Windows 10 1607+ registry and application-manifest opt-in or an extended path prefix.
Does APFS matching exactly reproduce macOS?
No. JavaScript NFC and lowercase approximate default case-insensitive, normalization-insensitive APFS. They do not exactly reproduce APFS Unicode 9.0 comparison, a case-sensitive volume or its runtime length limits.
Why are some names distinct under Linux?
Default ext4 is case-sensitive and distinguishes byte sequences. A directory with casefold enabled uses different comparison behavior and is not modeled by this profile.
Does folder selection include empty subdirectories?
A normal browser folder-file selection does not enumerate empty folders. Add one manually to the list with a trailing slash. File contents are never opened.
Are suggested names automatically applied?
No. A candidate is a starting point for one collision group. Check it against destination contents and other policies, rename with a separate tool, and rerun the audit.
Privacy
Folder selection only brings names and relative paths into this browser tab's memory. The tool does not read file contents or submit them to the site. JSON and CSV contain original paths and target roots, so review them for personal or internal names before sharing.
Comments & questions