Discord's October Update Makes Markdown Previews and .md Files Render Properly
Discord released an update on October 22, 2026, under which Markdown previews render correctly instead of displaying a run of raw formatting symbols. The change is described in Discord's update post and was reported the same day by The Verge.
The update also extends to file uploads. Markdown (.md) files uploaded to Discord now display rendered with their formatting, including tables. For a platform where technical teams routinely share READMEs, changelogs and design notes, that is the more practical of the two changes, because it applies to whole documents rather than to a line of text typed into the composer.
The October release is the latest in a series of Markdown corrections Discord has shipped this year. On February 4, 2026, Discord announced that it now properly renders Markdown in event previews displayed in a server's channel list. On March 6, 2026, it fixed an iOS bug that rendered dark squares before emojis within Markdown. On October 6, 2026, it fixed a desktop bug in which Markdown formatting did not show a live preview in the chat box when a message started with "+".
Markdown is a lightweight markup language: plain text with simple symbols, such as asterisks for emphasis or pipes for table columns, that a client turns into formatted output when it parses the text. Its appeal is that the same text stays readable as source and becomes formatted output on display. That property holds only if every client parses it the same way. Discord's fixes touch several distinct rendering paths: the desktop composer's live preview, event cards in the channel list, emoji handling on iOS, and now file attachments. Each path is separate code, so a parser that behaves correctly in one place can still misbehave in another. The sequence of fixes above is consistent with that pattern.
The broader context here is that Discord has been adding structured content to what began as a voice and text chat product. Servers now carry scheduled events, documentation-style posts and file attachments, and each of those surfaces has to present formatted text consistently. For developer communities, open-source maintainers and bot operators, rendering drift between desktop, mobile and previews makes shared text harder to trust, and small defects in those paths tend to surface as confusion rather than as outright failure.
In my view, the less visible work of making formatting behave the same across clients is what decides whether a chat platform can serve as a working space for technical documentation, not only for conversation. Rendering a table in an uploaded .md file correctly is a small change on a changelog, but it removes a step that people previously had to work around by copying text into another tool or reading raw syntax by eye.
What the update enables is straightforward. A README or design document shared into a server can be read as its author intended, tables included, without leaving the application. Whether the October 22 release fully resolves the inconsistencies across the desktop, iOS and preview surfaces will show up in how the next round of client updates treats them, and that is a question for future releases rather than for this one.
