Your Apple ID, not ours
Apple issues the certificate to you — the same way Xcode does. Your password never touches a command line or the disk.
Free & open source · no jailbreak · nothing leaves your PC
Sign any .ipa with your own Apple ID and install it over USB or Wi-Fi — the same way Xcode runs an app you wrote. No jailbreak. No paid developer account. Nothing between your Apple ID and Apple.
Windows 10 or 11 · 64-bit · MIT · verify your download
.ipa anywhere
No screenshot trickery — that is the app, reporting the phone it is actually talking to.
Your Apple ID is the most sensitive credential you own. Every line that touches it is readable.
Apple issues the certificate to you — the same way Xcode does. Your password never touches a command line or the disk.
No iPASide server. No third-party anisette host. Even the device headers Apple demands are generated offline, on your machine.
.deb or .dylibDrop in a Debian package and iPASide finds the dylibs itself, each labelled with its architecture. Rootful, rootless, roothide. Stack as many as you like.
Free signatures expire after 7 days. The Library counts each one down and renews what's due — daily, in the background, with iPASide closed.
Choose the device and the connection. With more than one attached, iPASide refuses to guess rather than installing onto the wrong one.
Byte-by-byte upload, then your phone's own installer steps — verifying, sandboxing, finalising. It ends at 100%, not at a spinner.
Once. Use a spare account if you'd rather — iPASide keeps the session, never the password.
.ipaAnywhere on the window. It reads the app's icon and details instantly, and warns you up front if the file can't be re-signed.
A 299 MB app takes 95 seconds over USB, 108 over Wi-Fi. You watch every step of it.
The part other tools leave to you. iPASide re-signs before the 7-day expiry, so the app just keeps opening.
The reason most people reach for a sideloader — so it's a first-class feature here, not a checkbox.
.deb. It unpacks the archive and finds the dylibs itself.arm64, arm64e or armv7, read from the binary — no guessing which package was right..deb packages and loose .dylib files, as many as you want, by drag and drop.These are Apple's rules, not iPASide's. No sideloader can lift them, and any that claims otherwise is selling you something.
then the app stops opening until it's re-signed. Leave the daily refresh on and you won't notice.
new apps per week. iPASide shows how many slots you have left instead of letting Apple refuse you mid-install.
Widgets, keyboards, share sheets and watch apps are stripped. The app works; its extras don't.
Purchased copies are encrypted and can't be re-signed by anyone. iPASide tells you before it starts.
A paid account lifts the first three. iPASide supports one — a free account is what's been tested.
Every release publishes a SHA256SUMS.txt. Here is the hash for the current one, and the one line that checks it:
published alongside each release on GitHub
(Get-FileHash .\iPASide-Setup-x64.exe -Algorithm SHA256).Hash
Or skip all of it and build from source — every step is scripted, including zsign.
pymobiledevice3 — pairing, lockdown, installation_proxy, AFC. USB and network transports.s2k derivation, two-step trusted-device 2FA.zsign, built from source: SHA-256 CodeDirectory, canonical DER entitlements, dylib injection.doctor, sideload, refresh, inspect and two dozen more, all with --json.
No. iPASide re-signs the app with a certificate Apple issues to your own Apple ID — the same mechanism Xcode uses to run an app you wrote. The phone stays completely stock.
No, a free Apple ID is enough. Apple gives free accounts a 7-day signature instead of a year and will not provision app extensions, which is why iPASide tracks the expiry and re-signs before your apps stop opening.
It authenticates directly with Apple from your own machine, over a connection verified against Apple's own certificate authority. It is never passed on a command line and never written to disk. There is no iPASide server for it to go to, and the code that handles it is in the open.
64-bit Windows 10 or 11, and Apple's Apple Devices app or iTunes — that is what lets Windows talk to an iPhone over USB. If it is missing, iPASide says so plainly and offers to fetch Apple's installer for you, checking that Apple actually signed it before running anything.
Yes, once Wi-Fi sync is enabled for the device. If iPASide reports your phone as USB-only while it is plainly on the same network, restart Bonjour Service and Apple Mobile Device Service — Apple's service discovers network devices when it starts and does not always notice a change made afterwards.
No. Those copies are FairPlay-encrypted and cannot be re-signed by anyone. iPASide detects it while reading the file and tells you, instead of failing halfway through with something cryptic.
Free provisioning is a documented Apple feature, and iPASide uses the same endpoints Xcode does — but it is not an Apple-sanctioned client, and only Apple can say what they act on. If that risk matters to you, use a spare Apple ID. That is the honest answer rather than a reassuring one.
MIT licensed, no paid tier, no account, no telemetry. The catch is Apple's limits above, and that the installer is not yet code-signed, so Windows will warn you the first time.
Windows only today. The desktop shell and the engine were both chosen with a macOS port in mind, and the platform-specific work that remains is written down in the repository rather than promised here.
MIT licensed · no account · no telemetry · no “pro” tier