Review Portable Filenames Before a Batch Upload
Admin ·
Start with a list of the names you intend to use. Keep the source names next to their proposed replacements so you can review which files might receive the same name in your destination.
Cross-Platform Filename Sanitizer
Compare the four names in the upload example
Select Load example and Sanitize filenames. The first two proposed names are Trip-North-.JPG and Trip-North-.jpg. Each row gives the other line number. The source spelling remains in the report.
Check the next two outputs. NUL.tar.gz becomes _NUL.tar.gz, keeping the compound archive extension. The final name is Café notes.txt. Unicode NFC combines the decomposed accent, and the trailing period is removed.
Microsoft file and directory naming rulesUnicode Standard Annex 15 on normalization forms
Leave space for a suffix and the extension
Enable Lowercase output and Add suffixes to colliding names, then sanitize again. Check that the first two lines become trip-north-.jpg and trip-north--2.jpg. The suffix sits before .jpg and both rows still show the original collision.
Paste ééééé.png on its own line and set Maximum bytes per filename to 8. The result is éé.png. Each accented é needs two UTF-8 bytes and .png needs four, so the output uses exactly eight. Under a tight cap, review the shortened result and check that the extension still suits the file.
Check the exported list before applying names
Download the UTF-8 text list to use the proposed names in order. Open the JSON report to check each source, candidate, final name, byte count and collision line. Keep the report beside the upload list while checking against the destination’s existing filenames.
The tool checks a conservative single-name policy. Confirm storage rules, accepted extensions and full directory path limits in the destination where you plan to use the names.
Common questions
What happens when two original names differed only by a Unicode accent sequence?
Canonically equivalent spellings produce the same NFC name. Both source strings stay in the JSON report so you can tell which rows collided.
Does a collision suffix change the file extension?
The number goes before the extension. If the combined name exceeds the limit, the sanitizer shortens at a Unicode character boundary and preserves as much of the extension as fits.