How to use this tool
- Enter text, normalization form.
- Select Update result to view the result.
- Check the method and assumptions below before using the result.
Input reference and sample values
Use the units and choices shown for each field. Sample values are provided for practice, not as recommendations.
| Input | Format and units | Sample |
|---|---|---|
| Text | Keep the structure and separators shown in the sample. Line breaks are retained in this input. | Café |
| Normalization form | Choose NFC — canonical composition / NFD — canonical decomposition / NFKC — compatibility composition / NFKD — compatibility decomposition. | NFC — canonical composition |
Result for these sample inputs
Café
- Before (code points)
- 5
- After (code points)
- 4
- Changed
- Yes
Select Try the example in the form to load these values and calculate them again. This replaces the current form inputs. Compare the result with the method and worked explanation below.
The method, explained
Apply the selected Unicode normalization form to the complete input. Report code-point counts before and after without removing accents or changing letter case.
Using text = Café, normalization form = NFC, the result is Café. Change these example inputs to match your task; use the method above to check each step.
What to keep in mind
Compatibility forms can change meaningful presentation distinctions. Normalization does not detect spoofing or make an identifier secure.
Common questions
Will this remove accents?
No. Canonical forms compose or decompose equivalent sequences. A decomposed accent remains in the text; compatibility forms additionally fold some presentation variants.
Does my text leave my device?
Processing runs locally in this browser. Your pasted text is not uploaded to an API or stored in a ClarityKit account.
Methodology maintained by ClarityKit. How these tools are built and checked.