How to Keep Slack Active in the Browser

Slack in a browser tab at app.slack.com runs the full client and follows the same presence rule as the desktop app: you are green for 10 minutes after your last click, keystroke, or scroll inside the Slack tab. The browser adds two dot-killers of its own on top of the usual sleep and lock flips: the tab can be silently unloaded to save memory, and the whole browser can close or restart. This page covers the tab-specific rules and their fixes. Where the on-device options run out, one alternative is Slack Green, the server-side tool we build, compared honestly at the end alongside everything else in how to keep Slack active.

What counts as input in a tab

The timer counts interaction with the Slack tab: typing, clicking, scrolling, switching channels while that tab has your input. Typing into another tab of the same window does not count; the input goes where the focus is, and Slack cannot see anything outside its own page.

The tab does not need to stay focused. After input, you keep the full 10 minutes even if you work in another tab or app, because the tab stays connected in the background. What it cannot survive is being unloaded, which is the next section.

The two browser traps

Tab discarding. Chrome's Memory Saver and Edge's sleeping tabs unload background tabs after a while, and an unloaded Slack tab is a disconnected Slack: the dot dies regardless of the timer. The tab still sits in the tab strip looking normal, which makes this the least visible cause on the whole diagnosis list. The fix is one setting:

• • Chrome: Settings, Performance, add app.slack.com to "Always keep these sites active".
• • Edge: Settings, System and performance, add app.slack.com under "Never put these sites to sleep".

The browser itself. Quitting the browser, a crash, an update restart, or closing the profile ends the session's connection and the dot with it. The desktop app quietly wins here: it reconnects on launch and does not share its process with fifty other tabs.

Tab or desktop app

Same timer, different failure modes. The tab needs no install and no admin rights, which makes it the route on locked-down and borrowed machines, and it is the surface where the whole extension category operates. The app survives tab hygiene, memory pressure, and browser restarts. If you may not install anything, the tab is the answer; if you can, the app plus the desktop guide removes the browser traps entirely.

What resets the timer in a tab

Browser questions people search

Does Slack work in the browser without the app? Yes. app.slack.com is the full client, including huddles in Chromium browsers. Some workspace admins disable browser access, which shows as a redirect to the app.

Does a background tab keep me active? For 10 minutes after your last input in it, yes. Past that you are away like on any desktop, and a discarded tab drops you regardless.

Does closing the tab set me to away? Within moments, unless another signed-in session is active. Slack shows the most active session across devices, per how Slack decides you are away.

Is the browser status different from the desktop app status? No. Same dot, same 10-minute rule. Only the failure modes differ: tabs get discarded, apps get closed less.

Why am I away while the Slack tab is open? Ten input-free minutes, a discarded tab, or system sleep. The full cause-by-cause walkthrough is in Slack keeps showing away while working.

The short version

The tab is the full Slack with the full 10-minute timer; input must land in the Slack tab, and the timer survives backgrounding but not discarding. Except app.slack.com from Memory Saver or sleeping tabs, keep the machine awake, and feed the timer by hand, extension, hardware, phone, or a server. The server route is Slack Green, and the full comparison with costs is in how to keep Slack active.