String Reverse Tool

String Reverse flips the order of text characters and produces the input in reverse order. The idea is simple, but real text can make it more interesting than reversing plain ASCII letters: Unicode characters, emoji, combining accents, line breaks, whitespace, and right-to-left scripts may behave differently depending on how characters are counted. The tool works for text experiments, palindrome checks, small puzzles, string debugging, teaching, and revealing hidden spaces or suffixes. It is not a cryptographic obfuscation method or a safe way to mask sensitive data. When the input contains emoji sequences or characters made from multiple code points, the reversed output should be inspected carefully.

Character-level reversal uses spread syntax: [...str].reverse().join(''). The spread operator iterates the string as a sequence of Unicode code points, which correctly handles characters outside the Basic Multilingual Plane that occupy two UTF-16 code units (surrogate pairs). The naive alternative, str.split('').reverse().join(''), splits on code units and breaks any emoji like the party popper 🎉 (U+1F389), the rocket 🚀 (U+1F680), or any character above U+FFFF. Grapheme clusters add another layer. A user-perceived character such as cafe with a combining acute accent (a + ◌́), a flag emoji built from two regional indicators, or a ZWJ-joined family emoji 👨‍👩‍👧 is several code points long. Code-point reversal still rearranges the pieces, so the family emoji becomes three separate human figures and the accent drifts off the base letter. Intl.Segmenter with granularity: 'grapheme' is the standards-compliant way to iterate grapheme clusters and keep these sequences intact during reversal. At the operation level the cost is O(n) in the number of segments, where n is the string length in code points or graphemes depending on the chosen segmentation. Reversing twice yields the original string, which is what makes the function useful for palindrome checks. For Unicode-heavy input, NFC normalization (str.normalize('NFC')) before reversal collapses base + combining sequences into precomposed forms when one exists, reducing surprises in the output. Right-to-left scripts like Arabic and Hebrew are stored in logical order but rendered right-to-left, so a reversed Arabic string still looks reversed even though the data order has flipped.

• Code-point reversal: [...str].reverse().join('') iterates by code point and preserves surrogate pairs above U+FFFF (most emoji)
• Naive byte trap: str.split('').reverse().join('') splits UTF-16 code units and corrupts any character above U+FFFF
• Grapheme clusters: Intl.Segmenter({ granularity: 'grapheme' }) keeps combining marks, flag sequences, and ZWJ emoji 👨‍👩‍👧 intact
• Word-level reversal: split(/\s+/), reverse, join(' '); preserves each word internally and only flips order
• Complexity: O(n) where n is the number of segments; reversing twice returns the original string
• NFC normalization: str.normalize('NFC') folds combining sequences into precomposed forms before reversal when one exists
• Bidi text: Arabic and Hebrew are stored in logical order; the rendered direction is the browser's BiDi layer, separate from the data reversal