ESign vs Scarlet: Which IPA Installer Should You Use in 2026?
ESign and Scarlet are the two names that come up in almost every iOS sideloading conversation — and they get compared as if they were the same kind of tool. They are not. One is a signer you feed with your own certificate; the other is an app store that runs on certificates someone else provides. That single difference decides how often your apps get revoked, how much control you have, and how much setup work you do. This comparison breaks down how each one really works so you can pick the right tool the first time.
The Quick Verdict
Choose Scarlet if you want the easiest start: install it, browse its built-in library and repositories, and install apps in a couple of taps — accepting that shared certificates can be revoked for everyone at once. Choose ESign if you already have (or plan to get) your own certificate and want to sign IPAs yourself, with full control over what signs your apps. Neither is “better” in the abstract; they serve different sideloading styles.
How Each Tool Actually Works
Scarlet: an installer running on shared certificates
Scarlet is a third-party app store. You install Scarlet itself using an enterprise certificate, and the apps inside it are signed with shared certificates maintained by the ecosystem around it. It also supports repositories (repos) — add a repo and its apps appear inside Scarlet, ready to install — plus tweak injection, backups, and the option to import your own certificate if you have one. Everything is designed so a beginner never has to think about signing. The official home of the app is usescarlet.com.
ESign: a signer that uses your certificate
ESign is an on-device IPA signer. It ships with no apps and no library: you import a certificate package (a .p12 file plus a .mobileprovision profile), import the IPA files you want, and ESign signs and installs them on the spot. One important note for 2026: the original ESign’s development ended, and what circulates under the name today is community rebuilds and certificate-seller bundles — a point covered in depth in this comparison of iPhone IPA signers. That makes your download source for ESign just as important as the certificate you use with it.
ESign vs Scarlet: Side-by-Side Comparison
| Feature | Scarlet | ESign |
|---|---|---|
| Tool type | App store / installer | IPA signer |
| Certificate | Shared enterprise certificates built in; can also import your own | You must supply your own (.p12 + provisioning profile) |
| Built-in app library | Yes, plus addable repos | No — you bring your own IPA files |
| Setup difficulty | Very easy | Moderate — certificate import required |
| Revoke risk | Higher — shared certs die for everyone at once | Lower with a private certificate — only your cert matters |
| Tweak injection | Yes (deb/dylib injection supported) | Limited signing options |
| Computer required | No | No |
| Jailbreak required | No | No |
| Best for | Beginners, browsing and one-tap installs | Users with their own certificate who sign specific IPAs |
Certificate Control: The Difference That Matters Most
Every sideloaded app lives or dies by its certificate. With Scarlet’s default setup, you share a certificate with thousands of strangers. When Apple revokes it — which happens in waves — every app signed with it stops opening for everyone simultaneously, and there is nothing you can do except wait or reinstall under a new certificate (our status hub tracks exactly this situation and the fixes). With ESign plus a certificate that belongs only to you, a mass revoke does not touch you; your apps keep working until your own certificate expires. That is the real trade: Scarlet trades stability for zero effort, ESign trades effort for stability.
Ease of Use
Scarlet wins for beginners, and it is not close. Install, trust, browse, tap — the full install guide takes about five minutes. ESign assumes you already understand certificates: you must obtain a valid .p12 and provisioning profile, import both correctly, and only then sign your first IPA. Users who try ESign without a certificate conclude it “doesn’t work,” when in reality it was never given the one thing it needs.
Features Beyond Signing
Scarlet is the richer environment: repos that update their apps automatically, tweak injection for adding .deb/.dylib modifications during install, app backup and restore, and multiple install methods including a computer-based one. ESign is deliberately narrower — it signs IPAs well, with options like bundle ID changes and signature settings, but it is a tool, not an ecosystem. If your habit is “find an app in a library and install it,” Scarlet matches it. If your habit is “I have this specific IPA file, sign it,” ESign matches it.
Which One Should You Use?
- You are new to sideloading: Scarlet. Learn the ecosystem first; you can graduate to your own certificate later — Scarlet even supports importing one via the custom certificate method.
- Your apps keep dying in revoke waves: ESign with a private certificate, or Scarlet with your own imported certificate. The tool matters less than owning the certificate.
- You mainly install a few specific IPAs: ESign. No library needed.
- You like browsing repos and tweaked apps: Scarlet, and see our guide to the best Scarlet alternatives if you want a backup installer for revoke days.
FAQ
Is ESign better than Scarlet?
For stability with your own certificate, yes. For ease of use and its built-in library, Scarlet is better. They solve different problems.
Can I use both ESign and Scarlet?
Yes. Many users browse and install with Scarlet day-to-day and keep ESign with a private certificate as the fallback when shared certificates get revoked.
Why did my ESign apps stop working?
Almost always the certificate you imported expired or was revoked. Import a fresh certificate package and re-sign the apps.
Is either tool safe?
Both are widely used, but safety depends on your sources: download the tools from their official channels and only sign IPAs you trust. See is Scarlet safe to use? for the full risk picture.
