Discord webhook sender and embed builder
This Discord webhook sender and embed builder lets you write a message, build up to 10 embeds with a live preview and post it to your channel straight from your browser. Every field is checked against the limits in Discord's developer docs, verified on September 27, 2026, so you see a title that is too long or a field without a name before Discord rejects the message.
Paste your webhook URL and press Send. You get the new message's ID back, or Discord's exact error if something is wrong. Mentions are off by default, and the JSON view shows the payload so you can copy it into your own code.
Message
Replaces the webhook's name for this message.
Replaces the webhook's avatar for this message.
Threads, forums and silent messages
Posts into an existing thread in the webhook's channel (thread_id).
For a webhook in a forum or media channel: starts a new post (thread_name).
Embeds (1 of 10)
271/6,000 characters across all embeds
Embed 1 of 1
Markdown works: **bold**, *italic*, __underline__, `code`, [text](https://link), lists and > quotes.
Preview
Your webhook's nameWebhook
Your first embed
Edit this embed and the preview updates as you type. Bold, italic, code and masked links work the way they do in Discord.
Fields
Up to 25 per embed
Embeds
Up to 10 per message
Sent with a webhook
An approximation in this site's colors. Discord's own rendering differs in small ways.
Send
Your webhook URL is sent only to Discord, from your browser. It isn't saved anywhere, so it's gone when you reload or leave the page.
What a Discord webhook is
A Discord webhook is a URL tied to one channel. Anything that sends a JSON POST request to that URL posts a message in the channel, with no bot account, no login and no connection to keep open. Discord's docs call these incoming webhooks and suggest them for one-way jobs such as build results, monitoring alerts and scheduled reports.
Each message can carry up to 2,000 characters of content and up to 10 embeds, and it can replace the webhook's name and avatar for that one message. The Twitch go-live notifier I built for Rivals League works this way: it posts through one webhook per game channel. To show a time in every reader's own time zone, paste a code from the timestamp generator into the content.
How to create a webhook in Discord
- Make sure you have the Manage Webhooks permission in the server. Owners and admins have it.
- Open Server Settings, go to Integrations and click Create Webhook, as Discord's help article describes.
- Pick the channel it posts to, give it a name and, if you like, an avatar.
- Click Copy Webhook URL and paste it into the Send box above.
If the channel is a forum or media channel, Discord needs to know which post the message belongs in. Open “Threads, forums and silent messages” in the tool and add a forum post title to start a new post, or a thread ID to reply in an existing one.
Discord embed limits
Discord answers with a 400 error and posts nothing if a message breaks any of these limits, which come from the embed limits and Execute Webhook sections of its docs. The embed builder checks each one as you type:
| Part | Limit |
|---|---|
| Message content | 2,000 characters |
| Embeds per message | 10 |
| Title | 256 characters |
| Description | 4,096 characters |
| Fields per embed | 25 |
| Field name and value | 256 and 1,024 characters |
| Footer text | 2,048 characters |
| Author name | 256 characters |
| All embeds in the message together | 6,000 characters |
The 6,000 total counts titles, descriptions, field names and values, footer text and author names across every embed in the message. Discord trims spaces at the start and end before counting, and so does this tool. The username override gets the same checks as webhook names, which Discord's docs limit to 80 characters without “discord” or “clyde” in them.
Webhooks vs bots
A webhook can only post. It can't read messages, answer slash commands, react, give roles or notice when someone joins, because nothing is connected to listen. Discord's docs point you to a bot as soon as your app needs to listen to events or respond to users. Webhooks made in Integrations can't send interactive buttons either: Execute Webhook only allows interactive components on webhooks owned by an application.
So a webhook is the right tool for a feed of news, alerts or reports. When members need to do something back, like claim a role, check in for a match or open a ticket, you need a bot. That is the work I do: see Discord integrations for bots that connect your tools to your server in both directions, or stream notification bots for go-live alerts that run without your own scripts.
Keep your webhook URL secret
The token in the URL is the only thing protecting a webhook. Anyone who has the URL can post as it, and Discord's API also lets them rename it, change its avatar or delete it without logging in.
- Keep it out of public GitHub repositories, screenshots and front-end code that ships to visitors.
- If it leaks, delete the webhook in Server Settings, Integrations, and create a new one. The old URL then answers with Unknown Webhook.
- Treat it like a bot token. The guide to keeping a bot token safe covers the same habits.
This tool sends your webhook URL to Discord only, straight from your browser, and keeps it in the page's memory until you leave. Nothing is stored or logged on this site. If you need alerts that run on their own, with the URL kept on a server, send a brief for a fixed quote.
Common questions
How do I send a message with a Discord webhook?
Send a POST request with a JSON body to the webhook URL, containing content, embeds or both. The tool above builds that body and sends it for you, and its JSON view shows the exact payload so you can reuse it with curl or in your own code.
Why is my Discord webhook not working?
Read the status code Discord sends back. 404 with Unknown Webhook means the webhook was deleted or the URL is wrong, and Discord asks apps not to keep retrying it. 400 Invalid Form Body names the field that broke a rule, 401 means the token part of the URL is wrong, and 429 means you are rate limited and should wait the retry_after seconds. A webhook in a forum channel also needs a thread ID or a post title.
Can a Discord webhook ping @everyone?
Only if the content contains @everyone and allowed_mentions lets it through. Discord's docs say webhooks parse only user mentions when allowed_mentions is left out. This tool sends an empty parse list unless you tick a box under Allow mentions, so nothing pings by accident.
Can I edit or delete a message sent with a webhook?
Yes, with the same webhook URL and the message ID this tool shows after a send. A PATCH request to the webhook URL plus /messages/ and the ID edits the message, and a DELETE request to that address removes it. Send allowed_mentions with the edit too, because an edit without it falls back to Discord's default mention rules.
Is it safe to paste my webhook URL into this tool?
The URL goes only to Discord, straight from your browser, and isn't saved; your browser's network tab shows the request going to discord.com and nowhere else. If you'd rather not paste a live URL anywhere, create a test webhook, use it, then delete it.
Sources
Limits and API behavior were checked against Discord's docs on September 27, 2026.
- Discord developer docs, Webhooks (incoming webhooks and when to use a bot instead)
- Discord developer docs, Webhook resource (Execute Webhook, webhook names, editing and deleting webhook messages, modify and delete with token)
- Discord developer docs, Message resource: embed object and embed limits
- Discord developer docs, Message resource: allowed mentions and their defaults
- Discord developer docs, Channel resource (1 to 100 character channel and thread names)
- Discord developer docs, Rate limits (429 response, retry_after, webhooks that return 404)
- Discord developer docs, JSON error codes (10015, 50027, 50035, 220001)
- Discord developer docs, API reference (base URL, API versions, error format)
- Discord Support, Intro to Webhooks (creating a webhook in Server Settings)
Need a bot that does more than post?
Webhooks cover one-way alerts. If the alerts should come from Twitch, a store or your own API on their own, or members should be able to act on them, I build that as a bot you own, with a fixed quote before any work starts.