Discord Embed Generator
The Discord embed generator builds valid embed JSON from a form: title, description, color, author, footer, fields, and optional timestamp. Copy the result and paste it into a webhook POST body or bot code.
What are Discord embeds?
Discord embeds are structured message cards that bots and webhooks can send. They have a colored left stripe, optional author and footer lines, a title, a description, and up to 25 fields arranged in rows. Regular user accounts cannot send embeds directly — only bots and webhooks can.
Embeds are written as JSON. The embed generator produces that JSON from the form fields so you do not have to write or debug the object structure by hand.
The form fields
Title goes at the top of the embed card in bold text. Discord truncates titles longer than 256 characters. Leave it blank if you only need a description.
Description is the main body text, rendered below the title. It supports basic Discord markdown including bold, italic, links, and spoiler tags. Descriptions longer than 4096 characters are rejected. Keep them concise for announcements.
Color sets the left stripe. Click the color swatch to open a visual picker. The picker defaults to Discord blurple #5865F2. The stripe updates live in the preview as you change it.
Author name appears at the top of the embed in smaller text above the title. Footer text appears at the bottom. Both are optional.
Adding fields
Fields let you display label-value pairs inside the embed body. Each field has a name, a value, and an optional inline flag. Up to 25 fields are supported per embed.
Inline fields sit side by side in the same row, up to 3 per line on desktop. Non-inline fields take full width. Use inline fields for short stats like rank, score, or platform. Use full-width fields for descriptions that need multiple lines.
Click Add field to add more rows. The button disables at 25 fields. Empty field names and values are filtered out of the output.
Timestamp toggle
Enable Include current timestamp to append an ISO timestamp to the embed. When Discord renders the embed, that timestamp appears as a relative countdown in the footer area — like "3 hours ago" — based on each viewer's local time.
The timestamp uses the moment you generate the JSON, not a future date. For event announcements with a specific start time, use the timestamp generator tool to create a fixed-point timestamp and paste it into the description manually.
The preview pane
The form shows an approximate preview of the embed below the fields. The preview uses a bordered card with a colored left stripe, just like Discord renders it. Fields appear in a grid matching the inline settings.
The preview is close to the final result but Discord clients add slight padding and font rendering differences. Test the actual embed in a private channel or test server before sending it to a live audience.
Copying and using the JSON
Click Copy embed JSON. The output is a JSON object wrapped in an embeds array, which is the shape Discord's API expects. Paste it into your webhook POST body under the embeds key, or pass it to your bot library's embed builder.
For webhooks, the full POST body usually looks like: {"content": "Optional plain text above the embed", "embeds": [ /* paste output here */ ]}. Content and embeds can coexist in the same message.
Discord markdown inside embeds
Embed descriptions and field values support most Discord markdown. You can use **bold**, *italic*, ~~strikethrough~~, `code`, and [masked links](https://example.com). Spoiler tags ||like this|| also render.
Headers using # syntax do not render in embed descriptions. Code blocks work but the triple-backtick fences show as part of the text in an embed field value. For code snippets, inline backticks are more reliable.
Limits and troubleshooting
Discord enforces these limits: title 256 chars, description 4096 chars, field name 256 chars, field value 1024 chars, footer text 2048 chars, author name 256 chars, and 25 fields maximum. The generator silently truncates titles and names that exceed limits, but Discord will reject a payload where the description or a field value exceeds its limit.
If Discord rejects a webhook payload, the most common causes are an invalid field name (empty string or non-string), a field value that is too long, or the color value being passed as a string instead of a number.
Explore more discord tools on Tolz.me.