Discord servers have no native "export member list" button. The data is there — every server has a members list with names, join dates, roles — but the only way to get it out of discord.com in 2026 is either through community-management bots or a browser extension that reads the DOM during your session.
This 2026 guide covers what fields a real Discord user list export should include, the official workarounds (and why they don't quite work), and how to do it in one click with DiscordKit's User List Exporter.

A real export should capture — at minimum — these fields:
| Field | Notes | |---|---| | User ID (snowflake) | Stable, immutable, primary key for joins | | Username | The original handle (e.g. discorduser) | | Display name | Currently shown name (e.g. Discord User) | | Global display name | The cross-server display name (introduced 2023) | | Nickname | Per-server nick, may be empty | | Server nickname | If different from global nickname | | Join date | Server-specific join timestamp (ISO 8601) | | Account creation date | Discord-wide account creation | | Roles | List of role names plus role IDs | | Boost status | Boost tier and start date, if any | | Avatar URL | Stable CDN URL to current avatar | | Bot status | Boolean — is this a bot user? | | Status | Online / idle / DND / offline at the time of export | | Voice channel | Currently connected voice channel ID, if any |
Most "Discord member list" tools skip half of these — especially join dates, global vs server nicknames, and roles. A real export should not.
Discord ships a built-in Server Insights panel for servers above the Partner threshold or with 500+ members and an active community. Insights shows engagement metrics, not raw member lists.
So Insights is useful for board-level reporting but useless for the audit / migration / outreach workflows you probably have in mind.
/membercount and similar commandsMany community-management bots expose member data through slash commands:
/membercount — total count only/whois @user — one user at a time/roleinfo <role> — users in a role, returned paginated, not exportableIf your server already runs MEE6, Carl-bot, Dyno, or similar, you might be tempted to script around these commands. The catch: every one of those endpoints requires the bot to be running, and most cap responses at 100 members per call. For a 5,000-member server you'd run 50 commands and manually paste 50 tables together.
Discord User List Exporter reads the full member list from the server view page DOM in a single pass and writes it to CSV or XLSX.
Add the User List Exporter from the product page. Chrome, Firefox, and Edge builds are available.
The extension detects the active server from the URL, then progressively loads every member shard from your authenticated session. Loading happens with backoff so it never triggers Discord's rate limits.

Three configuration panels:
The file downloads in seconds to minutes depending on server size. A 10,000-member server takes roughly 30-90 seconds; 100,000-member takes a few minutes. The extension throttles itself to Discord's published rate-limit budget.
user_id,username,display_name,global_name,nickname,joined_at,account_created_at,roles,boost_start,is_bot
218548978765438976,janedoe,Jane Doe,jane,#1989 Support — Tier 2,2023-04-12T16:33:21Z,2017-02-04T08:00:00Z,"@support;@veteran",2024-11-01T00:00:00Z,false
…
Most spreadsheet apps open CSV directly. If you'd rather keep role lists as separate columns (one per cell rather than semicolon-joined), the XLSX output gives that.
For most audit / migration needs, CSV with UTF-8 BOM is the safest pick because every downstream tool reads it.
| Workflow | Why the export helps | |---|---| | Audit / compliance | Spot inactive members, verify KYC information, prove moderation actions | | Server migration | Recreate your roster in the new platform (Slack, Matrix, custom) | | Marketing | DM outreach, mailing list building, role-based campaigns | | Growth analysis | Track joiner velocity, role distribution drift, churn detection | | Game night planning | Quickly check who's online or recently active |
DiscordKit's export respects your server's privacy settings — if a user has set their Discord profile to private, the columns that rely on profile visibility show "—" but the row is still exported (so the audit is complete).
When you export a server member list, you have a list of every member's user ID, username, join date, and roles. Treat that list the same way you'd treat an internal HR roster:
DiscordKit's exporter stores nothing on its own servers — the file is generated entirely in your browser.
Yes, if you can see the member list in Discord. The extension reads what's already visible to you. It does not bypass any privacy controls.
Boosts are included with start date. Role history is not — Discord does not expose historical roles to client-side extensions, only the current role set per member.
No. The export reads the active member list. Banned members live in the audit log, which is server-staff-only and not surfaced through the same DOM.
Yes, offline members appear with their last-known status. The "last seen" timestamp is not currently exported — Discord does not expose it to client-side tooling.
No, those use a different UI and a smaller membership model. DiscordKit has no DM-list export product.
The extension back-off automatically and resumes. You'll see a progress bar that pauses and re-starts; if it errors out completely, you can re-run with a delay.
Tens of thousands. There's no fixed cap, but the run time scales linearly. DiscordKit recommends chunking 50,000+ member servers into role-filtered sub-exports for spreadsheet performance.
Install: DiscordKit User List Exporter
Updated 2026-09-27. Maintained by the DiscordKit team. Discord is a trademark of Discord Inc.; this guide is unofficial and not affiliated with Discord Inc.