How to Clone or Copy a Discord Server to a New One (Channels, Roles, and Bots)
To clone a Discord server, you copy its structure (channels, categories, roles, and permissions) into a new server using a server template, a clone tool, or an AI builder. None of these methods copy members, messages, emojis, or bot configs, so you re-add bots and integrations manually after the copy.
That last sentence is the part most guides skip. There is no "Duplicate Server" button in Discord, and nothing you do can drag your members, chat history, or installed bots into a fresh server in one click. What you can clone is the skeleton: the layout of channels, the role list, and the permission overwrites that hold it all together. This guide walks through every realistic way to do that, in order of how clean the result is, then covers the manual cleanup that every method leaves behind.
What "cloning" a server actually means (and what it can't copy)
Before you pick a method, get clear on the line between structure and content, because it saves hours of confusion later.
What clones cleanly:
- Channels and categories (text, voice, forum, announcement)
- The order and nesting of those channels
- Roles, their names, colors, and permissions
- Channel-level permission overwrites (who can see/post where)
- Basic server settings like the verification level
What never clones automatically:
- Members (people have to be re-invited, full stop)
- Messages and chat history
- Custom emojis and stickers (most methods drop these)
- Bots (a bot is a separate app you re-invite and reconfigure)
- Webhooks and their URLs
- Integrations (Twitch subs, YouTube, linked roles)
- Bans and the audit log
So when someone says "clone my server," they almost always mean recreate the layout and roles so I don't have to build 40 channels by hand. That is achievable. Migrating an actual community with its people and posts is a different job, and we cover where that breaks down at the end.
Option 1: Use a server template
A server template is Discord's own built-in feature for copying structure. It captures your channels, categories, roles, and permission setup into a shareable link, and anyone with that link can spin up a new server from it.
How to create and use one
- Open the source server, go to Server Settings → Template.
- Click Generate Template, give it a name, and copy the link.
- Open the link (or click Create Template when starting a new server) and Discord builds a fresh server with that exact layout.
That's it for the structure. If you want the full walkthrough with screenshots and the gotchas around updating a template after you've changed the source, we wrote a dedicated guide on how to use a Discord server template.
The limits you need to know
Templates are the cleanest native option, but they have hard edges:
- No bots. A template stores no bot information. Any roles your bots created (like a "MEE6" role or a muted role) come across as empty roles with no bot attached.
- No bot configuration. Even after you re-invite a bot, its settings, level data, ticket panels, and automod rules do not come back. The template never had them.
- No emojis, no members, no messages. Standard for every method, but worth repeating.
- Permission integrations can drift. Templates copy permission overwrites, but if a role's position in the hierarchy mattered (and it usually does), double-check the order after creation, because subtle reordering can change who can manage whom.
Templates are perfect when you want an identical layout for a second community, a staging copy, or a "reset" of your own server. They are not a migration tool.
Option 2: Clone tools and what they actually carry over
Beyond Discord's native template, there are third-party "server cloner" bots and scripts. These read a source server through the Discord API and recreate its parts in a target server you control.
A good clone tool can copy more than a template does in one pass: channels, categories, roles, permission overwrites, and in some cases custom emojis and the server icon. That extra emoji and icon coverage is the main reason people reach for them over the native template.
The honest caveats
- Permissions. The bot doing the cloning can only assign permissions it itself has. If the cloner's own role sits below an important role, it physically cannot recreate that role's powers. You often finish with a layout that looks right but has subtly weaker permissions on the top roles.
- Rate limits. Discord throttles bulk channel and role creation. Large servers can take a while, and a poorly written tool can stall or partially clone.
- Trust and tokens. Some sketchier "cloner" tools ask for a user token, which is against Discord's Terms of Service and a security risk. Stick to tools that use a proper bot token and invite, and never paste your personal account token anywhere.
- Still no bots, members, or messages. A clone tool moves structure, not your community.
Clone tools are worth it when emojis and the exact icon matter and you don't mind a manual permission audit afterward. For anything involving combining communities rather than copying one, see our breakdown of whether you can merge two Discord servers — the short answer changes how you'd approach this entirely.
Option 3: Rebuild from a description with an AI builder
There's a third path that flips the problem. Instead of mechanically copying an existing server byte-for-byte, you describe the server you want and have it generated fresh. This is the fastest route when you're cloning the idea of a server rather than an exact mirror — for example, "I want another gaming community like my main one, but for a different game."
PeakBot's AI Server Builder does this in under 60 seconds. You write a plain-English description ("a community server for a 200-person study group with study-room voice channels, accountability text channels, role-gated resources, and onboarding") and it builds the full structure: channels, categories, roles, permissions, and automations. It is the only Discord bot that generates fully custom server layouts from natural language rather than dropping a preset template on you.
Why this beats a raw clone in a lot of cases:
- It fixes problems instead of copying them. If your original server grew messy over two years, a template clones the mess. A description-based rebuild gives you a clean structure built around what the server is actually for.
- Permissions are set up coherently from the start, so you skip the "why can't this role see that channel" debugging that clone tools create.
- You can iterate. Don't like the channel split? Re-describe and regenerate, rather than dragging channels around for an hour.
The AI Server Builder is a Pro feature ($8.25/month, or $69/year, per server). Note that, like every method here, it builds structure and automations — it won't import your old members or messages, because nothing can.
Re-adding bots, webhooks, and integrations
This is the manual phase no clone method removes. Budget real time for it.
Bots. For each bot you ran, go to its website or use its invite link and add it to the new server. Then reconfigure it from scratch: prefixes, automod rules, level roles, ticket categories, welcome messages. None of this travels with a clone. If you were juggling several bots — MEE6 for leveling, Carl-bot for reaction roles, Dyno for moderation — this is the moment to reconsider. Each is good at its thing (Carl-bot's reaction roles are genuinely solid, Dyno's moderation is battle-tested and cheap at $4.99/mo, MEE6 has the most name recognition), but reinstalling and reconfiguring four bots on a new server is four separate setup chores.
PeakBot replaces MEE6, Carl-bot, Dyno, and TidyCord with one bot, so re-adding it is a single invite covering AI moderation, XP and leveling, tickets, welcome messages, reaction roles, giveaways, and logging. With 30+ features free and no time limit, it's the lightest bot setup to redo on a fresh server. See the full free feature list before you reinstall four separate tools.
Webhooks. Webhook URLs are tied to the original channels and never clone. Recreate each one in Channel Settings → Integrations → Webhooks, and update wherever the URL was used (your posting scripts, IFTTT/Zapier flows, GitHub notifications).
Integrations. Twitch subscriber sync, YouTube membership roles, and Discord's linked-roles all have to be reconnected through Server Settings → Integrations on the new server. Re-link the platform accounts there.
Fixing permissions and role hierarchy after the copy
Even a perfect structure copy can leave permissions subtly broken, because hierarchy is positional and clone tools can't always preserve a bot's own standing.
Work through this checklist on the new server:
- Re-order roles top to bottom. A role can only manage roles below it. Drag your staff roles back above member roles, and make sure each bot's auto-created role sits high enough to do its job (most bots need their role near the top).
- Check the @everyone baseline. This role's permissions cascade everywhere. Confirm dangerous permissions (Manage Server, Mention Everyone, Administrator) aren't accidentally on.
- Spot-check channel overwrites. Open two or three sensitive channels (mod-only, announcements) and confirm the right roles can see and post.
- Test with a low role. Use Discord's "View Server As Role" feature (or a test account) to see the server as a plain member and catch anything left exposed.
- Re-grant bot roles. After inviting each bot, drag its role up to where it needs to be — a moderation bot below the roles it's meant to manage simply won't work.
Do this before you invite a single member. Fixing permissions on an empty server is calm; fixing them while hundreds of people are poking around is not.
FAQ: members, messages, and emoji
Can you clone a Discord server with its members?
No. There is no method — template, clone tool, or AI builder — that copies members into a new server. People are tied to a server by joining it, so everyone has to be re-invited with a fresh invite link. You can post the new invite in your old server to bring people over.
Do messages and chat history transfer when you copy a server?
No. Messages live in their original channels and never move during a clone. The new server's channels start empty. If preserving conversations matters, the closest option is keeping the old server alive as an archive, or reading our guide on how to back up a Discord server and restore it for what can and can't be saved.
Can you copy custom emojis and stickers to the new server?
Native templates do not copy emojis or stickers. Some third-party clone tools can carry emojis over, and you can always re-upload them manually by downloading each emoji image from the old server and uploading it under Server Settings → Emoji on the new one.
Is it against Discord's rules to use a clone tool?
Using a proper bot with an invite and a bot token is fine. What violates Discord's Terms of Service is any tool that asks for your personal user account token to self-bot the clone. Avoid those — they're both rule-breaking and a real account-security risk.
What's the fastest way to set up the new server once it's cloned?
Get the structure in place first (template, clone tool, or AI builder), fix the role hierarchy, then add one bot that covers moderation, leveling, tickets, and welcomes instead of stacking several. PeakBot is built for exactly that one-invite setup, and Pro adds the AI Server Builder if you'd rather generate the structure than clone it.
The short version
Cloning a Discord server means copying its structure, never its community. Use a template for an exact native copy, a clone tool if you also need emojis and the icon, or PeakBot's AI Server Builder to generate a clean, custom structure from a description in under 60 seconds. Then do the unavoidable manual work: re-invite bots, recreate webhooks and integrations, fix the role hierarchy, and finally invite people. Pick the method that matches whether you want an exact mirror or a fresh, better-organized start.
