Mozilla is now taking steps to close that gap on the desktop. As spotted by Neowin and WindowsReport in a newly opened Mozilla Bugzilla tracking ticket, Firefox engineers have begun early work on a feature that will lock open Private Browsing windows on desktop systems and require operating-system authentication before the session can be viewed or resumed.
Inside Mozilla Bugzilla Ticket 2082413
The foundational blueprint for this capability sits in Mozilla’s public issue tracker under Bug 2082413, a meta-ticket titled [meta] Lock private browsing windows filed by engineer Martin Raiber under the Firefox:: Private Browsing component.
In the ticket's user story, Raiber notes that users frequently leave private browsing windows open when stepping away from their hardware, exposing sensitive sessions to family members or coworkers on shared computers. To address this, the proposed desktop enhancement is designed to automatically lock active Private Browsing windows under three specific system events:
- When the computer enters system sleep.
- When the screensaver activates.
- When a system logout occurs.
Once a Private Browsing window is locked by one of those triggers, resuming the session will require OS-level re-authentication. In the Bugzilla description, Mozilla lists examples of system authentication mechanisms such as Touch ID, Face ID, or a standard OS PIN or password. Because the prompt mentions those only as examples of operating-system authentication, the exact prompt a user sees will ultimately depend on the underlying desktop OS and hardware—such as Windows Hello PIN or biometric prompts on Windows 10 and Windows 11 PCs, or Touch ID and system passwords on macOS.
It is important for desktop users to keep expectations grounded in what the ticket actually shows right now:
- Early Development Status: The Bugzilla entry is marked
NEWwith its target Firefox version, specific desktop platform fields, priority, and release milestone all currently listed as unspecified. - Modular Engineering Work: As a
metatracking bug, Ticket 2082413 already depends on nine separate open sub-bugs (2082415,2082417,2082421,2082462,2082463,2082467,2082471,2082474, and2082475), indicating that Mozilla is breaking the engineering work down into component tasks across its codebase. - No Release Timeline Yet: Mozilla has not announced a target release version, a Nightly testing date, or whether users will also get an on-demand manual lock button or toggle alongside the automatic system triggers.
Section Summary: Mozilla has opened meta-bug 2082413 with nine dependent sub-bugs to build automatic locking for desktop Firefox Private Browsing windows upon sleep, screensaver activation, or logout, gated behind OS-level authentication. No release milestone or platform-specific rollout schedule has been assigned yet.
Catching Up to Mobile Browsers and macOS Safari
If locking private tabs behind a biometric prompt or PIN sounds familiar, that is because mobile browsers—and one major desktop competitor—have already paved this road.
Mozilla explicitly notes in Bug 2082413 that this functionality is already present on Firefox for Android and is now being brought to desktop. On Android, Firefox users can enable a setting that hides private tabs behind the phone or tablet's configured screen lock—whether that is a fingerprint, facial recognition, or a device PIN—whenever they switch away from private browsing.
On the desktop side, Apple’s Safari has offered native Locked Private Browsing since Safari 17 on macOS Monterey, Ventura, Sonoma, and newer releases. Examining how Apple’s implementation works on macOS provides a useful point of comparison for the problem Mozilla is trying to solve, even though Mozilla has not confirmed whether Firefox will mirror every detail of Safari’s interface:
| Feature / Behavior | Firefox Desktop Proposal (Bug 2082413) | Firefox for Android (Existing) | Apple Safari on macOS (Safari 17+) |
|---|---|---|---|
| Current Availability | Early development (NEW meta-bug; no release date) | Available now in release builds | Available now (macOS Monterey 12 and later) |
| Automatic Lock Triggers | System sleep, screensaver activation, or system logout | Switching away from private tabs or backgrounding the app | Screen lock, sleep, screensaver, display off, or window inactivity in background/minimized state |
| Manual Lock Control | Unconfirmed in public meta-ticket | Handled via tab switching / app state | Yes (Window > Lock All Private Windows) |
| Unlock Method | OS-level re-authentication (e.g., PIN, password, or supported biometrics) | Android device biometric prompt or PIN | macOS password or Touch ID |
As Neowin and WindowsReport both point out, bringing native private-window locking to desktop Firefox would give Windows users a built-in privacy safeguard that remains conspicuously absent from standard desktop installations of Google Chrome and Microsoft Edge on Windows. While mobile editions of Chromium browsers have experimented with or rolled out biometric locks for Incognito and InPrivate tabs on phones, Windows desktop users who rely on Chrome or Edge still have no native browser-level lock that shields an open private window while leaving standard browser windows accessible.
Meanwhile, the desktop private-lock initiative arrives alongside other recent improvements to Firefox's privacy and enterprise toolsets. Mozilla's official support documentation notes that starting in Firefox version 151, Private Browsing mode gained the ability to instantly clear all data from a current private session without closing the entire browser. WindowsReport also notes that Mozilla has been expanding Firefox’s broader capabilities with on-premises management options for Firefox Enterprise and an experimental Smart Window AI tab for webpage summaries.
Section Summary: Firefox already locks private tabs on Android, and Apple’s Safari locks private windows on macOS both automatically and manually. Bringing this capability to desktop Firefox will give Windows users a native layer of session protection that desktop Chrome and Edge currently lack.
Session Privacy vs. Local Screen Privacy: What a Lock Actually Does
To understand why a feature like this matters—and where its limits lie—it helps to separate post-session data cleanup from live-session physical security.
According to Mozilla’s official Firefox Help documentation, standard Private Browsing is designed to prevent the browser from saving your visited pages, form entries, passwords, cookies, and temporary site data once you close all Private Browsing windows. It also enables Enhanced Tracking Protection and blocks third-party tracking cookies by default. However, Mozilla is equally candid about what Private Browsing does not do:
- Downloaded files remain on disk: If you download a PDF, archive, or installer while in a Private Window, the file stays in your computer’s storage even though it is cleared from Firefox’s internal download manager list after the session ends.
- Bookmarks are kept: Any webpage you bookmark inside a Private Window remains saved in your normal bookmark library.
- Network visibility is unchanged: Private Browsing does not mask your IP address or encrypt traffic beyond standard HTTPS, meaning websites, your internet service provider, or an enterprise IT administrator on a corporate or school network can still see the domains you visit.
A locked Private Browsing window addresses a completely different threat model: local "shoulder-surfing" and shared-profile snooping.
Consider a household PC where a single Windows user account is shared by family members, or a small business workstation where a user runs a regular Firefox window alongside a Private Browsing window used for personal banking, medical portals, or administrative logins. If the computer goes to sleep or triggers a screensaver without enforcing a full Windows lock screen—or if the user unlocks the PC to show a colleague something in a regular desktop window—an unlocked Private Browsing window sitting in the background is only an Alt + Tab away from exposure.
By intercepting access to the Private Browsing window after sleep, screensaver activation, or logout and demanding OS-level authentication before rendering the tabs, Firefox will let users keep long-running private sessions alive without leaving them exposed to the next person who touches the mouse. Importantly, locking the window pauses access and lets you resume the session after authenticating; it does not wipe your open tabs the way closing the window does.
Section Summary: Standard Private Browsing only clears history and cookies after the window closes. The proposed lock feature protects active, open private sessions from local onlookers after a PC sleeps or starts a screensaver, allowing the owner to re-authenticate and resume without losing open tabs.
Practical Guidance for Windows Users Right Now
Because Bug 2082413 is still in early development and has not shipped in Firefox Release, Beta, or Nightly builds with a documented user toggle, Windows users should not rely on Firefox to hide open private windows when stepping away from their desks today.
Until Mozilla finishes engineering the nine dependent tasks and ships desktop private-window locking, here is the most reliable way to protect sensitive browsing sessions on Windows 10 and Windows 11:
- Lock Windows Immediately When Stepping Away: Press
Windows Key + Levery time you leave your desk. This forces immediate OS-level re-authentication via Windows Hello PIN, fingerprint, facial recognition, or account password before anyone can view any open application. - Require Sign-In After Sleep or Screensaver: Verify under Settings > Accounts > Sign-in options that Windows is configured to require a sign-in set to Every time when the PC wakes from sleep, and ensure the
On resume, display logon screencheckbox is ticked in Windows Screen Saver Settings if you use a screensaver. - Use Separate Windows User Accounts on Shared PCs: If multiple people use the same computer at home, give each person a dedicated standard Windows user account rather than sharing a single desktop profile.
- Clear or Close Private Sessions When Finished: When you no longer need the active session, close all Private Browsing windows—or use Firefox’s built-in session-clearing control available in Firefox 151 and newer—so cookies and session history are purged immediately.
Should Mozilla also add an optional idle timer or a manual keyboard shortcut to lock Private Browsing windows on demand—similar to Safari's Lock All Private Windows command on macOS—when this feature lands on Windows? Share how you manage private sessions on shared PCs in the WindowsForum community discussion below.