Cross-Platform Filename Sanitizer
Review names before a bulk upload. Replace invalid characters, handle Windows device names, fit a UTF-8 byte limit and check case-insensitive collisions in one local batch.
Check Filename Collisions Before Upload
Cross-Platform Filename Sanitizer: how to use it
- Paste one filename per line, open a UTF-8 list or load the example.
- Choose the replacement character and byte limit. Adjust whitespace, case or collision suffixes, then run the sanitizer.
- Inspect the original and proposed names. Copy or download the list, or save the JSON report with every line and change.
Limits and notes
Up to 500 nonblank filename lines and 256,000 UTF-8 bytes of input. The byte limit applies to one filename, from 8 to 255 UTF-8 bytes. The tool prepares names for review. Existing files, storage provider rules and full path length require separate checks.
How your privacy works →Cross-Platform Filename Sanitizer: common questions
Why do two names collide when the letters differ in case?
The check uses a case-insensitive key after Unicode NFC normalization. That catches common collisions when files move between systems with different case handling.
What happens to NUL.tar.gz or COM¹.txt?
The sanitizer prefixes an underscore to Windows device names. It keeps the extension when the byte budget allows it.
Does the tool split or follow file paths?
Each input line describes one proposed filename. The replacement option applies to slashes and backslashes. Files and directories stay untouched.
What if a numbered collision suffix is already used?
The suffix option reserves each original candidate in the batch and checks each suffix against reserved and assigned names.
Why do some filenames lose more characters at the same limit?
UTF-8 uses different numbers of bytes for different characters. The sanitizer shortens at a character boundary and leaves room for the extension and any suffix.