How to Export Discord Messages Safely

Discord’s official data package is an account record, not a full transcript of both sides. That limitation determines how you should preserve a Discord dispute.

Request your Discord data package

On desktop or in a browser:

1. Click the cogwheel to open User Settings.
2. Select Data & Privacy and scroll to Request your data.
3. Click Request Data, choose the categories you need, then click Request My Data.
4. Confirm the request and watch the email address attached to the account.

On mobile:

1. Tap your avatar, then the cogwheel for Settings.
2. Tap Data & Privacy › Request all of my data.
3. Select the requested categories and tap Request My Data.

Discord says the package should arrive within 30 days. The email download link remains active for 30 days. Do not disable or delete the account while waiting because Discord says that cancels the request. Download the ZIP, preserve it unchanged, and save the request and delivery emails.

What the Messages folder contains

The Messages folder contains messages sent by your account. Discord separates direct messages, group messages, and server channels into folders identified by channel ID. A mapping JSON connects channel IDs to channel names.

Each channel folder contains information about its destination and a message transcript JSON. Discord documents four principal message fields: ID, exact timestamp, contents, and attachment CDN links. Server entries can identify the guild, channel ID, and channel name; DM entries can identify channel and user IDs.

This structure is valuable because IDs and timestamps are stronger reference points than a cropped screenshot. Preserve them. Do not rewrite JSON or replace IDs with display names in the source copy.

What it does not contain

The package does not contain messages written by other people. It also excludes manually deleted messages and correspondence with Discord Customer Support or Trust & Safety. If you left a server before requesting the package, Discord says it may not be represented, although recently departed servers may appear.

Attachment fields are links, not necessarily embedded copies. If an attachment is still available and you are permitted to retain it, save it promptly and note the source message ID. Do not assume a CDN URL will work indefinitely.

Why token-based exporters are risky

Some third-party “chat exporter” utilities ask for a Discord user token and automate the normal account to retrieve history. Discord calls automation of a normal user account a self-bot. Its policy says self-bots outside the OAuth2 or bot API are forbidden and can result in account termination.

Discord’s Protecting Your Data article also says self-bots used for scraping violate its API terms. This does not mean every independent viewer or JSON parser is prohibited. The concern is automating a normal user account with its token. Do not paste a user token into a tool or extension. Use the official package and ordinary on-screen preservation instead.

Preserve both sides of a dispute

Use the official package for your sent messages, then capture the visible conversation for the other participants’ messages.

1. Request and preserve the data package.
2. Copy message links for key messages and record message, channel, server, and user IDs where available.
3. Take overlapping screenshots or a continuous screen recording that shows the account or server, date dividers, and surrounding context.
4. Save original attachments and note which message each came from.
5. Record the device, date, account, and steps used.
6. Keep the source files unchanged and make working copies for excerpts or redaction.

Avoid capturing only isolated allegations. Include enough earlier and later conversation to show replies and context. If a member changes a display name, stable IDs help connect the records.

Report abuse and preserve before it disappears

Use Discord’s in-app reporting route for content that violates its policies. Preserve message links and IDs before blocking, leaving a server, or losing access. A report to Discord is separate from your own preservation and may not give you a complete transcript later.

For threats, exploitation, or immediate danger, contact the appropriate local authority. Discord directs governmental and law-enforcement requests through its Government Request Portal and asks agencies for valid account or message identifiers. Individuals should not pretend to submit a law-enforcement request; give preserved IDs and links to the investigator handling the matter.

The official package plus careful visual capture provides a candid record of each source. Keep originals, explain the gap between your sent-message package and the on-screen capture, and never describe the combined output as automatically accepted or complete.

Navigate the package without losing context

Discord’s package is organized around account data, not around a printable two-person conversation. Extract a working copy and keep the delivered ZIP untouched. In the Messages area, channel folders use channel identifiers; an index or channel metadata connects those identifiers to direct messages, group DMs, or server channels.

Discord’s current help article describes message data in JSON. Older packages and third-party descriptions sometimes mention CSV, but Discord does not currently promise CSV as the message transcript format. Do not rename a JSON file to .csv or rely on an old folder diagram. Record what your delivered package actually contains.

For each important channel, preserve its channel ID, server or guild information when present, and the message records. A message record can provide the message ID, exact timestamp, content, and attachment CDN URL. Those identifiers let another person locate or discuss a specific item without depending on a changeable display name.

The package contains only content sent by the requesting account because it is that account’s data-access package, not a server archive. A DM folder therefore is not a complete DM transcript. Put a clear note on any presentation made from it: “Official Discord package; requesting account’s sent messages only.”

Copy message links and IDs

Message links and IDs give each preserved screenshot a stable reference. Before leaving a server or blocking a user, copy links for key messages and record the server, channel, message, and user IDs that are visible to you.

On desktop, enable User Settings › Advanced › Developer Mode. You can then right-click a user, server, channel, or message and choose the relevant Copy ID command. To copy a message link, use the message’s context menu and Copy Message Link. Mobile menus vary, but Developer Mode also exposes copy-ID actions.

An ID does not prove authorship by itself. Pair it with the package record, visible profile and server context, and overlapping screenshots. Keep the full link string in notes rather than shortening it. If access later disappears, the link may stop opening for you, but the recorded identifiers remain useful for describing what you preserved.

Capture the messages Discord does not export

Visual capture supplies the other participants’ side that the account package omits. Use overlapping screenshots or a continuous screen recording, and show the channel heading, date dividers, reply previews, edited labels, and enough preceding and following conversation to explain each exchange.

Scroll at a readable speed and allow older messages and attachments to load. Capture participant profiles and role labels separately when identity matters. If a message has been edited, a current screenshot shows the current rendering, not every earlier version. If it was deleted before capture, the official package will not restore it.

Store screenshots and recordings in their original format. Make annotations, crops, or redactions only on copies. Maintain a simple index matching each key screenshot to its message link and ID. The screenshots versus exports guide explains why both sources are useful.

Preserve attachments before links expire

Discord’s package can provide attachment CDN links rather than embedding each file. If you are authorized to keep an attachment and it remains accessible, save it promptly from the message and record the message ID, original filename, download date, and link. Do not assume the URL is permanent.

Keep the downloaded attachment unchanged and create a separate viewing copy if conversion is needed. A broken link later does not prove that no attachment existed; conversely, a saved file needs its message context to show where it came from. Avoid opening suspicious executables or archives on your main device.

Report content while preserving your own record

Reporting and preservation are separate steps. Use Discord’s in-app Report Message or safety flow for content covered by its policies, and preserve the link and IDs first when it is safe to do so. Save the report confirmation, but do not expect a Trust & Safety report to return a transcript to you.

For an immediate threat, contact local emergency services. For other criminal concerns, provide investigators with the account, server, channel, message links, IDs, timestamps, screenshots, and original package you possess. Discord’s law-enforcement guidance directs government agencies to its Government Request Portal. That portal is not a route for an individual to impersonate an agency or request someone else’s account data.

Avoid self-bots and token disclosure

Discord expressly prohibits automating a normal user account as a self-bot and warns that doing so can terminate the account. A tool that asks you to paste a user token so it can crawl channels creates both a rules problem and a security risk: the token can grant access as you.

Use Discord’s official package, ordinary copy-link and copy-ID controls, and lawful screen capture. Parsing a ZIP you already received is different from logging in as your account and scraping Discord. Still review any local parser before using it, and never upload a sensitive package to an unknown website.

Assemble a practical dispute file

A clear Discord record separates sources instead of pretending they are one complete export.

1. Keep the untouched Discord ZIP and request and delivery emails.
2. Extract a working copy and index relevant channel and message IDs.
3. Save message links and permitted attachments.
4. Capture overlapping views of both sides with timestamps and channel context.
5. Write an acquisition note listing account, device, date, and each action.
6. Create excerpts or a printable chronology only from copies, with source labels.

Retain unrelated context securely and redact only a presentation copy. The preservation guide covers original-versus-working-copy practice, and the authentication guide covers account identity and authorship. For harassment, the harassment evidence guide and incident-log tool can help organize events without altering the messages.

Troubleshoot a missing package or channel

If the email has not arrived, allow the stated delivery period and check the email account attached to Discord. Do not delete or disable the Discord account while the request is pending. When a link arrives, download before its stated expiration and preserve the email.

If a channel is absent, confirm that Messages was among the requested categories and inspect the channel index. Discord says manually deleted messages are absent, and access or server departure can affect what appears. Do not infer that the conversation never existed. Preserve any lawful screenshots, links, and IDs already collected and describe the package’s one-sided limitation plainly.