The Wake Lock API (also known as Screen Wake Lock) is a web standard that allows websites to request the device's screen to stay on, preventing it from dimming or locking. This is especially useful for applications like recipe viewers, presentation tools, video players, navigation apps, or any scenario where users need the screen to remain active without constant touch interaction. It's part of the W3C Screen Wake Lock specification.

Supported browsers (as of 2025):

• Google Chrome 84+ (Desktop & Android)
• Microsoft Edge 84+
• Opera 70+
• Samsung Internet 14+
• Safari 16.4+ (iOS & macOS)
• Firefox — partial support (behind flags on some versions)

Note: The API requires a secure context (HTTPS or localhost) to function. Most modern Chromium-based browsers fully support it.

Yes, keeping the screen on will consume more battery power than allowing it to sleep normally. The screen is one of the most power-hungry components of any device. Use Wake Lock judiciously — only when the user genuinely needs the screen to stay on (e.g., reading a long article, following a recipe, or during a presentation). Our tool displays battery information so you can monitor your device's power status while testing.

Browsers automatically release the Wake Lock when the page becomes hidden (e.g., switching to another tab, minimizing the browser, or locking the phone). This is an intentional design to conserve battery. When you return to the page, you can re-acquire the lock. Our tool offers an "Auto re-acquire on tab switch" toggle that automatically requests a new lock when visibility is restored.

Absolutely! Wake Lock API is fully supported on Android (Chrome, Edge, Samsung Internet) and on iOS 16.4+ (Safari). In fact, mobile devices benefit the most from this API since screen timeout settings on phones are often short (30 seconds to 2 minutes). This tool works great on mobile browsers — test it on your phone to see it in action.

The Wake Lock API behavior is not directly affected by charging status — the lock works regardless of whether the device is plugged in. However, some operating systems may have their own power management policies. For example, many devices already keep the screen on while charging. The API gives web developers explicit control regardless of charging state.

Before the Wake Lock API, developers used hacks like playing an invisible video or using excessive JavaScript timers to keep screens awake. These methods were unreliable, wasteful, and often blocked by browsers. The Wake Lock API is the proper, standards-compliant way — it's more efficient, respects user intent, and integrates with the operating system's power management. Always prefer the Wake Lock API over legacy hacks.

Generally, no explicit permission prompt is shown to users for the Screen Wake Lock API, unlike APIs such as Geolocation or Notifications. However, the browser may silently deny the request in certain conditions (e.g., low battery, power-saving mode, or if the user has disabled the feature). Always handle promise rejections gracefully, as demonstrated by this tool's error handling.

Common use cases:

• 📖 Recipe & cooking apps — keep screen on while hands are messy
• 📊 Presentation tools — prevent screen sleep during slideshows
• 🗺️ Navigation apps — keep map visible while driving or walking
• 🎥 Video players — maintain screen during long playback sessions
• 📚 Reading apps — avoid interruptions during long-form reading
• 🎮 Game controllers — web-based games needing sustained screen activity