PixelOkay
Tools
PIXELOKAY DEVELOPER LAB / BINARY INSPECTION

Hex Editor Studio

Explore every byte, understand file structure, patch values precisely, and compare binaries—all privately in your browser.

⌘ Hex + ASCII◈ Non-destructive editing⇄ Binary diff↧ Local export
Binary workspaceReady · sample data loaded
Example · unsaved
Document size—
Selected offset—
Selected range—
Modifications—
Hexadecimal inspector

16 bytes per row · click to select

Sample documentNo selection
↑↓←→ NavigateShift Extend range0-F Edit byteDel Remove range

Binary comparison

NO SECOND FILE

Open another binary file to compare it with your current edited document. Differences are compared byte-for-byte; unequal lengths are reported separately.

Ready

Binary editing, without installation

01 / OPEN

Inspect raw data

Open arbitrary binary formats and browse their hexadecimal bytes and ASCII representations, using paged rendering even on large documents.

02 / PATCH

Edit with confidence

Overwrite, insert and delete byte sequences. Search across byte boundaries, replace multiple matches and undo changes before exporting.

03 / COMPARE

Review every difference

Compare the current document against a second binary, jump to mismatched offsets, and export a CSV of sampled changed and trailing bytes.

Frequently asked questions

Will this change my original file?

No. All edits are held locally. Export creates a new binary download or uses the native save picker when supported and explicitly requested.

What is the largest file supported?

The studio accepts files up to 512 MiB and reads visible rows, searches and comparisons in chunks. Very large files and highly fragmented edits may be slower on low-memory devices.

Can I edit executable or unknown file types?

Yes. Bytes are treated as binary data; no executable content is run. Edits can corrupt format structures, signatures and checksums, so retain a copy of the original.

Are search and replace operations safe?

Search accepts exact hex bytes or UTF-8 text. Replacement supports different byte lengths. All replacements can be undone, and large replace-all operations have safety limits and confirmation.

Using Hex Editor Studio

Inspect and edit local binary files with a virtualized hex/ASCII view, exact search and replace, undo, comparison, and binary or range exports.

Workflow

  1. Open a copy of the file and inspect the byte range in both hexadecimal and ASCII views.
  2. Search for an exact byte pattern or make a small insert, overwrite, or delete; use undo and compare views to review the change.
  3. Export the full binary or selected range and keep the original file for recovery.

Worked example

On a disposable copy of a ZIP file, search for the byte signature 50 4B 03 04 and inspect the surrounding bytes. Do not change the signature unless you understand the file format; export a selected range only when a partial binary is what you need.

Limits and data handling

The 512 MiB input cap is not a performance guarantee. Search, replace, and displayed differences are capped; the difference CSV samples changes rather than listing every changed byte. Editing may invalidate a format checksum, signature, or internal offsets. A download is a new file request and does not overwrite the original file automatically.

Frequently asked questions

Will an edited file keep its original checksum or signature?

Not necessarily. Any byte change may invalidate format-specific checksums, signatures, or offsets; validate the edited file with the format-specific tool.

Does the difference CSV contain every changed byte?

No. The comparison view is capped and the CSV samples differences; export or compare the binary files with a format-aware workflow when a complete change record is required.

Related tools