rom-weaver

Overview

rom-weaver is a free toolkit for patching and converting ROMs and disc images, with browser and command-line versions sharing an engine. It is a strong fit for people who need repeatable patch workflows or local file handling across several formats. Its breadth is useful, but support varies by format and task.

Key features

Patching and reusable workflows

rom-weaver applies patches, creates them from ROMs, and packages ordered patch sequences into reusable bundles. Its supported formats include IPS, IPS32, SOLID, BPS, UPS, VCDIFF, xdelta, GDIFF, PPF, and many others. Batch patching, checksum verification, and original-file backups make it more suitable than a single-purpose patcher for repeat or multi-file jobs: bundles preserve a sequence, while verification and backups help manage input and output integrity. Some formats have operation-specific limits, so a required format should be checked before building a workflow around it.

Conversion, cheats, and saves

The tool can probe and extract numerous archive and compressed image formats, including ZIP, 7z, RAR, CHD, RVZ, and Z3DS. Creation support varies, so it is useful for identifying and unpacking varied files but should not be treated as a universal two-way converter.

Supported cheat codes can be baked into ROMs, and selected database cheats can be saved as patch files. Runtime-memory cheats are unsupported, making rom-weaver a poor fit for live cheat use. Its Save Editor supports specified Pokémon save layouts and The Legend of Zelda: A Link to the Past SRAM, with game-recognition limits; users should confirm their game is covered before relying on it.

Local processing and hosting

The browser app processes files on-device with WebAssembly, while the CLI reads and writes local paths. The maker says ROMs, patches, and results are not uploaded to its server; the web app also has no analytics, advertising, tracking scripts, or tracking cookies, though it stores app data in browser storage. Offline browser use works after the app has been cached. These are meaningful advantages for privacy-conscious workflows, but remote files used in preloaded browser workflows must allow the app origin through CORS.

Hosts can preload browser workflows with bundle, ROM, and patch URLs or ingest files from same-origin OPFS storage. The web app can be self-hosted from a Docker image or static files and requires HTTPS except on localhost. This flexibility will matter to developers integrating patch steps into a host page, but is unnecessary overhead for someone who only needs an occasional patch.

Pricing

Free and open-source

The single plan costs nothing, requires no account, and includes browser and command-line versions. There is no free trial because the plan is free. The GNU AGPL v3.0 or later license makes the source available under open-source terms, while the maker directs bugs, format requests, and questions to GitHub issues and handles security reports separately. There are no paid tiers or plan quotas described, so users do not have a paid upgrade path for additional capacity or support.

Platforms

The browser version runs on the web, and the CLI has release binaries for macOS, Linux, and Windows, with architecture variants. The app can also be self-hosted. This gives technically comfortable users options across desktop systems without requiring a hosted file-processing service; the static web app requires HTTPS outside localhost.

Who it's for

rom-weaver is best for ROM patchers who need more than applying a single patch: batch jobs, patch creation, ordered reusable bundles, format conversion, or a CLI can all justify its broader toolkit. It also suits people who want files processed locally or need to self-host the web app. It is less compelling for users whose only requirement is a narrow, game-specific patcher, live cheats, or a save layout whose game recognition is not supported.

Pros and cons

Pros: Browser and CLI share an engine, giving repeatable workflows a choice of interface.

Pros: Batch patching, checksums, backups, and reusable bundles address practical risks in multi-step or repeated patch jobs.

Pros: On-device browser processing, local CLI paths, offline use after caching, and self-hosting provide several ways to keep workflows local.

Cons: Conversion creation support varies by format, so extraction does not guarantee the reverse operation.

Cons: Cheat and save tools have clear scope limits: no runtime-memory cheats and only specified save layouts with recognition constraints.

Cons: Remote browser workflow sources depend on CORS permission from the source host.

Alternatives

ROM Patching Software is the broader category directory for comparing patching tools. For a free browser-based tool without stated account or installation requirements, consider EZ ROM Patcher. Choose IUBPatchLib if you want MIT-licensed software for Linux, macOS, or Windows. Patcher64+ Tool is the more targeted choice for N64, NES, and SNES, provided you have 64-bit Windows 7 or newer and PowerShell 5.1 or later.

Mac users seeking a tool for macOS 10.9 or newer can consider MultiPatch. For IPS and BPS patching on Linux, macOS, or Windows, Floating IPS (Flips) is a narrower option; its community Flathub package is not verified, affiliated with, or supported by Alcaro. Gaming Optimizer is another free Windows option. Pokémon-focused users can consider Pokémon ROM Patcher, a fan-run index of Pokémon ROM hacks. Delta Patcher is a free alternative for Linux, macOS, and Windows.

Verdict

Choose rom-weaver if you want a free, local-first toolkit that can handle patch creation, application, reusable sequences, and varied file formats from either a browser or CLI. Its combination of workflow safeguards and hosting options is its strongest reason to choose it. Look elsewhere if you need a specifically supported save layout, runtime cheats, or dependable creation support for a particular conversion format.