Unicode normalize

Client

NFC, NFD, NFKC, and NFKD in one local tool.

About Unicode normalization

Apply NFC, NFD, NFKC, or NFKD normalization to text—code point counts and copy output, browser-only. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.

How to use this page

Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.

Loading…

Nearby workflows on Toolcore

  • Remove accents — Strip diacritics with Unicode NFD—ASCII-friendly slugs and legacy normalization in the browser. for the next text or markup step in your edit loop.
  • Unicode & JS escapes — Encode UTF-8 to \u{hex} escapes or decode \u{…}, \uXXXX, \xNN, and \n \t—client-side. for the next text or markup step in your edit loop.
  • String case converter — camelCase, snake_case, kebab-case, PascalCase, CONST_CASE from one paste—client-side. for the next text or markup step in your edit loop.
  • Line ending converter — Count LF, CRLF, and CR; normalize to one EOL style; optional UTF-8 BOM strip—local only, Git-friendly. for the next text or markup step in your edit loop.

Common use cases

  • Unicode normalize for quick local checks without uploading data.
  • Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

  • Unexpected input shape

    See the intro and how-to notes for accepted formats.

FAQ

Is processing local?

Yes—this runs entirely in your browser.

Agent prefill?

Use q or qb for the main text field when supported.

More tools

Related utilities you can open in another tab—mostly client-side.