About the project
A focused patching tool for Android
UniPatcher brings a desktop-style ROM patching workflow to phones and tablets while keeping the project open for inspection and contribution.
Why UniPatcher exists
Fan-made patches can translate a game, correct bugs, rebalance play or create an entirely new experience without redistributing the original copyrighted game. A patch stores the changes between files; the user applies those changes to a compatible ROM they provide themselves.
Many established patching tools began on desktop operating systems. UniPatcher gives Android users a practical local workflow: select a patch, select the correct ROM, choose an output and apply. The work stays centered on files rather than accounts or cloud processing.
Project scope
The app applies ten documented patch formats and includes a small set of ROM-specific utilities. Its boundaries are intentional: patch creation is available for XDelta3, checksum repair is for Sega Mega Drive and Genesis files, and the SMC utility removes a Super Nintendo header rather than adding one.
UniPatcher targets ROM files for older console systems. It is not a tool for editing installed Android applications, patching native Android games or bypassing software protections.
Project facts
- Current version
- 0.17.3
- Platform
- Android
- Minimum system
- Android 5.0 or newer
- License
- GNU GPLv3
Open-source development
UniPatcher's source code is published on GitHub under the GNU General Public License version 3. The repository provides an auditable project history, issue tracking and a place for technical contributions. The license covers the application code; it does not grant rights to third-party games, patches, trademarks or artwork.
How to support the project responsibly
Start with the FAQ when a file fails, because region, revision, checksum and header mismatches are common causes. If the problem appears to be in the app, search existing GitHub issues before opening a new one. A useful report names the patch format, Android version, UniPatcher version and exact error, without uploading copyrighted ROM data.
Clear documentation helps as much as code. Reproducible examples, precise terminology and confirmation that a problem still occurs on the current release reduce duplicate reports. Translations and interface improvements should preserve the same practical goal: make each file choice and consequence understandable before the user applies an irreversible change.