Developer Tools
View a Hex Dump
Transform pasted text with the hex dump viewer and copy the cleaned output.
Direct Answer
Use the Hex Dump Viewer when you need to inspect the raw bytes of a file or string, such as checking a file signature, debugging a binary format, or finding embedded text inside a binary.
Reading a Hex Dump Layout
A hex dump organizes raw bytes into three aligned columns so you can cross-reference a byte's position, its hexadecimal value, and its printable character all at once.
- The offset column (usually shown in hex) marks how many bytes into the file or string each row starts.
- The hex column shows each byte's value as two hexadecimal digits, commonly 16 bytes per row.
- The ASCII sidebar shows the same bytes as printable characters where possible, letting you spot readable text at a glance.
- Non-printable bytes appear as a dot (or similar placeholder) in the ASCII column since they have no visible character representation.
What a Hex Dump Is Useful For
Looking at raw bytes rather than a rendered or parsed view is the fastest way to answer certain debugging questions that higher-level tools can't easily answer.
- Checking the magic number (the first few bytes) to identify a file's true type regardless of its extension.
- Diagnosing a corrupted or truncated file by comparing its header bytes against a known-good example.
- Finding embedded, human-readable strings inside an otherwise binary file, like a version string or URL baked into a compiled binary.
- Verifying whether a text file has a byte order mark (BOM) or unexpected line-ending bytes that aren't visible in a normal text editor.
How to Use HEX Dump Viewer
- Paste or type your content into the input box.
- The transformed result appears instantly in the result panel below.
- Click Copy result to copy the output to your clipboard.
- Download .txt saves the transformed text as a file.
- Reset clears everything and lets you start over.
Reference
| Feature | Details |
|---|---|
| Purpose | Transform pasted text into a cleaner or different format. |
| Input | Text, lines, lists, or copied content. |
| Result | Transformed text ready to copy or download. |
| Best for | Cleanup, formatting, list preparation, and copy-paste workflows. |
| Category | Developer Tools |
| Works on | Desktop, tablet, and mobile browsers |
Common Ways People Search for This
People do not always know the exact tool name. These are plain-language searches this page is designed to answer:
- how do i hex dump viewer
- help me hex dump viewer
- easy way to hex dump viewer
- simple way to hex dump viewer
- website that can hex dump viewer
- app that can hex dump viewer
- tool that can hex dump viewer
- free website to hex dump viewer
A Focused HEX Dump Viewer Alternative
People looking for alternatives to JSONLint, Code Beautify, FreeFormatter, Browserling often want a simpler workflow. This hex dump viewer focuses on the task first: clear inputs, a visible result, useful related tools, free access, and no account requirement.
- Puts the tool input and result near the top of the page
- Free to use with no account or payment step
- Includes focused explanations and related tools
- Designed to avoid misleading download buttons and forced interstitials
Useful Related Tools
Frequently Asked Questions
What do the three columns in a hex dump mean?
The offset column shows the byte position within the file, usually in hexadecimal. The hex column shows each byte's actual value as two hex digits. The ASCII column shows the same bytes rendered as printable characters, letting you read any embedded text alongside its raw value.
Why do non-printable bytes show as a dot in the ASCII column?
Bytes below 32 (control characters) and many bytes above 126 don't correspond to a standard printable glyph, so a dot or similar placeholder is substituted to keep the column aligned. This makes it easy to visually distinguish stretches of binary data from stretches of readable text.
How do I identify a file's real type from its first bytes?
Many file formats start with a fixed sequence of bytes called a magic number or file signature, which stays the same regardless of the file's extension. Comparing the first several bytes shown in the hex dump against known signatures reveals the file's true format, even if it's been renamed.
What are the magic numbers for common file types like PNG, JPEG, PDF, and ZIP?
A PNG file starts with the bytes 89 50 4E 47 (which spell "PNG" partway through). A JPEG typically starts with FF D8 FF. A PDF starts with the ASCII text "%PDF" (25 50 44 46). A ZIP archive (which many other formats like .docx and .apk are built on) starts with PK, or 50 4B.
Why would a file extension say .jpg but the hex dump shows it isn't really a JPEG?
A file's extension is just a naming convention and can be changed without altering the actual file content, whether by mistake, a broken download, or intentional disguise. The hex dump's magic number reveals what the file actually is, independent of what its name claims.
How can a hex dump help diagnose a corrupted file?
Comparing the header bytes of a suspect file against a known-good file of the same format can reveal a missing or altered magic number, a truncated file that ends abruptly mid-structure, or unexpected bytes inserted where a fixed header is expected. This is often faster than trying to open the file in its native application and guessing at the error.
What does it mean to find 'embedded strings' in a binary using a hex dump?
Compiled programs, firmware images, and other binary files often contain runs of plain ASCII text, such as error messages, version numbers, or URLs, sitting alongside otherwise unreadable machine code. The ASCII sidebar in a hex dump surfaces these readable runs directly, which is a common first step in reverse engineering or debugging an unfamiliar binary.
Why are hex dump offsets usually shown in hexadecimal instead of decimal?
Hexadecimal aligns naturally with byte boundaries and common row widths like 16 bytes per line, since 16 is a clean power of two in hex (0x10). It's simply the convention most hex editors and dump tools follow, though the same offset could be shown in decimal without changing what it represents.
What's the difference between viewing a file as hex and viewing it as text?
A text view interprets every byte through a specific character encoding and can misrepresent, garble, or silently drop bytes that don't form valid characters in that encoding. A hex view shows the raw byte values with no interpretation, which is essential for binary files or when you suspect the encoding assumption itself might be wrong.
Why are hex dumps typically shown with 16 bytes per row?
16 bytes per row is a long-standing convention because it divides evenly and lines up cleanly with hexadecimal offsets, though some tools use 8 or 32 bytes per row instead. The row width doesn't change the data, only how it's visually chunked for readability.
Can a hex dump show Unicode or multi-byte text correctly?
The hex column always shows the true underlying bytes regardless of encoding, but the ASCII sidebar typically only renders single-byte printable ASCII characters correctly. Multi-byte UTF-8 sequences for non-ASCII characters will usually appear as several separate dots or placeholders in the ASCII column rather than the actual character.
Why might two 'identical looking' text files have different hex dumps?
Files that look the same in a text editor can differ at the byte level due to line-ending conventions (CRLF on Windows versus LF on Unix), an invisible byte order mark at the start of the file, or trailing whitespace that isn't visually obvious. A hex dump exposes these differences immediately, which a plain text diff can sometimes miss or misreport.
What is a byte order mark (BOM) and how does it appear in a hex dump?
A BOM is a special sequence of bytes some encodings place at the very start of a file to indicate byte order and encoding, such as EF BB BF for UTF-8. It's invisible in most text editors but shows up clearly as the first bytes in a hex dump, which is often the first clue when a file behaves unexpectedly in a parser that doesn't expect a BOM.