An embed is the rich card Discord renders under a message - colored bar, title, fields, footer. Regular users cannot type one; embeds are sent by webhooks and bots. The JSON this page produces is the exact payload shape the API expects: an embeds array inside the message body. For a webhook, POST it to the webhook URL with Content-Type: application/json; in a bot framework, pass the inner object to your library's embed parameter. Game communities run on these - restart announcements, wipe schedules, patch notes, giveaway cards.
Descriptions and field values speak normal Discord markdown: **bold**, *italics*, `code`, ~~strikethrough~~ and line breaks all render, and the preview above shows the common ones. Links only work as [text](url) inside descriptions and fields. Keep an eye on the running limits - Discord rejects the entire message if any single part crosses its cap, which is the number one "my webhook stopped working" cause.
Build it above and copy the JSON. Paste it as the body of a webhook request (Server Settings → Integrations → Webhooks → New Webhook, then POST the JSON to the webhook URL), or drop the embed object into your bot's send call. Plain users cannot type embeds into chat - they come from webhooks and bots.
Title 256 characters, description 4,096, up to 25 fields (name 256, value 1,024 each), footer 2,048, author name 256 - and everything combined must stay under 6,000 characters. The generator warns you when a field crosses its limit.
The three usual causes: the JSON is sent as plain text instead of with a Content-Type: application/json header, the embed object is not inside an "embeds" array, or a limit is exceeded (Discord rejects the whole message). Empty embeds are also dropped - at least one visible part is required.
No - the API wants a decimal color number. Pick the color above and the JSON gets the correct value automatically (it is the hex color converted to decimal).