LiveContainer in 2026: What It Is and Where to Get It Now

LiveContainer is a single sideloaded app that runs other apps inside itself — without iOS ever installing them. Only LiveContainer holds a signature and an app slot; every IPA you load into it rides along on that one slot. That is why people run ten or twenty sideloaded apps on a free Apple ID that officially allows three, and why the search for it never slows down.

The news in October 2026 is about where to get it. On October 4, 2026, GitHub hid both the LiveContainer organization and its lead developer’s account, and every installer that downloaded LiveContainer from there started failing with HTTP 404 Not Found. As of October 12 the original repository is still gone. The last official build — the nightly from September 18, 2026 — survives on a community mirror, and there is a way to check that the file you get is the real one. Below: what happened, where the verified build is, how the setup works now, and how to give apps inside it more memory with GetMoreRam.

What happened to LiveContainer on GitHub

On October 4 the developer behind LiveContainer, Duy Tran (khanhduytran0), posted on X that GitHub had logged him out mid-session, forced a password reset, and that both his profile and the LiveContainer organization had been shadowbanned. From the outside it looks like a deletion: the repository, its releases and the documentation site at livecontainer.github.io all return “not found”. GitHub has not explained the decision publicly.

Almost every install path pulled the IPA straight from LiveContainer’s GitHub releases, so reports titled Failed to download file: HTTP 404 Not Found piled up in iloader’s and SideStore’s trackers from October 5 onward.

The same day a community organization called LiveContainerMirror published a copy of the source and the last nightly build. According to the mirror’s own release notes, the two accounts were briefly unbanned — and then banned again after a commit re-adding an IPA download link to Releases. For now the maintainers point people to a Discord server for updates. If you read that LiveContainer is “back”, check the date: at the time of writing, the original repository still is not.

Where to download LiveContainer now

This is the part to get right, because LiveContainer is not an app you want from a random IPA site. Everything you run inside it lives in its containers, and the project’s own README warns that closed-source third-party builds have full access to your data, including keychain items and login credentials. A fake LiveContainer is the most dangerous kind of fake app there is.

What is known to be the real thing as of October 12, 2026:

• The last official build is Nightly 20260918 — the last nightly published before the repository was hidden, built from the September 18 commit (it reports itself as version 3.8.10).
• The LiveContainerMirror release (github.com/LiveContainerMirror/LiveContainer) hosts that build as Nightly Release @ 20260918, with two files: LiveContainer.ipa (standalone) and LiveContainer+SideStore.ipa.
• The combined file has been checked against the official build. SideInstaller, an open-source on-device installer, pins exactly one file from the mirror and refuses anything else under the same link. Its changelog says the copy matches the official build by SHA-256. The hash it accepts for LiveContainer+SideStore.ipa is:

bec41bc21d75a0f2e85a0aa589ce5772e24e410deb017486758a3bc0503c8de7

If the file you downloaded does not produce that hash, do not install it. There is no stable build on the mirror — only that nightly — so “stable” and “nightly” are the same build until the repository returns. When it does, go back to the official releases.

Forks such as LiveContainer-Plus are a separate case: open source, published under their own names, and adding features rather than impersonating the original.

Standalone or LiveContainer + SideStore

LiveContainer comes in two packages, and the choice is about app slots:

	Standalone LiveContainer	LiveContainer + SideStore
What it is	LiveContainer only	LiveContainer with SideStore built in
Free account slots used	1 for LiveContainer + 1 for SideStore or AltStore	1 in total
Who refreshes it	your separate SideStore or AltStore	the built-in SideStore

The combined build is what most people use: one slot, and the built-in SideStore — the AltStore fork that signs and refreshes apps on the phone itself — keeps LiveContainer alive from week to week without a computer.

How to install LiveContainer in 2026

You need a computer once, for the first install. The official guide names three installers — Impactor, iloader, or an existing SideStore — and explicitly says not to use Sideloadly, 3uTools, NB Tool or most online signers.

1. Get the IPA from the mirror and check the hash above. iloader’s one-click “LiveContainer+SideStore” button downloads from the old GitHub address, which is why it fails right now; its Import any IPA option works with the file you downloaded.
2. Install it with Impactor or iloader using your free Apple ID. Impactor has an advantage the official guide points out: it adds the increased-memory-limit entitlement to LiveContainer automatically (more on that below). In Impactor, keep “Only Register Main Bundle” selected.
3. Trust the developer profile in Settings → General → VPN & Device Management.
4. Log in to the built-in SideStore. Open it from the button in the top-left of LiveContainer’s Apps page, sign in again even if it looks signed in, connect LocalDevVPN, and tap Refresh All.
5. Import the certificate. Back in LiveContainer, go to Settings → Import Certificate from SideStore. When the button turns into Remove Certificate, open JIT-Less Mode Diagnose to confirm everything is green.
6. Add apps with the plus icon in the top-right and pick any IPA. Long-press an app for its settings, or add it to the Home Screen as a shortcut.

LocalDevVPN is the loopback VPN SideStore relies on to refresh over Wi-Fi instead of a cable. Older guides also list StosVPN and StikDebug’s built-in VPN; StosVPN left the App Store, and StikDebug no longer ships a VPN of its own, so LocalDevVPN is now the standard piece. Why it is needed at all is explained in LocalDevVPN and SideStore without a PC.

How LiveContainer runs apps without installing them

A free Apple ID can sign three apps at a time and register ten App IDs a week, and each signature lasts seven days. LiveContainer does not remove those limits — it sidesteps them. The README puts it plainly: the 3-app and 10-App-ID limits do not apply to apps inside it, because iOS only ever sees one app and one App ID.

Under the hood, LiveContainer patches the guest app’s executable so it loads as a library, then jumps to its entry point. The guest starts like any other iOS app — it just never went through the system installer. What follows from that:

• Guest apps are signed with LiveContainer’s certificate (JIT-less mode, the default). Below iOS 26, if JIT is available, signing can be skipped entirely; on iOS 26 and later JIT works only for apps whose developers added support — see how to enable JIT on iPhone.
• You can run more than one app at once. On iOS 16 and later, multitasking opens apps in resizable in-app windows, including Picture-in-Picture; a second LiveContainer is the other way to run apps side by side.
• Multiple accounts are built in. The same app can run in separate containers with separate logins.
• Guests are not sandboxed from each other. One guest app can read another’s data, and permissions you grant apply to all of them.
• Not every app works. Games built on unusual engines are the hardest case, and the developers say outright that game crashes are the least likely to get fixed.

The seven-day refresh still applies

The container multiplies how many apps one slot carries. It does nothing about the clock. When LiveContainer’s profile expires, nothing inside it launches until SideStore refreshes it — so LocalDevVPN has to connect and the refresh has to succeed at least once a week. The auto-refresh Shortcut works the same as with standalone SideStore: swap in LiveContainer’s “Refresh All Apps” action.

The developers have added a guide for one sneaky failure: apps expiring even after a timely refresh. The cause is a refresh that installs a profile missing an entitlement. StikDebug’s App Expiry tool shows it as “Missing Entitlements”; reinstalling the app’s IPA in SideStore usually fixes it. If refreshing every week is the part you are tired of, the fixes for the 7-day refresh compare what actually removes it.

GetMoreRam: more memory for emulators and games

iOS caps how much memory one app can use, and apps inside LiveContainer share LiveContainer’s cap. Apple offers an entitlement that raises it — Increased Memory Limit — and it is available on free accounts. The catch is that it has to be on LiveContainer’s own App ID, and users who tested it report that SideStore does not add it when it installs LiveContainer.

GetMoreRam is a small open-source app by hugeBlack, one of LiveContainer’s own contributors, that adds the entitlement without Xcode. It is still on GitHub, with its latest nightly from September 12, 2026. The steps, as the community walkthrough describes them:

1. Install GetMoreRam inside LiveContainer and open it.
2. In its settings, sign in with the same Apple ID that signs LiveContainer.
3. Open App IDs and tap Refresh.
4. Tap com.kdt.livecontainer.<your Team ID> and choose Add Increased Memory Limit. If a .LiveProcess entry appears too, repeat it there.
5. Reinstall LiveContainer (no need to delete it first) so Apple re-signs it with the new entitlement.

How much it buys depends on the device. In one published test, UTM’s reported maximum memory went from 3,297 MB to 6,065 MB after the change. iOS still sets a ceiling: the MeloNX project notes that iPhones with 8 GB and 12 GB of RAM share the same 6 GB limit, and one report on an iPhone 17 Pro Max with iOS 27 measured about 6 GB inside LiveContainer against about 8 GB for the same app installed directly. For the heaviest emulators, a container costs you some headroom.

Three things to know before you use it:

• Repeat it if LiveContainer expires. Missing the seven-day window means doing the whole process again.
• Extended Virtual Addressing is not available. That second entitlement, which some emulators need on devices with less RAM, is paid-only — GetMoreRam’s maintainers confirm it cannot add it to a free account.
• The sign-in will look unfamiliar. GetMoreRam talks to Apple’s developer service the way SideStore does, and users have reported a sign-in alert from an unknown Mac. The developer’s answer is that this is normal — and that if you do not trust the app, do not use it. If you installed LiveContainer with Impactor, you may not need GetMoreRam at all.

KSign and other signers with LiveContainer

Signing apps such as KSign, ESign and Feather come up constantly next to LiveContainer, and whether they can work together comes down to one detail of the certificate. LiveContainer needs a development profile — the get-task-allow entitlement — and its documentation is blunt: if LiveContainer is signed with a distribution profile, “LiveContainer won’t work at all”. The same docs list most online signers as unsupported installers.

The quick test is the JIT-Less Mode Diagnose page: if get-task-allow is missing or false, the certificate is the problem, not LiveContainer. How KSign itself handles certificates, and what its common errors mean, is in KSign on iOS: install, certificates and fixes. Shared and purchased certificates are a different model entirely — whose identity signs your apps, and why they all die in the same week — and that is covered in the best IPA signer for iPhone.

Common LiveContainer problems and fixes

• “Failed to download file: HTTP 404 Not Found.” Not your setup — it is the GitHub takedown. Install the verified mirror file manually, as above.
• “Certificate not found, did you log into built-in SideStore?” The official workaround: in built-in SideStore, Settings → Export Signing Certificate…, set a password, then import that file in LiveContainer’s settings.
• “The executable was signed with invalid entitlements.” Your SideStore or AltStore is too old; LiveContainer needs SideStore 0.6.2+ or AltStore 2.2.1+.
• App Group or Team ID shows red in the diagnose page. LiveContainer and SideStore were signed with different Apple IDs, or LiveContainer was installed with an unsupported tool. Sign both with the same account.
• LiveContainer crashes on iOS 26.4 or later. Use version 3.6.65 or newer — the September 18 nightly (3.8.10) qualifies.
• The file picker does nothing. Long-press the app → Settings → Fix File Picker.
• Notifications. Remote push notifications do not work inside LiveContainer, and features that need paid-account entitlements (push, Siri, iCloud) will not be fixed. Local notifications — reminders and alarms an app schedules itself — can work: enable Fix Local Notifications in the app’s settings. An app that truly needs push has to sit in its own slot outside the container.
• The pairing file stops working. Errors in SideStore or StikDebug that mention heartbeat or pairing usually mean the file needs regenerating — which needs a computer again. The error-by-error list is in StikDebug not working.

What not to do

• Don’t block Apple’s servers by DNS. Old guides recommended it; SideStore does not need it.
• Don’t delete expired apps. If something shows “no longer available”, refresh it — deleting LiveContainer takes every container’s data with it. (Making regular backups is exactly what forks like LiveContainer-Plus add.)
• Don’t share your pairing file. It carries your device’s identity.
• Don’t install LiveContainer from IPA sites or renamed, closed-source builds. While the repository is down, fakes have an easy story to tell.

LiveContainer FAQ

What is LiveContainer?

An app launcher — not an emulator or a hypervisor — that runs iOS apps inside itself without installing them, so a free Apple ID’s three-app limit stops being the ceiling.

Is LiveContainer gone?

The GitHub repository has been hidden since October 4, 2026, and is still unavailable as of October 12. A copy you already have keeps working as long as SideStore keeps refreshing it, and the last official build is available from the LiveContainerMirror release.

Is LiveContainer safe?

The official, open-source build is. The risk is fake builds: everything inside LiveContainer, including logins, is readable by the container app itself. Check the hash before installing.

Does LiveContainer work on iOS 26 and iOS 27?

Yes. JIT-less mode works on both; JIT itself is limited to apps that support the new iOS 26 method. Version 3.8.0 in July 2026 added support for the iOS 27 beta.

Where builds.io changes the math

LiveContainer exists to work around two limits of a free Apple ID — three apps and seven days — and October showed the third weak point: a setup that depends on one GitHub repository stops installing the day that repository disappears. Managed signing removes the constraints instead of routing around them:

• No three-app limit, so nothing needs to run inside a container — apps install normally, with push notifications and their own memory limits intact.
• No seven-day refresh and no VPN to keep connected; builds stay signed.
• No computer, ever — you install from Safari in one tap.

It is a subscription, so the honest trade is money for time. One expectation to set: when you first add a device, Apple processes it before apps go live — most are ready within a day, some take up to three. That happens once.

Comparing the free routes instead? See AltStore vs SideStore vs LiveContainer for the head-to-head and every free way to sideload, ranked for the effort-versus-payoff view.