LiveContainer on iOS: Run Apps Without Installing Them
Every sideloading method on this site shares one assumption: each app gets installed onto your iPhone as itself, with its own signature and its own slot in your certificate’s allowance. LiveContainer throws that assumption away. It is a single host app inside which other apps run as guests — never individually installed, never individually signed, and therefore not consuming the limits that shape every other sideloading workflow. If you have not met it yet, you will: it now appears in every serious sideloading roundup. This guide explains how it works, where its real limits are, and what Scarlet users in particular should take from it.
How LiveContainer Works
LiveContainer is itself an iOS app that you install once, by any of the usual methods — a signer like Scarlet, Feather, Ksign or an Apple ID-based tool. Inside LiveContainer, you import IPA files, and instead of installing them onto the home screen, LiveContainer loads and runs them within its own process space, roughly the way an emulator hosts its games. The guest app gets its own data container and behaves, for most purposes, like a normally installed app while it is running.
The consequences follow directly from that design. Because guest apps are never installed as apps, they do not count against the free Apple ID signing limits that strangle AltStore-style setups (a handful of app IDs and active apps), and they do not each need their own signing event. One signed container can host a shelf of guest apps. For users whose sideloading life is a constant negotiation with limits, that is a genuinely new shape of freedom.
LiveContainer vs Normal Installing
| LiveContainer | Normal sideloading (Scarlet, signers) | |
|---|---|---|
| How apps arrive | Imported into the container and run as guests | Signed and installed individually on the home screen |
| Signing limits | Only the container itself needs signing; guests don’t consume app slots | Every app consumes certificate/app-ID allowances and expires with them |
| Home screen presence | Guests live inside LiveContainer (shortcuts can make access quicker, but the container is the door) | Real icons, indistinguishable from App Store apps |
| Notifications & background behaviour | Limited — guests are not fully-fledged installed apps, so push and background features are restricted or absent | Works to the extent the app’s entitlements allow |
| Performance | Good for most apps; some JIT-dependent or deeply system-integrated apps struggle or refuse | Native — the app runs as itself |
| Revoke exposure | If the container’s signing dies, all guests go down with it — one point of failure | Shared-certificate installs share the same all-at-once revoke pattern; own-certificate installs are calmer |
The Honest Limits
- Not every app runs. Apps that lean on features a guest cannot fully have — push notifications, some extensions, certain anti-tamper checks, JIT-heavy emulation — may fail, misbehave, or detect the environment. Compatibility is per app and has to be discovered by trying.
- The container is a single point of failure. Revoke or expiry of LiveContainer itself shelves your whole guest library at once. Signing the container with your own certificate, as in our certificate import guide, is the grown-up configuration.
- It is a different daily experience. Opening a container to open an app is one more step than tapping an icon, every time. For apps you use hourly, that friction is real; for apps you use occasionally, it is nothing.
- Setup concepts stack. Developer Mode enters the picture for parts of this ecosystem, depending on tool and method — our Developer Mode explainer separates when that switch is and is not required.
What Scarlet Users Should Do With It
Treat LiveContainer as a complement, not a replacement. The pattern experienced users settle into: their two or three essential apps installed properly through Scarlet with a good certificate, and the long tail of “apks-I-mean-IPAs I just want to try” living as LiveContainer guests, where experimenting costs no signing slots and risks nothing. It is also the best sandbox we have for testing an IPA from a source you do not fully trust yet — a guest that misbehaves can be deleted without it ever having been an installed app. If you are surveying the whole modern toolkit, LiveContainer belongs on the same shelf as the signers in our Ksign & GBox explainer and the Scarlet alternatives roundup — the ecosystem is becoming a set of combinable parts rather than a single chosen app.
Getting Started: The Shape of a Setup
Setting LiveContainer up follows a fixed order, and knowing it in advance prevents the most common confusion. First, LiveContainer itself must reach your phone through an existing route — a signer such as Feather or Ksign, Scarlet, or an Apple ID-based installer; a phone with no sideloading method at all cannot bootstrap it from nothing. Second, inside LiveContainer, you import the IPAs you want as guests, from Files or a downloaded source. Third, you launch guests from within the container and live with them for a few days before judging the arrangement — the first hour, with its extra tap to open things, feels clumsier than the routine becomes. Users who get the most from it are deliberate about the division we described above: a small set of properly installed essentials, and everything experimental or occasional in the container. Users who try to move their entire app life inside it on day one usually bounce off the capability limits we listed and conclude, unfairly, that the tool does not work.
A last practical note: because guest apps write their data inside the container’s own storage area, deleting the container deletes everything in it at once. If a guest app holds data you care about — saves, documents, offline media — export it before you remove or reinstall LiveContainer, exactly as you would before deleting any sideloaded app.
FAQ
What is LiveContainer on iOS?
LiveContainer is an iOS app that runs other apps inside itself instead of installing them. You import IPAs into it, and they execute as “guest” apps within the container — which means they don’t consume individual signing slots or app-ID limits the way normally installed sideloaded apps do.
Do apps in LiveContainer need to be signed?
LiveContainer itself must be installed through a normal method (a signer or Scarlet), and its own signing can expire or be revoked like any sideloaded app. The guest apps inside it do not each need their own signing, which is precisely the point of the design.
Can LiveContainer run any app?
No. Most straightforward apps run well, but guests lack some capabilities of truly installed apps — push notifications and certain extensions are limited, and apps with strong environment checks or JIT requirements may not work. Treat compatibility as per-app and experimental.
Is LiveContainer better than Scarlet?
They do different jobs. Scarlet installs real apps that live on your home screen with full behaviour. LiveContainer hosts guests inside one app, trading some capability for freedom from per-app limits. Many users run both: essentials installed properly, experiments in the container.
Does LiveContainer stop revokes?
It reduces their surface but does not abolish them. Guest apps can’t be individually revoked because they were never individually signed — but if the container app’s own certificate is revoked or expires, everything inside it stops too. Signing the container with your own certificate is the stable configuration.
