Hexable

What Hexable Actually Does

Hexable is a hexadecimal editor and viewer. It lets you open binary files and see their raw contents displayed as hex values alongside an ASCII representation. You can edit byte values directly, search for patterns, insert or delete bytes, and convert between hex and other number formats. It is aimed at developers, reverse engineers, and anyone who needs to poke at binary data without writing a custom tool every time. Most people reach for it when they are debugging a file format issue, inspecting a compiled binary, or trying to understand what a weird byte sequence means. The interface is utilitarian. It opens a file, shows hex on the left, ASCII on the right, and lets you click any byte to change it. That is basically it.

Installing and Getting Started

You can download Hexable from the official site. At the time of writing, the current release supports Windows and offers a portable version if you do not want to install anything system-wide. The installer is small, roughly 30 megabytes. Run the setup, choose your installation path, and launch it. No account required, no telemetry toggle to hunt for. It just runs. Once open, go to File and select Open. Navigate to your target file. The main window splits into two sections. The left side shows the hex dump in groups of two-character hex bytes. The right side shows the corresponding ASCII characters. Non-printable bytes appear as periods. Memory addresses run down the left margin so you know exactly where each byte sits in the file. Click any byte to select it. Type a new two-character hex value and press Enter. The change applies immediately. Save with Ctrl+S if you want to write it back to disk. If you are only inspecting, leave the file open without saving. It does not auto-save. That is by design.

Basic Navigation and Search

Use the scroll wheel to move through large files quickly. The status bar at the bottom shows the current offset, the total file size, and the selection range if you highlight bytes. There is a Find dialog accessible from the Edit menu. You can search by hex string, ASCII text, or regular expressions. The hex string search is the most reliable when dealing with binary data. Regular expression searches work on the ASCII column only and sometimes miss non-printable sequences, which is a known limitation I have hit more than once. One thing beginners miss: Hexable supports multi-cursor editing if you hold Ctrl and click multiple bytes. This is useful when you need to patch the same value at several offsets without searching repeatedly. It does not support column-edit mode like some heavier editors. Do not expect Notepad++ style column selection here.

Practical Workflow for Binary Inspection

Here is how I actually use it day to day. Open a suspicious executable. Look at the first few bytes to confirm the file type. An ELF file starts with 7f 45 4c 46. A ZIP file starts with 50 4b 03 04. If those signatures do not match, something is wrong with the file or it has been renamed to hide its true format. Then I use the Find function to locate strings of interest. Passwords, URLs, error messages, API keys. Hexable can extract all printable strings automatically from the Strings menu. I export those to a text file and scan them manually. This usually cuts my initial triage time from twenty minutes down to about three, depending on file size. For larger files, the Find All function can locate every occurrence of a byte pattern. This is slower on multi-megabyte files. Expect a five to ten second delay on a 50 megabyte file when searching for a four-byte pattern. The application remains responsive during the search, which matters more than raw speed in my experience.

Common Pitfalls and Things I Have Learned the Hard Way

I once tried to patch a DLL by changing a single byte that controlled a version check. The file opened fine, the edit applied, and I saved without issues. When I ran the patched program, it crashed immediately. The problem was that the DLL had embedded checksums. Changing one byte invalidated the checksum, and the loader refused to execute it. Hexable does not recalculate checksums for you. It never will. If you are modifying files that contain integrity checks, you need to find and patch the checksum logic separately or bypass the check entirely. This is not a Hexable problem. It is a universal problem with binary patching. Another edge case: Hexable handles files larger than 4 gigabytes, but the selection and copy functions break above that threshold. If you select across the 4 GB boundary, the application returns garbled data. The workaround is to split the file into smaller chunks using a command-line tool or Python script first, then edit each chunk separately. I keep a small Python script for this exact purpose. It uses os.open and binary reads in 100 megabyte blocks. A third thing to watch: Hexable uses UTF-8 for its own interface strings. If you open a file that contains malformed UTF-8 sequences in the ASCII column, the display will show replacement characters instead of the raw bytes. The hex column remains accurate regardless. So always trust the hex column over the ASCII column when dealing with suspicious or corrupted binary data. The ASCII display is for your convenience, not your accuracy.

Advanced Features Worth Knowing

The Compare function under the View menu lets you open two files side by side and highlights differences in color. This is surprisingly effective for checking whether two builds of the same program differ at the byte level. It works reliably up to about 200 megabytes per file. Beyond that, the comparison becomes slow and the UI may freeze for thirty seconds or more on modest hardware. There is a built-in converter for number systems. Select any byte or group of bytes and choose Convert from the Edit menu. You can switch between hex, decimal, signed decimal, octal, and binary. This saves you from opening a calculator or writing a script every time you need a quick conversion. It handles single bytes and multi-byte values. For multi-byte values, it respects endianness based on your settings, which you can adjust in the Preferences dialog. Hexable also supports macros. You record a sequence of actions and replay them later. This is useful when you perform the same edit pattern repeatedly, such as stripping headers from a batch of files or replacing a magic number across multiple binaries. The macro recorder captures everything, including menu navigation. Playback is straightforward. I use this feature when processing firmware images in bulk, and it cuts my workflow from an hour to about ten minutes for a typical batch of fifty files.

Export and Import Options

You can export selections as raw hex, as C-style byte arrays, or as JSON. The C-style export is the most commonly used. It wraps the bytes in braces with commas, ready to paste into source code. The JSON export is less useful than it sounds because it escapes non-printable characters inconsistently. Use the raw hex export if you need clean output for scripting. Import works in the opposite direction. Paste a hex string and Hexable converts it into bytes. This is helpful when you extract a hex dump from documentation or a forum post and want to reconstruct the original bytes. The import dialog accepts spaces, colons, and no separators between byte pairs. It is forgiving enough that manual typos rarely break the conversion unless you type an invalid hex character.

Limitations and When to Use Something Else

Hexable is not a debugger. It cannot step through code, set breakpoints, or show register state. If you need to understand how a program executes, use a proper disassembler or debugger. Hexable is strictly for viewing and editing raw bytes. It also lacks real-time file watching. If you have Hexable open on a file and an external process modifies that file, Hexable will not detect the change. You have to manually refresh. I have lost edits twice because another tool wrote over the file I was looking at. Always close Hexable on a file before running external processes against it. For very large files above 2 gigabytes, consider a specialized hex editor like HxD or wxHexEditor. Hexable handles them, but performance degrades noticeably. The UI stutters during scrolling and search operations. If your workflow involves multi-gigabyte disk images regularly, the specialized tools are more stable. Hexable is fine for files up to about 1 gigabyte in my experience.

Final Notes

Hexable is a solid choice for routine hex editing tasks. It is free, lightweight, and does not clutter your system with unnecessary features. The learning curve is flat. You can be productive within five minutes of opening the application. The main things to remember are to trust the hex column over the ASCII column, to be aware of checksums when patching binaries, and to split oversized files before editing if you hit the 4 GB selection bug. I have been using it for about two years across countless firmware images, game mods, and reverse engineering projects. It has not failed me, but it also does not solve every problem. Know its boundaries. Use it for what it is good at. Move to other tools when the task grows beyond simple byte-level inspection and editing. You can download it from the Hexable website. The portable version is recommended if you want to keep things clean. The installer version adds a context menu entry in Windows Explorer, which is convenient but not essential.