How to hex editor vs hex inspector: choosing the right tool
- Step 1Drop the file for inspection — Drag the binary file into the inspector. The tool reads the tier-appropriate byte count (256B free, 1KB Pro, 8KB Developer) from the header.
- Step 2Navigate the hex grid — Each row shows offset, 16 hex bytes, and their ASCII equivalents. Unprintable bytes render as dots.
- Step 3Use annotations for known formats — The inspector highlights magic-byte ranges and known field positions for common formats — no need to look up the spec separately.
Frequently asked questions
Can the inspector edit bytes?+
No. Read-only by design — preventing accidental modification is a core feature for forensic integrity.
Why is the byte limit tiered?+
Rendering thousands of hex rows in a browser DOM is expensive. 256 bytes covers every magic-byte check; 1KB covers most format headers; 8KB covers extended headers for container formats.
Is it equivalent to running xxd in Linux?+
For header inspection, yes. The output format mirrors xxd: offset address, 16-byte hex group, ASCII sidebar per row.
Privacy first
Every JAD Security operation runs entirely in your browser. Files, passwords, and PGP private keys never leave your device — verified by zero outbound network requests during processing.