<p>When Apple stops signing a version of iOS, the IPSW that was perfectly restorable yesterday becomes a brick overnight. The signing window — Apple's silently enforced restore deadline — is one of the most misunderstood mechanics in the Apple ecosystem. Most status pages tell you <em>what</em> is signed. This article explains <em>why</em>, <em>how long</em>, and what actually happens upstream on Apple's signing server when an IPSW passes or fails verification.</p> <blockquote> <p><strong>Direct Answer:</strong> Apple usually keeps only the latest version of iOS fully signed. The immediately previous version typically stays signed for roughly 1–3 weeks after a new release, but the duration is variable and never publicly fixed. Once Apple stops signing a build, restoring that IPSW on iPhone or iPad returns Error 3194.</p> <p>If you've just wanted a one-line answer, that's it. If you want to understand the plumbing, keep going.</p> </blockquote> <h2>How Apple's Signing Window Actually Works</h2> <p>Every time you put an iPhone into Recovery Mode or DFU Mode and press Restore in Finder, iTunes, or the Apple Devices app, your computer connects to Apple's Tiny TSS (signing server) endpoints. Your computer sends:</p> <ol> <li>Your device's DeviceIdentifier (hardware model + board ID).</li> <li>A nonce derived from the device.</li> <li>A hash of the IPSW you want to install.</li> </ol> <p>TSS checks Apple's internal allow-list for that exact build. If matched, TSS returns an SHSH blob — a signed cryptographic ticket bound to your specific device, that build, and a nonce window. iBoot validates the blob before allowing the boot image to load. If TSS rejects the request — typically because Apple has removed the build from its allowed list — your restore fails almost immediately and the client surfaces Error 3194 (or an Apple Devices equivalent).</p> <p>This is why no two devices get the same blob — Apple signs per Device Identifier — and why an IPSW that Apple has stopped signing becomes impossible to restore on stock firmware, regardless of where you download it from.</p> <table> <thead> <tr> <th>Why Apple enforces a window</th> <th>Practical effect</th> </tr> </thead> <tbody> <tr> <td>Push users to patched builds</td> <td>Closes attack surface for disclosed iOS vulnerabilities.</td> </tr> <tr> <td>Limit fragmentation</td> <td>Keeps the active iOS install base predictable for app/SDK testing.</td> </tr> <tr> <td>Control restore paths</td> <td>Apple decides exactly what can be reinstalled on each iPhone, iPad, or Apple TV model.</td> </tr> <tr> <td>Reduce exploit economics</td> <td>A short window shrinks the value of leaked internal builds.</td> </tr> </tbody> </table> <p>There is no contractual duration. Apple chooses the date each time, and never pre-announces it.</p> <h2>How Long Apple Signs Each iOS Version (Typical Range)</h2> <p>While there is no fixed schedule, the pattern is stable enough to be useful as a guide:</p> <table> <thead> <tr> <th>Version status</th> <th>Typical signed window</th> </tr> </thead> <tbody> <tr> <td>Latest stable release</td> <td>Signed indefinitely until the next major release ships.</td> </tr> <tr> <td>Second-latest stable (N-1)</td> <td>~7–21 days after the new release, variable.</td> </tr> <tr> <td>Older stables (N-2 and earlier)</td> <td>Stop signing within hours of the new release.</td> </tr> <tr> <td>Beta builds</td> <td>~1–2 weeks per beta; signing turns off when the next seeds.</td> </tr> <tr> <td>Security-only revisions</td> <td>Sometimes re-signed briefly for vulnerability remediation.</td> </tr> </tbody> </table> <p>⚠️ These ranges are approximate and variable. Treat them as planning heuristics, not guarantees. Always verify current status on a live signing page before attempting restore.</p> <p>In practice, the "N-1" window rarely exceeds three weeks and often closes sooner. Apple has, on rare occasions, briefly re-signed an older build during a security emergency — but you should never plan around an event Apple does not pre-announce.</p> <h2>When This Works / When This Won't</h2> <h3>When This Works</h3> <ul> <li>Restoring the latest signed iOS on any supported iPhone or iPad.</li> <li>Downgrading from beta to the latest stable, as long as Apple still signs that stable.</li> <li>Briefly reinstalling a previous build (N-1) within the typical N-1 window above.</li> <li>Reinstalling the same version Apple just shipped (effectively a clean re-flash).</li> </ul> <h3>When This Won't Work</h3> <ul> <li>Restoring or downgrading to any build Apple has removed from the signing server.</li> <li>Using a saved SHSH blob on modern AES-protected devices — TSS still rejects past blobs absent an exploit path.</li> <li>Restoring across device families (e.g., an iPad IPSW on iPhone hardware) at the TSS layer.</li> <li>Skipping the model's correct IPSW selection for board variants.</li> </ul> <h3>⚠️ Common Mistakes</h3> <ul> <li>Confusing "IPSW downloaded" with "IPSW installable." A file on disk is not the same as a TSS-permitted restore.</li> <li>Trusting cached "Signed" statuses from non-authoritative sources. Always verify on a live page.</li> <li>Assuming the boot loop fix of "just restore" — if the build is unsigned, restore will fail with 3194 long before it could help.</li> </ul> <h2>What Happens When the Window Closes</h2> <p>When Apple closes signing for a build:</p> <ol> <li>TSS stops accepting signing requests for that exact Build Number + Device Identifier combination.</li> <li>Restore attempts in Finder, iTunes, or the Apple Devices app fail immediately with Error 3194, 14, or 35, depending on where validation breaks.</li> <li>The build cannot be installed on stock iPhone, iPad, or Apple TV firmware on that execution path.</li> <li>Anyone already running the build continues to function, but re-flashing or moving devices off that build later becomes harder.</li> </ol> <p><strong>What you lose when the window closes:</strong></p> <ul> <li>Ability to restore that build via stock restore.</li> <li>Ability to return from beta to older stable without waiting for a compatible signed build.</li> <li>Reverse-from-troubleshooting options (a stuck iPhone can no longer be re-flashed to that exact version).</li> </ul> <h2>Requirements Before You Start</h2> <p>Before relying on a signed IPSW, confirm:</p> <ol> <li>You have the correct IPSW for your iPhone model — board IDs vary, especially on iPad Pro and iPhone Pro lines.</li> <li>You are using a supported client: Finder (macOS Catalina or later), Apple Devices (Windows 10/11), or iTunes 12.6.5.x for legacy restores.</li> <li>Your USB cable supports data, not charge-only.</li> <li>You have a clean restore target — restoring erases the device.</li> <li>You have access to either an iCloud backup or a local Mac/PC backup if you want to recover data.</li> <li>For a downgrade, that the version you want is still listed as Signed on a status surface, not just "released."</li> </ol> <p>If any of those are missing, the signed window is the wrong bottleneck — your Error 3194 will be a tool or model mismatch, not Apple.</p> <h2>Compatibility Table — Signing Tools by Platform</h2> <table> <thead> <tr> <th>Platform</th> <th>Tool for restoring signed IPSW</th> <th>Notes</th> </tr> </thead> <tbody> <tr> <td>macOS Catalina or later</td> <td>Finder</td> <td>iTunes removed for iOS restore.</td> </tr> <tr> <td>macOS Mojave and earlier</td> <td>iTunes 12.9.x</td> <td>Legacy path.</td> </tr> <tr> <td>Windows 10 / 11</td> <td>Apple Devices app</td> <td>Successor to 64-bit iTunes.</td> </tr> <tr> <td>Windows legacy</td> <td>iTunes 12.6.5.3</td> <td>Only branch that still supports .ipsw drag-restore.</td> </tr> </tbody> </table> <p>Compatibility note: On Apple Silicon Macs, all restore paths now go through Finder. Windows ARM devices should use Apple Devices.</p> <h2>Direct Troubleshooting Cross-Reference</h2> <p>When status surfaces say Signed but restore still fails, the issue is rarely the signing window. Check:</p> <ul> <li>Recovery Mode vs DFU Mode for your exact model — wrong mode causes silent 3194–4014 conflicts.</li> <li>Error 3194 — TSS rejection (most often "unsigned for you").</li> <li>Error 4013 / 4014 — cable, USB controller, or kernel-level restore failure; signing-independent.</li> </ul> <p>If status surfaces say Unsigned, no tool-side workaround produces a stock restore. The only legal paths involve waiting for Apple to re-sign the build (rare) or letting the device sit on its current iOS version.</p> <h2>Frequently Asked Questions</h2> <h3>1. How long does Apple typically sign an iOS version?</h3> <p>Apple usually keeps only the latest build fully signed. The immediately prior version is typically signed for roughly 1–3 weeks after the new release, but the exact window is variable and never contractually fixed.</p> <h3>2. Why does Apple stop signing older iOS versions?</h3> <p>Stopping signing pushes users onto recently patched builds, limits ecosystem fragmentation, and lets Apple control the exact firmware each iPhone or iPad can be restored to.</p> <h3>3. What is the Apple signing server (TSS)?</h3> <p>TSS is Apple's signing endpoint. iTunes, Finder, or Apple Devices connects to it during restore; if Apple still signs that build for your Device Identifier, TSS returns a per-device SHSH2 blob and the restore proceeds.</p> <h3>4. What is Error 3194 and does it mean the IPSW is unsigned?</h3> <p>Error 3194 is the canonical indicator that Apple's TSS server refused the version. In most cases it means the IPSW is unsigned for your device. See Apple Support article 108396 for the official reference.</p> <h3>5. Can an iOS version be re-signed after Apple stops signing it?</h3> <p>Rarely. Apple has reopened signing for specific older builds during major security incidents, but you should not plan around it — once closed, an IPSW is not restorable on stock firmware absent a workaround.</p> <h3>6. What is the difference between signed and unsigned IPSW?</h3> <p>A signed IPSW can be restored on supported iPhone or iPad hardware. An unsigned IPSW is rejected by Apple's TSS server during restore and produces errors like 3194.</p> <h3>7. How can I check if an iOS version is still signed?</h3> <p>Check /signing on IPSW.io or a similar signing-status aggregator. The listing shows Signed / Unsigned / (rarely) Re-signed and the date the status was observed.</p> <h3>8. Does the signing window differ by device model?</h3> <p>Sometimes. Apple may keep older iPad or iPhone variants signed briefly longer, and Apple Watch builds follow a separate cadence. Always verify on the signing page filtered by model.</p> <h3>9. How do I know when Apple will stop signing an iOS version?</h3> <p>There is no public schedule. Watch IPSW.io signing updates, Apple Developer release notes, and trusted aggregators. Apple does not pre-announce unsigning.</p> <h3>10. Will saving an SHSH blob let me install unsigned iOS later?</h3> <p>On most modern, AES-protected devices, no — TSS rejects past SHSH blobs absent a targeted exploit. Blobs are not a general-purpose downgrade indirection in 2026.</p> <h3>11. Are iOS betas signed differently than stable releases?</h3> <p>Yes. Each beta has its own ~1–2 week window; signing closes as soon as the next beta seeds, on a cadence separate from the public release cadence.</p> <h3>12. Which Apple tool should I use to restore a signed IPSW?</h3> <p>On macOS Catalina or later: Finder. On modern Windows: the Apple Devices app. On legacy macOS/Windows: iTunes — specifically 12.6.5.x for drag-and-drop IPSW restores.</p> <h3>13. Does the signing window apply to Apple Silicon Macs restoring iPhone IPSW?</h3> <p>No — Apple Silicon Macs simply use Finder instead of iTunes. The signing mechanics are identical to any other host.</p> <h3>14. Is the signing window related to Activation Lock?</h3> <p>Indirectly only. Activation Lock is tied to Find My on the device; signing is a separate, restore-time validation by TSS. Restore will still fail with 3194 if the IPSW is unsigned, regardless of Activation Lock state.</p> <h3>15. Does Apple ever extend the signing window on request?</h3> <p>No. Apple does not accept requests, and the process is fully automated against the per-device allow-list.</p> <h2>Conclusion</h2> <p>The iOS signing window is not a public schedule, a release-date addendum, or a configurable setting — it is Apple's quiet gate that decides which IPSW any given iPhone, iPad, or Apple TV can be restored to on a given day. That gate usually sits at the latest stable release, with the prior version lingering for roughly one to three weeks and everything older closing within hours.</p> <p>Understanding that gate is what turns a confusing "Error 3194" into a clean decision: confirm signing, verify IPSW, then move. IPSW.io's signing status page and our downgrade pillar keep those checks one click away when the next build rolls out.</p>