Signed vs unsigned IPSW describes whether Apple currently authorizes a specific firmware build for installation on a specific device. A signed IPSW can normally pass Apple's restore verification; an unsigned IPSW is rejected by the standard restore process. This signing status is separate from whether the firmware is a public release or a beta.
Before you download or restore an IPSW, check the signing status for your exact iPhone or iPad model. If the target build is unsigned, do not assume that a third-party tool can simply “sign” it again: advanced blob-based restores only work in specific device and firmware conditions.
In this article
Part 1. What Do Signed and Unsigned IPSW Mean?
An IPSW is an Apple firmware package used to install or restore iOS or iPadOS on a compatible device. The file is device-specific, so the correct model and firmware build matter before you start any restore.

Signed IPSW
A signed IPSW is a firmware build that Apple is currently authorizing for the matching device. During a restore, Apple's signing service must approve the requested build. If the build is still signed and the file matches your device, the standard restore workflow can proceed.
Apple may authorize more than one build or software branch at the same time, and signing availability can differ by device. That is why it is better to check the current status than to assume that only one version is signed.
Unsigned IPSW
An unsigned IPSW is a firmware build that Apple is no longer authorizing through the normal restore process for that device. Finder, the Apple Devices app, or iTunes will reject a standard restore to an unsigned build.
“Unsigned” describes restore authorization. It does not automatically mean that the IPSW is a beta, modified, corrupted, or malicious file. A genuine Apple firmware file can become unsigned after Apple closes its signing window.
Part 2. Signed vs Unsigned IPSW: Quick Comparison
| Question | Signed IPSW | Unsigned IPSW |
|---|---|---|
| Is Apple authorizing a normal restore now? | Yes, for the matching device/build. | No. |
| Can standard Finder / Apple Devices / iTunes restore work? | Normally, yes. | No, the normal signing check rejects it. |
| Can it be a beta build? | Yes, while Apple is still authorizing that beta. | Yes, after the beta signing window closes. |
| Is it the normal choice for a restore or downgrade? | Yes, when the target build is available for your device. | No. Only advanced, device-specific exceptions may exist. |
| Do saved SHSH/APTicket files matter? | Not for a normal signed restore. | They may be required for advanced restore methods, but blobs alone are not enough. |
Part 3. How To Check If an IPSW Is Still Signed
Signing status changes over time, so check it immediately before you restore. The status must match your exact device model and target build.
- Identify your exact device model. An IPSW for a different device cannot be used just because the iOS version number is the same.
- Check a live firmware index. A current signing-status service such as IPSW.me separates signed and unsigned builds by device.
- Confirm the status again before restoring. A signing window can close after you downloaded the file, so the file's presence on your computer is not proof that Apple still authorizes it.

If the target build has already become unsigned, choose a currently signed version unless you already have the exact advanced restore prerequisites described in Part 5.
Part 4. How To Install a Signed IPSW Safely
For a normal computer-based restore, Apple currently directs Mac users to Finder and Windows users to the Apple Devices app. iTunes remains relevant on Windows systems without Apple Devices and on older macOS setups. A factory restore erases the device, so back up before you begin.
Step 1: Back Up Your iPhone or iPad
Create a current backup before a restore or downgrade. You can use Apple's backup workflow or follow this iPhone/iPad computer backup guide.

Step 2: Turn Off Find My Before a Factory Restore
Open Settings, tap your name, choose Find My > Find My iPhone, and turn it off when the restore workflow requires it. You may need your Apple Account password.

Step 3: Verify the IPSW and Start the Restore
Confirm that the IPSW matches your exact device and is still signed. Connect the device, then open Finder on Mac or Apple Devices on Windows. Use iTunes only if that is the supported app for your older setup.
If you are manually selecting a downloaded signed IPSW, use the file-selection restore workflow supported by your desktop app; the familiar manual method uses Option on Mac or Shift on Windows while choosing Restore iPhone. Keep the device connected until the restore completes.

Prefer a guided signed downgrade?
Dr.Fone - System Repair (iOS) provides a guided iOS upgrade/downgrade workflow that lists available firmware and verifies the downloaded firmware before installation. Its official downgrade guide also asks you to back up first because a downgrade normally erases device data.
For the current workflow, see the Dr.Fone iOS upgrade/downgrade guide.
Part 5. Can You Install an Unsigned IPSW?
Not through the normal Apple restore path. Once Apple stops authorizing the target build, Finder, Apple Devices, and iTunes cannot perform a standard restore to that unsigned IPSW.
An advanced restore may be possible only for specific devices and firmware combinations when you already have matching signing tickets (commonly called SHSH or SHSH2 blobs) and can satisfy the rest of the restore chain. This is not the same as making Apple sign the IPSW again.
Why an Unsigned Restore Is Device-Specific
- The signing ticket must match: the saved APTicket/SHSH data is tied to the device and target firmware.
- Nonce conditions matter: advanced restores can depend on identifiers and nonce values such as ECID and APNonce.
- SEP and baseband compatibility matter: a valid blob does not guarantee that the required restore components are compatible.
- Hardware and exploit support matter: some methods are limited to particular chip generations or device states.
- The command is not universal: FutureRestore options vary by device, target firmware, and restore method.
The official FutureRestore documentation explicitly requires matching signing tickets and device-specific conditions. If you already saved blobs, use the dedicated SHSH blobs downgrade guide to understand the compatibility chain before attempting anything.
What If You Do Not Have Matching SHSH Blobs?
For a normal restore or downgrade, choose a firmware version that is still signed for your device. Do not rely on a generic “IPSW signing tool” or a one-size-fits-all command that claims to turn any unsigned IPSW into an installable build.
Part 6. Are Beta IPSWs Signed? Which Route Should You Choose?
Yes, a beta IPSW can be signed while Apple is actively authorizing that beta build. Later, Apple can stop signing it. In other words, beta/public describes the release stage, while signed/unsigned describes whether the restore is currently authorized.
| Your situation | Best next step |
|---|---|
| The target IPSW is signed | Use the signed restore workflow after backing up. |
| The target IPSW is unsigned and you have no matching blobs | Choose a currently signed build instead. |
| The target IPSW is unsigned and you already saved matching blobs | Check the device-specific advanced restore requirements before proceeding. |
| You want to install or leave a beta | Check the signing status of the exact beta/public build first; do not assume beta means unsigned. |
If your goal is simply to move to an available signed iOS version without manually managing firmware files, Dr.Fone - System Repair (iOS) offers a guided upgrade/downgrade path for supported signed firmware.
Conclusion
The most important question is not whether you can download an IPSW file, but whether Apple is still authorizing that exact build for your device. A signed IPSW is the normal path for restoring or downgrading. An unsigned IPSW is rejected by standard restore tools, and advanced blob-based methods work only in specific compatibility conditions.
Check signing status immediately before you restore, back up your device first, and treat beta status separately from signing status. If you want a guided route, use an available signed firmware rather than trying to force an unsigned build onto an unsupported restore path.
FAQs About Signed and Unsigned IPSW Files
-
1. Can I sign an unsigned IPSW myself?
No. You cannot make Apple reopen a signing window with a generic signing tool. Advanced restore methods may reuse previously saved device-specific signing tickets in compatible setups, but that is not the same as re-signing the IPSW. -
2. Can SHSH blobs restore any unsigned IPSW?
No. The blob must match the device and target firmware, and the restore still depends on compatible nonce, SEP/baseband, hardware, and tool conditions. A saved blob by itself does not guarantee a successful downgrade. -
3. Is a beta IPSW always unsigned?
No. A beta IPSW can be signed while Apple is authorizing that beta. It becomes unsigned only after Apple stops approving restores to that build. -
4. Does restoring a signed IPSW erase my data?
A factory Restore erases the device and installs software again. Back up first. In troubleshooting situations where Apple offers both Update and Restore, Update is normally the less destructive option to try before Restore.

