Input
Output
Formatted result will be displayed here
Lowercasing maps each uppercase letter to its lowercase form while leaving digits and punctuation alone. The tricky cases are Greek final sigma and the Turkish dotted I, both of which have locale-specific rules. This tool applies the browser locale by default and exposes an explicit Unicode default option when you need deterministic output across environments, which matters for things like case-insensitive comparison in tests.
Lowercase input before sending to a case-sensitive index so equivalent queries consistently hit the same bucket.
Email addresses and category names often arrive with mixed casing. Lowercase them all for reliable deduplication.
Slugs should be lowercase; run a title through the converter before applying the rest of your slugifier logic.
Lowercase both sides of a comparison before checking equality to avoid surprises when the data source enforces casing inconsistently.
Final sigma is produced correctly at word ends when using the Greek locale; the default locale uses a non-positional sigma.
The local part is technically case sensitive per RFC 5321 but treated case-insensitively by most providers. Lowercasing for deduplication is standard practice.
No. Accents stay attached. Use a Unicode normalization tool separately if you need diacritic-free text.
Yes, but the result is a single run-together word. Use a text case converter if you want proper underscore or kebab separation.