Discord Age Verification and Teen by Default: What Server Owners Have to Do

Most of the coverage of Discord's age verification has been written for users: what the facial scan does, what happens to your ID, whether you can refuse. Very little of it has been written for the person who has to run a server through it.

That is the gap this post fills. The short version: almost nothing about your server is being taken away, but several things you built on top of Discord's defaults are about to behave differently, and a few of them are things you set up years ago and forgot.

What is actually happening

In February 2026 Discord announced that it would move its global user base to teen-by-default settings. Every account is treated as a teen account, with the stricter safety configuration that implies, unless the person behind it completes age assurance.

The rollout was scheduled for early March, met a large amount of pushback, and was delayed to the second half of 2026 so Discord could add verification methods and publish more detail about its vendors. In the meantime it is already live where the law requires it: the UK and Australia, with Brazil following.

Verification itself happens one of two ways today: an on-device facial age estimation, or a government ID submitted to a third-party vendor. A credit card option has been mentioned as a future addition. Discord's own figure is that over 90% of users will never see a prompt, because their age is inferred from signals the platform already has.

What changes inside your server

Four things, in rough order of how likely they are to catch you out.

1. Age-restricted channels stop being a formality

Marking a channel age-restricted used to be a click and a confirmation dialogue. Under the new model it is the mechanism that decides who can see the channel at all, and unverified or teen-classified accounts are kept out of it rather than warned about it.

That cuts both ways:

• If you have adult content in an unmarked channel, you are relying on a gate that no longer exists, and you are now the one at risk rather than Discord.
• If you marked channels age-restricted out of caution and they are really just swearing and horror screenshots, you are about to hide a chunk of your server from a slice of your members for no reason.

Go through your channel list once and mark what genuinely needs it, unmark what does not. This is the single highest-value hour you can spend on this whole topic.

2. DM-based flows get less reliable

Teen-default accounts have tighter control over DMs and friend requests from people they do not share a mutual with. Anything in your server that depends on reaching a member in their inbox becomes less dependable:

• Verification bots that DM a code.
• Warning DMs, which is a setting in Dashboard > Moderation > General worth checking.
• Ticket systems that continue a conversation privately.
• Mod teams that reach out to a member after an incident.

None of that stops working, but the failure rate rises, and a silent failure is worse than a loud one. This is a good moment to make sure your important flows have an in-server path as well as a DM path. Fenrai's verification gate runs in a channel with an ephemeral confirmation for exactly this reason: nothing has to arrive in a DM for a member to get in.

3. Stages and voice get quieter

Speaking on stage is one of the capabilities restricted for unverified accounts. If you run community stages, expect a period where some of the people you invite up cannot accept, and expect not to be told why. Have a fallback channel.

4. Your new-member funnel changes shape

A teen-default account is a more restricted account, which means the friction of joining your server goes up slightly for everyone. Small changes in friction show up in retention, not in message counts, and they show up about a week later. If your day-1 and day-7 cohort numbers dip in the month the rollout lands in your region, this is a candidate explanation before you go rewriting your welcome message. The retention cohort post covers how to read that chart properly.

What to do this month

A short list. None of it takes long.

1. Audit your age-restricted channels. Mark what needs marking. Unmark what does not.
2. Verify your own account if you administer any age-restricted content, before you are locked out of your own settings at a bad moment.
3. Check that your mods can verify too. A mod who cannot open the age-restricted channel cannot moderate it.
4. Give every DM-dependent flow an in-server fallback, starting with verification and tickets.
5. Write one line in your rules channel telling members what is happening, in your own words. The people who will be most upset are the ones who find out from a modal.
6. Do not build your own age gate. Asking members to post an ID to a mod channel or a ticket is a data protection liability you do not want, and it is worse than what you are objecting to.

The objection, stated fairly

There is a real criticism here and pretending otherwise is not useful. The EFF's position is that mandatory verification concentrates exactly the kind of identity data that leaks, and that the argument is not hypothetical given the breach of a third-party support vendor that exposed government ID images.

You cannot resolve that as a server owner. What you can do is keep your own hands out of it: use Discord's mechanism, mark your channels honestly, and store nothing yourself. That way your members' exposure is whatever Discord's exposure is, and no larger.

What this does not change

Worth saying plainly, because there is a lot of noise:

• Your bots keep working. Age assurance is about accounts and content access, not the bot API.
• Your moderation rules keep working. Account age, time since join, roles, activity windows: all unaffected.
• It is not a shadow ban. A teen-classified account is a normal member of your server with tighter defaults, not a second-class one, and treating them as suspicious is both wrong and bad for retention.
• It does not make your server safe. Verification says something about age. It says nothing about whether the account is compromised, which is the attack you are far more likely to see. That one is covered in how to stop scam links.

Common questions

Does every Discord user have to verify their age in 2026? No. Discord's stated figure is that over 90% of users will have their age determined from existing signals with no action required. Verification is prompted for the rest, and for anyone who wants access to age-restricted content or settings.

Will my server lose members because of teen-by-default? Some servers will see a small dip, mostly in servers built around age-restricted channels. Watch day-7 retention by joining week rather than message volume, which moves for a dozen unrelated reasons.

Do I have to mark my server age-restricted? Only if its content genuinely requires it. Marking a whole server or channel out of caution hides it from members unnecessarily. Marking nothing while hosting adult content puts the responsibility on you.

Can I verify members myself instead? You can gate access with a verification role, and you should, but that is a different thing from age assurance and it is not a substitute. Never collect identity documents yourself.

When does the global rollout actually happen? Discord has pushed it to the second half of 2026 and has not committed publicly to a precise date. It is already enforced where local law requires it, so the practical answer depends on where your members are.

What is the one thing to do if I do nothing else? Audit which of your channels are age-restricted and make that list honest. Everything else follows from it.