Whitespace Steganography Encoder

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

Description

Encode up to 128 payload bytes as one space-or-tab bit per line.

A byte payload can be encoded as a visible-to-machines stream of spaces and tabs. This encoder creates one whitespace bit per line for the paired decoder.

When to use this tool

Encode up to 128 payload bytes as one space-or-tab bit per line. 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

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.

payloadHex must contain an even number of hexadecimal digits, up to 256 digits or 128 bytes; empty input is accepted. Each byte is expanded most-significant bit first, using a space for zero and a tab for one, with newline separators.^[1]

Input field	Meaning and units	Accepted input
payloadHex	Payload hex.	Text

Output field	Interpretation
result	Object containing the following named result fields.
result.encodedText	Encoded text; use the stated units and sign convention.

json

{
  "input": {
    "payloadHex": "41"
  },
  "output": {
    "result": {
      "encodedText": " \n\t\n \n \n \n \n \n\t"
    }
  }
}

Limitations and assumptions

The tool does not append data to cover text or encrypt it. Editors and messaging systems can normalize whitespace and destroy the payload; the output has no integrity protection.
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: Whitespace Steganography Encoder — tool.io

Similar or alternative tools

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