Skip to content

Choose your path

Built around the job you need to finish

Reverse intact grapheme clusters or Unicode scalars, optionally within line records with exact delimiter preservation, and inspect full source-to-output mappings.

Unicode application developer

Reverse supplementary characters without creating invalid surrogate sequences.

Compare A+emoji+decomposed accent under grapheme and scalar modes; inspect original offsets.

Surrogate pairs stay intact and scalar-mode mark reordering is explicit.

Multilingual content editor

Preserve common composed display clusters without promising visual mirroring.

Reverse ZWJ emoji, flags and accents; review logical ordering and stated bidi limits.

Understands runtime graphemes and does not treat reversal as RTL mirroring.

Mobile log-file reviewer

Keep line records while reversing their content.

Import mixed CRLF/CR/LF data, select within-lines, export raw bytes and inspect 220 mappings.

Each delimiter remains in its original slot and complete output survives preview limits.

Authoritative checks for this tool

Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.

Was this tool helpful?

Reference & details

How it works

Explicit reversal unit

Grapheme mode uses runtime Intl.Segmenter; scalar mode iterates code points. Neither splits valid surrogate pairs.

Line-aware option

Within-lines preserves CRLF, CR, LF, VT, FF, NEL, LS and PS. Whole-text mode reverses all selected units including separators.

Complete trace and transfer

Each output unit records original and output UTF-16 positions. The full raw text and complete mapping report are separately downloadable; preview is capped, export is not silently truncated.

Updated: August 2026

Example Scenarios

Reverse supplementary characters without creating invalid surrogate sequences. Compare A+emoji+decomposed accent under grapheme and scalar modes; inspect original offsets.

Preserve common composed display clusters without promising visual mirroring. Reverse ZWJ emoji, flags and accents; review logical ordering and stated bidi limits.

Keep line records while reversing their content. Import mixed CRLF/CR/LF data, select within-lines, export raw bytes and inspect 220 mappings.

Common Mistakes to Avoid

Assuming visual order matches logical order

Use escaped mapping and offsets when bidi or invisible characters matter.

Using reversal as the only backup

Retain the original and use explicit Undo; re-segmentation can prevent a universal double-reversal identity.

FAQ

No. Both modes preserve Unicode scalars. Grapheme mode additionally keeps common combining and ZWJ clusters intact according to runtime segmentation.

Individual code points reverse, so combining marks and ZWJ sequences may be reordered. Whole-text CRLF becomes LFCR in scalar mode.

Yes. Within-lines mode reverses each record content while retaining every supported delimiter in its original slot.

No. It changes logical text order; bidirectional rendering can look different. No direction controls, normalization or transliteration are added.

Not universally for graphemes. The reversed string may segment differently. Keep your source and use Undo rather than relying on a second reversal.

About String Reverse

Reverse Unicode grapheme clusters or scalars, preserve line delimiters when selected and inspect exact source-to-output mappings before exporting.