BACK TO BLOG

If you've heard the term "sideloading" thrown around in iOS communities and wondered what it actually means, you're in the right place. This guide covers everything from the basics of what sideloading is, to how it works under the hood, to how you can get started today. Whether you're a complete beginner or just looking to understand the process better, this article will walk you through it all.

In This Article

What Does Sideloading Mean?

Sideloading simply means installing an app on your device through a method other than the official app store. On Android, this is as simple as downloading an APK file and tapping "Install." On iOS, it's more involved because Apple requires every app to be cryptographically signed with a valid developer certificate before the operating system will allow it to run.

The term "sideloading" comes from the idea of loading software from the "side" rather than through the "front door" (the App Store). It's not hacking, it's not jailbreaking, and it doesn't exploit any vulnerability. Sideloading uses Apple's own developer infrastructure, the same system that every App Store developer uses to test their apps before submission.

Why Do People Sideload?

There are many legitimate reasons to install apps outside the App Store:

  • Open-source software. Many excellent iOS apps are developed as open-source projects but never submitted to the App Store. The developers make the source code and IPA files freely available for anyone to install.
  • Emulators. Classic game emulators like Delta, PPSSPP, and RetroArch allow you to play games from older consoles. Apple has historically been inconsistent about allowing these on the App Store, and many users prefer to sideload them for reliability.
  • Beta and development builds. Developers testing their own apps on real hardware need to sideload since the app isn't on the App Store yet. While TestFlight covers some of this, it has limitations on tester count and build duration.
  • Apps Apple doesn't allow. Apple's App Store review guidelines prohibit certain categories of apps. Some of these are perfectly legal and useful, they just don't fit Apple's rules. Sideloading is the only way to run them on iOS.
  • Customization tools. Apps that modify system behavior, provide alternative launchers, or offer functionality that iOS doesn't natively support are typically only available through sideloading.
  • Regional availability. Some apps are only available in certain countries' App Stores. Sideloading bypasses regional restrictions since you're installing the IPA file directly.

How Does iOS Sideloading Work?

Every iOS app is distributed as an IPA file, essentially a ZIP archive containing the compiled app, its resources, and metadata. Before this IPA can run on a device, it must be signed with two things:

  1. A P12 certificate — a digital identity issued by Apple that identifies the developer or organization that signed the app.
  2. A provisioning profile — a file that specifies which devices (by UDID) are allowed to run the app and what capabilities (push notifications, iCloud, etc.) the app can use.

The signing process embeds these credentials into the IPA file, creating a tamper-proof package that iOS can verify. When you install the signed IPA, iOS checks the signature against Apple's root certificates, confirms your device's UDID is listed in the provisioning profile, and if everything checks out, allows the app to run.

There are several types of certificates used for sideloading:

  • Free/enterprise certificates — shared certificates available publicly. They don't require your UDID to be registered (they use broad provisioning), which makes them easy to use but also easy for Apple to detect. They are unreliable and not recommended — most get revoked within days, sometimes hours. Fine for a quick test, but not for daily use.
  • Paid Apple Developer certificates ($99/year) — allow up to 100 registered devices, 1-year expiration, and full capabilities. This is what indie developers use, but managing your own developer account is complex.
  • Signing services (recommended) — platforms like FlareStore that provide paid certificates with your UDID individually registered. This gives you the stability of a personal developer certificate without the hassle of managing an Apple Developer account yourself. Your UDID registration means the certificate is tied to your specific device, keeping usage private and dramatically reducing revocation risk.

The Sideloading Process Step by Step

Here's the general flow, regardless of which tools you use:

  1. Get your UDID. Your device's unique identifier is needed to register on a paid certificate. Tools like FlareStore's UDID Grabber make this a 30-second process. (Free/enterprise certificates skip this step since they don't require UDID registration, but that's also why they're unreliable.)
  2. Get a signing certificate. We recommend purchasing a certificate from flarestore.vip for the most reliable experience. Free certificates exist for quick testing but get revoked constantly and are not suitable for regular use.
  3. Find an IPA file. Download the app you want to install. IPA files are available from developer websites, GitHub releases, community repositories, and other sources.
  4. Sign the IPA. Use a signing tool to attach your certificate and provisioning profile to the IPA. FlareStore's Web Signer does this entirely in the browser. Other options include Xcode (Mac only), AltStore, or on-device tools like Feather.
  5. Install the signed app. Depending on your tool, this happens via OTA (over-the-air) installation, USB connection, or direct on-device installation.
  6. Enable Developer Mode. On iOS 16 and later, you must enable Developer Mode in Settings before the app will launch. This is a one-time step.
  7. Optional: Protect against revocation. Install a DNS profile to block Apple's certificate revocation checks, keeping your apps working even if the certificate gets revoked.

Sideloading vs Jailbreaking

These are completely different things, but they're often confused:

Sideloading uses Apple's official developer signing system. Your device stays on stock iOS with all security features intact. Apps run in the normal iOS sandbox with the same restrictions as App Store apps. No exploits are involved.

Jailbreaking exploits a vulnerability in iOS to gain root access to the operating system. It disables security protections, allows unsigned code to run, and can modify system-level behavior. Jailbreaking voids your warranty and can introduce security risks.

You do not need to jailbreak your device to sideload. Sideloading works on every iPhone and iPad running any version of iOS, completely stock.

Common Concerns

Is sideloading legal?

In most jurisdictions, yes. You're using Apple's own developer tools for their intended purpose (running software on your own device). The EU's Digital Markets Act has further enshrined the right to sideload on iOS.

Can sideloading damage my device?

No. Sideloaded apps run in the same sandbox as App Store apps. They cannot modify the operating system, access other apps' data, or damage hardware. The worst that can happen is the app doesn't work.

Will I lose my warranty?

No. Sideloading does not void your Apple warranty. It uses supported Apple developer features, not exploits.

Can Apple detect that I'm sideloading?

Apple can see that a developer certificate is being used to sign apps for your device, but this is expected behavior. It's the same process every developer uses. Apple does not penalize users for sideloading.

Getting Started with FlareStore

If you're ready to try sideloading, FlareStore provides everything you need:

  1. Grab your UDID at flarestore.app/udid/
  2. Purchase a certificate at flarestore.vip — paid certificates are far more reliable than free alternatives and will save you from constant revocation headaches
  3. Sign apps at flarestore.app/signer/
  4. Read the full guide for your device at flarestore.app/guide/

The entire process can be done from your iPhone, no computer required. While free certificates exist at flarestore.app/certs/ for a quick test, they are shared among thousands of users and get revoked frequently. For any real use, a paid certificate from flarestore.vip is the way to go.