Scarlet on iPhone: What It Is, and Why Apps Keep Dying
Most people meet Scarlet the same way: searching for a modded Roblox or Free Fire build, finding a site that promises it in one tap with no computer, and installing something called Scarlet along the way. A week later the icons are still on the Home Screen but nothing opens.
That pattern is not bad luck, and it is not something you did wrong. It is how the whole arrangement works. Here is what Scarlet actually is, why apps installed through it die in batches, and what the “anti-revoke” fix in every guide really does to your phone.
Scarlet is a store, not a signer
This is the distinction that explains everything else, and almost no guide draws it.
A signer — eSign is the usual example — is a tool you feed your own certificate to. You bring a .p12 and a provisioning profile, it signs an app, and the result lives or dies with the certificate you supplied. We went through that machinery in how eSign actually works.
Scarlet is the other shape. It ships as a library: a browsable list of ready-made tweaks and modded games, already signed, ready to install with a tap. You never see a certificate, never choose one, never manage one. That is exactly why it feels easier — and exactly why you have no control over what happens next.
The certificate you never chose
Everything in that library is signed with a certificate somebody else holds. You are not a customer of it; you are a passenger on it, along with everyone else who installed anything from the same source.
When Apple revokes that certificate — and enterprise certificates distributing modded apps to strangers get revoked — nothing is targeted at you. The signature stops validating, and every app that came from that source stops opening on the same day. Yours, and everyone else’s. The icons stay; the apps are gone.
That is the mechanism behind the pattern people describe as “Scarlet stopped working again.” It did not break. Its certificate did, and it will keep happening, because the arrangement guarantees it: one certificate, thousands of strangers, mods that Apple has every reason to look for. We wrote up the full anatomy of a revoke wave in why sideloaded apps get revoked.
What “anti-revoke” actually does
Every Scarlet guide eventually recommends an anti-revoke DNS profile. It is worth knowing what you are installing.
When you launch a signed app, iOS checks with Apple whether the certificate is still valid. The anti-revoke profile points that check at a server that never answers, so your phone cannot learn the certificate was pulled and keeps opening what is already installed.
Three things nobody puts in the thumbnail. It does not repair the certificate — that is dead everywhere, and new installs still fail, because installing needs a valid signature and not just a launch. It routes your DNS through a stranger’s server for as long as the profile stays on the phone. And it is a workaround with a shelf life, not a fix. The trade-off in full: the free certificate method and its DNS bypass.
Four sites say they are the official one
Search the name and you get scarletios.app, scarletapps.com, scarletiosstore.com, scarletiosdownload.com — each with a Direct Install button and each calling itself official. They cannot all be right, and there is no authoritative home page to check them against.
This matters more here than with a normal app, because Direct Install means you tap a button and a signed binary lands on your phone without you ever seeing a file. Whatever that binary is, it is what you now have. The same red flags apply as with certificate sellers — and one rule covers most of the risk: nothing about installing an app ever needs your Apple ID password. Anyone asking is after the account. More tells in certificate scams and what to watch for.
If you came for game mods, read this part
The autocomplete tells the honest story about who searches for Scarlet: Free Fire, Roblox, mod menus. So here is the thing that guide never mentions.
Those are online games with server-side checks. Single-player mods change what happens on your device, and nobody is watching. A multiplayer client that reports impossible things is the exact pattern anti-cheat looks for, and the penalty does not land on Scarlet — it lands on your account. You can lose a profile you spent a year on for a mod menu that worked for a weekend.
Offline and single-player games are a different conversation entirely: the modified build changes your own save and nothing else. That is where unlocked builds are genuinely worth having, and it is most of what a catalog like ours carries.
What to use instead
If what you actually want is a tweaked app that keeps working, the question is never which installer has the prettier list. It is who holds the certificate and how many strangers are on it.
- Your own developer account plus a signer. Most control, $99 a year, and you maintain it yourself.
- A free certificate with SideStore or AltStore. Free, and it costs a pairing file made on a computer once, a seven-day signature, and a refresh that has to keep succeeding — the honest shape of it is in our SideStore guide.
- Managed signing. The certificate is maintained for you, your device sits on it by UDID, and installs stay signed rather than expiring on a timer. That is what builds.io does: one tap from the phone, with a one-time Apple processing step of up to three days when a new device is added.
Whichever route you take, ask the question Scarlet never lets you ask: whose certificate is this, and what happens to my apps the day it goes?