How to Make a Table in Discord (That Actually Lines Up)
Discord does not render markdown pipe tables. Here is how to build a clean monospace table in a code block, with worked examples and fixes for mobile.

You paste a neat markdown table into Discord and it lands as a row of pipes and dashes. No columns. No rows. Just text. Discord does not render pipe tables, and there is no table button hiding in the message box. The workaround is a text table inside a code block, and it looks good once you know which parts to control.
Why pipe tables do not render
Discord supports a small set of markdown: bold, italic, underline, strikethrough, headers, subtext, spoilers, inline code, code blocks, block quotes, and lists. Tables are not on that list. A line like `| Player | Score |` is treated as ordinary characters, so the pipes show up literally.
Even if Discord did read the pipes, normal message text uses a proportional font. An `i` is narrower than an `m`, so a column built from spaces drifts as soon as the content changes. A code block switches to a monospace font where every character takes the same width. That is the whole trick. The table is still plain text, but the spacing holds.
Use the Discord table generator to build the grid without counting spaces by hand. It handles the borders, padding, and a character counter so you can see whether the message will fit before you post.
Build a table step by step
- Open the table generator and set the number of rows and columns. Keep the header row on if the first row is a label row.
- Type into the cells, or paste comma-separated or tab-separated data from a spreadsheet and choose the fill option. Tab-separated data from Excel or Google Sheets is the most reliable.
- Pick a border style. Box drawing looks like a drawn table, ASCII is safer across fonts, and minimal drops the frame for short lists.
- Set alignment per column. Left for names and labels, right for numbers, center only for short markers.
- Copy the full output, including the opening and closing triple backticks. Those fences are what make the table monospace.
- Paste it into Discord and check the result on a phone before you pin or announce it.
What the code block looks like
A minimal table is just three lines of text wrapped in fences. The fences need to sit on their own lines:
```
┌──────────┬───────┐
│ Session │ Time │
├──────────┼───────┤
│ Opening │ 18:00 │
│ Workshop │ 19:30 │
└──────────┴───────┘
```You can add a language tag after the first fence, but it does not change the table. It only tells Discord to attempt syntax highlighting. For a plain table, leave it off.
Two things break the block. A missing closing fence leaves the rest of your message inside the code block. A cell that contains three backticks closes the fence early, so keep backticks out of cell text or replace them with a different character.
Worked example: a raid schedule
Suppose your server runs three sessions on a raid night. Copy this into the generator's import box:
Session,Time,Host
Opening,18:00,Ari
Boss run,19:30,Bea
Cleanup,21:00,CyrusWith box borders, a header row, and left alignment for every column, the copied message looks like this:
┌──────────┬───────┬───────┐
│ Session │ Time │ Host │
├──────────┼───────┼───────┤
│ Opening │ 18:00 │ Ari │
│ Boss run │ 19:30 │ Bea │
│ Cleanup │ 21:00 │ Cyrus │
└──────────┴───────┴───────┘The times are short enough that left alignment reads fine. If you add time zones or longer labels, right alignment for the time column keeps the digits together and makes the schedule easier to scan.
Worked example: a leaderboard
Numbers are where alignment earns its keep. A leaderboard with left-aligned points looks ragged because 9 and 900 start at the same place. Right alignment puts the last digit in a straight line:
┌──────────┬────────┬──────┐
│ Player │ Points │ Wins │
├──────────┼────────┼──────┤
│ Nova │ 2450 │ 12 │
│ Kite │ 980 │ 5 │
│ Ember │ 120 │ 1 │
└──────────┴────────┴──────┘That table is a snapshot. Discord does not update it when someone plays another match. If your community needs a live scoreboard, use a bot command or a linked spreadsheet. A code block table is for information that is already final when you post it.
Pick the right border style
- Box drawing uses characters like `┌`, `─`, and `│`. It looks like a real table and suits announcements, schedules, and pinned reference posts.
- ASCII uses `+`, `-`, and `|`. It is less pretty, but it survives fonts, terminals, and copy-paste into other apps with fewer surprises.
- Minimal removes the frame and separates columns with spaces. It works for two or three short columns and feels lighter than a full grid.
Border characters are also characters. A wide table with long borders costs more of the message limit than the same content with minimal borders. That rarely matters until you build something with many columns.
Emoji, CJK text, and alignment problems
Monospace does not mean every character is one cell wide. Chinese, Japanese, and Korean characters usually take two cells. Most emoji take two, and some emoji are built from several code points joined together, so a single visible symbol can take more space than expected.
A good generator measures display width rather than counting characters, which gets common CJK text and emoji closer to the correct padding. It still cannot account for every font or every Discord client. If a column drifts after you post, the emoji is usually the cause. Move it to its own column or remove it.
Combining marks, skin tone modifiers, and zero-width joiners make the math harder. Keep cells short, avoid decorative emoji inside tight columns, and use plain letters and numbers when exact alignment matters more than personality. The text formatter is useful for styling the heading or note around the table, but keep the table itself plain.
Why the table wraps on mobile
Mobile clients often wrap long code block lines instead of scrolling sideways. The spaces are still there, and copying the message preserves them, but the visual grid breaks across extra lines on a narrow screen.
Plan for the smallest screen your members use. Three or four short columns usually fit. Eight columns may look fine on a desktop monitor and turn into a wall of broken lines on a phone. Shorten headers, remove optional columns, or split a wide table into two narrower posts.
When embed fields are the better choice
Bots and webhooks can send embeds with up to 25 fields, and each field has a name and a value. Two or three inline fields can imitate a small table with a cleaner layout and no monospace spacing to maintain. The catch is that fields are not a real grid either. Long values wrap inside their column, and field names cannot carry every kind of markdown.
Use embed fields when a bot is already sending the message and the data fits into short label and value pairs. Use a code block table when a person is posting in chat and alignment is the point. The embed generator helps you test the field layout before handing it to a bot or webhook.
The 2,000 and 4,000 character limits
At the time of writing, a standard Discord message holds 2,000 characters, and Nitro raises that to 4,000. Every space used for padding, every border character, and both code fences count toward the total.
A table that fits under 2,000 is safe for everyone. If it only fits under 4,000, some members may not be able to send or copy the same message. Split a long table into two messages and keep a complete set of fences around each half. Do not leave one code block open across two messages.
Troubleshooting
- Visible backticks mean the code fence is broken. Check that the opening and closing fences each sit on their own line.
- Uneven columns usually mean part of the table is outside the code block. Select the whole block and paste it again from the tool.
- One column of jumbled text means the separator was not recognized. Copy with tabs from a spreadsheet, or use commas and quote fields that contain commas.
- A rejected message is often over the limit. Remove an empty column, shorten long labels, or switch to minimal borders.
- A grid that breaks on a phone needs fewer columns, not smaller text. Code blocks do not get a horizontal scrollbar on every mobile client.
The final check is simple. Read the table in the Discord preview, then read it on a phone. If the columns hold and the message fits, you are done. If not, change the layout rather than fighting the spacing.