File, binary & compression tools
A file with the wrong extension, a download that might be corrupted, or a build artifact that changed for reasons the diff doesn't explain — these are the moments you need to look past the file's name and into its actual bytes. This page covers inspecting files as hex and ASCII, detecting real format from magic bytes, comparing binaries byte by byte, and computing checksums or compressing data.
File Type Checker reads magic bytes and flags it when the extension doesn't match what the content actually is, catching a renamed or mislabeled file before it causes problems downstream. Compare Binary Files reports the exact byte offsets where two files diverge instead of just saying they differ, and Executable file inspector reads ELF, PE and Mach-O headers directly. Source Map Viewer turns a minified stack trace back into the original file and line.
8 tools
Encode, checksum and compress
Files, Binary & Compression tools FAQ
File Type Checker reads the file's magic bytes — the signature at the start of the content — rather than trusting the extension, and flags it when the two disagree. That catches a renamed file, a failed export, or a download that got the wrong extension before you try to open it with the wrong program.
Compare Binary Files reads both files byte by byte and reports the exact offsets where they diverge, instead of just telling you the files aren't identical. That's useful for comparing build outputs, firmware images or any binary where a text diff tool would just show garbage.
Source Map Viewer takes a minified file's source map and maps a line and column in the compiled output back to the original file, line and function name. You need the .map file generated alongside the build; without it, the mapping isn't recoverable from the minified code alone.