An open-source Android application for rebuilding split APK packages into a single, signed, installable APK directly on your device.
Mergify supports APKS, XAPK, and APKM packages, automatically detects available split APK components, and provides flexible controls for device configuration, split selection, APK signing, output customization, and installation.
Whether you want to automatically configure your APK based on your device or manually select the exact splits you want to include, Mergify gives you full control over the APK reconstruction process.
- 📦 Source Code: GitHub Repository
- 📥 Download: GitHub Releases
Mergify's main functionality is organized into four major feature areas:
- 🎯 Auto Detect — Automatically configure APK splits based on your device
- 📲 Auto Install — Install the generated APK and optionally remove the existing application
- ✍️ Signing — Sign generated APKs with configurable signing schemes and keystores
- ⚙️ Processing — Configure APK processing, output, compression, filenames, and logs
Mergify provides flexible ways to determine which APK splits should be included in the final output.
When enabled, Mergify automatically detects the device configuration, including:
- ABI
- DPI
- Language
The detected configuration is then used to determine the appropriate APK splits for the generated output.
This allows the resulting APK to be tailored to the target device without requiring manual split selection.
Auto Config provides more granular control over split configuration.
ABI, DPI, and Language can each be configured independently using options such as:
- From Device — Automatically use the detected device configuration
- Disabled — Disable the corresponding split type
- Custom — Manually specify the desired configuration
This allows users to combine automatic device detection with manual configuration when needed.
When Auto Config is disabled, Mergify provides a Split Picker before the merge process begins.
Users can manually select which available APK splits should be included in the final output.
This provides complete control over the components included in the generated APK.
Mergify is designed to rebuild split APK packages into standalone APK files.
- Automatic split APK detection
- ABI split filtering
- DPI split filtering
- Language split filtering
- Standalone APK generation
- Optional native library extraction
- Configurable compression level
Choose how you want to provide the APK package:
- 📁 Import packages using direct file paths
- 📱 Extract APKs directly from installed applications
- 📂 Import packages through Android Storage Access Framework (SAF)
Mergify can discover visible installed applications through Android's package visibility system. The application filters the available packages to identify non-system applications containing split APK components, allowing users to select an installed application and extract its base APK and split APKs for further processing.
Mergify can automatically initiate the installation process after the APK has been successfully merged.
When enabled, Mergify requests the Android Package Installer immediately after the merge process completes.
The final installation decision remains under the control of the user and Android's package installation system. Mergify only requests the installation through the appropriate Android permission.
Mergify does not silently install applications.
Mergify can optionally request the removal of the existing installed application before installing the newly generated APK.
This can be useful when the generated APK has a different signing certificate from the original installed application.
The feature uses Android's package deletion request mechanism and still requires confirmation through the Android system where applicable.
When enabled, Mergify automatically deletes the generated APK file from storage after the installation process.
This option is only available when Auto Install is enabled.
The Auto Install feature requires permission to install applications from unknown sources.
For APKs that are not signed, standard Android installation requirements still apply. Devices using modified environments or signature verification patches may behave differently from standard Android devices.
Mergify includes built-in APK signing configuration with support for multiple signing schemes and keystore management.
Signing can be enabled or disabled depending on the user's requirements.
When signing is enabled, users can select the signing schemes to use:
- V1
- V2
- V3
- V4
Mergify allows users to manage signing keystores directly from the application.
Supported operations include:
- Generate a new keystore
- Import an existing keystore
- Select a previously imported or generated keystore
- Use the selected keystore to sign generated APKs
Currently supported keystore format:
- PKCS#12 (
.p12)
Unsigned APKs generally cannot be installed through the standard Android installation process.
On modified or rooted Android environments with signature verification changes, installation behavior may differ from standard Android devices.
Mergify itself does not include or require any signature verification bypass mechanism.
Mergify provides additional configuration options for controlling the APK reconstruction and output process.
Users can enable or disable native library extraction during APK processing.
This option exposes the corresponding APKEditor processing configuration directly to the user.
Users can configure where generated APK files are stored.
The default output directory is the device's Download folder.
Generated APK filenames can be customized using:
- File Name Prefix
- File Name Suffix
- Append Timestamp
- Append Version Name
These options allow users to create more descriptive output filenames and avoid filename conflicts when generating multiple APKs.
Users can configure the compression level used during APK output processing.
Mergify provides configurable logging levels:
- Default
- Simple
The selected log level controls the amount and style of processing information displayed during APK reconstruction.
Mergify provides a modern Android interface with customizable appearance options.
Mergify supports Material You and Dynamic Color on supported Android versions, allowing the application's interface to adapt to the device's system color palette.
A dark appearance is available for users who prefer a darker interface.
Mergify also provides a Pure Black theme for a completely black interface.
Mergify supports multiple languages and allows users to either follow the system language or select a language manually.
Available languages:
- System
- English
- العربية
- Deutsch
- Español
- Français
- हिन्दी
- Indonesia
- Italiano
- 日本語
- 한국어
- Bahasa Melayu
- Português
- Русский
- Türkçe
- Tiếng Việt
- 中文
| Format | Support |
|---|---|
| APKS | ✅ |
| XAPK | ✅ |
| APKM | ✅ |
Mergify is focused on processing split APK packages and reconstructing their components into a standalone APK.
A typical Mergify workflow looks like this:
- Select an APKS, XAPK, or APKM package, or extract APKs from an installed application.
- Mergify analyzes the available APK split components.
- Configure the desired device and split behavior using Auto Detect, Auto Config, or the * Split Picker*.
- Compatible ABI, DPI, and language splits are selected according to the configured options.
- Configure processing and output options if required.
- Optionally configure APK signing and select a keystore.
- Mergify reconstructs the selected APK components into a standalone APK.
- The generated APK is signed if signing is enabled.
- The final APK is saved to the configured output directory.
- If Auto Install is enabled, Mergify requests Android's package installer to install the generated APK.
- If configured, the existing application can be requested for removal before installation.
- If Delete Output APK is enabled, the generated APK file is removed after the installation process.
|
|
|
|
|
|
|
|
Click any screenshot to view the full-size image.
Used to read APK split packages and supported files from external storage on supported Android versions.
Legacy storage permission used for writing generated APK files on Android 9 (API 28) and below.
Provides broad file-system access for direct file imports and APK output generation without relying exclusively on Android's document picker.
Required to request APK installation through Android's package installer.
Mergify does not silently install applications. The final installation process is handled by Android's package installation system and may require user confirmation.
Used to request removal of an existing installed application when the Remove Existing App option is enabled.
Android may still require user confirmation before the application is removed.
Mergify uses Android's package visibility mechanism to discover visible installed applications that expose a launcher activity.
The application filters the available packages to identify non-system applications containing split APK components, allowing users to select an installed application and extract its base APK and split APKs for further processing.
Mergify does not require the broad QUERY_ALL_PACKAGES permission for this functionality.
- Android 10 (API 29) or higher
- A device capable of installing APK packages
- Permission to install applications from unknown sources when using the Auto Install feature
Mergify is built using and incorporates the following open-source projects and libraries.
Used for APK processing, package reconstruction, and split APK merging.
Repository: https://github.com/REAndroid/APKEditor
License: Apache License 2.0
Part of the APKEditor ecosystem and included through the APKEditor integration.
Repository: https://github.com/REAndroid/ARSCLib
License: Apache License 2.0
Used for APK signing and signature generation.
Repository: https://android.googlesource.com/platform/tools/apksig/
License: Apache License 2.0
Used for Android application compatibility and UI framework support.
Repository: https://github.com/androidx/androidx/tree/androidx-main/appcompat
License: Apache License 2.0
Used for Material Design UI components and application interface elements.
Repository: https://github.com/material-components/material-components-android
License: Apache License 2.0
Some icons used in the Mergify user interface are sourced from Google Material Symbols.
Website: https://fonts.google.com/icons
License: Apache License 2.0
Used for cryptographic functionality.
Repository: https://github.com/bcgit/bc-java
License: MIT License
All third-party libraries and projects remain the property of their respective authors and contributors. Their use in Mergify is subject to the terms and conditions of their respective licenses.
Testing-only dependencies, including JUnit and Espresso, are not listed above as they are used exclusively for application testing and are not part of the application's runtime functionality.
When an APK is rebuilt and signed with a different signing key from the original application, Android treats it as a different signing identity.
As a result, an existing installation of the original application may need to be removed before the newly generated APK can be installed.
Mergify provides the Remove Existing App option to assist with this workflow through Android's package deletion request system.
Unsigned APKs generally cannot be installed through the standard Android installation process.
On modified or rooted Android environments with signature verification changes, installation behavior may differ from standard Android devices.
Mergify itself does not include or require any signature verification bypass mechanism.
Mergify is intended for educational, research, interoperability, and APK package management purposes.
Users are responsible for complying with software licenses, distribution terms, copyright requirements, and applicable laws when processing APK packages.
Mergify does not distribute third-party APKs and does not bypass Android security mechanisms.
Users are responsible for ensuring that they have the necessary rights and permissions to process any APK packages used with the application.
Mergify is licensed under the Apache License, Version 2.0.
See the LICENSE file for the full license text.