MachineTradecraft
Global site search

Search guides, labs, glossary, and research

Type two or more characters to search.

Start with a channel, artifact, or defense term

Examples include zero-width, metadata, tokenizer, or prompt injection.
    Text & Unicode · Formatting channel

    Whitespace & Formatting Differential

    Many whitespace code points render as blank space while remaining categorically distinct. The laboratory replaces them with labelled boxes and compares conservative and aggressive normalization.

    Browse all labs Open universal Machine View
    Quick answer

    What does the Whitespace & Formatting show?

    Many whitespace code points render as blank space while remaining categorically distinct. The laboratory replaces them with labelled boxes and compares conservative and aggressive normalization.

    Human visibility
    Invisible or low-salience
    Machine receiver
    Raw-text parser
    Robustness
    Usually fragile under formatting

    Research boundary: this page uses bounded, inert data and fixed safe examples. It never executes decoded content, requests secrets, calls third-party services, or performs actions against external systems.

    FIRST RUN / THREE STEPS

    Start with the prepared, bounded workflow.

    Nothing runs automatically
    1. Review the prepared starter input

      A bounded benign input is already present. Change it only when you are ready to test a different authorized artifact.

    2. Run Reveal whitespace

      Run the normal first-pass analysis for the prepared values above.

    3. Scan before expanding

      Read the summary first, then scan findings and expand only the machine views you need.

    INPUT / CONTROL PLANE

    Prepare the input and choose one action.

    Ready

    The recommended first run is separated from alternate analyses. Inputs and selected files stay on this host.

    Current input state Prepared starter input loaded

    The form is prefilled with a bounded safe starting point. Nothing runs until you choose an action.

    29 / 4,096 bytes

    Enter or paste one bounded, authorized artifact. The original value remains in the form so you can revise and rerun it.

    Maximum: 4,096 UTF-8 bytes.

    Choose the normalization profile used for this run. The selection changes only this local analysis.

    Switch prepared example3 options

    Loading a sample changes only the form values. Review the result and run an action yourself.

    Prepared benign examples
    ACTION HIERARCHY

    Run the recommended first pass.

    Alternate actions remain available below, but the first pass is the clearest place to start.

    Other analyses1 action

    Inputs remain on this host. Text operations are size-limited; uploaded files are processed from PHP’s temporary upload and are not retained by the application.

    OUTPUT / MACHINE VIEWS

    Scan the result from summary to evidence.

    Run Reveal whitespace to create the first result.

    The prepared starter input is ready. The output will lead with a summary and visible qualifications before the expandable machine views.

    SummaryFindingsMachine views
    Interpretation framework

    The same artifact can produce several valid observations.

    01

    Human view

    What a person naturally reads, sees, or hears.

    02

    Structural view

    What a parser, DOM, container reader, or metadata extractor exposes.

    03

    Decoder view

    What becomes meaningful only with a rule, key, tokenizer, model, or tool.

    04

    Defensive view

    What normalization, rendering, OCR, canonicalization, or policy changes.

    Evidence and decision boundary

    Use the result as bounded evidence, not as a universal verdict.

    Many whitespace code points render as blank space while remaining categorically distinct. The laboratory replaces them with labelled boxes and compares conservative and aggressive normalization.

    Interpretation rule

    Record the receiver and transformation.

    Machine-decodable is receiver-relative. Record the parser, preprocessing, codebook, tokenizer, key, model, and transformation path before generalizing from one result.

    Limitations

    What this page does not prove

    Collapsing whitespace can destroy legitimate formatting, programming-language indentation, and typographic distinctions. The original is always retained in the result.

    Continue the investigation

    Related labs and source reports

    Invisible Unicode Code-point scanner or exact tokenizer Homoglyphs & Confusables Code-point and script analyzer Bidirectional Text Renderer and logical parser Structural Steganography in Normal-Looking English Writing Research report Invisible Unicode and Modern Language-Model Tokenizers Research report
    Continue exploring

    Move from the current explanation to a related guide, evidence source, or controlled workbench.

    Laboratory catalogChoose a focused local experimentBrowse 40 bounded laboratories spanning representation, files, messages, models, provenance, agents, supply chains, and defense.Open this path Topic guideUnderstand invisible Unicode and AICompare code points, glyphs, normalization, bidi controls, confusables, and tokenizer behavior.Open this path Defensive architectureBuild a safer model-ingestion boundaryPreserve evidence, compare representations, canonicalize allowlisted fields, retain provenance, and minimize privilege.Open this path