Netstring Byte Record Encoder

Encode a single byte netstring with ASCII decimal byte length, colon and comma; binary payload bytes are not converted to text.

Description

Encode a single byte netstring with ASCII decimal byte length, colon and comma; binary payload bytes are not converted to text.

A netstring preserves arbitrary payload octets by declaring their length before the payload.

When to use this tool

Encode a single byte netstring with ASCII decimal byte length, colon and comma; binary payload bytes are not converted to text.

Prepare the supplied bytes fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter bytes. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.bytes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Validate bytes, emit their ASCII decimal count, colon, unchanged payload and comma. Reject a total record longer than 128 bytes.^[1]

Input field	Meaning and representation	Accepted input
bytes	bytes.	List of integers from 0 to 255; at most 128 bytes

Output field	Interpretation
result	Object containing the named outputs below.
result.bytes	The bytes list in the ordering and representation described above.

json

{
  "input": {
    "bytes": [
      0,
      255
    ]
  },
  "output": {
    "result": {
      "bytes": [
        50,
        58,
        0,
        255,
        44
      ]
    }
  }
}

Limitations and assumptions

No character encoding is applied and no stream is sent. The local output budget leaves fewer than 128 payload bytes available.
All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.

Alternative or Complementary methods

Use a stateful protocol parser when processing partial streams or validating complete packets. Retain the declared prefix width, byte order and payload-versus-frame boundary convention when composing these operations.

References

Tool behavior and example: Netstring Byte Record Encoder — tool.io

Similar or alternative tools

Netstring Byte Record Decoder
Decode exactly one complete binary netstring with canonical ASCII decimal length and terminal comma; no concatenated records or leading-zero lengths.
Byte Frame Chunk Carry Tool
Advance one fixed-byte streaming frame chunk with explicit incomplete carry, emitting complete frames and retaining the new tail; no sync search.