Skip to content
AwakeTabOpen timer
Learn

How AwakeTab is checked

Every support claim on AwakeTab rests today on four kinds of source: browser documentation, the wake lock code inside the browser engines, vendor support pages and automated tests. None rests on a real-device run yet. The device matrix at the end of this page lists the planned cases. Each one says "Results pending" until it is recorded, and no page cites a device before then. Sources last checked 26 September 2026.

Sources checked Saturday, 26 September 20264 min readBy Soubhik Biswas

What does each claim rest on today?

Each fact comes from one of four places, and its page says when it was last checked.

  • Browser documentationVersion floors come from MDN's browser compatibility data and each vendor's release notes.
  • Engine source codeWhy a lock is refused comes from reading the wake lock code in Chromium, WebKit and Firefox.
  • Vendor support pagesOperating-system behaviour, such as Low Power Mode's 30-second Auto-Lock, comes from Apple, Microsoft and Google.
  • Automated testsThe tool runs in a browser against a simulated wake lock that can grant, refuse or take back the lock. Other tests fail if a claim the source check removed comes back.

When a browser changes, the matrix and the affected pages change with it, and the change is dated in the changelog.

What did the source check find?

The version floors hold: Chrome and Edge 84, Opera 70, Samsung Internet 14, Firefox 126 and Safari 16.4. iPhone and iPad Home Screen web apps need iOS or iPadOS 18.4. In every engine the lock lasts only while the tab is visible, and a browser refuses it or takes it back for four reasons only: the page is hidden or inactive, a Permissions-Policy blocks it, Safari has had no recent tap, or Firefox is at 5 % battery or less and not charging. A page served over plain http has no wake lock at all, which is "unsupported" rather than a refusal.

Good to knowBattery savers are not on that list. Chromium's code has no check for Android Battery Saver, Windows Energy saver or Chrome's Energy Saver, and WebKit has no check for Low Power Mode. A saver can still shorten the operating system's own timeout.

What did the check correct?

The 26 September 2026 check found claims the sources did not support. They are fixed on every English page and in the translations.

  • Battery saversNo engine checks them. Every page that said otherwise was corrected.
  • Caffeine for MacIt holds a macOS power assertion. The F15 key press belongs to Caffeine for Windows.
  • NoSleep.jsIt uses the Wake Lock API where present, and a video only as a fallback.
  • PowerToys AwakeIt has a "Keep screen on" switch, and it does not work at the lock screen.
  • macOS idle sleepWhile Chrome holds the display on, the Mac does not idle-sleep, per Apple's IOKit documentation.
  • Names and versionsWindows 11 24H2 renamed Battery saver to Energy saver, and iPadOS 26 removed Split View.

What still needs a real device?

No document or source file can answer these. Until the device run, no page claims an answer.

  • Safari under iPhone Low Power ModeWebKit has no check for it, but only a device shows whether the screen stays on.
  • Operating-system saversWhether Android Battery Saver or Windows Energy saver dims or turns off a display the browser asked to keep on.
  • Edge and Samsung Internet efficiency modesHow their own power features treat a visible tab.
  • The video fallback on current iOSIt has not been re-checked.
  • The floating window with its tab hiddenWhether it keeps the screen on while its tab is hidden.
  • Mac clamshell modeWhat each MacBook needs to stay awake with the lid closed.

A recorded row carries the date, the exact OS and browser version, the power state, the outcome and an evidence note.

Sources

All checked 26 September 2026.

What this page does not tell you

A source check says what the browser is built to do, not what your device did today. Every browser still releases the lock when the tab is hidden, a closed laptop lid usually still sleeps the computer, and the device matrix below is still pending.

Try it hereTry itStart a session, switch tabs, then come back and watch the pill. Ends at … if you start now.Start a 15-minute session

Questions

No. It means our own run on that device has not been recorded yet. The support claim itself comes from browser documentation and engine source.

Soubhik Biswas · Builds AwakeTab. Sources checked Saturday, 26 September 2026. About AwakeTab