Get your signed IPA onto your iPhone.
- Choose a compatible IPA file you own or have permission to install.
- Select a shared certificate or provide your .p12, its password, and matching .mobileprovision file.
- Tap “Sign IPA” and keep this page open. Download the signed IPA, or prepare an installation link if available.
- Open the installation link in Safari on your iPhone or iPad. Tap “Install on iPhone” and confirm the iOS installation prompt.
- If iOS asks you to trust an enterprise developer, open Settings, General, VPN & Device Management. Follow the trust instructions. Newer iOS versions may require a restart.
If the profile doesn’t allow the app ID
Enable “Match app ID to profile” below the certificate choice and sign again. A profile limited to one app ID requires the signed copy to use that ID. The signer checks the app, signature, and installation link use the permitted ID.
Apps signed with the same fixed ID replace each other on your device. Changing an app’s ID may affect sign-in, keychain access, notifications, or other features. A compatible wildcard profile lets you keep the original ID.
If installation fails
iOS checks the signing certificate and provisioning profile independently of the signer. A revoked or expired certificate will not be fixed by re-signing. An Ad Hoc profile must include your device, and a profile must allow the app’s bundle identifier. Some apps also require entitlements or extra profiles that this basic flow cannot supply.
A signing certificate includes an RSA private key in .p12 format. A .cer file alone cannot sign an app. A provisioning profile and password must match the certificate. Export the full Apple certificate chain with the .p12 if the signer reports an unsupported issuer.
Private review sites
The signer can download a signed IPA while the website is private. Direct installation needs a public HTTPS manifest and IPA address that iOS can fetch without a login. The owner must enable public access before preparing install links.
App compatibility and size
This signer accepts standard IPAs up to 200 MB with a maximum unpacked size of 512 MB. Signing uses your browser’s memory. Smaller apps work better on phones; try a desktop browser if signing runs out of memory. Encrypted App Store downloads and ZIP64 archives are not supported. If an IPA includes app extensions or a Watch app, compatibility mode removes those components so the main app can use one profile; their companion features will not be included. The main app and nested frameworks remain supported.
The tool signs compatible app code using your certificate. It does not promise permanent installs, bypass iOS verification, or decrypt apps.
Certificate availability
“Not verified” means the owner hasn’t reported a successful installation. “Owner tested” means the owner tested it on a device; it does not guarantee it will work for you or remain unrevoked. Only share certificates and apps you have permission to use. Enterprise certificates are intended for eligible internal distribution.
Apple’s distribution and installation guidance
Open-source signing engine
AmaazSign uses the zsign signing engine and the browser runtime from SylvaSigner. Certificate inspection uses Forge. zsign license · SylvaSigner license · Forge license · OpenSSL license
Return to the signer