Cyclically Shift Unicode

Grapheme cluster (default): a “user-perceived character”. `🏳️‍🌈` = 1, `café` = 4. Use for human-readable rotations. Code point: a single Unicode value (0-0x10FFFF). `🌍` = 1, `🏳️‍🌈` = 4, `café` = 4 or 5 (depends on NFC vs decomposed). Use when emulating other tools’ “characters” count. UTF-16 code unit: raw .charAt – surrogates separate. `🌍` = 2 (high surrogate + low surrogate), `café` = 4. Use only for matching JavaScript’s native .length and .charAt semantics.

Zero-Width Joiner (U+200D). It glues multiple emoji or characters into one rendered glyph. Examples: 👨‍👩‍👧‍👦 = `👨 + ZWJ + 👩 + ZWJ + 👧 + ZWJ + 👦`, 🏳️‍🌈 = `🏳 + VS16 (variation selector) + ZWJ + 🌈`, 👩🏽‍💻 = `👩 + skin-tone modifier + ZWJ + 💻`. Without grapheme awareness, these break apart on rotation. The Intl.Segmenter API knows the Unicode Standard’s grapheme breaking rules and keeps them together.

Characters that attach to the preceding base character. Examples: `é` can be `e + ◌́` (U+0301 combining acute accent – 2 code points) OR `é` (U+00E9 – 1 code point). Most modern text uses precomposed forms (NFC), but pasted-from-PDF or scientific notation often uses combining marks. Indic scripts (Devanagari, Tamil, Bengali) heavily use combining vowel marks – `कि` is `क` (consonant) + `ि` (vowel mark above it). Treating them as separate units would split the consonant from its vowel.

After modular reduction. If your text has 10 graphemes and you shift by 23, the effective shift is `23 mod 10 = 3` – same as shifting by 3. The stats card shows the reduced value so you know what actually happened. Negative effective shift = direction was inverted (you entered a negative number with Left direction → effectively a Right shift).

Apply the inverse: a Left shift of N → undo with Right shift of N (or Left shift of `length – N`). Negative N inverts direction implicitly, so Left -3 = Right 3 for undo. The stats card’s effective shift makes this easy to compute.

No – cyclic shift is trivially reversible and offers zero cryptographic strength. It’s a permutation of the input, fully recoverable without a key. Caesar ciphers are a different concept (each character mapped to character N positions later in the alphabet, which is also trivial to break). For real encryption use AES; for toy ciphers, this tool is fine for puzzles and pedagogy.

Logical-order rotation: the bytes/code points are rotated regardless of display direction. Arabic shaping (initial/medial/final forms) is applied by the browser after rotation, so the displayed result may look different from what you’d expect if you were rotating “visually”. This is correct behavior – text storage is always logical-order in Unicode. If you want visual-order rotation, you’d have to reverse the text first.

Yes. Text never leaves your browser. Intl.Segmenter runs locally as part of the V8/JavaScriptCore/SpiderMonkey runtime. The shifted text + download are all generated in memory and offered locally.