Binary Inspector Studio
Answer questions like 'What is this file?' and 'Does the extension match reality?' without executing code or uploading confidential files. Pure client-side static binary forensics.
- Offline signature registry detecting hundreds of formats and magic numbers
- Extension vs content mismatch detection (e.g., executables disguised as .jpg)
- Virtualized Hex Viewer with offset jumping, multi-byte integers, endian switching, and search
- ASCII/UTF-8/UTF-16 strings extraction with pattern recognition (URLs, emails, IPs, paths, UUIDs)
- Shannon entropy analysis with block distribution graph to spot compressed or packed regions
- Low-level structural parsing for PNG, JPEG, ZIP, RIFF/WAV, MP3, PDF, PE, ELF, Mach-O, and WASM
- Embedded file signature detection and file carving extraction
- Cryptographic hashes (SHA-256, SHA-512, MD5, SHA-1) and byte-by-byte comparison mode
Drop a file to inspect
or click to select file (multi-file and large files supported)
About Solasu Binary Inspector Studio
Binary Inspector Studio is an offline-capable browser forensics workbench designed to inspect arbitrary binary files, extensionless data, corrupted payloads, and suspicious containers safely inside browser memory. Files are never uploaded, never executed as programs, and your original files are never altered.
Comprehensive Signature Database & Extension Mismatch Detection
Featuring a built-in static signature registry covering hundreds of file formats, the tool determines true file types from header magic bytes with high certainty.
Detects extension spoofing instantly. For example, if a file named 'invoice.pdf' actually contains a Windows executable (MZ header) or an archive, a prominent mismatch alert is displayed immediately.
Virtualized Hex Viewer with Multi-Byte Integer Inspection
Inspect raw bytes with 16-byte offset rows, hexadecimal dumps, and ASCII decoding. Virtualized rendering ensures smooth navigation even across large binary files.
Decode selected bytes as 8-bit, 16-bit, 32-bit, or 64-bit signed/unsigned integers with one-click Little-Endian / Big-Endian switching, hex/text searching, and direct offset jumping.
Strings Extraction, Pattern Recognition & Shannon Entropy
Extract readable strings across ASCII, UTF-8, and UTF-16LE encodings. Automatically identifies structural forensic patterns such as URLs, email addresses, IPv4/IPv6 addresses, file paths, and UUIDs.
Calculate Shannon entropy across configurable byte blocks and visualize density variations with an SVG area graph to spotlight compressed, encrypted, or packed sections.
Static Executable Parsing: PE, ELF, Mach-O, and WASM
Examine binary structures for Windows PE (EXE/DLL), Linux ELF, macOS Mach-O, and WebAssembly (WASM). Inspect entry points, section tables, raw offsets, and risky attributes such as W+X (Writable and Executable) flags.
Safety guarantee: This tool performs purely static parsing. Binary code is never executed, invoked, or passed to OS runtimes.
Embedded Signatures, Carving Preview & Binary Diff Comparison
Scan for secondary container signatures embedded at non-zero offsets (such as PNGs, ZIPs, or executables hidden within carrier files) and carve candidate data slices directly to your device.
Compare two files byte-by-byte to verify exact cryptographic identity or pinpoint changed ranges and offset differences.
Binary Forensics & Inspection FAQ
Are my files uploaded to an external server or third-party API?
No. All inspection runs strictly inside your local browser memory using JavaScript and Web APIs. No network requests are made with your file data.
Is it safe to inspect suspicious or potentially malicious files?
Yes, because the files are only read as raw binary data and are never executed. However, static analysis cannot guarantee whether a file is safe or malicious. Always exercise appropriate caution with unknown files.
Can I inspect large files?
Yes. Through memory-conscious slicing and virtualized table rows, files up to hundreds of megabytes can be inspected within standard browser memory limits.
Can I export inspection results?
Yes. Full forensic summaries can be exported as structured JSON, CSV, plaintext TXT, or standalone styled HTML reports.