Clean Filenames
View on WordPress.orgScores higher than 5% of indexed plugins
About
Removes or replace international or special characters that can make your filenames not compliant with some servers or services.
What It Does
Clean Filenames (sanitize-spanish-filenames) automatically rewrites uploaded filenames to strip or replace accented and other non-ASCII characters, producing ASCII-only file names that are safe for legacy servers, CDNs, and downstream services. It works on new uploads going through the WordPress media library, reducing broken links and encoding errors caused by characters like ñ, é, or ü. Despite the slug, the sanitization is broadly useful for any Latin-script language, not only Spanish.
Who It's For
This plugin is a good fit for site owners on restrictive shared hosting or CDN setups that mishandle UTF-8 filenames, particularly Spanish, French, Portuguese, German, and other Latin-alphabet publishers. It also helps international e-commerce stores and content creators pushing assets to third-party APIs, FTP pipelines, or legacy asset managers that reject non-ASCII names. If you have ever seen garbled filenames in your media library or broken image URLs after migration, this is built for you.
Who Should Skip It
If your hosting stack already handles UTF-8 filenames correctly and your media workflow never crosses into external systems, this plugin adds no real value and is one more thing to maintain. Sites that rely on preserving original filenames for SEO, legal archival, or asset-tracking purposes should also skip it, since the rewrite is destructive and irreversible.
The Bottom Line
Clean Filenames does one focused job and does it well, with a perfect user rating on the small sample available. The drawbacks are real, though: only 3,000 installs, no public support history, and an overall quality score of 56.81 that reflects limited adoption and testing. It is worth installing for users on UTF-8-fragile stacks, but anyone with modern managed hosting may not need it.
Related Plugins
Pick this if you want a similar ASCII-only filename cleaner but with 30,000 installs, a more mature codebase, and broader community validation.
Choose this instead if your real need is improving the upload experience inside Contact Form 7, not sanitizing filenames on the media library.
Go with this if you need to allow additional file extensions in WPForms forms, which is a different problem from cleaning character encoding in filenames.
Pick this if your concern is the directory structure of media uploads rather than the character set of individual filenames.
Choose this if you run a WooCommerce store and need customer file uploads on product pages, a use case this plugin does not cover.