Loading...

tools / binary-inspector

Binary Inspector

Inspect pasted hex or Base64 bytes, magic numbers, endian clues, file signatures, encoding mistakes, and binary payload notes.

P2Logs & ErrorsHigh severity
90
debug signal score
4 signals

4 signals detected. Start with png magic bytes.

Detected signals

PNG magic bytes

PNG file signature is present.

Check whether the parser expects image bytes, metadata, or a different transport encoding.

ZIP magic bytes

ZIP-like archive signature is present.

Confirm whether this is a ZIP/JAR/APK/DOCX-style container.

Encoded JSON clue

The binary payload may contain JSON or Base64-encoded JSON.

Decode safely and validate character encoding before parsing.

Invalid magic number

The file or protocol header does not match expectations.

Compare the first bytes with the expected format and confirm endian assumptions.

Highlighted lines
line 1
89504E470D0A1A0A
PNG magic bytes
line 2
PK\x03\x04
ZIP magic bytes
line 3
7b226572726f72223a747275657d
Encoded JSON clue
line 4
invalid magic number
Invalid magic number
Fix checklist
Check whether the parser expects image bytes, metadata, or a different transport encoding.
Confirm whether this is a ZIP/JAR/APK/DOCX-style container.
Decode safely and validate character encoding before parsing.
Compare the first bytes with the expected format and confirm endian assumptions.
Identify the first 8-16 bytes.
Check expected file/protocol signature.
Confirm Base64, hex, UTF-8, and endian assumptions.

DebugTools product

Binary Inspector

Binary Inspector is a focused DebugTools mini-product for developers. Inspect pasted hex or Base64 bytes, magic numbers, endian clues, file signatures, encoding mistakes, and binary payload notes.

Use cases

  • Turn pasted failures into a cleaner root-cause checklist.
  • Separate the first error from retries, noise, and downstream symptoms.
  • Prepare a concise report for an issue, pull request, or incident note.

How it works

  • Paste or load the snippet you want to inspect in Binary Inspector.
  • Run the tool in the browser and review the highlighted output.
  • Copy, export, or turn the result into the next debugging step.

Privacy

  • Binary Inspector is local-first. The core workflow runs in your browser and does not require sending pasted content to DebugTools servers.

This tool history

Recent Binary Inspector sessions

Only visits for this tool are shown. Pasted content, tokens, request bodies, and logs are not stored here.

Loading this tool history...