Paste any Urdu or Arabic text and see the exact Unicode codepoint, decimal value, character name, and encoding block for every single character. Built for developers, typographers, and anyone debugging text rendering issues.
Developers building applications that accept Urdu or Arabic input use this to debug encoding issues, particularly around invisible bidirectional control characters that can silently break search, sorting, or string comparison logic. Typographers and font designers use it to confirm exactly which characters a piece of sample text contains before testing font coverage. Translators and localization specialists use it to verify that text copied from one system into another hasn't picked up stray characters during the transfer. If you've ever had two pieces of text that look visually identical but fail to match in code, this tool is usually the fastest way to find out why.
A few patterns come up repeatedly when inspecting real-world Urdu and Arabic text. Stray bidirectional control characters, like the Left-to-Right Mark (U+200E) or Right-to-Left Mark (U+200F), are invisible but can silently affect how surrounding text renders, and they're a common artifact of copying text out of certain word processors. Combining diacritical marks (the harakat, like zabar and zer) appear as separate codepoints attached to a base letter rather than a single merged character, which matters if you're writing code that counts or manipulates characters. And visually similar-looking Urdu and Arabic letters sometimes have entirely different codepoints depending on which keyboard or input method originally produced them, which this tool makes immediately visible. For more background on why these issues cause visible problems, see our article on why Urdu text breaks online.
Need to fix broken text direction instead of just inspecting it? Try our RTL/LTR Text Fixer, or browse all 11 tools.