AxelBase Normalizer

Convert between NFC & NFD • Instant • Private

Raw
0 chars | 0 codepoints
Raw
0 chars | 0 codepoints

About AxelBase Unicode Normalizer

AxelBase Unicode Normalizer is a free, open-source, zero-server web tool that instantly converts text between Unicode Normalization Form C (NFC – composed) and Normalization Form D (NFD – decomposed) while showing you exactly what’s happening under the hood.

Every modern system handles accented characters, emoji, and complex scripts differently. macOS and iOS use NFD by default. Windows, Windows, Linux, and most web standards prefer NFC. This invisible difference causes silent, hard-to-debug issues: failed string comparisons, duplicate database records, broken full-text search, incorrect sorting, and even security vulnerabilities via homograph attacks.

Our tool eliminates these problems at the source. Using only native browser APIs (String.prototype.normalize()), it runs 100% client-side — nothing ever leaves your device. You get instant conversion, real-time detection of current normalization form, character/code-point counters, copy-to-clipboard, and shareable URLs, all with zero tracking, zero cookies, and zero data collection.

Whether you’re a developer cleaning user input, a database administrator fixing duplicate entries, a security engineer hunting homograph issues, or a content creator ensuring consistent filenames across platforms — this tool gives you immediate, trustworthy results without compromising privacy.

Built with SvelteKit + Bootstrap 5, fully static, and deployable anywhere (GitHub Pages, Vercel, Netlify, Cloudflare Pages), it works offline after the first load and is licensed under the MIT License so you can fork, embed, or extend it freely.

Consistent Unicode shouldn’t be hard. With AxelBase Normalizer, it’s instant, private, and always accurate.

How to Use

  1. 1
    Paste or type any text into the left box. Works with Latin, Cyrillic, Arabic, CJK, emoji, mathematical symbols — everything Unicode supports.
  2. 2
    Observe the live badge above the output — it instantly tells you whether your input is Composed (NFC), Decomposed (NFD), Mixed, or Unnormalized.
  3. 3
    Click “Normalize to NFC” for maximum web/database compatibility or “Normalize to NFD” for macOS/HFS+ compatibility or linguistic analysis.
  4. 4
    Use Swap to flip input/output, Copy Result to grab clean text, or Share via URL to send the exact state to colleagues — the link even pre-fills the input when opened.
  5. 5
    Watch the Characters vs Code Points counters — they prove the conversion worked (e.g., “é” as one code point in NFC vs two in NFD).

No installation. No account. No data sent. Just pure, instant Unicode normalization.

Frequently Asked Questions

Never. All processing happens inside your browser using native JavaScript. No requests are made, no logs exist, and no third-party services are contacted.

Use NFC for web forms, APIs, databases, URLs, and cross-platform compatibility (recommended default). Use NFD when working with macOS/iOS file systems, certain linguistic tools, or when you must match Apple’s HFS+ behavior exactly.

Yes! After the first visit, your browser caches everything. Open the page without internet and it works perfectly.

Because decomposed forms use multiple code points for a single visible character. Example: “é” in NFC = 1 code point, in NFD = 2 code points (“e” + combining acute). The counters prove the conversion succeeded.

Absolutely. The complete source is available on GitHub under the MIT License. Fork it, embed it, improve it — it’s yours.