Discord Chat Exporter

LET’S GET YOUR HISTORY HOME.

Help & support.

A guide to making your first export—and getting unstuck along the way.

Never post an API token, private conversation, or unredacted export in a support request. The maintainer will never need your token.

Make your first export

  1. Install from the Chrome Web Store and open a server channel or direct message at https://discord.com. The desktop app is not supported.
  2. Open the extension from the browser toolbar. Paste your API token and select Connect. The extension only uses the token you explicitly provide; it never extracts credentials from Discord.
  3. Confirm the source, server, and conversation. Choose Every channel in this source if you want separate files for all returned text channels or direct messages.
  4. Choose JSON for structured message data, CSV for spreadsheets, or TXT for a readable transcript.
  5. Leave All time enabled for all available history, or turn it off and set dates. Dates use UTC; the Through date includes the entire day.
  6. Select Export conversation. Follow progress in the new tab, and choose download locations if prompted.
  7. Use Clear in the popup to remove your token after exporting.

About the API token

This version asks for an API token that can read the selected messages. Discord does not provide a supported way for users to reveal or export their personal session token, and this project will not extract it from browser storage, cookies, or network traffic. Do not use developer tools, token-finder extensions, or third-party websites to obtain or test a token; never share one in a support request.

Discord OAuth scopes are limited: the standard guilds scope only returns basic server information, dm_channels.read requires Discord approval, and messages.read is documented for local RPC access rather than ordinary extension API access. An OAuth sign-in button therefore cannot currently replace the credential this version expects. If you do not already have an authorized token, there is no safe setup path for this version today. See Discord's OAuth2 scope documentation.

Only use credentials and data you are authorized to access. Follow Discord's terms and your community's rules. See the privacy policy for how a supplied token is stored and used.

Troubleshooting

The popup says to open Discord

Use the browser version at discord.com and open an actual channel or DM. Keep that tab active, then reopen the popup. The server overview and DM list do not select a conversation.

No servers or conversations appear

Paste your token and select Connect. If it has changed or expired, clear it and connect again. Select another source to refresh the list. The extension lists text and announcement channels; categories, voice, forums, and threads are excluded.

401: token rejected

The API did not accept the token. Clear it in the popup and enter a valid token. Reconnect before retrying the export. Never send the token to the maintainer.

403: permission denied / 404: unavailable

Your credentials cannot read the selected conversation, or the channel was deleted or is no longer available. Choose a conversation you can access. A batch stops at the first error; completed files are kept.

429: rate limit reached

The extension waits and retries rate-limited requests up to three times. If the rate limit continues, wait before using Try again. Avoid running other bulk API tasks at the same time.

The export is slow or looks stuck

Large histories are paginated and may take time. The message count updates as batches arrive. Check whether your browser has a save dialog open. Keep the browser running; sleeping, restarting, or reloading the extension can interrupt an export. Large exports also depend on available browser memory.

How do I cancel or retry?

Select Cancel export in the export tab or popup. Already saved files remain on your device. Use Try again to start over; this does not resume a partial export. Browsers may rename files when the same name already exists.

Where is my file?

Open your browser’s Downloads page. The extension hands each file to the browser’s download manager. A completed export means the downloads were requested; disk or browser errors can still prevent a file from being saved.

The export is empty or attachment links stopped working

Check the date range and channel selection. Empty histories produce valid empty files. Attachment URLs are links, not copied attachment files; Discord may expire them. Save attachments separately while the links work.

CSV values start with an apostrophe

Cells starting with characters that spreadsheets may interpret as formulas are prefixed with an apostrophe for safer opening. Use JSON when you need the exact original message text.

Report an issue

Search existing GitHub issues, then open a bug report with your extension version, browser version, operating system, source type, file format, and steps to reproduce. Include the visible error with private identifiers removed.

GitHub issues are public. Do not attach personal exports, tokens, private channel names, or browser session data. Feature suggestions are welcome in the same issue tracker.