Protocols & Binary Serialization
Paste escaped RESP text or Hex bytes to inspect complete frames without contacting a Redis server.
Paste RESP data or load an example.
Parsed locally; no Redis connection or upload.
Paste RESP data or load an example.
When a Redis client log shows $5 or a reply changes shape after HELLO 3, the raw frame matters more than the value printed by the client. A Redis RESP parser lets you trace each prefix and byte span before deciding whether the command or capture is at fault.
Read static RESP bytes as a structured record while keeping their boundaries visible.
The Redis RESP parser joins complete RESP3 chunks only after checking each declared byte count and its terminator. The tree still marks the streamed source and the number of chunks, so a missing final segment is never shown as a finished value.
A binary bulk keeps Hex, a map keeps ordered key/value entries, and an attribute stays attached to the following value. The typed JSON makes these differences explicit where ordinary JSON strings or objects would hide them.
Escaped text is the default: literal backslash-r and backslash-n become CRLF bytes. Switch to Hex when a bulk contains non-text bytes; bare LF is never silently repaired.
Auto accepts shared RESP2/RESP3 types and flags RESP3-only prefixes. Selecting RESP2 rejects those prefixes; a shared type alone cannot reveal the negotiated connection version.
Read the byte range and declared length on each node. A top-level array with text arguments gets a command-shape summary, while the JSON view keeps type tags for binary and map values.
The RESP protocol decoder distinguishes null bulk from empty bulk, arrays from maps, and a server error value from a parser failure.
A declared bulk length is compared with actual UTF-8 bytes and the final CRLF; the first mismatch reports a byte offset and editor line.
Several top-level replies or command frames stay in order. A request-shaped array shows the command name and argument previews without claiming that Redis would accept it.
Redis RESP decoder output retains Hex for binary data, decimal text for large numbers, ordered map entries and RESP3 attributes.
Paste its escaped wire text or Hex bytes. A top-level array of strings shows a command name and argument count; this checks the frame structure, not server-side command semantics.
It is a dollar sign, the byte length, CRLF, exactly that many data bytes and another CRLF. A three-byte UTF-8 character therefore needs length 3 even though it looks like one character.
RESP3 adds null, boolean, double, big number, map, set, attribute, push and other types. Auto reports only the minimum required version; a shared type cannot identify the connection mode.
Redis can accept a legacy inline command form in limited contexts. This Redis RESP parser reads framed RESP values, so inline command text is outside its input contract.
$-1 is a null bulk, while $0 followed by CRLF CRLF is an empty bulk. The tree and typed JSON keep them separate.
Still have a wire-format question?
Paste the captured bytes and check the first failing offset before changing a client or server. The Redis RESP parser exports the typed result only after a complete successful read.
Processing happens locally in your browser.