Conversions
One input, every shape. The tool says what it read.
Everything runs in your browser. Nothing is sent.
Samples:
Detection is ambiguous, and stays so. 4111 is valid hexadecimal,
valid text and valid Base64 all at once. The tool always says which one it picked, and
"read as" overrides it in one click.
b8 sits on the left, b1 on the right. Read backwards, a TVR (95) or
an AIP (82) says the opposite of what it says, and the answer still looks
believable.
Base64 is read in groups of 4 characters, the trailing = is only padding.
An unexpected byte count almost always comes from there.
Are those bytes part of a stream? Read a TLV stream names the tags as well as decoding them.