Test whether your Urdu text is in the composed NFC form or the decomposed NFD form, and see both side by side.
Quick Answer
The Urdu NFC/NFD Text Tester checks which normalization form your text is in. It tells you whether it is already composed as NFC or decomposed as NFD, shows both forms, and reports whether they differ, which matters when a letter and its mark can be stored as one character or two. Everything runs in your browser.
Test NFC and NFD Forms
Paste Urdu text to see its composed and decomposed forms.
Result
- Current form
- –
- NFC code points
- 0
- NFD code points
- 0
- Forms differ
- –
Rate This Tool
Tap a star to rate the Urdu NFC/NFD Text Tester.
What the Urdu NFC/NFD Text Tester Does
The Urdu NFC/NFD Text Tester checks which Unicode normalization form your text is in. It reports whether the text is already composed, the NFC form, or decomposed, the NFD form, or neither, and it shows both forms so you can compare them.
This matters because a letter with a mark can be stored as a single composed character or as a base letter followed by a separate mark, and the two look the same but are not equal.
Everything runs on your own device. Your text is never uploaded or stored, so it stays private while you test it.
How to Test the Forms
- Paste your text. Enter Urdu text, especially with letters that carry a mark.
- Read the current form. See whether the text is NFC, NFD, or neither.
- Compare the forms. See the composed and decomposed versions and their code point counts.
- Copy or download. Copy the report, or save it as a text file.
NFC and NFD
NFC is the composed form, where a letter and its mark are joined into one character where possible. NFD is the decomposed form, where they are kept as a base letter and a separate mark. The two are canonically equivalent, meaning they represent the same text, but they are stored differently.
Why It Matters for Urdu
Some Urdu and Arabic letters have both a composed and a decomposed form, such as an alef with a mark above it. If one system stores the composed form and another the decomposed, a search or a comparison can fail even though the text looks identical. Testing the form catches this.
When the Forms Differ
When the composed and decomposed forms have different code point counts, the text contains something that composes or decomposes. When the counts are equal, the two forms are the same, which is common for plain Urdu text without marks.
A Worked Example
Text:
Loading example…
Result:
Loading example…
The live tester is preparing this example…
The result above comes from the same function the tool uses, so it reflects real behavior. Press Load Example to try it.
Who Uses This Tester
Developers use it to debug search and comparison. Database and search engineers use it to check stored text. Anyone whose text will not match uses it to see the form.
Accuracy and Limits
The tester uses the browser’s built-in normalization to produce the NFC and NFD forms, exactly as the Unicode standard defines them. It reports the current form and whether the two differ. For the compatibility forms, NFKC and NFKD, use the normalization checker.
Good to know: to change the text into a chosen form, use the normalization converter.
Your Data Stays Private
The tester runs fully in your browser with standard web technology. Your text is not uploaded or stored, and it is not sent to any analytics service. Only your star rating is sent, to record the tool’s rating. When you close the page, your text is gone.
Frequently Asked Questions
What does the Urdu NFC/NFD Text Tester do?
It checks which normalization form your text is in, NFC or NFD, shows both forms, and reports whether they differ.
What is the difference between NFC and NFD?
NFC composes a letter and its mark into one character where possible, while NFD keeps them as a base letter and a separate mark. They mean the same text but are stored differently.
Why does the form matter for Urdu?
Some letters have both forms, so if one system stores composed and another decomposed, a search or comparison can fail even though the text looks the same.
What if the forms do not differ?
Then the text has nothing that composes or decomposes, which is common for plain Urdu without marks. The code point counts will be equal.
How do I change the form?
Use the normalization converter to turn the text into a chosen form, such as NFC.
Is my data safe?
Yes. Everything runs in your browser. Your text is never uploaded, saved, or shared.
Is this tool free?
Yes, it is completely free and needs no account to use.
Does it work on mobile?
Yes. It works on phones, tablets, and computers.
Explore More Free Urdu Unicode and RTL Tools
Inspectors, detectors, cleaners, and normalizers built for real Urdu Unicode text.
Open the Urdu Tools hubSources and standards
- The Unicode Standard and code charts (Arabic block U+0600, Arabic Supplement, Presentation Forms). unicode.org/charts
- UAX #9, Unicode Bidirectional Algorithm (RTL, marks, isolates, overrides). unicode.org/reports/tr9
- UAX #15, Unicode Normalization Forms (NFC, NFD, NFKC, NFKD). unicode.org/reports/tr15
- MDN Web Docs, String.prototype.normalize and code point methods. developer.mozilla.org
This free tool uses the browser’s built-in normalization to show the NFC and NFD forms of your text and report the current form. For the compatibility forms, NFKC and NFKD, use the normalization checker. Your star rating is stored on the site.