Hex Analyzer & Patcher Pro

1) Installation & running

Windows

1. Download the installer or EXE package.
2. Run the application.
3. If Windows SmartScreen appears, select More info → Run anyway (only if you trust the source).

macOS / Linux

If you provide a packaged build for macOS or Linux, the steps are the same: download → run.

2) Understanding the interface

3) Quick start (recommended workflow)

4) Core workflows (deep guide)

Workflow A — Compare Original vs Modified

1. Load Original and Modified.
2. Click Compare.
3. Review:
   • Diff count: total number of changed offsets.
   • Conflict count: if Target is loaded, offsets that don’t match expected Original.

Workflow B — Review conflicts

If conflicts exist, the tool assumes SKIP per conflict (safe). You can approve them one by one.

Workflow C — Apply patch to Target

1. Load Target.
2. Click Apply Patch → Target.
3. Choose output file name with Save As.
4. Read the result summary: applied, skipped, conflicts applied, conflicts skipped.

Workflow D — Export a patch (shareable file)

Exporting a patch lets you share changes without sending full binary files (when allowed).

1. After compare, click Export Patch.
2. Choose:
   • JSON (recommended): includes metadata + machine readable.
   • CSV: easy to inspect in Excel.

Workflow E — Import a patch (no Modified file required)

1. Click Import Patch and select a patch JSON file.
2. Load a Target (optional but recommended).
3. Review conflicts and apply.

5) Hex viewer & 3-way viewer

Hex Viewer (single view)

The Hex Viewer shows bytes with highlighting for changed bytes and conflicts.

3-Way Viewer (side-by-side)

This view shows Original, Modified, and Target side-by-side at the same offsets. It is the fastest way to understand why conflicts happen.

6) Search (Hex / Text)

Search in different buffers

Use the In: dropdown to choose where to search:

• original — searches the Original file
• modified — searches the Modified file
• target — searches the Target file
• view — searches the overlay view when safe (may be limited for very large files)

Hex search

Hex search supports two input styles:

• Spaced bytes like DE AD BE EF
• Continuous hex like DEADBEEF

Wildcards are supported using ?? to match any byte:

AA ?? FF
10 20 ?? ?? 33

Text search

Text search uses UTF-8 best-effort. You can enable case-insensitive for text searches.

Search results navigation

• Click Find All to list matches
• Use Prev / Next to jump through matches
• Matches are highlighted in the viewer

7) Patch export/import (formats)

JSON patch (recommended)

The JSON patch is designed for automation and verification.

{
  "format": "mkpatch/v1",
  "created_unix": 1730000000,
  "meta": {
    "original_path": "...",
    "modified_path": "...",
    "original_size": "1048576",
    "modified_size": "1048576",
    "original_sha256": "...",
    "modified_sha256": "..."
  },
  "diffs": [
    { "offset": 4096, "original": 171, "modified": 172 },
    { "offset": 4097, "original": 1, "modified": 0 }
  ]
}

CSV patch

CSV is great for human inspection in spreadsheet tools:

offset_hex,offset_dec,original_hex,modified_hex,original_dec,modified_dec
0x1000,4096,AB,AC,171,172

8) Batch apply (folder mode)

Batch mode is designed for applying the same patch to many target files quickly.

1. Compare or import a patch (so diffs exist).
2. Click Batch Apply (Folder).
3. Select the input folder containing target files.
4. Select an output folder.
5. Choose whether to override conflicts in batch mode.

9) Strings, metadata, and hashes

Strings extraction

Use this to quickly discover readable labels embedded in the file (ASCII strings).

• Select the source: Original, Modified, or Target
• Choose minimum length (e.g., 4–8)
• Click Extract

Hashes

Hashes help you verify file identity and integrity:

• CRC32 — quick check
• MD5 — legacy hash used in many workflows
• SHA256 — strong modern hash for verification

Metadata / patterns

The app attempts to extract common identifiers (best-effort). This is a convenience feature to help you spot mismatches early.

10) Safety & best practices

Recommended safety checklist

1. Backup Original and Target files before making changes.
2. Compare file sizes and (if applicable) key identifiers.
3. Review conflicts. Default SKIP is safer than force applying.
4. Apply patch into a new output file (Save As).
5. Verify output using hashes and, where relevant, known validation tools.

Understanding conflicts

Conflicts usually mean one of the following:

• Target is from a different variant/version.
• Target has already been modified.
• Patch is not compatible across regions/hardware revisions.
• You are applying changes to the wrong base file.

11) Troubleshooting & FAQ

The app is slow or freezes on big files

Large binaries can take time to scan. The app uses chunked compare and can cancel. If you still see slowness, close other apps and try again.

I get many conflicts — is that normal?

Many conflicts usually mean the patch does not match the target’s base. This is a signal to stop and verify: correct target, correct original base, correct version/variant.

Why can’t I import CSV patches?

CSV export is designed for inspection. JSON import is supported because it preserves structure, types, and metadata.

My output file doesn’t work

Common causes:

• Applied patch to the wrong target version.
• Forced conflicts incorrectly (“Override all”).
• Binary requires recalculating checksums after changes.

FAQ

12) Screenshots (click to enlarge)

Place your images in a folder named pic next to this HTML file with names: 20.webp, 21.webp, 22.webp, 23.webp, 24.webp, 25.webp.

2-Day Free Trial & Pricing

Try Hex Analyzer & Patcher Pro free for 2 days with full access to all professional features. After the trial, purchase a lifetime license for $60 with premium support and updates included.

13) Contact us