Instantly verify whether Apple is still signing a firmware for your device. Look up by device identifier or iOS version — before you attempt a restore or downgrade.
Enter your device identifier — e.g. iPhone17,2 — and see every firmware version with its current signing status in one table.
Enter an iOS version — e.g. 18.0.1 — and see which devices Apple is still signing it for, and which have been cut off.
A Signed badge means Apple accepts this firmware right now. Unsigned means restores to that version are no longer possible.
Click the download icon next to any firmware to access its full IPSW restore file details, checksums, and direct download link.
Try: iPhone17,2 · iPad16,1 · iPhone12,1
Could not fetch signing data. Check the identifier and try again.
| iOS Version | Build ID | Status | Release Date | Actions |
|---|
Save blobs now — you can only save blobs for versions Apple is currently signing. Once Apple closes signing (typically 48–72 hours after a new release), it's permanently too late, even with your ECID. Blobs saved while signed can potentially be used later with futurerestore if a compatible exploit becomes available for your chip.
Go to Settings → General → About → scroll to ECID. On Mac, find it in System Information → USB. It's a unique hex or decimal ID tied to your device's chip — required for all blob saving.
Use TSS Saver (web-based, no install needed) or blobsaver (desktop app, auto-saves on a schedule). Both are free and trusted by the jailbreak community. See tools below.
Provide your ECID, device identifier (e.g. iPhone17,2), and optionally your APNonce or generator. For most users, ECID + device model is sufficient to save blobs for all currently-signed versions.
Download the .shsh2 files and back them up in multiple places — cloud storage, external drive, and locally. TSS Saver also stores them server-side under your ECID so you can retrieve them later.
When a compatible exploit exists (e.g. checkm8 for A11 and older), use futurerestore with your saved blobs to restore to the target version. This is the main use case for saved blobs.
These are the most trusted, actively maintained tools in the iOS blob-saving ecosystem.
The most popular web-based blob saver in the jailbreak community. Enter your ECID and device model — TSS Saver fetches and stores your SHSH2 blobs for all currently-signed firmware versions server-side. No installation needed. Retrieve your blobs anytime by ECID.
An open-source desktop GUI app that automatically saves SHSH2 blobs for all currently-signed iOS versions on a recurring schedule — so you never miss a signing window. Stores blobs locally and optionally on a remote server. The set-it-and-forget-it solution.
The advanced command-line tool that actually performs the downgrade using your saved SHSH2 blobs. Requires a compatible bootchain exploit for your chip (e.g. checkm8 for A11 and older). Not a standalone solution — blobs saved with TSS Saver or blobsaver are used here.
⚠ Prerequisite: futurerestore only works if a bootchain exploit exists for your specific chip. For A12+ devices (iPhone XS and newer), no public exploit currently exists. This tool is most useful for A11 and older (iPhone X, 8, and below).
A lightweight command-line utility for manually requesting and saving SHSH2 blobs directly from Apple's TSS servers. Ideal for power users who want to script blob saving, integrate it into automation, or save blobs for specific builds without a GUI.
Every time you restore or update an iPhone or iPad, Apple's servers cryptographically verify the firmware before it's installed. This verification process — called TSS (Tatsu Signing Server) checking — means Apple can control exactly which software versions run on its hardware at any given moment. If Apple is no longer "signing" a version, restoring to it becomes impossible through normal means, even if you have the IPSW file.
An SHSH2 blob is a signed ticket from Apple's TSS servers tied to your specific device's ECID (unique hardware ID) and a particular firmware version. If you save blobs while a version is still being signed, you may be able to use them later with tools like futurerestore — but only if a compatible bootchain exploit exists. Tools like blobsaver can automatically save blobs for all currently-signed versions.
Most jailbreaks target a specific iOS version range. If you accidentally update past the jailbreakable window, you cannot go back once Apple closes signing. Checking signing status before updating lets you make an informed decision — stay on a jailbreakable version or accept you'll lose root access. The window can close within hours of a new release.
A full suite of iOS lookup tools — identify any device, check jailbreak compatibility, and now verify signing status — all in one place.
Instantly decode any iPhone or iPad hardware model identifier. Enter a model string like iPhone17,2 and get the full device name, chip, storage options, release date, and technical specifications in seconds.
Find out exactly which iOS versions are jailbreakable on your device, which tools to use, and whether a public exploit exists right now. Covers checkm8, Dopamine, palera1n, unc0ver, and every major tool from iOS 1 through iOS 18.
Check in real time whether Apple is currently signing a specific iOS firmware for your device — or see which devices a version is signed for. Essential before any restore, downgrade, or jailbreak attempt. Data is live from Apple's TSS servers.
Everything you need to know about iOS signing status, firmware windows, and how to use this tool.
iPhone17,2).Option (Mac) or Shift (Windows) and click "Restore iPhone…", then select your downloaded IPSW. The restore will fail if Apple is not currently signing that version.
18.2.1) is the human-readable release designation you see in Settings. The build ID (e.g. 22C161) is Apple's internal identifier that uniquely distinguishes each firmware build — including carrier variants, regional builds, or re-releases with the same version number but different code.shasum -a 256 filename.ipsw. On Windows: certutil -hashfile filename.ipsw SHA256.
[OS major][OS minor][Revision]. For example, 22C161: