Some members in your Discord server report that the channel description appears as plain text while others see bold, italic, code blocks, and clickable links. This happens because Discord requires the Read Message History permission for markdown rendering to work correctly. Without this permission, the client treats the description as raw text and ignores any formatting. This article explains the exact permission that controls markdown rendering and provides a step-by-step fix to apply it to the affected roles or members.
Key Takeaways: Fixing Markdown Rendering for Channel Descriptions
- Server Settings > Roles > [Role] > Permissions > Read Message History: Enabling this permission allows markdown in channel descriptions to render for members with that role
- Server Settings > Roles > [Role] > Permissions > View Channels: This permission alone is not enough; members also need Read Message History for markdown to appear
- Server Settings > Roles > [Role] > Permissions > Manage Channels: Owners and admins have this permission which includes Read Message History, so they always see formatted descriptions
Why Markdown Rendering Depends on Read Message History
Discord processes channel descriptions using the same markdown engine that formats chat messages. When a member opens a channel, the client requests the description data from the server. The server checks whether the member has the Read Message History permission for that channel. If the permission is granted, the server sends the full description with markdown syntax. The client then parses the syntax and renders bold, italic, code blocks, headers, and links.
If the member lacks Read Message History, the server sends the description as plain text only. The client does not attempt to parse any formatting. This is a deliberate design choice by Discord for performance and permission control. The permission is named after message history, but it also controls whether the description is processed as formatted content.
Who Is Affected
The problem typically affects:
- New members who have not been assigned a role with Read Message History
- Roles that have View Channels enabled but Read Message History disabled
- Members with the @everyone role if that role has Read Message History turned off for a specific channel
Server owners and administrators always see formatted descriptions because they have the Manage Channels permission, which includes Read Message History by default.
Steps to Enable Read Message History for Roles
Follow these steps to grant the Read Message History permission to a role. This will allow all members with that role to see markdown-rendered channel descriptions in every channel where the role has access.
- Open Server Settings
Right-click the server name in the left sidebar and select Server Settings from the context menu. Alternatively, click the server name at the top of the channel list and choose Server Settings. - Go to the Roles tab
In the left navigation pane of Server Settings, click Roles. A list of all roles in the server appears. - Select the role to edit
Click the name of the role that is affected by the markdown issue. For example, if new members have the @everyone role and cannot see formatted descriptions, click @everyone. - Navigate to the Permissions tab
Inside the role editor, click the Permissions tab at the top of the page. - Enable Read Message History
Scroll down to the General Permissions section. Find the permission labeled Read Message History. Click the green checkmark icon to enable it. The toggle changes from a gray X to a green checkmark. - Save changes
Click the Save Changes button at the bottom of the Permissions tab. Discord applies the new permission immediately.
Grant Permission for a Single Channel Only
If you want markdown to render only in specific channels, you can override the role permission at the channel level.
- Open channel settings
Right-click the channel name in the channel list and select Edit Channel. - Go to Permissions
In the left pane, click Permissions. - Add a role override
Click the + icon next to Roles/Members. Select the role from the list and click Save. - Enable Read Message History
Find Read Message History in the permissions list. Click the green checkmark to enable it for this channel only. - Save channel changes
Click Save Changes at the bottom of the page.
If Discord Still Has Issues After the Main Fix
Member Still Sees Plain Text After Permission Change
Ask the affected member to restart Discord. Permission changes sometimes require a fresh client connection to take effect. The member can close Discord completely and reopen it, or press Ctrl + R on Windows to reload the client. If the issue persists, have the member check their client version under User Settings > Advanced > Developer Mode and ensure they are not running a cached old version.
Markdown Works in One Channel but Not Another
Channel-specific permission overrides can cause inconsistent behavior. Open the channel where markdown does not render and check its Permissions tab. If a role or member override is set to deny Read Message History, that denial overrides the role-level grant. Remove the deny override or change it to a neutral gray slash to allow the role-level permission to apply.
Description Contains Valid Markdown but Links Are Not Clickable
Discord renders links in channel descriptions only if the member has Read Message History enabled. If links appear as plain text like https://example.com instead of a clickable anchor, confirm that the permission is set correctly. Also note that Discord does not render inline images or embeds in channel descriptions. Only standard markdown links work.
Read Message History Permission: Enabled vs Disabled
| Item | Read Message History Enabled | Read Message History Disabled |
|---|---|---|
| Channel description rendering | Markdown is parsed and displayed with formatting | Description appears as plain text without any formatting |
| Message history visibility | Member can scroll up and read past messages | Member sees only messages sent after they joined the channel |
| Link behavior | Links in description are clickable | Links appear as raw text and cannot be clicked |
| Code blocks | Rendered with syntax highlighting and monospace font | Shown as plain text with backticks visible |
| Headers | Rendered as larger bold text | Shown as plain text with hash symbols visible |
The table shows that enabling Read Message History affects more than just markdown. It also controls whether members can read previous messages and interact with formatted content. If you want members to see formatted descriptions but do not want them to read old messages, you cannot achieve this with the current permission system. The two features are linked.
You can now fix the markdown rendering issue by enabling the Read Message History permission for the affected roles or channels. Start by editing the role that does not see formatted descriptions. If the problem persists in a specific channel, add a channel-level override. Remember that members must restart Discord after permission changes for the client to reload the description with proper formatting. For advanced control, consider creating a dedicated role with Read Message History enabled only for the channels where formatted descriptions are necessary.