Remove Accents & Diacritics (ASCII Normalizer)
Convert accented Latin letters like é, ñ, and ü to plain ASCII equivalents for URLs, databases, and legacy systems.
- Sin límites de longitud
- Sin registro
- Gratis para siempre
- Tu texto nunca sale de tu navegador
Creating URL-Friendly Slugs
URLs tolerate accents poorly. Browsers percent-encode accented characters, so “café” becomes a slug full of %C3%A9 escapes, which is ugly to read, fragile to copy, and inconsistent with the rest of your URL structure. A URL built from plain ASCII letters is stable: “/cafe-paris” survives email, chat, print, and every redirect and CMS rewrite without a character escaping wrong halfway through.
Search engines can generally read percent-encoded URLs, but readable, consistent slugs remain the practical choice: they are easier for people to type and share, easier for analytics to group, and simpler for your own tooling to handle. Transliterating the text before generating the slug—é to e, ñ to n, ü to u—gives you that clean ASCII base in one pass, ready to be lowercased and hyphenated into a permalink.
The same logic applies to file names, directory names, and cache keys. A file called “café_menu.pdf” causes different problems on different operating systems and servers; “cafe_menu.pdf” works everywhere. Normalizing accents before you create the file or upload it avoids a whole class of “it works on my machine” bugs.
Normalizing Data for Legacy Systems
Not every system speaks Unicode. Legacy databases, mainframe exports, older APIs, and strict CSV pipelines often expect ASCII-only input, and feeding them accented characters produces mojibake, rejected rows, or silent corruption that surfaces much later. ASCII-folding—the technical name for converting é to e, ñ to n, and ü to u—is the standard normalization these integrations require, and it is exactly what this tool performs.
Accent removal is also a normalization step in its own right. Two systems may store “José” and “Jose” for the same person, and matching them requires folding both sides to the same form. Customer databases, deduplication jobs, and search indexes routinely normalize names this way so that a query for one spelling finds the other.
One caution: transliteration changes the written form of a name, and accents can carry legal or personal identity. When the original spelling matters—legal documents, passports, official records—keep the accented original in your data and use the folded version only for matching, slugs, and legacy exports. Folding for comparison is safe; overwriting the source with the folded form is a decision to make deliberately.
Preguntas frecuentes
Will this translate words or just change the letters?
It only changes the letters. The tool transliterates accented characters to their plain ASCII equivalents—über becomes uber and señor becomes senor—but it does not translate meaning or change words between languages. “Café” stays the same word, just written without its accent. If you need an actual translation into another language, that is a separate job; this tool exists to normalize spelling, not to change what the text says.
Tu texto nunca sale de tu navegador
Cada herramienta se ejecuta localmente en tu dispositivo. Nada de lo que pegues se sube, se almacena ni se rastrea.