Slack in the browser: what the free tier covers

Anyone looking for the price of Slack in a browser will come away empty handed, and that is the correct result. There is no browser edition to buy. The pricing page lists four plans, Free, Pro, Business+, and Enterprise+, and the client used to reach the workspace is not part of the calculation.

That leaves two questions worth answering separately. The first is what the free plan actually covers, since that is where the real boundary sits. The second is what it costs to stop treating Slack as a tab and give it a window of its own, which is a different budget entirely and is frequently confused with the first. Both are answered below from the published figures.

The browser is not a pricing tier

Slack charges per member per month. The rate is identical whether that member signs in through Chrome, through Safari, or through the desktop application. There is no browser discount and no application surcharge.

The reason is structural: the plan attaches to the workspace and its members, not to the software. Someone who belongs to a paid workspace gets paid features regardless of how they open it. Someone on a free workspace stays inside free limits even after installing the official client on a new machine. Entitlement follows membership.

Once that is settled, the budget splits cleanly. Slack costs what it costs based on headcount and plan, and nothing about the choice of client moves it. Separately, turning a daily tab into a standalone window costs somewhere between nothing and the price of a tool, depending on the route chosen. Resolving the fixed side first makes the second decision much smaller than it looks.

There is exactly one thing the browser route saves: disk space, since nothing gets installed. That is worth noting for completeness and worth nothing on an invoice.

Two free limits, and they are not the same limit

The free plan is described as free forever, at zero cost. The conditions attached to it are specific, and the most important pair is frequently collapsed into one number.

The first limit is on visibility:

90 days of message history Messages are saved and searchable for 90 days. Upgrade to access the previous 12 months messages. Source: slack.com

The second limit is on existence. The data retention row of the same comparison table states that on the free plan, data is deleted after one year, while paid plans retain it indefinitely by default with the option to configure that.

Ninety days is the window that can be read and searched. One year is the window in which the material still exists at all. Anything older than ninety days is hidden but recoverable by upgrading, up to the previous twelve months. Anything past the one year mark is gone and upgrading does not bring it back.

This distinction decides how much time a team actually has. A group running on the free plan with a vague intention to pay "if this becomes important" is working against a one year clock, not a ninety day one. For a project that will produce a decision record worth keeping, that is the number to plan around.

What the free plan covers

The rest of the free conditions are published in the same comparison table, and they apply identically in the browser.

Item	Free plan
Message history	90 days
Data retention	Up to one year, then deleted
App integrations	Up to 10
Huddles	One to one only
Slack Connect	One to one direct messages only
Workspaces	1
Posting permissions	Restricted in the general channel only
Customer support	24 hours a day, seven days a week

Reading down the column, the free plan is not a stripped back product. Channels, search, audio and video clips, canvases, lists, and Workflow Builder are all present. Security items such as two factor authentication and session duration are present. What is constrained is quantity: how long, how many, how many people.

Two of those rows cause most of the friction in practice. Huddles being one to one means the first attempt to pull a third person into a call fails, which tends to happen at exactly the wrong moment. The ten app ceiling sounds generous until it is set against a directory that lists more than 2,600 apps, at which point it becomes a queue rather than a limit.

The support row surprises people in the other direction. Free workspaces still get around the clock access to customer support. What the paid plans add is a first response time commitment, four hours on Pro and Business+, and priority handling on Enterprise+. Free does not mean unsupported.

What the paid plans cost

Prices are shown in the local currency of the page. Viewed with Japanese pricing, the figures are as follows, before any applicable consumption tax.

Plan	Billed monthly	Billed annually
Free	0 yen	0 yen
Pro	1,050 yen per user per month	925 yen per user per month
Business+	2,160 yen per user per month	1,920 yen per user per month
Enterprise+	Contact sales	Contact sales

Moving to Pro removes exactly the rows that were constrained by quantity. Message history becomes unlimited, the app ceiling disappears, huddles work in groups, and Slack Connect expands to dedicated channels with up to 250 organisations. The shape of the product does not change; the ceilings do.

The pricing page also carries a promotional rate, fifty percent off for three months on Pro and Business+. The conditions are printed alongside it: the purchase must be made online within seven days of the team being created, it does not apply to annual plans or to Enterprise+, it is limited to one use per customer, and standard pricing resumes after the discount period. An established workspace considering an upgrade will not qualify, so the undiscounted numbers are the honest basis for comparison.

The billing unit is per user, which is the figure most often misread. A team of five on annual Pro pays 4,625 yen per month, not 925. The gap between monthly and annual billing on Pro is 125 yen per user per month, which is 1,500 yen per user per year, so a ten person team saves 15,000 yen annually by committing up front. Annual billing fixes the headcount for a year, so it repays a stable team and penalises one that is still changing shape.

Before committing to any of this, there is a short test that settles whether an upgrade is needed at all, and it takes four questions. Has anyone needed a message older than ninety days in the last month? Has the app directory refused an eleventh integration? Has a huddle failed because a third person tried to join? Is anyone working with an outside company through anything other than a one to one direct message?

A team that answers no to all four is not being constrained by the free plan today, and paying now buys headroom rather than a fix. A team that answers yes to one of them has a specific line item to justify, which is a much easier case to make than a general sense that the paid version would be better. The one exception is the retention rule, which does not announce itself: nobody notices data being deleted after a year until they go looking for it, so a workspace that holds decisions worth keeping should be counted as a yes even if nothing has gone wrong yet.

This also sets the order of operations correctly. The plan decision is about how a team works and how long its records matter. The client decision, browser or application or standalone window, is about how one person opens the thing every morning. Solving the second does not reduce the first, and stalling on the first is not a reason to leave the second unaddressed.

Giving Slack its own window costs nothing to start

This is the other budget, and it is much smaller than most people expect. There are three routes that involve no payment at all.

The first is Slack's own desktop application, distributed at no cost. It requires macOS 13 or later and application version 4.44 or later. Where the machine meets those conditions and software installation is permitted, this is the obvious first attempt, and it also lifts the browser restriction on notifications reaching only the workspace currently open.

The second is Add to Dock in Safari, a macOS feature that produces a standalone window with a Dock icon. The third is Chrome's option to install a page as an application, which does the same thing through Chrome's menu. Neither costs anything, because both are parts of software already installed.

Only the fourth route involves money: a general purpose site to app tool that wraps any URL into a standalone Mac application. Tools in this category divide into one time purchases and subscriptions, and prices differ. This is the only layer where comparison shopping has any point, and the Pricing page sets out what that looks like. Checking whether the first three routes already solve the problem is the faster move, since two of them take under a minute to test.

The costs that never appear on an invoice

Paying nothing is not the same as spending nothing, and the unpriced costs are the ones that quietly decide whether a free route survives contact with daily use.

The first is method sprawl. Slack through the official client, an internal timesheet through Safari, a client dashboard through Chrome, and each one is created differently, updated differently, and removed differently. The bill stays at zero while the number of procedures to remember climbs to three.

The second is retrieval time. Opening Slack twenty times a day and hunting through a tab strip for it each time produces a cost that appears on no pricing page, which is precisely why it goes unexamined for years.

The third is collateral damage during cleanup. Clearing browser storage to fix an unrelated site signs the user out of Slack at the same time, because the session lives in that same storage. A separate window keeps unrelated maintenance from reaching it.

The fourth applies to teams rather than individuals. Every method that a person invents for themselves is a method nobody else can be told to follow. When a new colleague asks how to get the internal console onto the Dock, an answer that consists of three different procedures depending on the site is not an answer. Consistency has a value that shows up as time, not currency.

What to change first

Check the two free plan limits against actual use, since ninety days and one year decide more than any other number here. Then try the free routes in order: the official client if the machine allows it, Add to Dock or install as an app if not. Only count the number of other daily sites that need the same treatment afterwards, because that number, not the Slack invoice, is what decides whether a tool such as Kagemusha is worth paying for. A quick look at the Supported services list against a real set of tabs answers it faster than any estimate.