Zero-Width Steganography Encoder

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

Description

Encode up to 128 payload bytes as a U+200B/U+200C bit stream.

Zero-width characters can represent a byte stream without rendering ordinary visible glyphs. This encoder produces the strict two-character format accepted by the paired decoder.

When to use this tool

Encode up to 128 payload bytes as a U+200B/U+200C bit stream. Use it when the input measurements and conventions below match the operation you need.

  • Prepare payloadHex, 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

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

The input is an even-length hexadecimal string of at most 256 digits, representing up to 128 bytes. It expands each byte most-significant bit first, maps zero to U+200B and one to U+200C, and joins the characters without separators; empty input gives empty output.1

Input fieldMeaning and unitsAccepted input
payloadHexPayload hex.Text
Output fieldInterpretation
resultObject containing the following named result fields.
result.encodedTextEncoded text; use the stated units and sign convention.
json
{
  "input": {
    "payloadHex": "41"
  },
  "output": {
    "result": {
      "encodedText": "\u200b\u200c\u200b\u200b\u200b\u200b\u200b\u200c"
    }
  }
}

Limitations and assumptions

  • The output is an encoded stream, without attached cover text, encryption or authentication. Text sanitation can remove these characters and make the payload unrecoverable.
  • 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

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

Similar or alternative tools

  • Zero-Width Steganography Decoder

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

  • Whitespace Steganography Encoder

    Bounded lossless byte-hex steganographic encoder using one space/tab bit per line. No encryption, authentication or robustness to text normalization.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies