How to edit AndroidManifest.xml on Android

Published Nov 9, 2026 · 5 min read · Steps checked against Manifesto 1.0

You can edit AndroidManifest.xml on Android with Manifesto. Inside an APK the manifest is compiled binary XML, so a text editor shows unreadable bytes. Manifesto decodes it to readable XML with ARSCLib 1.4.0 and encodes it back when you save. The catch: the changed APK must be re-signed, so it can't install over the original app.

Why can't I just open AndroidManifest.xml in a text editor?

AndroidManifest.xml inside an APK is not plain text. The build tools compile it into Android's binary XML format, with strings stored in a table and attributes stored as IDs. If you unzip an APK and open the file, you see mostly unreadable bytes.

Manifesto handles the conversion for you. It decodes the compiled XML to text when you open it ("Decoding compiled XML…"), and encodes your edited text back to binary when you save. It does this per file with ARSCLib, so it doesn't unpack the whole APK first.

How do I edit the manifest inside an APK?

Manifesto gives you two ways in. A project is better for several changes; the quick path suits one small edit.

In an APK project:

Long-press the .apk in the file manager (or tap it, then Options) and tap Open as project.
Open the Resources tab, or the Explorer tab, and tap AndroidManifest.xml.
Edit the XML, then tap the save icon (Validate and save). The change appears in the History tab.
Tap Build and sign. Manifesto writes <name>-modified-signed.apk in the project folder, signed with its debug key.

Quick edit, without a project:

Tap the .apk, then tap View on the info sheet to browse its contents.
Tap AndroidManifest.xml, make your change and save.
Go back. In Update compiled XML?, leave Sign APK after updating on (it is on by default) if you want an installable file, then tap Update.

The quick edit writes the change into the APK file you opened and replaces it. Copy the APK first if you want to keep the original. With Sign APK after updating on, Manifesto signs it with its debug key using V1, V2 and V3.

What can I change in AndroidManifest.xml?

The manifest declares the app's identity, its components and what it may access. These are the edits people make most often:

Change	Where in the manifest	Notes
App name	`android:label` on `<application>`	Often a reference like `@string/app_name`. Change the string in the Resources tab instead.
Remove a permission	A `<uses-permission>` line	The app may crash if its code still uses that permission.
Add a permission	A new `<uses-permission android:name="..."/>`	Runtime permissions still need the user to grant them.
Debuggable flag	`android:debuggable="true"` on `<application>`	Lets debugging tools attach to your own build.
Min or target SDK	`<uses-sdk>` attributes	Lowering minSdk doesn't remove calls to newer APIs, so the app can still crash on older Android.

To rename an app that uses @string/app_name, open res/values/strings.xml in the Resources tab, change the value, and tap Validate and save. Manifesto applies the edit back into resources.arsc when you build. The docs on editing resources and the manifest cover resources.arsc and binary XML in more detail.

Why won't my edited APK install?

An edited APK fails to install for one of a few reasons:

Different signature: Android only installs an update when it is signed with the same key as the installed app. Your edited APK is signed with Manifesto's debug key, or your own key if you re-sign it with Sign, so uninstall the original first. Uninstalling deletes its data.
Not signed: if you turned off Sign APK after updating in the quick edit, the APK has no valid signature. Run Sign on it, as in how to sign an APK on Android.
Invalid manifest: a typo in a class name or a missing component can make the app install but crash on start. Check your last change against the original manifest, fix it and build again.

Can I edit the manifest in an XAPK, APKS or AAB?

Manifesto edits the manifest of a single .apk. Split sets and bundles can be viewed but not rebuilt, so convert them first:

APKS, XAPK, APKM: use Convert to APK to merge them, as in installing XAPK and split APKs.
AAB: use Convert to APK to build a universal APK. See converting AAB to APK on Android.

Once you have a single APK, edit it with Manifesto's APK editor for Android as above.

Only edit the manifest of apps you own or are allowed to modify. Editing it is not a way to bypass licence checks or unlock paid features.

Frequently asked questions

Can I edit AndroidManifest.xml on Android without a PC?

Yes. Manifesto decodes the binary manifest inside an APK to readable XML on the phone, lets you edit it, and encodes it back to binary when you save. Then Build and sign produces a new APK you can install.

Why does AndroidManifest.xml look like random characters?

Inside an APK the manifest is compiled into Android's binary XML format, not plain text. You need a tool that decodes it. Manifesto does this with ARSCLib when you open the file and re-encodes it when you save.

How do I change an app's name in the manifest?

Find android:label on the application tag. If it points to a string such as @string/app_name, change that string in the Resources tab instead, under res/values/strings.xml. Then tap Validate and save and Build and sign to produce the renamed APK.

Do I need to sign the APK after editing the manifest?

Yes. Any change to the APK breaks its signature, and Android won't install an unsigned APK. Build and sign signs a project build with the debug key. For the quick edit, leave Sign APK after updating on, or use Sign afterwards with your own keystore.

Why does my app crash after I removed a permission?

The app's code may still call an API that needs that permission, and Android throws an error when the permission is missing. Put the uses-permission line back, or only remove permissions for features you know the app doesn't use.