Sign on-device
Bring an IPA, certificate, and profile to the device. The existing zsign workflow handles the signing pass locally.
Version 2.1 · open source
On-device IPA signer
The calmer way to sign.
ForgeSign brings a focused signing, install, and library workflow to iPhone and iPad. Choose your materials, see what is ready, and keep the pass local.
iOS 16+
No account
Local-first
Designed around the passPreflight, sign, install, and return to your library without losing the thread.
On-deviceFiles and signing stay in your workflow.
2.1Open IPA previews directly in ForgeSign.
16+Built for iPhone and iPad.
OpenInspect the project on GitHub.
Latest release · Version 2.1
From Files to signing in one tap.
ForgeSign 2.1 adds a dedicated quick action to IPA previews in Files and hands the selected archive directly into the signing workflow.
✓IPA previews in Files now show ForgeSign in the bottom quick-action menu.
✓Tapping ForgeSign opens the app with the selected IPA already loaded.
✓IPA registration uses Apple’s canonical file type for reliable handoff.
✓Ordinary ZIP archives remain a separate alternate import path.
ForgeSign 2.1 · Dark-mode review
A closer look at the signing workflow.
The app stays glassy and legible in dark mode, with the same information hierarchy across each tab.
A complete signing pass
Small details that remove friction.
The interface stays quiet until you need a decision, then puts the next useful action in reach.
Preflight first
See package, bundle, encryption, and architecture signals before committing to a signing run.
Remembered certificates
Keep validated certificate details and optional passwords available for repeat signing without re-entering everything.
Optional dylib injection
Opt in to compatible decrypted Mach-O dylibs, with a separate app-extension toggle, before the normal signer runs.
Sources that hand off
Save repository feeds, inspect available IPAs, and send a selected download into the same signing flow.
Library and install
Keep signed history together with reinstall, share, delete, and the existing semi-local install path.
The rhythm
Inspect. Prepare. Sign. Install.
Optional tools stay beside the core pass, so the familiar signing route remains familiar.
Inspect
Choose an IPA and read the preflight signals before signing.
Prepare
Add a certificate, profile, and any optional bundle or dylib choices.
Sign
Run the on-device signer and save the result to the library.
Install
Use the existing install action when the signed app is ready.
Workflow review
What the new screens make obvious.
A product review of the interaction itself: fewer hidden steps, clearer boundaries, and a library you can return to.
Preflight before commitment
The IPA gets a quick read before the signing action, so a missing or unsuitable input is visible earlier.
Optional means optional
Dylib injection and app-extension handling are surfaced as an opt-in layer around the unchanged normal route.
Finish where you started
Sources feed the same signer, while Library keeps signed history close for the next install or share.
Questions, answered
Keep the edges clear.
Is the downloaded IPA signed?
No. The release is intentionally unsigned so you can sign it with your own certificate and provisioning profile before installing.
What does 2.1 add?
ForgeSign 2.1 adds an Open in ForgeSign quick action to IPA previews in Files, then loads the selected archive directly into the signing workflow.
What kind of dylib can be injected?
Use a compatible, decrypted Mach-O dylib that matches the target architecture. Injection is performed on a disposable IPA copy before the existing signer; the original input is left untouched.
Does ForgeSign upload my files?
The signing workflow is designed to run on-device. You remain responsible for the source IPAs, certificates, profiles, and modifications you choose to use.
Where is the source?
ForgeSign is developed in public on GitHub. Issues and release notes live there too.
Ready for a quieter signing pass?
Download ForgeSign 2.1 and bring your own signing materials.