Slack Workspace Limits (2026): What the Free Plan Really Restricts

Slack Free has no message limit. It has a 90-day window, which is a different thing, and the change happened in September 2022.

Four years later, roughly half the comparison charts on the internet still say “10,000 messages.” Some of them were updated this year. They copied the wrong source and nobody checked. If you are making a decision about where to host a community, start by throwing out everything you think you know about Slack’s free tier.

Quick answer

Limit	Free	Paid (Pro and up)
Message and file history	Last 90 days visible	Full history
Permanent deletion	Anything over 1 year, gone	No
Message count	No limit	No limit
Members per workspace	No published cap	No published cap
Channels per workspace	No published cap	No published cap
Apps and integrations	10	Unlimited
Huddles	1:1 only (2 people)	Up to 50, 25 on video
Slack Connect (external)	1:1 DMs only	Channels
Guest accounts	Not available	Available
File size	1 GB per file	1 GB per file
Channel name prefixes	6	99

Source for all of it: Slack’s usage limits for free workspaces and feature limitations on the free version. Check those two pages rather than any chart, including this one.

What actually changed in 2022, and why the wrong version stuck

Before 1 September 2022, a free Slack workspace showed you the most recent 10,000 messages and 5 GB of uploads. Hit either and older content vanished from view.

Slack replaced both with time. Now you see the last 90 days of messages and files, no matter how many or how large. Slack’s argument at the time was that most active free teams would end up with more accessible history, not less, and for a busy community that is plainly true: a 500-person Slack burns through 10,000 messages in a fortnight.

For a quiet workspace it is a straightforward downgrade. A small team that sent 10,000 messages over three years used to be able to read all of them. Now they can read the last quarter.

Both things are true at once, which is probably why so much coverage garbled it. What is not defensible is a chart published in 2026 that still lists “10,000 messages” as a current Slack limit.

The one-year cliff nobody mentions

Here is the part that should change your decision, and it is missing from most articles that get the 90 days right.

Messages older than 90 days are hidden, not deleted. Upgrade and they come back instantly. That is a genuinely reasonable free tier.

But since 26 August 2024, Slack permanently deletes customer data — messages and files — more than one year old from free workspaces, on a rolling basis. That deletion is not reversible. Upgrading in month fourteen will not return month one.

So a free Slack community is a rolling one-year archive with a three-month reading window. If anything valuable is accumulating in there — decisions, answers, onboarding threads, the good explanation someone wrote once — it has a hard expiry date. Plan for that or move it somewhere else, but do not assume you can pay later and recover it.

What Slack does not limit

This is where Slack differs sharply from WhatsApp or a basic Telegram group, and it is worth saying plainly because people arrive expecting a member cap.

There is no member limit. Slack’s paid-versus-free FAQ answers the question about team and channel size with a single word: “Nope.” Enterprise Grid gets marketed at up to 500,000 people, but Grid is a federation of many workspaces under one organisation, not the ceiling of your single workspace.

There is no published channel limit. Slack’s own guidance for large teams goes further and argues there is “really no such thing as too many channels,” noting that big organisations often run two to three times as many channels as people. Whatever your Slack problem is, it is not that you ran out of room.

The free plan’s constraints are all about time and capability, never about size. That inversion is the single most useful thing to understand about Slack pricing, and it means the usual community-scaling advice — split the group, cap the room, start a second one — does not apply here at all.

The capability limits that actually bite a community

Ten apps sounds generous until you count. A moderation bot, a welcome bot, a Google Calendar integration, an RSS feed, a GitHub connector, and a form tool is six, and you have not added anything distinctive yet. Community workspaces hit this ceiling far faster than small teams do, because a community runs on automation that a ten-person startup does not need.

Huddles being capped at two people on Free rules out the casual group call, which for a distributed community is often the whole point.

Slack Connect on Free is 1:1 DMs only. If you were planning to run shared channels with partner organisations, sponsors, or a sister community, that is a paid feature, and existing Connect channels disconnect if you downgrade into Free.

Guest accounts do not exist on Free. Everyone you invite gets full workspace access, which means you cannot bring in a speaker, a contractor, or a partner for one channel.

What to do about it

1. Decide whether history is actually your product

For a lot of communities it is not. A support Slack where the same six questions get asked weekly loses nothing to a 90-day window. A research or open-source community where the archive is the value loses everything.

Be honest about which you are before you spend money. Paying per member per month to retain messages nobody rereads is the most common Slack mistake I see communities make.

2. Get canonical knowledge out of chat

If the answer matters, it should not live only in a Slack thread — that is true on every plan and the 90-day window just makes the consequence arrive sooner. A docs site, a GitHub wiki, a Notion page, anything with a stable URL.

The practical version: when a good answer appears in a channel, someone writes it down somewhere permanent that day. Communities that do this find the 90-day limit stops mattering almost entirely.

3. Check whether you qualify for a discount before you assume Pro pricing

Slack has historically offered nonprofit discounts and free-plan upgrades to qualifying organisations, and pricing has moved more than once — the Pro tier last changed publicly in September 2022. Do not budget from a number in an article. Open slack.com/pricing, and if you are a nonprofit or an open-source project, ask before you pay list.

4. Solve the invite problem, because Slack never did

This is the one that has nothing to do with plan limits and everything to do with running a public community on Slack.

Slack has no public join link. There is no equivalent of a Discord invite or a t.me username. An admin sends email invitations one at a time, or you allow anyone with a given email domain to join themselves — which works for a company and is meaningless for a community open to the public.

That gap is why Slackin existed: a small self-hosted app that put a signup form in front of a workspace and auto-invited whoever filled it in. Thousands of open-source communities ran it. Then Slack restricted the invite APIs and token types it depended on, and it stopped working. It is archived. Deploying it in 2026 is not an option, and the full history plus the current alternatives is worth reading if you are staring at a dead Slackin badge in a README right now.

The honest free replacement is a page you control with a Google Form behind it and a human sending invites in batches. It works. It does not scale past a few dozen a week, and every organiser who has done it will tell you the same thing about how quickly that gets old.

5. Screen at the door, since you are inviting manually anyway

There is one upside to Slack’s missing invite link: nobody can join your workspace without a human deciding they should. Discord and Telegram admins pay real money for that property.

If you are already the bottleneck, make the bottleneck useful. Ask one question that a spammer will not bother answering. Verify the email. Say plainly who the community is for. You are spending the effort regardless — you may as well get a filter out of it.

A practical decision table

Situation	What to do
Read that Slack Free caps at 10,000 messages	Ignore it — that ended in 2022
Need history older than 90 days	Upgrade, or get knowledge out of chat
Anything in the workspace over a year old matters	Export or upgrade now, before deletion
Out of app slots at 10	Cut feeds and duplicate bots before paying
Need shared channels with partners	Paid — Free is 1:1 DMs only
Inviting people by hand, one at a time	Put a signup page in front of it
Worried about workspace size	Do not be. There is no member cap.

How Inviter fits (optional)

Inviter is a hosted front door for a Slack workspace you already run: a public page, applications with approval, email verification, country allow and deny rules, captcha, plus events and Stripe ticketing. It handles the intake Slack never gave you a way to do, and you stay on Slack. Free to start; Pro is $19.99/month or $191.90/year. See Inviter for Slack, pricing, and /communities/slack.

A form and a recurring calendar reminder to send invites will also work, and for a community getting five signups a week it is the right answer. The point is that Slack will not do it for you and has shown no sign of intending to.

The free plan is fine. The gaps are elsewhere.

Ninety days of history, ten apps, and no group calls is a reasonable trade for free software, and Slack Free is more generous than its reputation on the things communities actually stress: members and channels are uncapped, which is more than WhatsApp or a Telegram supergroup can say.

What you should worry about is the one-year deletion clock quietly running on everything worth keeping, and the fact that in 2026 the most-cited numbers about Slack’s free tier describe a plan that has not existed since 2022. Read Slack’s own two help pages. They take four minutes and they are right, which puts them ahead of most of the competition.