Get in touch
Have a tool request, a bug report, or just want to say hi? Send us a message and we'll get back to you.
Before you contact us
Many questions are already answered in the guides section. If a tool is not working, first check that you are using the latest version of your browser, and confirm the input you pasted is valid - a malformed invite code or a truncated webhook URL is the cause of most failures.
For tool requests, tell us what you are trying to accomplish rather than just naming a feature. The best suggestions are the ones we can build entirely in the browser without accounts or payments, because those are the tools this site exists for.
Please never paste tokens, passwords or other secrets into the contact form. This site cannot and will not use your credentials, and emails are not an encrypted channel. Treat anything you send by email the way you would treat any public message.
How quickly will you reply?
The site is maintained by a small team, so replies are not instant, but every message is read. Bug reports that include the exact page, the browser you use and a screenshot are the fastest to fix. Tool requests are triaged by how many people they help and how well they fit the in-browser, privacy-first philosophy of the site.
What makes a great tool request?
The best requests describe the problem, not just the feature. "I want to preview how an embed looks in my server before I send it" tells us more than "add an embed preview", because it explains the workflow we need to support. If the feature exists somewhere else, link to it so we can see exactly what you mean.
Tools that fit this site best share three properties: they run entirely in the browser, they produce something you can copy-paste, and they relate to Discord or social media. Tools that need a backend, a login or payment integration are a poor fit for the current architecture, but we still like to hear about them - they sometimes reveal a simpler variant that does work locally.
Reporting a bug
A useful bug report has three parts: the page and tool you were using, the browser and device you were on, and the steps that produced the problem. Screenshots or a short description of what you expected versus what happened help us reproduce and fix it quickly.
A few common issues have simple fixes: if a copy button does nothing, the browser may be blocking clipboard access - click once on the page first and try again. If a network tool shows an error, the input was usually malformed or Discord's API was temporarily unreachable. Trying the same input a second time often resolves it.
Other ways to get help
The guides section answers most how-to questions about Discord formatting, sizes and limits. The blog covers deeper topics like snowflake IDs and webhooks. And the tools themselves usually include hints about the exact format they expect - checking the placeholder text in an input is the quickest way to spot a formatting mistake.
If your question is really about Discord's own features, the official Discord help center and developer documentation are the authoritative sources. We maintain this site independently and cannot answer questions about your account, your server's settings or Discord support cases.
What to expect from our reply
Messages are read in the order they arrive, and the reply comes from a human - not an automated response. If you reported a bug, the reply confirms what we found and, when it is reproducible, gives you an estimate of when a fix will ship. If you made a tool request, the reply tells you whether it fits the site and, if it does, whether it is likely to be built soon.
We do not sell contact details, add you to mailing lists or send promotional follow-ups. Once your question is answered, the conversation ends unless you continue it. That matches the privacy stance of the rest of the site: minimal data, no tracking, no pressure.
Because email is not encrypted in transit by default, keep the message free of secrets. If you are reporting a security issue involving a webhook URL or token, revoke the credential first, then describe the incident without including the sensitive value itself.
Common topics we hear about
The most frequent messages fall into a few buckets. Tool requests for Discord-related utilities are the largest group, followed by questions about whether a tool will be expanded, bug reports for a specific tool on a specific browser, and suggestions for new guides. Less common but always welcome are corrections to a guide, links to official Discord documentation we may have missed, and translation or accessibility suggestions.
If your message is about something other than this site, the fastest way to a good answer is the official Discord help center. We cannot access your account, review your server, or speak for Discord support, but we can usually point you to the exact page that covers your situation.
Accessibility of this page
The contact form is a plain HTML form that opens your email client with the fields pre-filled - there is no JavaScript dependency and no third-party form service. If the form does not work for you, you can send an email directly to the address shown in the footer, with the same fields filled in by hand. Every message, regardless of how it arrives, is read by the same people.
If you are using assistive technology and the form or any other page on this site is difficult to use, telling us exactly what happened is one of the most helpful things you can do. Accessibility issues are treated as bugs and fixed in priority order.
Finally, if you are writing about the site, tool or a guide and want a fact-check or a quote, mention that in the message and we will reply with the technical details you need.