SHSH Blobs Explained for Non-Technical Users
An SHSH blob is a small saved record of Apple’s authorization for your specific device to install one specific iOS build, captured while that build was still signed. On their own, they don’t let you install anything — they’re a saved permission slip, not a firmware file. What they can enable, combined with additional tools beyond Finder or iTunes, is restoring to that exact build again later even after Apple stops signing it for everyone else. They cannot get you onto a version you never had a saved blob for, and they don’t work like a universal downgrade key.
What a blob actually is, in plain terms
When your device restores or updates through Finder, Apple Devices, or iTunes, it briefly contacts Apple’s signing server, which returns a signed authorization specific to that exact device and that exact build. An SHSH blob is a saved copy of that authorization.
Think of it less like a file and more like a receipt proving Apple once said “yes” to this specific combination of your device and this specific iOS build. The receipt itself doesn’t contain the iOS software — you’d still need the actual IPSW file separately.
For the underlying mechanics of what “signed” means and why Apple closes windows at all, see what IPSW signing means and why Apple stops signing firmware.
What blobs can and can’t do
| Can | Can’t |
|---|---|
| Prove your device was once authorized for a specific build | Authorize a build you never had a blob saved for |
| Potentially enable a restore to that build later, with additional tools | Work like a normal Finder/iTunes restore on their own |
| Be saved in advance, before a signing window closes | Be retroactively created after the window already closed |
| Apply to the exact device they were saved for | Transfer to a different device, even the same model |
Why “SHSH2” specifically, not just “SHSH”
You’ll see both terms used. SHSH2 is the current generation of this mechanism, used since Apple strengthened the original SHSH system. If you’re reading anything current about blobs, it’s almost certainly referring to SHSH2 — the original SHSH format is effectively obsolete on modern devices and iOS versions.
Do you need to do anything with blobs right now?
For the vast majority of readers, no. Blobs only matter if:
- You’re actively trying to downgrade to a version Apple no longer signs, and
- You (or a tool acting on your behalf) saved a blob for that exact device and build while it was still signed
If you’re downgrading to a version that’s currently signed, you don’t need blobs at all — a standard restore through Finder or Apple Devices works without them. See downgrading iOS without losing data for the standard path.
What actually using a saved blob involves
Being upfront about this: using an SHSH2 blob to restore to an unsigned build is not something Finder, Apple Devices, or iTunes can do on their own. It requires additional third-party software designed specifically for this purpose, combined with the saved blob and the matching IPSW file.
This guide doesn’t walk through that process. It sits outside what a general audience needs, and some of the surrounding tooling and communities blur into territory that isn’t consistent with Apple’s terms of service. If you’re at the point of actually needing this, you’re likely already past what a beginner-level explainer can responsibly cover — proceed carefully and understand you’re operating outside Apple’s supported restore paths.
When this won’t work
- You want to downgrade but never saved a blob for the target build. There’s no way to retroactively obtain one once the signing window has closed — blobs can only be saved while a build is still signed.
- You saved a blob for the wrong device. Blobs are tied to one specific device’s hardware identifiers. A blob saved from one iPhone cannot be used on another, even the identical model.
- You’re hoping blobs let you install any past iOS version freely. They only cover builds you specifically saved a blob for, at the time they were signed. There’s no blanket “unlock all history” effect.
- You want a beginner-friendly walkthrough of the actual restore-with-blobs process. As noted above, this involves third-party tooling this guide intentionally doesn’t cover.
- You’re trying to use a blob on a device that’s already on a much newer, incompatible major iOS version. Compatibility constraints beyond just the blob itself can prevent a successful restore in some cross-major-version scenarios.
Frequently asked questions
Do I need to save SHSH blobs for every iOS update, just in case?
Only if you specifically want the option to downgrade to that exact build later, after Apple stops signing it. Most users never touch this and never need to.
Are SHSH blobs the same as a backup?
No. A backup contains your data — photos, settings, app data. A blob contains only Apple’s authorization for a specific device-and-build combination. You need both separately if you want your data preserved after a blob-assisted restore.
Can I check whether I already have blobs saved for my device?
This depends on whether you or a tool you’ve used previously saved any — there’s no built-in iOS feature that tracks this for you. If you’ve never intentionally used a blob-saving tool, you almost certainly don’t have any saved.
Does Apple provide any official way to save or use SHSH blobs?
No. This is entirely outside Apple’s own tools and documentation. Apple’s own restore path (Finder, Apple Devices, iTunes) doesn’t reference or require blobs at all — it works directly against current signing status.
If I have a saved blob, will Finder let me restore to that older version?
No — Finder, Apple Devices, and iTunes only check live signing status and don’t recognize or use saved blobs. Using a blob to restore to an unsigned build requires separate third-party tooling outside those apps.
Is saving or using SHSH blobs against Apple’s terms of service?
Saving a blob itself is just recording data your device already received during a normal, permitted restore. Using third-party tools to install unsigned firmware sits in a greyer area relative to Apple’s intended use of its devices — this is worth understanding before proceeding, and this guide doesn’t take a position beyond describing the mechanism factually.
Do blobs expire?
The saved blob data itself doesn’t expire on its own, but its usefulness depends on compatible tooling and IPSW availability remaining functional over time, which isn’t guaranteed indefinitely.
Why do some people say blobs “don’t matter as much anymore”?
Device security architecture has evolved on newer hardware, which affects how much a blob-based restore path can achieve compared to older device generations. This is a nuanced, hardware-generation-specific topic — if it matters to your specific device, verify current specifics for your exact model before relying on older general information.
This site is not affiliated with, endorsed by, or sponsored by Apple Inc. All firmware download links resolve to Apple’s official servers — we do not host, mirror, or distribute firmware files.
