Skip to content

Decoder

zhttp reads the encodings common in HTTP traffic, one inside another. A Base64 value that holds gzip that holds JSON reads as Base64 › gzip and shows the JSON.

  • A JSON Web Token: a JWT chip shows beside any header, query parameter or cookie that holds one, such as an Authorization: Bearer header. Click it.
  • A header, query parameter or cookie: right-click it in the inspector › Decode.
  • Part of a body: select the text, right-click › Decode.

A card opens with what the value holds. Copy copies it, and Open in Decoder takes the value to the Decoder window.

Open it with Ctrl Shift D, or Open decoder in the command palette. Paste or type a value in the top half; what it holds shows in the bottom half as you type.

Encode at the top turns the text into Base64, Base64URL, URL encoding or hex instead. Esc closes the window.

Encoding
JWT The header and payload, as JSON. exp, nbf, iat and auth_time are listed as local times, with how long ago or how soon. An exp that has passed shows red, an nbf still to come amber.
Base64, Base64URL With or without padding, on one line or wrapped
Hex Plain, spaced or colon-separated
URL encoding %xx escapes
gzip, zlib, Brotli Inside any of the above
Unix time 10, 13 or 16 digits: seconds, milliseconds or microseconds, as a date from 2000 to 2099

Up to six steps are followed. When a value reads more than one way, a choice of readings shows at the top of the card, such as Base64 and Hex. A reading that ends in bytes rather than text is offered only when no reading ends in text, and shows them as hex.