Binary File Inspector

Inspect a file's raw bytes with an online hex viewer, binary representation and ASCII preview. Identify common file signatures, extract readable strings, search for byte patterns and calculate a SHA-256 checksum without uploading the file to this website.

Hex viewer Binary and ASCII File signatures SHA-256 Local processing

Inspect a Binary File

Select a file or drag it into the area below. The browser reads the selected file as bytes and displays a bounded sample. The original file is never modified.

Privacy: This tool processes the selected file in your browser. It does not send file contents to a PHP upload handler or execute the file. The default inspection limit is 8 MiB.

Choose a file or drag it here

Any file type is accepted. Executables are inspected as bytes only and are not run.

Select File

No file selected

Original file size —

Bytes inspected —

Detected format —

Hexadecimal and ASCII Viewer

Each row shows a file offset, hexadecimal bytes and a readable ASCII preview. Non-printable bytes are shown as dots in the preview so control codes do not disrupt the layout.

Select a file to display its bytes.

Offset	Hexadecimal bytes	ASCII preview
No file loaded.

Offsets start at 0x00. The viewer displays a limited number of rows per page to keep the interface responsive.

Search for Bytes or Text

Search the inspected bytes for a hexadecimal pattern or an ASCII text string. Hex searches can contain spaces, for example 50 4B 03 04.

Search mode

Search pattern

No search performed.

Extract Printable ASCII Strings

Extract consecutive printable ASCII characters from the inspected bytes. This can help locate embedded messages, file paths, metadata, identifiers and other readable text. It does not decode every possible character encoding.

Minimum string length

Maximum strings to display

Select a file to extract printable strings.

No strings extracted.

SHA-256 File Checksum

SHA-256 produces a 256-bit digest commonly represented as 64 hexadecimal characters. It can help compare file contents, but a matching hash alone does not establish that a file is safe or authentic.

For files larger than the inspection limit, the inspector only reads the leading sample. It will not label a hash of that sample as the SHA-256 of the entire original file.

No hash calculated.

—

How to Use the Binary File Inspector

Select a file from your device or drag it into the file area.
Review the detected file signature and the first bytes in hexadecimal.
Use the hex viewer to navigate offsets and compare bytes with the ASCII preview.
Search for a byte pattern or text string within the inspected sample.
Extract printable strings or calculate a SHA-256 digest where supported.
Download a JSON report if you need a record of the inspection.

A file signature can help identify a likely format, but a signature match does not prove that the file is valid, complete, harmless or trustworthy.

What Are Magic Bytes?

Magic bytes are byte patterns commonly found at specific positions in a file. Many formats use an identifiable signature near the beginning, although some formats require additional structural checks or use signatures at other offsets.

Format	Common signature (hex)	Typical use
PNG	89 50 4E 47 0D 0A 1A 0A	Raster images
JPEG	FF D8 FF	Photographs and images
GIF	47 49 46 38	Images and animations
PDF	25 50 44 46	Portable documents
ZIP	50 4B 03 04	Archives and some office formats
Windows executable	4D 5A	PE-family executable files begin with MZ
ELF	7F 45 4C 46	Linux and Unix executable formats
WebAssembly	00 61 73 6D	WebAssembly modules
WAV / RIFF	52 49 46 46	RIFF-based multimedia; inspect further bytes to identify subtype

The inspector recognizes common signatures using the bytes available in the sample. Its identification is intentionally lightweight: it does not fully parse every file format.

Frequently Asked Questions

1. What does a binary file inspector do?

It shows the raw bytes of a file in forms such as hexadecimal, binary and printable ASCII. This helps developers inspect file headers, investigate data formats and locate readable strings.

2. Are my files uploaded to Binarios.org?

This page reads the selected file through the browser's local File API. Its inspection code does not upload the file to a server. Normal website delivery and hosting are separate from processing the selected file.

3. Why is there an 8 MiB inspection limit?

Reading and displaying large files can consume significant browser memory. The limit helps keep the tool responsive on shared devices and mobile browsers. Larger files can be inspected in chunks with dedicated desktop tools.

4. Does detecting a file signature prove the file is safe?

No. A signature indicates that certain bytes match a known pattern. It does not validate the complete file, establish its origin or prove that it is free of malicious content.

5. Can the inspector execute an EXE or other program?

No. It reads the selected file as bytes and does not execute or emulate it. Avoid opening suspicious files with other applications unless you understand the risks.

6. Why are some bytes shown as dots?

The ASCII preview displays printable ASCII bytes directly and replaces other byte values with dots. This avoids displaying control characters that could disrupt the layout or terminal-style output.

7. What is the difference between hexadecimal and binary?

Binary uses base 2 and represents values with 0 and 1. Hexadecimal uses base 16 and represents each digit with 0–9 and A–F. One hexadecimal digit represents four binary bits, so hex is more compact for reading byte values.

8. Is the SHA-256 hash a malware detector?

No. A hash is a digest of data. It can help identify a particular byte sequence or compare files, but it does not independently determine whether the file is malicious.

Related Binary Tools

Continue exploring binary representations, character codes and number-system conversions with these tools.