How to Launch a Discord Bot for Free: Intents, Verification and Servers
You can launch a Discord bot for free by sharing an invite link, but build it around slash commands so you avoid privileged intents, which Discord now gates by how many unique users can see your app. Verify the app when you want a listing in the App Directory. Server admins are your real audience, so make the permissions you request small and explainable.
Who actually decides whether your bot gets installed?
A Discord bot is not installed by the people who will use it. It is installed by a server owner or a moderator, and they see exactly which permissions your invite asks for before they press the button. A bot that asks for administrator rights to play a trivia game loses that moment. Request only what each feature needs, and write a short line for each permission on your page explaining why it is there.
So the audience for your launch has two layers: admins, who must trust you, and members, who must enjoy what you built. Write the landing page for the admin, with the member’s experience shown in a short clip.
When do privileged intents become a problem?
Discord’s developer documentation, read on 13 November 2026, names three privileged intents: Guild Presences, Guild Members and Message Content. They are off by default. It also says that since 10 June 2026 the point at which you must apply for access is based on the number of unique users who can see your app across all its servers: over 10,000, you apply; under it, you switch the intents on yourself in the Developer Portal. A bot in 50 large servers can cross that line while one in 200 small servers does not.
Past the threshold you get a notice and 90 days to apply, your bot keeps working and joining servers during review, and approved apps reapply each year. The page’s main advice is the one to follow from day one: check whether you need the intent at all. Text commands that read message content are the usual reason people request it, and slash commands replace them without needing any privileged intent.
How do you get into the App Directory?
Discord’s page on enabling discovery gives two steps. First, verify the app: your team owner completes identity and application verification, with the requirements listed in the Developer Portal. Second, opt in to Discovery under the app’s settings, add the app’s metadata and images, and enable it. Discord says it can take up to 24 hours before the app shows in the App Directory and the App Launcher. Verification also opens up monetisation features such as purchases and subscriptions.
- Open the Developer Portal, pick the app and read the App Verification requirements on its page.
- Complete them, including the team owner’s identity check, and submit.
- Once verified, open the Discovery settings and read the criteria for enabling it.
- Fill in the description and images, enable Discovery and search for your app by name after a day.
Do not wait for this before you launch. Share the invite link first, collect a few dozen servers that actually use the bot, and verify when you want the directory listing. We could not read the support articles that list the verification requirements because they returned an access error, so go by the requirements shown in your own Developer Portal.
Where do your first ten servers come from?
- A server you run. Use your own community as the test bed for a month before asking anyone else to trust the bot.
- Communities around the job. A music-queue bot belongs where people listen together; a study-timer bot where students gather. Ask a moderator, offer a one-day trial and let the bot do its job in front of the members.
- A support server. Create a small server for your bot with a changelog channel and a place to report bugs. Cautious admins look for one before they install.
- A public page. Put the bot on its own page through the free launch form, with the invite link as the outbound link. The page is yours to point at from the other places.
The Discord bot places page lists directories and lists to submit to; read each one’s rules and check that the site is still maintained. The guide on building a Discord bot covers the build, and the Discord bot ideas page has concepts, as do the board’s gaming ideas.
What should the first month look like?
| When | Job | Done when |
|---|---|---|
| Days 1 to 7 | Slash commands, error messages, a support server | A stranger can add it and use one command without help |
| Days 8 to 14 | Run it in your own server and two friendly ones | You have read every error log and fixed the top three |
| Days 15 to 21 | Ask ten moderators to try it for a day | At least three keep it after the day ends |
| Days 22 to 30 | Publish the page, post in relevant communities, apply for verification if you want the directory | You know which source sent servers that stayed |
Count servers that still have the bot after fourteen days, not servers that added it. Admins remove bots that spam, ask for too much or break; the removal rate tells you more than the install count. If you have no following to start with, the answer on launching with no following applies.
Frequently asked questions
Does a Discord bot need verification to work?
No. An unverified bot works through an invite link. Discord’s documentation ties verification to the App Directory and monetisation: your team owner completes identity and application checks, opts in to Discovery and, after up to 24 hours, the app is searchable. Read the requirements in your own Developer Portal, since they can change.
What is the Message Content intent?
It is one of three privileged intents; it controls whether your bot receives the text, embeds, attachments, components and poll fields of messages. It is off by default, and above 10,000 unique users who can see your app you must apply for it. Slash commands usually remove the need for it.
Is it free to list a bot in the App Directory?
Discord’s enabling-discovery page lists identity and application verification and then opt-in, and mentions no fee. We read it on 13 November 2026 and could not read the support articles on verification, so confirm in your Developer Portal what your app needs before you plan around a listing.
How do I get my bot into more servers?
Ask moderators of communities where the bot’s job already comes up, run a short trial and keep a support server with a changelog. Give admins a plain account of the permissions you request. A listing helps later, but admins who have seen the bot work are the quickest route to more servers.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.