Comparison
AwakeTab vs nosleep.page
Both are browser tabs that use the Screen Wake Lock API, and both stop when the tab is hidden. Pick nosleep.page if you want one quick timer with nothing to set: 30 minutes, 1 hour, 2 hours or your own length. Pick AwakeTab if you want a status pill that only says "Screen awake" once the browser agrees, an end time on the clock, or an offer to resume after a reload.
On this page
Side by side
Facts about nosleep.page come from its own site, checked 26 September 2026. Where its site does not say, the table says so. Rows marked Same are real ties.
When nosleep.page is the better choice
It is a good page. In these cases we would send you there.
- You want the simplest page nosleep.page asks very little of you: pick 30 minutes, 1 hour, 2 hours or a custom length, and keep the tab in front.
- You do not need status or an end time AwakeTab's pill, end time and resume are extras. If you never look at them, a simpler page does the same job.
- It already works for you Both ask the browser for the same wake lock and both stop when the tab is hidden, so switching will not keep your screen on any longer.
When AwakeTab is the better choice
These are the jobs AwakeTab was built for.
- You want to know it is really working The pill says "Screen awake" only after the browser grants the lock. If the browser refuses, it says "Blocked — here's the fix" and tells you what to try.
- You need to stop at a set time Until a time ends the session at, say, 7:30 AM, so you do not have to work out the minutes. Pick ∞ instead to run until you stop it.
- A reload should not lose your session After a reload, AwakeTab offers to resume with the time you had left.
- Your browser is older On browsers without the Screen Wake Lock API, a tap starts a video fallback and the pill says "Awake via video fallback". It needs this tab visible and uses a little more battery.
- The tab can't stay visible On desktop Chrome and Edge, AwakeTab for Chrome uses Chrome's power setting, so it keeps working with the tab hidden or the window minimised.
If you are a developer
nosleep.page is a page to use, not code to add. To build the same behaviour into your own site, AwakeTab vs NoSleep.js compares the library options and the Screen Wake Lock API guide covers the errors to handle. AwakeTab’s engine, @awaketab/wake, is on the library page; the npm package is coming soon.
What neither can do
Neither keeps the screen on while its tab is hidden. Neither keeps a laptop awake once you close the lid. Neither changes your status in Teams or Slack. On a phone, neither can keep another app lit, since the phone shows one app at once. Which browsers support the wake lock, and from which version, is set out in the wake lock browser support matrix.
Try it
Start a session, switch tabs, then come back and watch the pill.
Questions
Is nosleep.page the same thing as NoSleep.js?
No. nosleep.page is a website you open and use. NoSleep.js is a JavaScript library, last released in December 2020, that developers add to their own sites. If you build sites, the AwakeTab vs NoSleep.js page compares the libraries.
Can I keep both open at once?
You can, but only the tab in front holds the screen. A browser gives the wake lock to a visible page and takes it back from a hidden one, so a second tab behind the first adds nothing. Pick one and keep it in view.
Why does AwakeTab ask me to tap Start on an iPhone?
Safari grants a wake lock only after a recent tap on the page. That applies to any site using the Wake Lock API. After the first tap, AwakeTab starts, and the pill says "Screen awake" once Safari confirms.