File cleanup guide
How to Create Clean Filenames
Clean filenames are easier to scan, share, upload, and manage. This guide explains a simple naming workflow for web-friendly files and bulk filename cleanup.
Quick workflow
A simple way to do it
-
1
Remove confusing spaces, symbols, duplicate separators, and inconsistent casing.
-
2
Use short readable words that describe the file.
-
3
Choose hyphens or underscores consistently for the whole batch.
Worked example: a PDF menu
With the default lowercase, accent removal, keep-extension, hyphen, and duplicate options enabled, "Café Menu.PDF" becomes cafe-menu.pdf. Paste the same name twice and the second result is cafe-menu-2.pdf. The tool normalizes the basename and final extension separately; copying these results does not rename files on your computer.
Choose names before choosing separators
Use a meaningful subject and a distinguishing date or version, such as menu-autumn-2026.pdf. Hyphens and underscores are both available; use one style for the batch. Ampersands become the word and. Accent removal handles decomposed accent marks, but the remaining allowed letters are ASCII, so non-Latin names may lose meaningful text.
Extensions and fallback names
Only the last dot separates the extension. With defaults, archive.tar.gz becomes archive-tar.gz, which may not be what an archive workflow expects. Names reduced to nothing use the fallback, initially file. Review hidden files and compound extensions separately, and remember that changing a suffix does not convert a file’s format.
Checklist before a batch rename
Keep a mapping from each original name to its result. Check extensions, empty-name fallbacks, case changes, and every duplicate. Compare the proposed names with the destination folder before applying them through your own file manager or script. Keep a backup when other documents or published links refer to the old names.
Limitations: uniqueness and file-system rules
Duplicate handling adds suffixes for repeated normalized names in the pasted list; it does not inspect existing files or guarantee that a generated suffix will not collide with another input name. It does not enforce every operating system’s reserved names or path-length limits. Review the full output rather than treating the unique option as permission to overwrite files.
Related Bizzon tools