Enter text and choose an action.
Result
Method and example
Character reversal operates on the shared grapheme segmentation layer rather than UTF-16 code units. Word-order mode normalizes runs of whitespace; each-word mode preserves whitespace while reversing each non-whitespace segment.
Worked example
hello becomes olleh. One two three becomes three two one in word-order mode, while each-word mode produces enO owt eerht.
Behavior and limits
- Grapheme reversal keeps supported emoji and combining sequences intact.
- Word-order mode uses whitespace-delimited tokens, not grammatical parsing.
- This tool changes order only; it does not substitute upside-down decorative characters.
- The lightweight fallback cannot guarantee perfect segmentation in every older runtime.
Common mistakes
- Reversing UTF-16 code units and breaking surrogate pairs
- Confusing reverse text with upside-down Unicode styling
- Expecting word-order reversal to preserve every spacing run
- Rendering input with innerHTML
Large-text handling
Character counting, case conversion, and reversal accept up to 5,000,000 UTF-16 code units and run only after an explicit action. Morse translation uses a lower 100,000-character text limit because encoded output can expand substantially.