Discord Webhook Sender & Message Builder
A Discord webhook is a link that posts messages to one channel as if a bot sent them. This sender builds that message in a form, shows you exactly how Discord will draw it, and posts it from your own browser. Nothing about your webhook travels to Tolz.me.
What a webhook actually is
When you create a webhook, Discord gives you a long link that ends with a random token. That link holds two things: the ID of the channel it posts into, and a secret token. Discord checks the token, then posts whatever you send to the channel. The message shows up with the name and avatar you choose, and Discord marks it as coming from an app.
Because the link is a secret, treat it like a password. Anyone who holds it can post to that channel, and anyone who holds it can read what your integration posted. Rotating the webhook, which means deleting it and creating a new one, is the quickest way to cut off an old link.
Webhooks work without a bot, without a server application, and without any code on your machine. They are the simplest way for a script, a spreadsheet, or a laptop shortcut to put a message in a channel.
Create a webhook in Discord
Open your server and go to Server Settings. In the left column choose Integrations, then Webhooks, then New Webhook. Pick the channel the webhook should post into, give it a name such as Release Bot, and choose an avatar. Press Save Webhook and Discord shows the link with a Copy button.
The new webhook link looks like this: https://discord.com/api/webhooks/000000000000000000/a-long-random-token. Everything after the webhook ID is the secret part. Paste the whole link into the sender, tick the box to reveal it if you need to check it, and the tool reads the ID back to you so you can confirm it points at the channel you expect.
Server owners can also add a webhook by name from the channel itself. Press the channel name in the top bar, choose Edit Channel, then Integrations, and add the webhook from the same list.
Build the message and send it
Classic mode gives you the plain text of a message, a display name, an avatar link, and up to ten embeds. An embed is the card Discord shows with a coloured stripe on the left. Each embed can carry a title, a link, a description, an author line, a footer, an image, a thumbnail, a timestamp, and up to twenty five fields. Inline fields sit beside each other in rows of three, which is handy for short stats.
Toggle text to speech to have Discord read the message aloud. Toggle hide embeds when a link in the text would preview itself and spoil the layout. Toggle silent to post without a push notification, which matters for automated posts that would otherwise ping everyone.
Files are uploaded with the message. Choose up to ten files and the sender posts them as multipart form data, with the message body in a payload_json field and each file in its own files slot. The preview shows the file cards Discord will draw under the message.
Three messages worth copying
For a release announcement, set the username to the name of your project, pick a colour for the embed stripe, put the version in the title, and add three inline fields for the date, the size, and the changelog link. Put the full notes in the description and keep the footer for the project name.
For a forum channel, leave the thread name field filled in. Discord creates the thread for you and posts the message as the first entry. Add a thread ID instead when you want to reply inside a thread that already exists.
For a correction, send the message once, copy the message ID that appears in the result panel, paste it into the message ID field, fix the text, and press Edit. The Edit button sends a PATCH to that message. The Load message button pulls an existing message back into the editor so you can start from it instead of typing everything again.
Discord limits to keep in mind
Discord rejects a message that breaks its rules, and it does not always explain why. These are the numbers that matter most when you build a webhook message.
Message content holds up to 2000 characters. A webhook name runs from 1 to 80 characters, and Discord refuses the words Clyde and Discord in it. A message can carry 10 embeds. Inside one embed, the title holds 256 characters, the description 4096, the footer 2048, the author name 256, and each field name 256 with a field value of 1024. An embed holds up to 25 fields. Across every embed in one message the total stays under 6000 characters. A thread name holds 100 characters and a webhook message can carry up to 10 files.
The sender counts every one of these as you type and turns the counter red when a limit is passed. Discord also rate limits webhooks. Sending more than about 5 requests every 2 seconds from one webhook gets you a 429 reply, and the sender shows the wait time Discord asked for.
Components v2 in plain words
Components v2 is the newer way to build a message out of blocks instead of one body of text. You can stack text blocks, sections with a thumbnail or a link button beside them, containers with a coloured accent bar, media galleries, separators, and rows of link buttons.
There are two rules that catch people out. A components v2 message cannot also carry plain text, embeds, or files, so the sender hides those panels while you are in that mode and warns you when a leftover field would be dropped. Second, a webhook that belongs to an ordinary user can only send link buttons, which open a page. Interactive buttons that do something need a webhook owned by an application with the right permissions.
If you are not sure which mode you need, stay in classic mode. It is what most channels expect and it is the mode that supports embeds.
Your webhook link stays in your browser
The sender posts to Discord directly from the page. Discord allows this, so the request never passes through Tolz.me and we never see your webhook link, your message, or your files.
The link stays in React state while you work. If you tick remember in this tab, it is kept in sessionStorage, which clears when you close the tab. It is never written to localStorage, never put into a saved draft, and never included in an exported JSON file or a share link. The share link carries the draft in the part of the address after the hash, which browsers do not send to a server, and the tool refuses to build one if the draft text happens to contain a webhook link.
Drafts, exports, and sharing
Your work is saved in the browser as you type, so a reload does not lose it. Named drafts go further: give one a name, save it, and load it back later. Saved drafts stay on your device.
Export writes the draft to a JSON file and copies the same JSON to the clipboard. Import reads that file back, and it also accepts a raw Discord payload, which is handy when you want to take a message you built somewhere else and edit it here.
Share link puts the draft into the address after the hash. Send that link to a teammate and they open the same draft in their editor. Because the link lives in the hash, it never touches a server on the way.
Explore more discord tools on Tolz.me.