The original IPA
Use an IPA from a source you trust. A damaged archive or incompatible app cannot be repaired merely by signing it again.
No-computer IPA signing - August promotion $8
How to sign an IPA without a computer
You can sign an IPA from an iPhone without using a Mac or Windows PC. The important part is having certificate files created for the correct device, then choosing either an on-device signing app or a browser-based signer.
What “without a computer” actually means
An IPA is an iPhone or iPad application package. Before iOS can install it outside the App Store, the package must be signed with a valid Apple Developer certificate and a provisioning profile that authorizes the target device. Signing changes the app package; it does not remove Apple’s certificate, entitlement, or device-registration requirements.
A computer is one way to perform that signing step, but it is not the only way. If your certificate package already contains a .p12 file, its password, and a matching .mobileprovision profile, you can complete the workflow from Safari or from a compatible signing app installed on the iPhone.
The device match matters.
The provisioning profile must include the exact UDID of the iPhone or iPad where the signed app will be installed. A valid certificate alone is not enough when the device is missing from the profile.
Files and information you need
Prepare these items before starting. Keeping them together avoids most signing and installation failures.
P12 certificate
The .p12 file contains the signing identity. It must still be valid and must match the provisioning profile.
Certificate password
The password unlocks the P12 file during signing. Enter it exactly as delivered, including capitalization.
Provisioning profile
The .mobileprovision file controls the permitted app capabilities and devices. Your UDID must be present.
Step 1: collect the UDID from the iPhone
- Open the UDID page in Safari. Visit the CertDrop UDID page on the device that will run the app.
- Follow the displayed profile instructions. iOS may ask you to allow a configuration profile download and then open Settings to complete the identification step.
- Check the returned identifier. A modern iPhone UDID is a long device identifier. Copy it carefully rather than typing it from memory.
- Use that same UDID for the certificate order. A profile created for another phone will not authorize the current device.
Collecting the UDID does not sign or modify an app. It supplies the device identifier required when the provisioning profile is created.
Step 2: obtain a matching certificate package
If you already have a working P12 certificate, password, and mobileprovision profile for this device, you can continue to the signing step. Otherwise, submit the UDID through the CertDrop order form and use a reachable non-iCloud email address for digital delivery.
When the files arrive, save all three components in the Files app. Do not rename only one file to make it appear to match another certificate package—the cryptographic relationship is inside the files, not in their filenames.
Step 3: choose an iPhone-only signing method
| Method | Best when | What happens | Main consideration |
|---|---|---|---|
| On-device signing app | You already have a compatible app such as ESign or Feather installed. | You import the certificate package and IPA, then sign directly on the iPhone. | The signing app itself must already open and work on the device. |
| Browser-based signer | You want to process an IPA in Safari without configuring a separate signing app. | You upload the IPA and certificate inputs, wait for signing, and receive the signed result. | Use a trusted service and avoid closing the page while the signing job is running. |
Method A: sign with an app on the iPhone
- Import the certificate. In the signing app, select the P12 file and enter its certificate password.
- Import the provisioning profile. Select the mobileprovision file delivered for the same certificate and device.
- Add the IPA. Open or share the IPA into the signing app from the Files app.
- Select the matching identity and profile. If the app lists several certificates, confirm that you are not mixing files from different packages.
- Start signing and wait for completion. Keep the signing app open until it reports success or provides a signed IPA.
- Install the signed result. Follow the app’s installation flow and keep the device online while iOS verifies the application.
Method B: use the CertDrop browser signer
- Open the CertDrop signer in Safari. The signer works as a separate tool from the certificate checkout.
- Select the original IPA. Large apps can take time to upload, so keep Safari active and use a stable connection.
- Add the P12, mobileprovision, and password. Use files from the same certificate package.
- Submit the signing job. The progress screen will show the current queue or processing state.
- Use the completed result. Download or follow the provided installation option once the job succeeds.
A signing service cannot make an incompatible IPA compatible with your iOS version, replace missing entitlements, or authorize a device absent from the profile. Those issues must be corrected at the source.
Common problems and what they mean
The P12 will not import
Recheck the password and confirm that the file is a genuine P12 rather than a renamed archive or certificate from another format.
The device is not registered
The provisioning profile probably does not include this iPhone’s UDID. Generate or obtain a profile containing the correct identifier.
The profile and certificate do not match
Do not combine a P12 from one delivery with a mobileprovision file from another. Use the original matching pair.
Unable to verify app integrity
Possible causes include a revoked or expired certificate, profile mismatch, incompatible entitlements, or a damaged IPA. See the iPhone signing error guide.
The signed IPA will not install
Check available storage, network access, iOS compatibility, and whether another copy of the app with a conflicting bundle identifier is installed.
The signing job stops or times out
Keep Safari or the signing app open, avoid switching networks during upload, and retry with the original files if the connection was interrupted.
Security and certificate limitations
Your P12 file and password can be used to sign applications, so treat them as sensitive credentials. Store them somewhere private, avoid sending them in public chats, and upload them only to a signing service you intend to use.
A certificate’s stated duration is not an unconditional guarantee that every signed application will remain available for that entire period. Apple can revoke certificates, app entitlements can be incompatible, and changes to iOS can affect installation behavior. CertDrop provides the certificate files and signing workflow but cannot override Apple’s platform controls.
Frequently asked questions
Can I sign an IPA using only my iPhone?
Yes. You can use a compatible signing app on the iPhone or a browser-based signing service. Both methods require a valid P12 certificate, its password, and a matching mobileprovision profile that includes the device UDID.
What files are required to sign an IPA?
You need the IPA, a P12 Apple Developer certificate, the P12 password, and a mobileprovision profile that matches the certificate and includes the target device.
Do I need a computer to find my iPhone UDID?
No. CertDrop provides a mobile UDID collection flow that can be completed from Safari on the iPhone.
Should I use an iPhone signing app or an online signer?
An iPhone signing app is convenient when it is already installed and you expect to sign repeatedly. A browser signer is simpler when you want to sign one IPA without importing certificate files into another app.
Why does a signed IPA fail to install?
Common causes include a missing device UDID, a provisioning profile that does not match the certificate, an incorrect P12 password, an expired or revoked certificate, or an IPA that is not compatible with the device.