
From Monday 16 November 2026, Discord stops giving bots the details of channels they cannot view. If your bot lists, audits, backs up or logs channels, it will quietly see fewer channels or placeholder ones from that day. That raises three questions: what GET /guilds/{guild.id}/channels will still return, what the Gateway sends instead, and what to change in your code before then.
Quick answer: After 16 November, GET /guilds/{guild.id}/channels returns only the channels your bot can view: channels where it has View Channel, voice channels it is connected to, and categories with at least one such channel inside. Everything else is left out without an error. The Gateway still sends the hidden channels, named ___hidden___ and flagged CHANNEL_OBFUSCATED (1 << 17), with only id, type, position and parent_id real. There is no opt-out; the Private Channel Obfuscation toggle in the Developer Portal only tests the Gateway side early. Detect hidden channels by the flag, never treat a missing channel as deleted, and give the bot View Channel where it needs to look. Since discord.js 14.28.0, a channel picked in a slash command option carries appPermissions, so you can check the bot's access before saving it.
Discord announced the change on 12 August 2026 in its developer change log, tagged as a breaking change for the Gateway and the HTTP API, and says it "becomes mandatory for all bots on November 16, 2026." We checked the entry again on 1 November 2026: the date and the wording have not changed. None of this shows up as an error. A backup just comes out smaller, a log line mentions #___hidden___, and a permission report shows a lone @everyone deny instead of the real role overwrites.
What changes on 16 November
| Where | Until 16 November | From 16 November 2026 |
|---|---|---|
| Gateway: Guild Create, Channel Create, Channel Update | Full data for every channel, including ones the bot cannot view | Channels the bot cannot view still arrive, named ___hidden___, with the CHANNEL_OBFUSCATED flag and other sensitive fields "nulled or reduced" |
GET /guilds/{guild.id}/channels | Every channel in the guild | Channels the bot cannot view are left out of the response |
| Interaction payloads | Full channel data | No change, full channel data |
Discord gives its reason plainly: "Channels a user doesn't have access to shouldn't be accessible or visible to that user. This change is happening to respect the privacy of users. Because it's happening for users this means it will also apply to bots."
Two things the docs do not give you. There is no time of day, only the date. And there is no opt-out: neither the change log nor the API reference mentions a way to keep the old behaviour, and the Gateway docs say obfuscation is "planned to apply to all bots automatically, even when they don't provide this capability." For the wider list of API changes to watch this year, see Discord API changes in 2026.
What GET /guilds/{guild.id}/channels returns after 16 November
You still get a list of channel objects, only fewer of them. The Get Guild Channels reference says the endpoint "will omit any channel your bot doesn't have permissions to view" from 16 November, and defines viewing as "having VIEW_CHANNEL permission on a channel or by being connected to a voice channel." Categories follow their contents: "Channel categories are viewable if any of their child channels are viewable." The Gateway uses the same definition to decide which channels it obfuscates.
| Channel | In the response from 16 November |
|---|---|
| Channel where the bot has View Channel (from its roles, an overwrite or Administrator) | Yes |
| Voice channel the bot is connected to | Yes |
| Category with at least one channel inside that the bot can view | Yes, even without View Channel on the category itself |
| Any other channel or category | No, left out without an error |
| Threads | No, the endpoint "Does not include threads" anyway |
What that means for your code:
- Nothing in the response says a channel is missing. There is no count and no placeholder, and the HTTP API never sets
CHANNEL_OBFUSCATED. To see how many channels the bot cannot view, count the flagged channels the Gateway sent you, as in the code further down. - Every library call built on this endpoint returns the shorter list:
guild.channels.fetch()without an ID in discord.js andGuild.fetch_channels()in discord.py. In discord.js that call does not remove anything fromguild.channels.cache, so the cache keeps the___hidden___copies from the Gateway and holds more channels than the fetch returned. - If a listed channel sits in a category, that category is listed too, because a category with a viewable channel counts as viewable. A category in the list does not prove that the bot has View Channel on it.
- You cannot preview the shorter list. The Private Channel Obfuscation toggle and the Identify capability only change the Gateway; for HTTP, Discord says "There is no early opt-in."
Which bots are affected
Discord's change log names bots that "mirror or audit a server's full channel list, calculate permissions across every channel, or report on channel structure regardless of the bot's own access." It also says: "If your bot only acts in channels it has permission to view, this change does not affect you."
In practice, check these first:
- Backup and server-clone bots that copy channels, topics and permission overwrites.
- Audit and permission-report bots that show who can see which channel.
- Logging bots that post channel creates, renames and permission changes.
- Stats bots, web dashboards and setup wizards that count channels or build a channel picker from the REST list.
A bot with the Administrator permission will not notice anything. Discord's permissions table says Administrator "bypasses channel permission overwrites", so such a bot can view every channel. The bots that lose data are the carefully configured ones that only got the permissions they needed.
Endpoints and events, according to the docs
This is what Discord documents beyond the channel list endpoint:
- Gateway. Obfuscated channels "are dispatched through the normal Channel Create and Channel Update gateway events, including within the channel list of a Guild Create event." Those events belong to the
GUILDSintent, so this is not an intent change. Our intents and Gateway guide covers how intents work. - Regaining access. When the bot can see a channel again (a permission overwrite change, a change to its roles, a change to a role's permissions, or joining a voice channel it could not see), the Gateway sends a Channel Update with the full channel. If the parent category was hidden as well, the category gets its own Channel Update.
- Interactions. They "are built through a separate path that does not apply obfuscation, so an app always receives full channel data in interaction payloads for channels it can act on."
What the docs do not say, as of 1 November 2026:
- What the Gateway sends at the moment a bot loses access to a channel it could see. Only the way back is described.
- Whether Channel Delete fires for channels the bot cannot view.
- Anything about thread events or thread endpoints. Guild Create's
threadslist already only contains "active threads in the guild that current user has permission to view". - Anything about
GET /channels/{channel.id}, audit logs, invites or webhooks in connection with this change. - Exactly which fields are "nulled or reduced".
- Which channels count as ones an app "can act on" in interaction payloads, for example a channel the bot cannot view that a user picks in a slash command option.
- Anything about API versions.
What ___hidden___ means
___hidden___ is the placeholder name Discord puts on a channel your bot cannot view. Only a few fields on such a channel can be trusted:
| Field | On an obfuscated channel |
|---|---|
id, type, position, parent_id | Real. Discord says these "will not be obfuscated" |
name | "___hidden___" |
flags | CHANNEL_OBFUSCATED is set: 1 << 17, which is 131072 |
permission_overwrites | A single entry denying VIEW_CHANNEL for the @everyone role |
| Everything else | "nulled or reduced", and "should not be relied on" |
Detect hidden channels with the flag, never with the name. Discord says so directly: "Do not rely on inspecting name or any other obfuscated field." The overwrite is a placeholder as well, so it tells you nothing about which roles can really see the channel.
How to test with Private Channel Obfuscation before 16 November
Discord offers two switches for the Gateway side, both "temporary and for testing":
- Developer Portal toggle. Open your application in the Developer Portal, go to Overview > Bot and enable Private Channel Obfuscation. No code change, any library. Discord does not say whether a running session picks it up, so restart the bot after flipping it.
- Identify capability. Send
1 << 15(32768) in thecapabilitiesfield of your Identify payload. Discord calls thisCHANNEL_OBFUSCATIONand warns that "This opt-in mechanism will change before the feature reaches general availability." Few libraries can send it today. The stable discord.js 14.28.0 cannot: it still uses@discordjs/ws1.2.3, which has no such option, and only the development branch of@discordjs/wshas one. The Identify code of discord.py and Discord.Net has no such field either.
capabilities is a separate Identify field from intents. The MESSAGE_CONTENT intent happens to be 1 << 15 as well, so sending that intent does not turn on the test.
A short test run:
- Use a separate test application and test server if you have them. The toggle is an application setting, so try it there before you touch your production application.
- Create a text channel, deny View Channel for
@everyone, and do not give the bot access. - Enable the toggle, restart the bot and run every feature that lists, audits, backs up or logs channels. Look for
___hidden___in the output and for channels that vanish. - Give the bot View Channel on the test channel. A Channel Update with the real name should arrive. Remove the access again and see what your library does, because Discord does not document that direction.
- HTTP has no early opt-in. For code that calls
GET /guilds/{guild.id}/channels, filter the response yourself to the channels the bot can view and check that nothing breaks on the shorter list.
Code changes to make now
Detect obfuscated channels by the flag
discord.js gives every channel a flags bitfield. The named constant ChannelFlags.ChannelObfuscated arrived in discord-api-types 0.38.54 on 28 August 2026. discord.js 14.28.0 depends on ^0.38.50, so a fresh install or npm update picks up a version that has it (0.38.57 was the newest on 1 November 2026). The raw bit works with any version:
const { ChannelFlags } = require('discord.js');
// Named in discord-api-types 0.38.54 and newer, the raw bit works everywhere.
const OBFUSCATED = ChannelFlags.ChannelObfuscated ?? (1 << 17);
function isObfuscated(channel) {
return ((channel.flags?.bitfield ?? 0) & OBFUSCATED) !== 0;
}
function channelReport(guild) {
const visible = [];
const hidden = [];
for (const channel of guild.channels.cache.values()) {
if (isObfuscated(channel)) {
// Only id, type, position and parent_id are real on this object.
hidden.push({ id: channel.id, type: channel.type, parentId: channel.parentId });
} else {
visible.push({ id: channel.id, name: channel.name });
}
}
return { visible, hidden };
}
In JDA 6.7.0 the check is channel.isObfuscated(). discord.py and Discord.Net have no named flag yet (see the library table further down), so use the permission check from the next section there. In discord.py, text, voice and category channels do not even expose flags; only forum channels and threads do.
Check View Channel before you read a channel
An obfuscated channel carries a single @everyone deny for View Channel, so the permission calculation in discord.js, discord.py and Discord.Net comes out as "cannot view" for it. That makes the plain permission check a decent detector, and you want it anyway before you read messages:
import discord
def bot_can_view(channel: discord.abc.GuildChannel) -> bool:
# False for an obfuscated channel: its only overwrite denies View Channel for @everyone.
return channel.permissions_for(channel.guild.me).view_channel
async def export_history(channel: discord.TextChannel):
perms = channel.permissions_for(channel.guild.me)
if not (perms.view_channel and perms.read_message_history):
return None # store channel.id as "skipped, no access" instead
return [message async for message in channel.history(limit=100)]
In discord.js the same check is channel.viewable, and in Discord.Net it is guild.CurrentUser.GetPermissions(channel).ViewChannel.
One catch: Discord counts a category as viewable when any channel inside it is viewable, so it sends that category with real data even if the bot has no View Channel on the category itself. A pure permission check marks such a category as hidden. Where your library exposes the flag, trust the flag for categories.
Check a picked channel with discord.js 14.28.0
discord.js 14.28.0, released on 30 October 2026, adds two properties to every channel object: permissions and appPermissions (PR 11577). They are filled from interaction data. When a user picks a channel in a slash command option, Discord's payload carries its own calculation, overwrites included, of the invoking member's permissions (permissions) and of the bot's permissions (appPermissions) in that channel. Discord added the bot half on 16 July 2026; interaction.appPermissions already covered the channel the command was used in.
After 16 November this is the cleanest check for setup commands. When an admin picks a private log channel the bot cannot view, a permission calculation in your own code only has the placeholder overwrite to work with, while appPermissions comes from Discord:
const { MessageFlags, PermissionFlagsBits } = require('discord.js');
// Handler for a /setlogchannel command with a required channel option named "channel".
async function setLogChannel(interaction) {
const channel = interaction.options.getChannel('channel', true);
// discord.js 14.28.0+: Discord's calculation for the bot in the picked channel.
// Implicit permissions are not applied, so test View Channel explicitly.
const needed = [PermissionFlagsBits.ViewChannel, PermissionFlagsBits.SendMessages];
if (!channel.appPermissions?.has(needed)) {
await interaction.reply({
content: `I cannot view or post in ${channel}. Allow View Channel and Send Messages for my role there, then run this again.`,
flags: MessageFlags.Ephemeral,
});
return;
}
await saveLogChannel(interaction.guildId, channel.id); // your own storage
await interaction.reply({ content: `Logging to ${channel} from now on.`, flags: MessageFlags.Ephemeral });
}
Three details from Discord's docs and the discord.js source:
app_permissionsleaves out implicit permissions, so a channel the bot cannot view can still show Send Messages. That is why the example checks View Channel as well.appPermissionsisnullwhen the bot user is not in the server, and both properties arenullon channels that did not come from interaction data. The optional chaining above treatsnullas no access.- discord.js merges the picked channel into its channel cache, and the two values stay on the cached object until another interaction resolves that channel. Read them inside the handler, not later from the cache.
An older 14.x install updates with npm install discord.js@^14.28.0. Our discord.js v14 guide shows how to check which version you run.
Missing is not deleted
From 16 November the REST list and the Gateway cache disagree, as the endpoint section above explains. So:
- Never treat "not in the REST list" as "deleted". If you sync a database of channels, or settings such as a log channel or ticket category, against that list, mark missing channels as not visible to the bot and keep the ID and the settings.
- Do not overwrite stored names, topics or overwrites with data from a channel that has the flag. Keep the last good copy and mark it hidden.
- When a later Channel Update arrives without the flag, it carries full data again. Refresh from that.
- Tell the user. Discord points bots that manage channels to its docs on how to "detect channels your bot can't see and surface that to users". A dashboard line such as "2 channels are hidden from the bot" saves you a support ticket.
Logging bots
A logging bot gets Channel Create events for new private channels it cannot view, with the placeholder name. Log those as hidden channels instead of printing #___hidden___, and do not log the switch to the placeholder as a rename or a permission change. A discord.py version, where log() stands for whatever posts to your log channel:
@bot.event
async def on_guild_channel_create(channel):
if not bot_can_view(channel):
await log(f"A channel the bot cannot view was created (id {channel.id})")
return
await log(f"#{channel.name} was created")
@bot.event
async def on_guild_channel_update(before, after):
was_visible, is_visible = bot_can_view(before), bot_can_view(after)
if was_visible and not is_visible:
await log(f"The bot can no longer view #{before.name} (id {after.id})")
elif is_visible and not was_visible:
await log(f"The bot can view #{after.name} again (id {after.id})")
elif is_visible and before.name != after.name:
await log(f"#{before.name} was renamed to #{after.name}")
The "can view again" branch is the documented case. The "can no longer view" branch only fires if Discord sends an update at the moment access is lost, which the docs do not promise. For log structure in general, see our guide to Discord bot error handling and logging.
Backup and audit bots
- Skip flagged or non-viewable channels when you copy settings, and record their
id,type,positionandparent_idwith a "not visible" marker so the backup still shows where they sat. - Never restore a channel from obfuscated data. You would get a channel named
___hidden___with only an@everyonedeny, and the real role overwrites would be gone. - Keep your last complete backup. A backup taken before 16 November still holds the real data for private channels, so do not let rotation replace it with an incomplete one.
- In audit reports, print "bot cannot view this channel" instead of permissions calculated from the placeholder overwrite.
- Discord's new Get Channel Member Permissions and Get Channel Role Permissions endpoints (30 October 2026) save you the permission math for channels the bot can view. They do not cover hidden channels: both require View Channel.
- End every backup or audit with a line such as "3 channels were left out because the bot cannot view them", plus how to fix it.
Our Discord server backup guide covers what backup bots save in the first place.
What server owners should check
If you run a server rather than a bot, the question is simple: which bots need to see which private channels?
- List the bots that log, back up, audit or manage channels, and the private channels each one should cover: the log channel, ticket categories, staff channels you want in backups.
- For each of those channels or categories, open the channel settings, go to Permissions, add the bot's role (or the bot itself) and allow View Channel. Channels synced to their category follow the category's permissions. Channels that are not synced need their own overwrite. If the bot still fails there with
Missing Access(50001) orMissing Permissions(50013), our Discord bot permission errors guide shows which overwrite or role order is in the way. - Keep in mind that View Channel in a text channel includes reading its messages. Discord describes it as: "Allows guild members to view a channel, which includes reading messages in text channels and joining voice channels". Only grant it on private channels to bots you trust with that content. If you would rather keep a bot out, accept that its backups and reports will skip that channel from 16 November.
- Do not hand out Administrator just to keep a backup bot complete. It works because Administrator bypasses every overwrite, but it also gives the bot every other permission.
- After 16 November, compare the bot's output with your channel list. A backup or audit with fewer channels than before, or entries called
___hidden___, means the bot lacks View Channel there.
Library support on 1 November 2026
Each row names the newest release on 1 November 2026.
| Library | What it says about obfuscation | Check to use |
|---|---|---|
| discord.js | Nothing about obfuscation in the release notes up to 14.28.0 (30 October 2026), which adds permissions and appPermissions to channels from interaction data. discord-api-types 0.38.54 added ChannelFlags.ChannelObfuscated and GatewayCapabilityBits.ChannelObfuscation | channel.flags against ChannelFlags.ChannelObfuscated or 1 << 17, and channel.appPermissions for a channel picked in a command |
| discord.py | Nothing in the changelog up to 2.7.1 | channel.permissions_for(guild.me).view_channel |
| JDA | 6.7.0 (20 September 2026) "makes JDA aware of Channel Obfuscation" and is marked as a breaking change. In interactions you get a detached snapshot of the channel instead of the obfuscated cached one | channel.isObfuscated(), added in PR 3042 |
| Discord.Net | Nothing in the changelog up to 3.20.2 (8 October 2026) | guild.CurrentUser.GetPermissions(channel).ViewChannel |
Channel obfuscation is a Discord API change, so your bot sees the same channels wherever it runs. If it runs on our Discord bot hosting, the paid plans restart it after a crash, but the code changes above are yours to make: custom bot coding and debugging are not part of the plans.
FAQ
When does Discord channel obfuscation become mandatory for bots? On Monday 16 November 2026, for all bots. Discord gives the date but no time, and the date was unchanged when we checked the change log on 1 November 2026. Until then you can turn it on for your own application with the Private Channel Obfuscation toggle in the Developer Portal.
What is Private Channel Obfuscation in the Discord Developer Portal?
A temporary test switch under Overview > Bot in your application's settings. With it on, the Gateway already sends the channels your bot cannot view as ___hidden___ with the CHANNEL_OBFUSCATED flag, so you can test before 16 November. It does not change GET /guilds/{guild.id}/channels, because Discord offers no early opt-in for HTTP. Discord calls the toggle "temporary and for testing".
Can a bot opt out of channel obfuscation? Not according to Discord's documentation, which mentions no opt-out and calls the change mandatory for all bots. A bot only gets full data for a channel it can view, so the fix is View Channel on the channels the bot needs.
Why is my Discord bot missing channels?
From 16 November, GET /guilds/{guild.id}/channels returns only the channels the bot can view, plus categories with a viewable channel inside, and leaves out the rest without an error. In discord.js, guild.channels.fetch() uses that endpoint, and so does Guild.fetch_channels() in discord.py. Give the bot View Channel on the channels it needs, or treat the missing ones as hidden rather than deleted.
How do I detect a hidden channel in code?
Check the channel's flags for CHANNEL_OBFUSCATED (1 << 17). Discord says not to rely on the placeholder name or any other obfuscated field. The flag only appears on Gateway data, because the HTTP endpoint leaves hidden channels out instead.
Do slash commands still get full channel data?
Yes. Discord builds interaction payloads "through a separate path that does not apply obfuscation", so your app gets full channel data in interactions for channels it can act on. In discord.js 14.28.0 and newer, a channel picked in a command option also carries appPermissions, Discord's calculation of the bot's permissions in that channel.
Related guides: Discord API changes in 2026 | Discord bot intents and the Gateway | Discord server backup solutions | Discord bot error handling and logging
Sources
All opened on 1 November 2026:
- Discord change log: Channel Obfuscation for Users and Bots (12 August 2026), Resolved Channel app_permissions in Interactions (16 July 2026), New Endpoints for getting member and role permissions (30 October 2026), and the edit history of the change log
- Discord API reference: Get Guild Channels, channel object, Obfuscated Channels, Get Channel Member Permissions, Gateway capabilities, permissions and implicit permissions, Channel Visibility
- discord.js: 14.28.0 release, PR 11577, source at 14.28.0: BaseChannel.js, CommandInteraction.js, package.json; @discordjs/ws 1.2.3 and the development branch
- discord-api-types: 0.38.54 and 0.38.57
- discord.py: changelog and PyPI
- JDA: 6.7.0 release and PR 3042
- Discord.Net: changelog