> For the complete documentation index, see [llms.txt](https://docs.discordtotelegram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.discordtotelegram.com/fundamentals/how-to-settings-for-task/get_discord_bot_token.md).

# How to Get a Discord Bot Token

A Discord bot token authenticates bot accounts with Discord servers. This secret string grants access to Discord API routes and the real-time gateway. The guide explains token generation, copying, and security through the Discord Developer Portal at discord.com/developers/applications. D2T Auto Forward requires this token for message forwarding.

***

## TL;DR

Open discord.com/developers/applications. Select the application, navigate to the Bot page, and click Reset Token if the copy button is hidden. Complete Discord identity verification, copy the new token immediately, and store it securely. Discord displays regenerated tokens exactly once.

***

## What Is a Discord Bot Token?

A Discord bot token is a secret string that authenticates a bot account with Discord servers. Discord uses tokens instead of usernames and passwords for bot authentication. The token grants the bot access to API routes and the real-time gateway. API routes allow the bot to send messages, manage channels, and perform server actions. The real-time gateway enables WebSocket connections for live event handling. Tokens function as passwords and must remain private. Anyone with the token controls the bot and can send requests as the application. Discord invalidates old tokens immediately after generating new ones. This security measure prevents unauthorized access from leaked credentials. Token exposure creates immediate security risk for bot-controlled servers. Watch the [RedFox Official YouTube channel](https://www.youtube.com/channel/UCYw0Y-7wtBHyM6sDGdHH1lA) for visual token generation guidance.

***

## When Should the Token Be Reset?

Reset the token when the copy button disappears from the Bot page. Discord hides tokens after the first view for security. Regeneration is the only method to obtain a usable token again. Reset tokens immediately after accidental leaks in repositories, screenshots, or chat messages. Reset tokens when team members leave projects or after security incidents. Reset tokens before major deployment changes. Discord invalidates old tokens instantly upon regeneration. Services using the old token stop working until updated. Security guidance consistently emphasizes this practice. Common reset reasons include viewing the token once and closing the page, losing secure storage, accidental sharing, or intentional invalidation for security.

***

## How Do I Get a Bot Token Step by Step?

Navigate to discord.com/developers/applications and sign in with the Discord account that owns the application. Click the application that owns the bot. Create a new application if none exists. Click Bot in the left sidebar. Scroll to the Token area. Click Reset Token if the copy button is not visible. Confirm the reset action in the pop-up window. Complete the identity verification step. Discord requires password prompts, MFA codes, or passkeys depending on account security settings. Copy the new token immediately after Discord displays the token. Paste the token into the target system. Store the token in a secure location such as a password manager or cloud secret manager. Update the token in all environments including code, .env files, CI secrets, hosting platforms, and third-party integrations. Restart the bot or redeploy the service. Discord only exposes regenerated tokens once. The pre-flight checklist ensures correct application selection, existing bot user, available verification method, and prepared safe storage.

***

## What Verification Step Should Be Expected?

Discord requires identity verification before revealing regenerated tokens. The verification method depends on account security settings. Possible methods include account password, two-factor authentication code from an authenticator app, passkey or security key, and SMS backup code. The verification flow remains consistent across methods. Verify identity, then copy the new token immediately. Discord implemented this requirement in 2020 to prevent unauthorized token access. Verification adds approximately 5-10 seconds to the token generation process. This step prevents unauthorized token access effectively. Users must have access to their chosen verification method before initiating token reset. Failed verification attempts lock token regeneration for 15 minutes.

***

## Where Should the Token Be Stored?

Store tokens in a .env file used by bot code. Add the .env file to .gitignore to prevent public exposure. Use cloud secret managers such as Vercel, Railway, Render, AWS Secrets Manager, or Google Cloud Secret Manager. Enter the token in the bot connection form inside the D2T Auto Forward web dashboard at discordtotelegram.com. Use a secure local password manager during deployment preparation. Never store tokens in public GitHub repositories. Never store tokens in screenshots or screen recordings. Never store tokens in chat messages or email. Never store tokens in unencrypted text files on shared drives. Cloud secret managers prevent token leakage effectively. The D2T Auto Forward dashboard encrypts tokens at rest and in transit. Token exposure in public repositories leads to immediate bot compromise.

***

## What Happens If a Token Is Leaked?

Reset the token immediately after a leak. Update every service that uses the old token value. Code or setups using the older token stop working until the new token replaces the old token. Reset the token in the Developer Portal. Replace the token in code, .env files, CI secrets, and hosting platforms. Restart the bot or redeploy the service. Audit logs and app behavior for unauthorized actions. Remove the leaked token from screenshots, chat history, notes, or commit history. Leaked tokens allow attackers to control the bot and access server data. Discord detects and blocks suspicious token usage quickly. Immediate response minimizes damage significantly. Rotate tokens proactively every 90 days as a security best practice.

***

## Related Guides

* [How to Add a Discord Bot to a Server](/fundamentals/how-to-settings-for-task/how-to-add-discord-bot-to-server-discord.md)
* [Auto Send Discord Messages to Another Channel With a Bot](/fundamentals/how-to-settings-for-task/auto-send-discord-messages-to-anther-channel-with-bot.md)
* [Discord to Discord: Setup Guide](/fundamentals/how-to-settings-for-task/discord-to-discord.md)
* [System Settings](/fundamentals/system-settings.md)

***

## Key Takeaways

* Discord bot tokens authenticate bots with Discord servers through secret strings.
* Discord displays regenerated tokens once. Copy and store the token immediately.
* Reset tokens when lost, leaked, or when the copy button disappears.
* Never store tokens in public repositories, screenshots, or chat messages.
* Update the new token in all environments before restarting the bot.
* Cloud secret managers prevent token leakage effectively.

***

## Frequently Asked Questions

**Can the same token be copied more than once?**

No. Discord hides the token after the first view. Reset the token to obtain the token again.

**Does resetting the token break the running bot?**

Yes. The old token stops working immediately. Update all services with the new token.

**Can a token be recovered without resetting?**

No. Discord provides no reveal or recover function. Reset is the only option.

**Should the token be shared with team members?**

No. Team members should access tokens through secure secret managers. Direct sharing creates leak risks.

**How often should the token be rotated?**

Rotate tokens every 90 days or after suspected leaks, team departures, or major deployments.

**What happens if verification fails?**

Discord locks token regeneration for 15 minutes after failed verification attempts.

**Can tokens be used across multiple applications?**

No. Tokens are tied to specific bot applications. Each application requires a unique token.

***

## Get Started

Generate a Discord bot token and connect the token to D2T Auto Forward in under two minutes:

* **Web Dashboard:** [D2T Auto Forward web dashboard at discordtotelegram.com](https://discordtotelegram.com)
* **Android:** [D2T Auto Forward Android app on Google Play](https://play.google.com/store/apps/details?id=com.autoforward.dc2tele)
* **iOS:** [D2T Auto Forward iOS app on the App Store](https://apps.apple.com/app/d2t-auto-forward-message/id6743234921)
* **Video Tutorial:** [RedFox Official YouTube channel](https://www.youtube.com/channel/UCYw0Y-7wtBHyM6sDGdHH1lA)