How to test text against Unicode properties
Use Text to test for a full sample or String to test under Quick Test (single string). Properties to Test groups the choices under General Category, Binary Properties, and Script. Select a property, choose Match any (OR) or Match all (AND), then read the result in Preview or Character Results. The page reads your text and leaves it unchanged.
Check Unicode character properties
- Paste text into Text to test, or enter a short value in String to test under Quick Test (single string).
- In Properties to Test, select labels under General Category, Binary Properties, or Script. The page keeps only definitions that the current browser can compile.
- Choose Match any (OR) when one selected property is enough, or Match all (AND) when each selected property must match the same code point.
- Optionally enter a raw property body in Custom property expression (optional), then inspect Preview or Character Results.
Text: ABC123
Property: Letter (any)
Matches: A B CIn this example, the three letters match the selected property and the digits do not. The checklist can be shorter when a property definition fails compilation.
Use a Unicode property regex expression
Custom property expression (optional) takes the body used inside a Unicode property escape. Enter Script=Greek to test Greek script membership or Emoji to test the Emoji binary property. If the value cannot compile, the page displays Not a valid Unicode property: \p{...} and leaves that expression out of the test.
Clear properties unchecks the selected labels and clears the custom expression. With no selected property and no valid custom expression, Properties to Test shows No properties selected. The results area asks you to select a property, and Quick Test (single string) asks for one before it runs.
Understand the Unicode test results
Quick Test (single string) checks each code point and returns Every character matches, No characters match, or Mixed - some characters match. The main view marks each analyzed unit in Preview and lists Cluster #, Char, Code Points, CP Count, and Status in Character Results.
When Intl.Segmenter with grapheme granularity is available, one row can contain several code points that appear as one visible character. The cluster matches when at least one of its code points passes the combined test. Without Intl.Segmenter, the full-text view uses Array.from and creates one row per code point.
Filter and export matching characters
Use Show to choose All characters, Matches only, or Non-matches only. Copy Report and CSV include the rows currently displayed, so the selected filter controls both exports. Show all rows resets the table view.
Where Unicode property checks come up
Paste ABC123, select Letter (any), and compare the letters with the digits in Preview or Character Results. The original sample stays available for another property check.
For script checks, select Greek, Latin, Han, or another label under Script. Emoji and White Space can identify matching code points in text that is about to be stored or displayed.
Choose the right text analysis tool
Unicode Property Tester answers a property membership check. Use the Text Analysis Tools category for related text checks. Choose Unicode Inspector for names, blocks, encodings, and other code-point details. Choose Invisible Character Detector for hidden characters such as zero-width spaces or bidi overrides. Choose Homoglyph Detector when Cyrillic, Greek, or Armenian characters may resemble Latin letters.
Frequently asked questions
How do I test text against Unicode properties?
Paste text into Text to test, select a property, and choose Match any (OR) or Match all (AND). Preview and Character Results then show the matching units.
Can I test a Unicode script such as Greek?
Select Greek under Script, or enter Script=Greek in Custom property expression (optional). The results show which analyzed units satisfy the script test.
What does Match all (AND) check?
Match all (AND) requires one code point to satisfy every selected property. With Match any (OR), a code point matches when at least one selected property is true.
Why can one visible character have several code points?
A grapheme cluster can contain multiple code points. When Intl.Segmenter is available, Character Results keeps the cluster in one row and marks it when at least one code point matches.
What happens if my Unicode property expression is invalid?
An invalid expression shows Not a valid Unicode property: \p{...} and is not applied. Select a listed property or correct the expression before testing.