Menu

Text Obfuscator

Hide secret messages invisibly inside any text using zero-width Unicode characters. Decode hidden payloads, clean files, or inspect zero-width density. UTF-8 aware, carrier text verified, round-trip PASS/FAIL shown.

Zero-Width Text Obfuscation Studio Steganography
Ready
Text Input / Carrier 0 lines • 0 chars
Output / Decoded 0 lines • 0 chars
🔒 Hide Text mode. The "Secret Message" below is encoded as zero-width Unicode characters and inserted invisibly into your carrier text. The visible text stays identical. Round-trip validation runs automatically.
Complete Guide to Zero-Width Text Obfuscation

What Zero-Width Text Obfuscation Is

Zero-width text obfuscation is a form of steganography — hiding a message inside another message so that only the intended recipient knows the first message exists. Unlike encryption, which makes a message unreadable, steganography makes a message invisible.

The technique uses zero-width Unicode characters: characters that occupy no visual space when rendered. They are invisible in normal text display. But they are real bytes that survive copy-paste, file transfer, and most text processing.

Character Scheme — Explicitly Defined

This tool uses exactly four zero-width characters. Each has a specific role in the payload format:

CharacterUnicodeRole
Zero-Width Space (ZWSP)U+200BBinary 0
Zero-Width Non-Joiner (ZWNJ)U+200CBinary 1
Zero-Width Joiner (ZWJ)U+200DStart marker
Word Joiner (WJ)U+2060End marker

Payload Format — Byte-Level Encoding

Encoding pipeline:

  1. Secret message → UTF-8 bytes via TextEncoder API
  2. Each byte → 8 bits (MSB first)
  3. Each bit → ZWSP (0) or ZWNJ (1)
  4. Wrap with ZWJ start marker + WJ end marker
  5. Insert into carrier text after first word

Decoding pipeline reverses this exactly: locate ZWJ start marker, collect 8 bits per byte until WJ end marker, convert bytes to UTF-8 via TextDecoder.

UTF-8 Support — Emoji, Urdu, Multiline

The tool uses the TextEncoder/TextDecoder API, which correctly handles any Unicode content:

Secret messageUTF-8 bytesZero-width chars
Hello5 bytes40 bits → 40 chars
مرحبا10 bytes (2 per Arabic char)80 bits → 80 chars
😀4 bytes (surrogate pair)32 bits → 32 chars
Hi 👋 World13 bytes104 bits → 104 chars

Byte-level comparison — not string comparison — ensures correctness even when JavaScript would treat surrogate pairs as two chars.

Carrier Text Preservation — Verified

After hiding, the tool verifies the visible text is byte-for-byte identical to the original carrier by stripping all zero-width characters and comparing. This check is performed both after encoding and after round-trip decoding. If the visible text is modified, the round-trip reports FAIL.

"Visible text unchanged" refers to normal display behavior. Not every platform preserves zero-width characters. The following strip them and will break the hidden payload:
  • Gmail web compose
  • Slack messages
  • Discord messages
  • Twitter/X posts
  • Some CMS WYSIWYG editors
  • Text sanitizers in messaging APIs

Validation — Clear Errors

Decode mode reports specific errors:

  • No start marker found — input contains no hidden payload
  • Start marker found but no end marker — payload is incomplete/truncated
  • Payload length not a multiple of 8 — data corruption
  • Invalid UTF-8 bytes — payload encoding is not UTF-8

Every error includes the specific condition. No silent fallback to garbage output.

Round-Trip Validation

After encoding, the tool automatically:

  1. Decodes the output back to the hidden message
  2. Compares byte-for-byte with the original secret via UTF-8 encoding
  3. Strips zero-width chars from output and compares to original carrier

The results panel shows:

  • ✅ Payload recovered — decode matches original secret
  • ✅ Carrier preserved — visible text matches original
  • ❌ Round-trip FAILED — with specific reason

What This Tool Cannot Do

  • It cannot encrypt. Zero-width is encoding, not encryption. Anyone with a decoder can read the hidden text.
  • It cannot hide secrets safely. Do not embed passwords, API keys, or tokens.
  • It cannot survive every platform. See the strip list above.
  • It cannot hide from a hex editor. The Unicode bytes E2 80 8B (ZWSP), E2 80 8C (ZWNJ), E2 80 8D (ZWJ), E2 81 A0 (WJ) are all visible in raw byte inspection.
  • It cannot protect against deliberate analysis. Anyone who knows about zero-width steganography can extract the payload.

Security Claims — What This Tool Is Not

This is steganography, not encryption. It hides the existence of a message, not its content. If someone suspects the message is there, they can extract it. The appropriate mental model is a watermark or a canary token, not a lock. Use AES-GCM, ChaCha20-Poly1305, or GPG for actual confidentiality.

Real Use Cases

  • Watermarking generated content — embed a unique ID for provenance tracking
  • Canary tokens — send the same text to N recipients with distinct IDs; a leak identifies the source
  • A/B test tracking — tag visible content with the variant ID
  • Workflow state — embed approval stage or template version
  • Invisible notes — add private annotations to a shared document

Frequently Asked Questions

Does the hidden text change how the carrier text looks?
In normal text display, no. Zero-width characters occupy zero visual space. The visible text renders identically. But some platforms strip them entirely, which removes the hidden payload. See the strip list above.
Does it support emoji and non-Latin scripts?
Yes. The tool uses the TextEncoder API for UTF-8 byte-level encoding, which correctly handles emoji, Arabic, Urdu, Hindi, Chinese, and any other Unicode content. Round-trip is verified byte-for-byte.
What happens if the hidden payload is stripped?
Decode mode reports a clear error: "No start marker found" or "Incomplete payload." No silent failure.
Will the hidden text survive copy-paste?
Usually yes in text editors and file transfers. But Gmail, Slack, Discord, Twitter, and some CMS editors strip zero-width characters. Test on your target platform before relying on this.
Is this encryption?
No. It is steganography — hiding the existence of a message. Anyone with a decoder can read the hidden text. Do not use for secrets.
How much text can I hide?
No hard limit, but each byte becomes 8 zero-width characters. A 100-byte secret becomes 800 zero-width chars (~2400 bytes in UTF-8). For very large payloads, the carrier needs to be proportionally large or the file becomes obvious in a hex editor.
Can I hide multiple separate messages?
This tool supports one payload per operation. To hide multiple messages, run the tool multiple times on the output of the previous operation.
How do I decode?
Enable "🔓 Decode" mode, paste the carrier text, click Process. The tool extracts the hidden payload. If the payload is stripped, you see a clear error.
How do I remove hidden data?
Enable "🧹 Clean" mode and paste the text. The tool removes all four zero-width character types.
Is my text uploaded to your server?
No. Everything runs in your browser using JavaScript. Your text never leaves your device.
Can antivirus detect hidden text?
Some endpoint security tools flag files containing zero-width characters as suspicious, because malware has used the technique. Add a clear visible comment if you distribute the file.
Does the seed affect the output?
The seed affects the placement position of the payload within the carrier text. Different seeds produce different insertion positions. The payload encoding itself is deterministic.
Can I recover hidden text if I forget the seed?
Yes. The payload encoding does not depend on the seed — the seed only affects insertion position. Decode always works regardless of seed.
What is the maximum carrier text size?
No hard limit, but files above 5 MB may cause browser slowdowns. For very large text, use a command-line tool.
What is the difference between this and the Markdown obfuscator?
The Markdown obfuscator is tailored for Markdown structure (fences, headings). This text obfuscator works on any plain text and includes Inspect mode for analysis.

Related Tools