Zero-Width Steganography Decoder

Bounded lossless byte-hex steganographic decoder using U+200B/U+200C bits. No encryption, authentication or robustness to text normalization.

Description

Decode a strict U+200B/U+200C bit stream to payload hexadecimal.

A zero-width transport encoding can map two specific Unicode characters to binary digits. This decoder reads only that exact character stream and returns its bytes as hexadecimal.

When to use this tool

Decode a strict U+200B/U+200C bit stream to payload hexadecimal. Use it when the input measurements and conventions below match the operation you need.

Prepare encodedText, respecting the measurement basis and boundaries below.
Compare the worked example with your intended operation before reusing its result.

How to use the tool and how it works

Enter every field in the input table using the stated units and exact supported selector spelling where applicable.
Run the tool. Correct input errors before interpreting an output.
Read the result fields below; use accompanying flags and the stated sign, boundary or model convention when interpreting a number.

U+200B represents zero and U+200C represents one. The tool groups the stream most-significant bit first into complete eight-bit bytes and returns lowercase payloadHex; empty input is allowed and the limit is 1,024 bits.^[1]

Input field	Meaning and units	Accepted input
encodedText	Encoded text.	Text

Output field	Interpretation
result	Object containing the following named result fields.
result.payloadHex	Payload hex; use the stated units and sign convention.

json

{
  "input": {
    "encodedText": "\u200b\u200c\u200b\u200b\u200b\u200b\u200b\u200c"
  },
  "output": {
    "result": {
      "payloadHex": "41"
    }
  }
}

Limitations and assumptions

Ordinary cover text, other invisible characters and incomplete bytes are rejected. No decryption, hidden-text discovery or integrity check is performed, and Unicode normalization or filtering can damage the stream.
Every declared field is required and unexpected fields are rejected. Numeric inputs must be finite; input errors are distinct from a valid false result or an explicitly qualified output.
Extremely large inputs and nonfinite or excessively large outputs are rejected. List positions reported by the tool use zero-based indices unless stated otherwise.

Alternative or Complementary methods

Use the applicable protocol specification and a reviewed implementation for real verification, hashing or key management. A format label, probability model or tentative text mapping does not replace that operation. Compare the scope of the nearby tools below before substituting one.

References

Tool behavior and example: Zero-Width Steganography Decoder — tool.io

Similar or alternative tools

Zero-Width Steganography Encoder
Bounded lossless byte-hex steganographic encoder using U+200B/U+200C bits. No encryption, authentication or robustness to text normalization.
Whitespace Steganography Decoder
Bounded lossless byte-hex steganographic decoder using one space/tab bit per line. No encryption, authentication or robustness to text normalization.