Arabic readers see أحمد and احمد as the same name. A computer sees two different strings. Normalization is the small step that closes that gap before you search, merge duplicates or match records.
Arabic text normalization is the step that rewrites Arabic text into one consistent spelling before it is searched, compared or indexed. It folds variants that readers treat as the same word, such as أ, إ and آ into ا, ة into ه and ى into ي, and removes diacritics and tatweel, so a search for احمد also finds أحمد.
The name covers two related ideas. Unicode normalization, defined in UAX #15, deals with characters that can be encoded in more than one way: under the NFKC form, a presentation form such as the lam-alef ligature ﻻ becomes the two ordinary letters لا. Arabic orthographic normalization goes further and merges letters that Unicode treats as genuinely different, such as alef with hamza and bare alef. No Unicode form will ever make أ equal ا, which is why search code adds its own rules on top.
Both work on a copy of the text, never on what people read. The original keeps its hamzas and diacritics for display; the normalized copy exists only to be matched. And one function has to run on both sides: on the stored text when it is saved, and on every query as it comes in.
| Name | Notes | |
|---|---|---|
| English | Arabic text normalization | British spelling: normalisation. Search engineers also say "folding" or "orthographic normalization". |
| Modern Standard Arabic | توحيد النص العربي | Also «توحيد الإملاء» when the focus is on spelling variants. |
| Also heard in Syria | «توحيد الهمزات», normalize | Developers often use the English verb; the hamza rule is usually the first one people name. |
| In code or standards | normalize("NFKC"), UAX #15 | Unicode's normalization forms. A function such as normalizeArabic adds the Arabic folding rules on top. |
A landlord on a property app in Damascus posts «شقّة للإيجار في المزّة», with a shadda on two letters and a hamza under the alef. A student looking for a room types «شقه ايجار المزه» on a phone. As raw text, not one word of the query appears in the listing.
Run both through the same normalizer and tokenizer and the listing becomes شقه, ايجار, في, مزه, while the query becomes شقه, ايجار, مزه: every word of the query is now in the listing. The shaddas are gone, ة became ه, the hamza fell off the alef, and the article ال and the prefix لل were trimmed from the start of words. That last step goes beyond normalization in the strict sense, but the tested helper does it in the same pass.
The listing page still shows «شقّة للإيجار في المزّة» exactly as the landlord wrote it.
Rewriting Arabic text into one standard spelling before matching it: hamza forms of alef become ا, ة becomes ه, ى becomes ي, and diacritics and tatweel are removed. It runs on a copy used for search, not on the text people read.
The folding rules are those in our tested JavaScript and Dart helpers (Node 24 and flutter test, 16 November 2026). The property-app example was run through the same JavaScript helper.
Send us a few searches that should work. We will show you which spelling gets in the way.