WRITE IT ONCE. MAKE IT READABLE.
Discord Text Formatter
Discord Text Formatter with live Markdown preview, bold, italic, strikethrough, spoiler, code blocks and one-click copy. Free, private and no login.
Markdown editor
Plain text · always editableDiscord preview
Type in the left editor; the preview updates automatically.
COMPLETE GUIDE
Discord Text Formatter: syntax, examples and troubleshooting
How to format text in Discord
Discord Text Formatter is a browser-based writing workspace for anyone preparing a message that needs to look clear in Discord. Type your message in the editor, watch a Discord-inspired preview update immediately, and copy the original Markdown when it looks right. You do not need a bot, account connection, extension, download, or special permission. The tool runs locally in your browser. The preview helps you catch mistakes before you paste a formatted announcement, game instruction, server rule, event schedule, or welcome message into a Discord channel.
Discord supports a useful subset of Markdown, which means ordinary keyboard characters can change how a message appears. Two asterisks around a phrase make it bold, one asterisk can make it italic, and two tildes create strikethrough. Discord also supports underline with two underscores, inline code with single backticks, code blocks with triple backticks, and spoiler formatting with two vertical bars. You must copy the Markdown characters, not just a picture of the preview. Discord interprets those characters when it renders your message.
Bold and italic Markdown syntax
To make bold text, type **important announcement** in the editor. Your readers should see a heavier weight around the words when the syntax is interpreted by Discord. Bold is useful for deadlines, names, steps, or an important warning, but an entire long post in bold becomes hard to scan. Use bold selectively and preserve readable line breaks. If you want a title larger than body text, Discord also recognizes Markdown headings on their own lines, starting with a hash symbol followed by a space.
For italics, put one asterisk or underscore on each side of the relevant phrase, such as *optional step* or _editorial note_. Italics are best for a short aside, emphasis, or a stage direction rather than every sentence. You can combine bold and italic with three asterisks on both sides of the same words. Formatting may behave differently when punctuation, unmatched symbols, or extra spaces are involved, so always inspect the preview and, for critical messages, send a test in a private channel.
Strikethrough and underline
Use ~~outdated information~~ to display text with a line through it. Strikethrough is effective for showing a revised plan, an old price that is no longer available, or an item that has been crossed off, although editing the original message is often clearer for important facts. Underlining uses __two underscores__ and can help indicate a label or section. When you combine underline, bold, italic, and strikethrough, carefully close each pair of formatting markers. An unmatched symbol is one of the most common reasons a Discord message appears as plain text.
Inline code is ideal for commands, filenames, setting names, keyboard shortcuts, and short technical terms. Surround a short phrase with one backtick on each side: `npm run build` is an example. Code displays in a monospaced style, and characters inside code should not be treated as bold or italic markup. A code block is better for multiple lines of configuration or a longer snippet. Put three backticks on a line before the code and another three on a line after it. You can write a language name after the opening backticks when Discord supports highlighting for that language.
Inline code and multiline code blocks
Discord also allows spoilers using two vertical bars around the hidden text. For example, ||the answer is forty-two|| creates a spoiler that recipients can reveal. This is convenient for story endings, game hints, puzzles, and content someone may prefer not to see immediately. Spoilers are not secure encryption: recipients can reveal the text, notifications may expose surrounding context, and bots or other clients might treat messages differently. Do not put secrets, passwords, or private personal data into a spoiler and assume it will remain protected.
Large announcements often benefit from headings, block quotes, and lists. Start a heading with # and a space, or use ## and ### for smaller heading levels. Begin a quotation with > followed by a space; many Discord clients also accept a three-character greater-than quote marker for multiple lines. Start a list item with a hyphen and a space or use numbered items such as 1. First step and 2. Second step. These patterns help structure server rules, release notes, community guidelines, and instructions without relying on decorative Unicode characters.
How to use the live editor
The toolbar above this editor inserts familiar Markdown markers around your current selection. Select a word or sentence first, then choose Bold, Italic, Strikethrough, Code, Spoiler, or another formatting action. If nothing is selected, the tool inserts paired markers and moves your cursor between them so you can continue typing. The editing surface remains a normal text box: you can paste drafts, undo your changes, use keyboard shortcuts, and move text around. On phones, you can still type directly even when selection controls feel different.
The live preview is intentionally a close browser simulation of common Discord message formatting, not a connection to Discord and not a promise of pixel-perfect rendering in every app version. The appearance of fonts, spoiler reveal controls, syntax highlighting, lists, and embeds can vary between desktop, web, and mobile clients. Discord may also interpret some combinations or special cases differently. For that reason, your final quality check should be to paste the copied Markdown into the specific Discord channel where it will be published.
Why Discord formatting stops working
When formatting fails, first look for missing opening or closing characters. **bold without the closing asterisks will not behave like a complete bold pair. Likewise, a multiline code fence needs three opening backticks and three closing backticks. A heading requires a space after its hash character, and quote or list markers generally belong at the beginning of a line. Extra backslashes can escape Markdown characters on purpose, so \\*this\\* may render as literal asterisks instead of italic styling.
A second source of confusion is copying rich text from another editor. Microsoft Word, Google Docs, email software, and some web pages use rich-text formatting that Discord does not necessarily preserve when you paste. This tool copies the plain Markdown source that Discord understands. Some typographic characters, including smart quotes, are fine as text but are not substitutes for the ASCII asterisk, underscore, backtick, tilde, hash, or vertical bar used as formatting markers. Check the actual characters if the preview does not match what you expected.
Paste plain Markdown, not rich text
A third issue is context. Formatting inside a fenced code block is supposed to remain literal code; bold markers there should not become bold. The same applies to most text inside inline code. Conversely, a bot message, webhook payload, integration, or embed can have its own rendering restrictions, and application configuration may suppress some kinds of mentions or links. A user in a channel without permission to send messages cannot fix that with a formatter. If the message is rejected, check Discord permissions and length constraints separately from Markdown syntax.
If your goal is to create a reusable server announcement, write the main message in sections rather than one long unbroken block. Put a short heading first, make important dates easy to find, use a compact numbered list for actions, and reserve code blocks for commands rather than prose. Avoid excessive decorative formatting, which can reduce accessibility. On mobile, read the preview at a narrow width and verify that emoji, punctuation, long URLs, and multiline content remain legible. The same principles work for patch notes, community rules, bug reports, and FAQ posts.
Tips for readable Discord messages
The copy button gives you the editable source, including asterisks and backticks, so you can paste the result into Discord without manually reconstructing the syntax. It does not send your draft to our server, create Discord messages, manage a bot, or automatically post on your behalf. Your input is not saved as an account draft. If the clipboard permission is unavailable in your browser, you can select and copy the text directly. This simple workflow keeps the tool fast and useful for sensitive drafts that you prefer not to upload.
Finally, use a formatter as a writing aid rather than a guarantee of every future Discord feature. Discord can add or change supported formatting, while themes, accessibility settings, localization, and user clients may change how the result appears. If you encounter a discrepancy, consult Discord's current Markdown documentation and test a small example before changing a large announcement. Clear wording and predictable structure matter more than visual effects, and combining both usually produces the most readable message.
Frequently asked questions
Is this an official Discord text formatter?
No. This is an independent, browser-based utility and is not owned by, endorsed by, or affiliated with Discord. The live preview approximates familiar Discord Markdown styles, and the final result should be tested in Discord.
How do I make text bold in Discord?
Put two asterisks before and after the text: **bold text**. Copy that entire source including the asterisks, then paste it into Discord.
How do I make italic or strikethrough text?
Use *italic text* or _italic text_ for italics, and ~~struck out~~ for strikethrough. Underline uses __two underscores__ on each side.
How do Discord code blocks work?
Type three backticks before the code and another three after it, typically on their own lines. Inline code only needs one backtick on each side. Formatting marks inside a code block remain literal code.
Why is my Discord Markdown showing the asterisks?
Check that the opening and closing markers match, that you did not accidentally escape them with a backslash, and that you are not typing inside a code block. Test short text in the actual Discord client.
Can I preview spoilers, headings and lists?
Yes. The editor gives a Discord-inspired rendering of common spoilers, headings, block quotes and lists, but some client details and complex nesting can differ from Discord. Paste and test the final message.
Does this tool send my messages to Discord?
No. This tool neither connects to your Discord account nor posts messages. Your draft is processed locally in your browser. You choose when and where to paste copied Markdown.
Can I use this on mobile or with a Discord bot?
The editor works on modern mobile browsers. You can copy the Markdown text into a bot workflow or webhook configuration, but actual rendering depends on that integration and its permissions.
What happens if my Discord message is too long?
The editor shows a character count and warns above 2,000 characters, a common standard message threshold. Discord limits can differ by account or integration, so check your client or API requirements.