Back to Documentation

How to Use Discord Server Cloner - Complete Guide

Complete guide on how to use Discord Server Cloner to clone Discord servers with selective options, secure token management, and advanced features.

Who it's for: Discord server administrators who want to clone server structures, settings, roles, channels, and messages to another server.

Outcome: You will know how to download, set up, and use Discord Server Cloner to clone servers with complete control over what gets cloned, manage tokens securely, and use all advanced features.

Prerequisites

  • Windows operating system
  • Valid Discord token with appropriate permissions
  • Internet connection
  • Discord permissions: guilds.read, channels.read, messages.read, guilds.manage, channels.manage, roles.manage

Privacy & Security Notice

We never store your token. The Discord Server Cloner application does not store your Discord token or any other personal information on our servers. Everything is stored locally on your computer using Windows Credential Manager.

  • Your Discord token is stored securely in Windows Credential Manager on your local machine
  • No data is sent to external servers (except Discord's API for cloning operations)
  • No telemetry, tracking, or analytics are collected
  • All operations are performed locally on your computer
  • Your token is automatically cleared from memory when you close the application

Installation

  1. 1

    Download the executable

    Download the Discord Server Cloner executable from the project page. The application is a standalone Windows executable - no installation or Python required.

    Download Discord Server Cloner.exe from the project page
  2. 2

    Launch the application

    Run the executable file. The application will start with a modern GUI interface. You'll see options for entering your Discord token and selecting servers.

    Double-click Discord Server Cloner.exe to launch
  3. 3

    Get your Discord token

    You need a Discord token to authenticate. Open Discord in your web browser, press F12 to open Developer Tools, go to the Network tab, look for any Discord API request, and copy the authorization header value. Never share your token with anyone.

    F12 → Network tab → Find Discord API request → Copy authorization header

Configuration

  1. 1

    Enter your Discord token

    Paste your Discord token into the token input field and click "Verify" to authenticate. Your token will be stored securely using Windows Credential Manager.

    Paste token → Click "Verify"
  2. 2

    Select source server

    Click "Select a server" to choose the server you want to clone. You can search by name or enter the server ID manually. The server must be one you have access to.

    Click "Select a server" → Search or enter ID → Select server
  3. 3

    Select destination server

    Choose where you want to clone the server to. You can select an existing server (preferably empty) or create a new server. The destination server should be one you can manage.

    Click "Select a server" in destination section → Choose server or create new
  4. 4

    Configure cloning options

    Before starting, configure what you want to clone. Check the options for: Clone roles, Clone text channels, Clone voice channels, Clone messages, Clone name and icon, Clone categories. Set a message limit if cloning messages. Then click "Start Cloning" and monitor the progress.

    Configure options → Set message limit (if cloning messages) → Click "Start Cloning"

Verification

Test the complete workflow: download, launch, enter token, select servers, configure options, and start cloning. You should see progress updates and the cloning should complete successfully.

Launch app → Enter token → Select servers → Configure options → Start cloning

Expected output:

✅ Cloning started
📊 Progress: Roles (0/10), Channels (0/25), Messages (0/1000)
⏱️ Estimated time: 5 minutes

Common Errors & Quick Fixes

Authentication error or invalid token

Fix: Verify your Discord token is valid and hasn't expired. Check that you copied the full token. Try logging out and back into Discord, then get a new token. Ensure you have the necessary permissions.

Cannot find server

Fix: Verify both source and destination servers exist and you have access to them. Check that server IDs are correct. Ensure you have the required permissions in both servers.

Same server error

Fix: Source and destination server IDs cannot be the same. Select a different destination server. You cannot clone a server to itself.

Rate limit errors

Fix: The app handles rate limits automatically. If you see rate limit messages, wait a few moments. The app will automatically retry when the limit resets. Consider cloning in smaller batches (fewer channels at once).

Progress lost or interrupted

Fix: Check for cloning_progress.json in the application directory. Progress may be recoverable if the file exists. Enable progress persistence in settings. You can resume or restart the process.

Token not saving

Fix: Ensure Windows Credential Manager is accessible. Try running the app with appropriate permissions. Check that your user account has permission to use the credential store.

Permission denied errors

Fix: Ensure you have the required Discord permissions in both source and destination servers: guilds.read, channels.read, messages.read, guilds.manage, channels.manage, roles.manage. Check your role position in the servers.

Important Notes

  • Use selective cloning options to clone only what you need
  • Set appropriate message limits to avoid hitting Discord API limits
  • Always use an empty destination server when possible to avoid conflicts
  • Keep your Discord token secure and log out after use to invalidate it
  • Monitor cloning progress and check for any errors
  • Remember: Personal use only - commercial use is prohibited
  • Check the documentation for advanced features like server explorer and message viewer
  • Use progress persistence to resume interrupted cloning operations
Tested on: Windows 10/11, Discord API v10, Discord Server Cloner v0.1.0
Last updated: 1/23/2025