# APK Explorer & Editor: Inspect and Modify Android APK Files > APK Explorer & Editor (AEE) is an open-source Android application for inspecting installed applications and APK files, exporting contents, editing selected resources, assembling smali, and signing rebuilt packages. It suits users who need controlled package inspection or modification rather than ordinary app installation. **apk-editor/APK-Explorer-Editor** — Source code of APK Explorer & Editor (AEE), an open-source tool to explore the contents of an installed APK! - Repository: https://github.com/apk-editor/APK-Explorer-Editor - Website: https://apk-editor.github.io/ - Stars: 1,377 · Forks: 199 - Language: Java - License: GPL-3.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/apk-editor-apk-explorer-editor ## What AEE inspects and which Android workflows it supports APK Explorer & Editor, or AEE, is designed around inspecting Android package contents rather than managing applications as a normal user does through a launcher. The README identifies its main audience through one direct boundary: the application is made to explore the contents of an installed APK. A user can select an installed application, or choose an APK file from device storage, then navigate through the package contents. The supported tasks extend beyond a file browser. AEE can save individual resources such as icons, fonts, graphics, and binary XML files to device storage. It can export and manage APKs and split APKs, including installing and sharing those packages. The project also includes an installer for APKs, split APKs, and app bundles. That combination makes it relevant to Android package inspection, package export, and manual package distribution workflows. The editing scope is narrower than a general-purpose development environment. AEE includes a built-in text and XML editor, supports deleting or replacing resources, can assemble modified smali files into new `classes.dex` files, and can decode and inspect `resources.arsc`. The documentation also states that it can create signed APKs and app bundles after those operations. These features position AEE between a package viewer and a lightweight mobile APK modification tool. ## How AEE organizes package inspection and rebuilding The visible workflow starts with an installed application or a selected APK file. From that entry point, AEE exposes the package contents for navigation. The resource list includes ordinary application assets as well as Android-specific files, and the README specifically calls out icons, fonts, graphics, and binary XML. AEE can export an individual file, so the inspection workflow is not limited to viewing metadata. Editing is file-oriented. Its built-in editor is available for text and XML content, while resources can be deleted or replaced. For code-level package changes, modified smali files can be assembled into a new `classes.dex`. The README separately identifies `resources.arsc` decoding and viewing as a supported operation. These are distinct stages: inspect the package, change a selected file or resource, assemble any modified smali into a new DEX, and then create or sign the resulting package. AEE also handles package formats that are not equivalent to a single monolithic APK. Split APKs and app bundles have explicit support in the feature list, including export, installation, sharing, and package creation. The README does not explain the internal class structure, parser implementation, or signing pipeline, so those details cannot be inferred. The practical model that can be confirmed is a mobile, resource-oriented flow with explicit stages for extraction, editing, reassembly, signing, and installation. ## Installing AEE and completing a first package inspection The project provides distribution channels rather than a documented local build tutorial. The README links to Google Play, F-Droid, the IzzyOnDroid repository, and GitHub Releases. A new Android user should obtain AEE from one of those listed channels and install it through the device's normal application installation flow. The repository includes `gradlew`, `gradlew.bat`, `app/`, `build.gradle`, and `settings.gradle`, but the README does not give verified Gradle commands for building or installing the application from source, so no build command is reproduced here. For a first real use, open AEE after installation and begin with an installed application or an APK selected from device storage. The README documents both entry paths. Once the package opens, navigate through its contents rather than editing immediately. This provides a way to confirm that AEE can read the package and identify the resources relevant to the task. The next safe step is to select a resource that can be inspected without changing package structure, such as an icon, font, graphic, or XML file. Use the export or save function to place that item in device storage. AEE documents saving individual resource files, but it does not specify the destination directory or the exact on-screen labels. For changes to text or XML, open the built-in editor and review the result before assembling or signing a package. ## AEE package rebuilding limits and editing constraints The README includes a direct warning that the built-in text and XML editor can be buggy when working with very large APKs. This is the clearest documented failure mode. It means that package size can affect editing reliability, particularly when an editor has to work with a large file or a large amount of package content. The README does not describe a size threshold, retry behavior, or recovery procedure, so users should not assume that every large package can be edited safely. Package signing is another boundary. AEE can create signed APKs and app bundles and can resign packages with an AEE custom key. The README does not say whether it preserves an original application's signing identity, how key management works beyond that mention, or whether every installed app can be rebuilt and installed successfully. Changing package contents can also interact with signing relationships and split package layout, but those technical requirements are not explained in the project documentation. For that reason, AEE is not a transparent replacement for an Android build pipeline. Its documented editor is intended for direct package changes, while large-package behavior is explicitly imperfect. The project is better suited to controlled inspection, selective resource extraction, and carefully validated modifications than to bulk editing of very large APKs. ## Where AEE differs from installing from source or using a package viewer A package viewer can list and extract files from an APK, but that is only part of AEE's documented scope. AEE adds an in-app editor, resource replacement and deletion, `resources.arsc` decoding, smali assembly into `classes.dex`, package creation, signing, and installation support. Its distinction is therefore the path from inspection to a new or resigned package, not simply the ability to browse a ZIP-like archive. Compared with an Android Studio-based application development workflow, AEE is a Java application focused on inspecting and modifying existing packages. The README does not claim that AEE builds source projects, manages Gradle dependencies, or provides the same project model as Android Studio. Those capabilities should not be inferred from the presence of Gradle files in the repository. Compared with a basic archive utility, AEE understands more Android package concepts, including split APKs, app bundles, smali, DEX output, `resources.arsc`, and signed package creation. The tradeoff is that it exposes a more complex and failure-prone editing path. A viewer may be enough for extraction, while AEE becomes relevant when the user needs to edit resources or assemble a modified package on Android. ## AEE licensing, releases, and maintenance cost APK Explorer & Editor is released under the GNU General Public License, version 3 or later, according to the README. The license text says that the software may be redistributed and modified under those terms. It also includes the standard warranty disclaimer and directs users to the GNU General Public License for details. This is a license identification, not legal advice about a particular distribution or modification. The repository is not archived, and its last push was on 2026-10-07. Recent releases listed in the project documentation include v0.36 on 2026-09-06, v0.35 on 2026-07-06, and v0.34 on 2026-05-04. These release dates indicate recent project activity, but the README does not provide release notes, migration instructions, a compatibility policy, or an upgrade procedure. Upgrading therefore carries an unresolved verification cost for users whose APK editing depends on signing, split package handling, or DEX assembly. AEE is a mobile application distributed through several channels, including Google Play, F-Droid, IzzyOnDroid, and GitHub Releases. The README does not document a rollback process or version compatibility matrix. Users should verify the available release and the behavior of their specific package format before relying on it for production package modifications. ## Conclusion APK Explorer & Editor fits Android users who need to inspect or modify APK contents, while users who only need to install applications have simpler choices. Before adoption, verify the APK or split APK workflow on the target device and confirm that any edits remain compatible with the application's signing and packaging requirements. ## FAQ ### What can APK Explorer & Editor inspect? AEE can explore an installed application or an APK file selected from device storage. It can navigate package contents, save individual resources, decode and view `resources.arsc`, and inspect or modify supported text and XML files. ### Can AEE edit and rebuild an APK? Yes, within the documented scope. AEE includes text and XML editing, resource deletion and replacement, smali assembly into new `classes.dex` files, and creation or resigning of APKs and app bundles. ### Does AEE support split APKs and app bundles? Yes. The README documents export, installation, sharing, and signing or creation support for APKs, split APKs, and app bundles. It does not document the internal handling rules or all format limitations. ### What is the main limitation of AEE's editor? The README states that the built-in text and XML editor can be buggy when working with very large APKs. No specific size threshold or recovery procedure is provided. ### How can a new user obtain APK Explorer & Editor? The README lists Google Play, F-Droid, the IzzyOnDroid repository, and GitHub Releases as distribution options. It does not provide verified source-build commands. ## Sources - [apk-editor/APK-Explorer-Editor on GitHub](https://github.com/apk-editor/APK-Explorer-Editor) - [License: GPL-3.0](https://github.com/apk-editor/APK-Explorer-Editor/blob/master/LICENSE) - [Project website](https://apk-editor.github.io/) - [README](https://github.com/apk-editor/APK-Explorer-Editor/blob/master/README.md) - [Releases](https://github.com/apk-editor/APK-Explorer-Editor/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/apk-editor-apk-explorer-editor