Device guide
Keep the screen on in Linux
Chrome and Edge 84 and later, and Firefox 126 and later, can keep a Linux screen on while the AwakeTab tab is visible. The browser asks your desktop not to blank the screen. Whether that holds depends on the desktop, which has to honour the GNOME SessionManager or freedesktop ScreenSaver inhibit. We have not yet recorded real-device results on Linux.
- Chrome and Edge 84 or later
- Firefox 126 or later
- Your desktop must honour the inhibit
- Device results not yet recorded
Try it
Start a session, switch tabs, then come back and watch the pill.
Set it up on Linux
Two steps start a session. The next two tell you whether your desktop is listening, and what to try if it is not.
Step 1: Open AwakeTab in Chrome, Edge or Firefox and press Start
Browser › awaketab.comPick a length, or leave it running until you stop it, then press Start. The pill says "Screen awake" once the browser has granted the lock.
Step 2: Keep the window visible
No minimising while it runsMinimise the window or switch tabs and the browser releases the lock. The pill changes to "Paused — tab hidden", and AwakeTab asks again when you come back.
Step 3: Wait past your blank time once
Leave the machine alone for longer than the blank delayThe pill reports what the browser answered, not what the desktop did. So the first time, stay away for longer than your screen-blank delay. If the screen stays on, your desktop honours the request.
Step 4: If it still blanks, try the other engine
Chrome or Edge, then FirefoxOn Linux, Chrome and Edge ask over D-Bus, through GNOME SessionManager or the freedesktop PowerManagement and ScreenSaver services. Firefox is a separate engine with its own code, so it is worth one try.
Which Linux setups keep the screen on
These results come from Chromium’s and Firefox’s source and browser documentation, checked 26 September 2026. They depend on your desktop, and no Linux device run is recorded yet.
What turns the screen off anyway
If the screen still blanks, one of these is usually the reason.
- A desktop that ignores the request The pill can say "Screen awake" while the desktop blanks anyway, because the browser cannot make it listen.
- A hidden tab A minimised window or another tab in front lets the display go. Bring it back and AwakeTab asks again.
- A low battery in Firefox At 5 % or less and not charging, Firefox refuses the lock. Keep the screen on in Firefox
- A screen lock with its own schedule A managed machine can lock the screen on its own timer, separate from display sleep. Lock screen versus display sleep
Questions
Does it work on Wayland and X11?
Those are display protocols, not desktops, so they are not what decides it. What matters is whether your desktop implements GNOME SessionManager or freedesktop ScreenSaver inhibit, because that is what the browser asks.
The pill says Screen awake, but the screen still blanked. Why?
The pill shows the browser's answer. The browser granted the lock, but your desktop did not keep the screen on. Try the other engine, or change your desktop's own blank delay for this session.
Can AwakeTab stop by itself on low battery on a Linux laptop?
In Chrome and Edge, yes: they share the battery level with pages, so you can pick a level in AwakeTab's settings. Firefox removed that API in version 52, so there it cannot.
Have you tested this on a Linux machine?
Not yet. The support rows come from browser documentation and source code. Real-device results will appear in the table once they are recorded.