Skip to main content

Apple signing

Generate an iOS certificate signing request and private key

Create a clean CSR for Apple Developer and download the matching private key immediately. This is the fastest starting point for App Store, ad-hoc, or internal iOS signing workflows.

  • Generate a fresh Apple-ready CSR without opening Keychain Access or the macOS certificate assistant.
  • Keep manual signing, CI secrets setup, and cloud build onboarding on the same page.
  • Use the resulting private key later when you export a distribution identity as a .p12 file.

Workflow

  1. 1. Enter the certificate subject details you want attached to the signing request.
  2. 2. Download the CSR and matching private key.
  3. 3. Upload the CSR in Apple Developer when creating your certificate.
  4. 4. Pair the issued certificate with the private key and export a portable .p12 when your build pipeline needs it.

Input

CSR subject details

Use the same person or organization identity you want represented in the Apple certificate request.

Output

Your generated signing request

Nothing is shown until the CSR is generated. Once ready, download both files and store the private key securely.

Generate a certificate request to see the subject summary and download buttons here.

When you need a fresh CSR

Use this before creating a new Apple Distribution certificate, rotating signing material, or onboarding a new app to an automated build system.

What to store securely

The private key is the sensitive asset. Put it in your company vault, password manager, or build secrets store and never commit it to the repository.

What comes next

After Apple issues the certificate, pair it with the private key and export a .p12 to connect local signing, CI jobs, or cloud builds.

FAQ

Frequently asked questions

These are the questions that usually come immediately after a team generates a CSR for an iOS release pipeline.

What does this iOS certificate generator create?

It creates a certificate signing request in CSR format and the matching private key in PEM format. Upload the CSR to Apple Developer, keep the private key secure, and export the issued certificate as a .p12 when you need it for CI or cloud builds.

Is the private key stored on the server?

No. The request is processed only long enough to generate the files and return them in the response. The tool does not persist the private key or write it to a database.

Can I use the generated CSR for App Store, ad-hoc, or enterprise signing?

Yes. The CSR is the starting point for any Apple certificate that requires a signing request. The certificate type is chosen later inside Apple Developer when you issue the certificate.

What should I do after Apple issues the certificate?

Download the certificate from Apple, import it into Keychain Access together with the private key, and export the combined identity as a .p12 if your CI or build platform needs a portable signing asset.