Identify the format
Inspect header signatures instead of trusting a filename extension. See the actual evidence and detection confidence.
Binary analysis studio V2 · File forensics
File Structure Explorer
Explore magic bytes, file headers, offsets, structural regions and embedded content. Search the raw bytes and recover readable strings—without uploading your file to a server.
◆ Format detection◆ Hex + ASCII◆ Structure map◆ Deep scans
YOUR WORKSPACE
File inspector
Drop a file to start exploring
Any file type · No account · No server upload
Select multiple files to inspect them one by one. Analysis uses small, on-demand file slices. Very large files are supported, but full-file scans can take time.
Detected type——
File size——
Structure regions—Mapped elements
Leading bytes—First 8 bytes
Analyzing…0%
DETECTION
—File type
—
BYTE PROFILE
—First 256 KiB sample
Shannon entropy of the sampled bytes, not a compression or encryption verdict.
00–1F80–9FE0–FF
STRUCTURAL PREVIEW
File map
Region blocks are illustrative, not drawn to byte scale. Select a block to jump to its exact offset.
HEX EDITOR-STYLE VIEW
16 bytes per row · 1 KiB per pageRead-only byte inspector
Click a byte to inspect it. Shift-click for a selection, or use arrow keys and Shift+arrow when focused. Offset numbers and byte values are hexadecimal.
OFFSETHEX BYTES 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0FASCII
SELECTION
Click a byte to inspect its value.
Values are interpreted from the selected starting offset, using up to 8 bytes remaining in this page.
Export exact byte range
Start offset and byte length; up to 16 MiB per export. Original file is never changed.
Bookmarks 0
No bookmarks yet. Select a byte and choose Bookmark offset.
FORMAT-AWARE PARSING
Bounded, read-only mapHeaders, chunks & regions
These are parsed regions, not a complete file-format validation. Overlapping regions can represent nested headers and data.
CARVING HINTS
Embedded file signatures
Potential signatures found at arbitrary offsets. A signature is only a clue; it does not prove a valid embedded file. Results are limited to the selected scan scope.
Run “Scan signatures” to discover patterns.
| Offset | Pattern | Confidence | Action |
|---|
STRING EXTRACTION
Readable strings
ASCII and UTF-16LE/BE printable runs; not a universal multilingual text decoder. Content may include sensitive strings—exports stay on your device.
Run “Extract strings” to populate this view.
| Offset | Encoding | Text (preview) | Action |
|---|
—
BYTE-LEVEL SEARCH
Up to 300 matchesFind patterns in raw data
Hex accepts spaces, ?? and nibble wildcards such as 4?. Text mode matches the exact UTF-8 byte sequence, not case-insensitive text.
Enter a pattern to search within the selected analysis scope.
| Match offset | Matched length | Action |
|---|
HOW IT WORKS
From unknown bytes to useful answers.
Navigate the structure
Jump to known chunks, headers, tables and file offsets, then examine the exact bytes in the hex viewer.
Explore deeper
Find embedded signatures, extract printable text and run hex or UTF-8 searches. Export findings for review.
FREQUENTLY ASKED QUESTIONS
Details worth knowing.
Does PixelOkay upload my file?
No. This tool uses the browser File API and a local web worker to inspect the file. It does not send file contents to a server. Like any website, the page itself must still be loaded from its hosting origin.
Does it open any file format?
Any file can be opened for generic hex and ASCII inspection. Format-specific structure parsing is available for selected formats such as PNG, JPEG, ZIP, PDF, RIFF, ISO BMFF, ELF, PE, SQLite, WebAssembly and GIF. Unknown formats receive a generic view.
Can it fix a damaged file or extract archive contents?
No. This is a read-only forensic and debugging aid. Detected signatures and parsed header values are hints, not proof of integrity. It does not repair data or decompress archives.
What does scan scope mean?
Signature, text and byte-pattern scans examine the beginning of the file up to the chosen limit. Choose “Entire file” for a full scan, bearing in mind that larger files require more processing time. Structural parsing reads independent bounded regions where needed.