Filename Cleaner
Filename Cleaner does not rename originals. For each selected name it separates the final extension, normalizes the basename with NFKD, replaces runs outside ASCII-style word characters, dots, and hyphens with a hyphen, collapses repeated hyphens, preserves the extension text, and downloads renamed-files.zip. Accents can disappear, name collisions are not resolved, and filesystem-specific reserved names or length rules are not validated.
Runs locally — files stay on your deviceAre files renamed on disk?
No. Copies with transformed names are placed in a downloaded ZIP.
Portable-looking names still need collision and platform checks
Character normalization can make names simpler, but operating systems differ on reserved words, case sensitivity, maximum length, and trailing characters.
How it works
Each basename is NFKD-normalized and sanitized; the final extension is appended unchanged. JSZip packages all copies as renamed-files.zip.
Key concepts
Basename only
The final extension is separated and preserved as entered.
Normalization can lose distinctions
Different accented names can collapse to the same cleaned form.
When to use it
- Simplify names containing spaces or accents.
- Prepare a small batch for systems favoring ASCII names.
- Create cleaned copies while keeping originals.
When not to use it
- Do not rely on it for guaranteed cross-platform validity.
- Do not process batches with possible resulting collisions without review.
- Do not expect directory paths or filesystem metadata.
Worked examples
Spaces and accents
- Input
Résumé final.pdf- Expected output
Resume-final.pdf
NFKD separates accents, which are then removed.
Repeated punctuation
- Input
a b.txt- Expected output
a-b.txt
The replacement hyphens collapse.
Collision
- Input
résumé.txt and resume.txt- Expected output
Potential duplicate name
No unique suffix is added.
Common mistakes
Expecting in-place rename
Browsers cannot rename arbitrary originals here. Correction: Extract and organize the downloaded copies.
Ignoring collisions
Distinct inputs can clean identically. Correction: Review and make names unique first.
Assuming all platform rules
Reserved names and maximum lengths are unchecked. Correction: Validate for the destination filesystem.
Best practices
- Keep originals.
- Review every proposed output name and collision.
- Apply destination-specific naming rules afterward.
Related operations and differences
Add Prefix to Filenames
Choose Add Prefix to Filenames when you need to add a prefix to selected filenames.; use Filename Cleaner specifically for rename clean.
Add Suffix to Filenames
Choose Add Suffix to Filenames when you need to add a suffix before every extension.; use Filename Cleaner specifically for rename clean.
Compare Two Files
Choose Compare Two Files when you need to compare two files securely by SHA-256.; use Filename Cleaner specifically for rename clean.
File Checksum Comparator
Choose File Checksum Comparator when you need to compare a file digest with an expected checksum.; use Filename Cleaner specifically for rename clean.
File Hash Calculator
Choose File Hash Calculator when you need to calculate a local cryptographic file digest.; use Filename Cleaner specifically for rename clean.
File Size Calculator
Choose File Size Calculator when you need to inspect exact and human-readable file sizes.; use Filename Cleaner specifically for rename clean.
Limitations and privacy
- No collision handling, reserved-name validation, length enforcement, path preservation, preview, custom replacement, or undo inside the ZIP.
- Only the basename is cleaned; extension text is retained.
- Output is a ZIP of copies.
Processing happens in this browser. Selected file contents are not uploaded by this tool.
Downloads and copied results remain on this device; handle them according to their sensitivity.
Frequently asked questions
Are accents preserved?
They can be removed by normalization and filtering.
Are extensions changed?
No.
Can two outputs have the same name?
Yes.
What is downloaded?
renamed-files.zip.