100% Client-Side Privacy
Adawaty Pro • adawaty-pro.com
48+ Offline Client-Side Converters & Technical Guides
Home / Gaming & Modding / IPS / BPS Patcher
Read Technical Guides →

IPS / BPS Patcher

Apply real IPS or BPS binary ROM patches directly inside the browser — 100% private client-side processing.

100% Client-Side JS

Active Converter

Smart Auto-Fix:
1. Source File(s) or Paste Input: No file selected
2. Live Output (Editable):
Client-Side Binary Delta Patching (IPS & BPS1)

IPS / BPS ROM Patcher: Applying Fan Translations & Binary Delta Patches In-Browser

Technical Anatomy of .IPS and .BPS Binary Patch Formats

ROM hacking and fan-translation communities never distribute copyrighted game ROMs—instead, they ship tiny binary delta patches (.ips or .bps) that describe only the exact bytes modified relative to a clean original dump.

An IPS patch begins with the 5-byte magic header 50 41 54 43 48 (PATCH) and streams variable hunks: a 3-byte big-endian offset, a 2-byte big-endian size, and the raw replacement bytes. If size equals 0x0000, the hunk switches to RLE (Run-Length Encoding)—reading a 2-byte repeat count and 1 fill byte—until reaching the 3-byte EOF (45 4F 46) footer. Modern BPS patches begin with BPS1, encode variable-length integers (VLQs) for SourceRead/TargetRead/SourceCopy/TargetCopy delta commands, and finish with three 32-bit CRC-32 checksums.

Raw .IPS Binary Hunk Structure vs. Patched ROM Result

# Input: Binary .IPS Patch Hex Breakdown
50 41 54 43 48   -> "PATCH" Header (5 bytes)
00 00 10         -> Target Offset: 0x000010 (3-byte Big-Endian)
00 04            -> Length: 4 bytes
48 41 43 4B      -> Replacement Payload: "HACK"
45 4F 46         -> "EOF" Terminator (3 bytes)

# Result: Original ROM bytes at 0x000010..0x000013 overwritten cleanly in RAM!

Real-World Software & Hardware Ecosystem

Retro enthusiasts apply .ips and .bps patches sourced from ROMhacking.net, SMW Central, and PokeCommunity—traditionally handled by desktop utilities like Lunar IPS or Flips (Floating IPS)—for play on RetroArch, mGBA, bsnes, Analogue Pocket, and EverDrive flashcarts.

Troubleshooting & Edge Cases

  • The Famous 0x454F46 IPS Offset Bug: Because 45 4F 46 spells EOF, an IPS patch cannot start a hunk at exact byte offset 0x454F46 (4,542,278) without confusing naive parsers—one reason N64/GBA hacks over 4 MB prefer .bps.
  • IPS 16 MB Ceiling: Because IPS offsets are strictly 24-bit unsigned integers (0xFFFFFF), IPS cannot address bytes beyond 16,777,215 bytes (16 MB).
  • ROM Expansion: If an IPS hunk writes past the end of the original ROM buffer, our patcher dynamically allocates an expanded Uint8Array to fit the new ROM size automatically.

IPS vs. BPS Binary Patch Specification Matrix

Feature.IPS (Legacy).BPS (Beat Modern)
Header Magic50 41 54 43 48 ("PATCH")42 50 53 31 ("BPS1")
Max ROM Size16 MB (24-bit offset cap)Unlimited (VLQ integers)
Integrity CheckNone (silent mismatch risk)3× CRC-32 checksums (source/target/patch)

Verifying Clean No-Intro Base ROMs Before Patching

# Confirm your base ROM SHA-1 matches the patch README before applying:
sha1sum base_rom.sfc
# Check if SNES ROM has a 512-byte SMC copier header (size % 1024 == 512):
stat -c%s base_rom.sfc

Frequently Asked Questions

How does the binary .IPS (International Patching System) format modify a ROM file?

An .IPS file starts with the 5-byte ASCII header 'PATCH', followed by sequential hunks: a 3-byte big-endian target offset, a 2-byte big-endian payload length, and the raw replacement bytes (or a 0x0000 length signaling RLE run-length encoding), ending with the 3-byte 'EOF' marker (45 4F 46).

Why is .BPS (Beat Patching System) preferred over .IPS for modern ROM hacks?

IPS uses 3-byte offsets—capping patchable ROMs at 16 MB—and includes no checksum verification, so patching the wrong ROM version silently corrupts the game. BPS uses variable-length integers (supporting multi-gigabyte files), delta copy actions, and trailing CRC-32 checksums for source, target, and patch integrity.

Why did my patched SNES ROM crash with a black screen after applying an .IPS patch?

90% of SNES patch failures come from a 512-byte SMC copier header mismatch: the patch was authored for a headerless No-Intro ROM, but your ROM has a 512-byte header (or vice versa), shifting every single IPS offset by 0x200 bytes.

Does this patcher upload my copyrighted ROM file to a remote server?

Never. Both the base ROM/BIN and the .IPS or .BPS patch file are merged strictly inside your browser's local Uint8Array memory, then saved directly to your downloads folder.

Deep-Dive Technical Guides on Adawaty Pro