iPhone Pairing File Guide: Make, Import and Fix It (2026)

ByScarlet iOS Team Updated on

A pairing file is a small file that lets an app on your iPhone talk to the iPhone’s own developer services, the same way a trusted computer does. SideStore, StikDebug, LiveContainer, Feather, KSign and several other sideloading apps need one, and “invalid pairing file” is one of the most common reasons they stop working. This guide explains what the file is, the ways to make one, how to put it into an app, why it stops working and how to keep it safe. Last checked: 2 November 2026, against the GitHub pages of iloader, idevice_pair and StikDebug and the SideStore documentation.

The Short Version

  • A pairing file (usually a .plist or .mobiledevicepairing file) is a record that your iPhone trusts a “computer”. Apps use it to reach the iPhone’s developer services without a cable.
  • It is specific to one device. A file made for one iPhone does not work on another.
  • The easiest way to make and place one is iloader on a Mac, Windows or Linux computer. idevice_pair and Impactor can do it too.
  • It stops working when you reset the iPhone or change its passcode, often after an iOS update, and sometimes at random. The fix is to make a new one.
  • Treat it like a password: never share it or download one someone else made.

What a Pairing File Is

When you plug an iPhone into a computer and tap Trust, the two devices exchange keys and the computer keeps a “pair record”. With that record, the computer can use the iPhone’s developer services: installing apps, reading logs, starting a debugger. A pairing file is a copy of that record that you hand to an app on the iPhone itself. The app then acts as the trusted computer, talking to the iPhone over a local loopback connection (often through a small VPN app such as LocalDevVPN), so it can do those jobs with no computer around.

The StikDebug guide describes the file as “device-specific”, and the StikDebug README lists it as either .plist or .mobiledevicepairing. There are two kinds: the classic lockdown pairing, which works on every iOS version, and remote pairing (RPPairing), which needs iOS 17.4 or later.

Which Apps Need One

  • SideStore, to install and refresh apps on the device.
  • StikDebug, to enable JIT for emulators and other apps.
  • LiveContainer when it is installed together with SideStore.
  • Feather and KSign, which can use it for installing.
  • Smaller tools such as Protokolle, Antrag and SparseBox, which idevice_pair also lists.

Scarlet iOS does not use a pairing file. It installs apps with its own certificate and needs no computer setup at all.

How to Make a Pairing File

All three computer tools below are free and open source. Download them only from their GitHub pages (iloader also from iloader.app); the iloader page warns not to download it from any other site. Before you start, set a passcode on the iPhone and keep it unlocked on the home screen while pairing.

Option 1: iloader (easiest)

  1. On Windows, install iTunes first (it brings the USB driver). On Linux, install usbmuxd if it is missing. A Mac needs nothing extra.
  2. Install iloader from its GitHub releases or iloader.app and open it.
  3. Connect the iPhone with a USB cable and tap Trust if it asks.
  4. Click Manage Pairing File.
  5. Click Place next to each app you want to pair, for example StikDebug or SideStore. “Pairing file placed successfully!” appears in green.

When iloader installs SideStore or LiveContainer + SideStore for you, it places the pairing files automatically, so you only need these steps to replace an old one or to add another app.

Option 2: idevice_pair

idevice_pair (by jkcoxson, version 1.1.0) is a small tool that only makes pairing files. Pick the device, choose Lockdown or Remote pairing, click Create, then either Save to file or click an app’s name to write the file straight into that app. It can also check that a new file actually works, which helps when an app keeps rejecting yours.

Option 3: Impactor

Impactor (formerly PlumeImpactor) has a Utilities page that appears when a device is connected. From there it can install SideStore or LiveContainer, re-trust the device and place a pairing file into a supported app.

Without a computer (newer devices only)

StikDebug has a built-in pairing menu (Settings, then Pair a Device), but its guide says this only works for devices on iOS/iPadOS 27 or later and for Apple TV. On older versions you still need a computer once.

How to Import It Into an App

If you used iloader’s or idevice_pair’s “place” option, you are done. If you saved the file instead, send it to the iPhone (AirDrop, Files or iCloud Drive) and open the app:

  • StikDebug: tap Select Pairing File and pick the file.
  • SideStore: it asks for the file on first launch and when the old one stops working.
  • Feather / KSign: both have an option to import a pairing file; follow the app’s own instructions, as the menu names change between versions.

Then turn on the loopback VPN the app uses (LocalDevVPN for StikDebug and SideStore) and stay on Wi-Fi.

Why a Pairing File Stops Working

  • Passcode change or reset: the StikDebug guide warns the file expires if you reset or change the passcode.
  • iOS update or device reset: SideStore’s documentation says the file “may expire” after you update or reset the device, and that it also happens “at random times”, which is on Apple’s side.
  • Wrong device: a file from another iPhone, or from before a restore, will not work.
  • VPN off: errors such as “heartbeat” or “connection dropped” in StikDebug often mean the VPN is off or you are not on Wi-Fi, not a bad file.

The fix is almost always the same: connect the iPhone to the computer, keep it unlocked, and make and place a fresh file. In iloader, clear the old one with Delete Stored Pairing first, then tap Trust on the iPhone again. For SideStore-specific messages such as “The current pairing file is invalid”, see our SideStore errors guide.

Is a Pairing File Safe?

It gives the holder the same access a computer you trusted has, so treat it like a password. Do not post it in a Discord chat or upload it to a website “for help”, and never use one that somebody else made for you; it would not work anyway, since it is tied to your device. If you think a file has leaked, removing trust resets it: on the iPhone go to Settings > General > Transfer or Reset iPhone > Reset > Reset Location & Privacy, which makes every computer ask for Trust again. Then make a new file.

Pairing File or Scarlet?

A pairing file is part of the do-it-yourself route: your own Apple Account, your own certificate, a one-time computer setup and a 7-day refresh on a free account, which SideStore can do on the device. Scarlet iOS skips all of that: no computer, no Apple Account and no pairing file, because it provides the certificate. That certificate is shared, so Apple can revoke it. Our free sideloading tools compared guide shows both routes side by side. To try Scarlet, see how to install Scarlet iOS or start from our Scarlet iOS install page.

FAQ

Where is the pairing file on my computer?
The computer keeps its pair records in its own lockdown folder, but you do not need to look for it. iloader and idevice_pair make and export the file for you.

Can I use one pairing file for two iPhones?
No. Each file is made for one device.

Do I need a new file after every iOS update?
Not always, but often. If an app reports an invalid or missing pairing file after an update, make a new one.

Does a pairing file need a paid developer account?
No. Making one only needs a computer the iPhone trusts. The apps that use it are still signed with your own Apple Account, with Apple’s usual limits for free accounts.

Similar Posts