← Back to all guides
Guide

Export Slack Messages: You Cannot Do This Yourself

Updated Nov 14, 2026

There is no export button on your Slack account. Your messages live inside a workspace, and the workspace belongs to whoever set it up. If that person is not you, getting your history out means asking them to run the export, or filing a privacy request and waiting. This guide covers both paths and what actually lands once the archive arrives.

Export at a glance

Request method
Privacy / support form
Delivery time
Days
Archive format
JSON, CSV
Sensitivity
High: health, biometric, financial, precise location
Primary use
Backup: preserve a copy for yourself

Archive file map

Top-level structure of the export. Each entry is a file or directory with its format badge and what it contains.

<date>/messages.jsonJSON
One file per channel per date. User IDs and Unix timestamps, mapped through the lookup files
users.jsonJSON
User ID to display name, email and role. The lookup table that makes messages readable
channels.jsonJSON
Channel ID to name and metadata. Same job for channels that users.json does for people
channel_audit_report.csvCSV
Separate download from the admin panel. One row per message with channel, sender and timestamp

Who owns the export

Slack treats a workspace as a shared space. Your messages are partly yours, but they also belong to the people you sent them to, and to the organisation that hosts the workspace. So the export tool sits with the workspace owner or an admin. You cannot run it yourself unless you happen to be one of those people.

This is not a Slack-specific quirk. Most workplace tools work the same way. The practical effect is that requesting your data is a conversation, not a click.

What each plan can export

The scope of the export depends on what the workspace pays for. This matters because it determines whether your direct messages are in the archive at all.

  • Free workspaces: public channel messages only. No private channels, no direct messages, no group messages. The export covers public channels and the user list, and that is it.
  • Standard and Plus: public channels, plus the ability to request private channels and multi-party direct messages. The admin has to apply to Slack for the expanded export tool first.
  • Business+ and Enterprise Grid: the full export, including single direct messages. Enterprise Grid runs the export from organisation-level settings rather than workspace settings.
  • If you are on a free workspace, the archive will not contain your private conversations. That is the plan limit, not a configuration choice.

How to get your data out

There are two routes. If you are the workspace owner or an admin, you can run the export yourself. If you are not, you need to ask someone who is, or file a privacy request.

  1. If you are the admin: open the desktop client. Go to Admin in the left sidebar, then Workspace settings, then Security, then Import and export data. Open the Export tab. On Enterprise Grid, this sits under organisation settings instead.
  2. Choose the date range. You can export all messages or a specific window. On paid plans with the expanded tool, you can also include private channels and direct messages.
  3. Start the export. Slack emails you when the ZIP is ready. They do not publish how long this takes.
  4. Download the file on a stable connection. An interrupted download restarts the entire export rather than resuming from where it stopped.
  5. If you are not the admin: ask them to run an export and share the file with you. There is no built-in way to request this from inside Slack.
  6. The other route is a privacy request. Go to slack.com/trust/privacy-request, submit against the email address on your Slack account, and wait. Slack verifies the request against your account before releasing anything. There is no published timeline for how long this takes.

What the archive contains

  • A folder per date that has messages. Empty dates are silently absent, so a gap in the archive is a gap in the record rather than an error.
  • messages.json per channel, per date. Every message is a JSON object with a user ID, a Unix timestamp, and the message text.
  • users.json: a lookup table mapping user IDs to display names, email addresses and roles.
  • channels.json: channel IDs mapped to channel names and metadata.
  • On paid plans with the expanded export, a separate set of files covers private channels and direct messages in the same format.
  • The channel audit report, available as a separate CSV download from the same admin panel. One row per message with the channel name, sender and timestamp in plain columns.

File links, not files

Every attachment in the export is a URL, not the file itself. If the file has been deleted, or the channel it was shared in has been deleted, the link no longer resolves. The picture you shared in a channel last March may already be gone from Slack's side, and the export will hand you a dead link rather than the image.

On Enterprise Grid with a single-user text export, files are included inline. On every other plan and export type, they are references. If anything in a channel matters to you, save it separately before the link expires.

Slack does not document how long the download link on the export ZIP itself stays valid. Take the file as soon as the email arrives.

Reading the JSON

The archive is raw JSON. User IDs are strings like U04FK6XAB2, timestamps are Unix integers, and channel references are IDs rather than names. Before any of it reads as text, you have to map the IDs through users.json and channels.json.

A few practical options for making it usable:

  • Open any JSON file in a browser tab. Most browsers render it as a collapsible tree, which is enough for a quick look.
  • Use a JSON viewer extension or a tool like jsonviewer.stack.hu for a cleaner interface.
  • Write a short script to walk the messages and print them as readable text. The structure is flat: each message has a user, a timestamp and a text field. A Python script in twenty lines does the job.
  • Budget an afternoon for a large workspace, or find a Slack export viewer. Several exist, though none are maintained by Slack and their longevity is uncertain.

What is not in the export

  • Thread replies are flattened. They appear inline in timestamp order rather than nested, so you cannot reliably reconstruct which message was a reply to which.
  • Edited and deleted messages only appear if your workspace retention settings kept them. On many plans, they did not. The history in the export can quietly differ from the history that used to exist.
  • Bot messages are included in broad exports, and Slack documents no way to filter them out. Slackbot traffic alone can be a large share of the volume.
  • Actions artifacts, workflow run logs, Pages deploy history and repository secrets are not part of any Slack export. Those belong to the integrations, not the messaging layer.
  • Slack Connect channels and guest accounts are not addressed in Slack's own export documentation. Take what arrives rather than expecting a clear answer either way.

Quick version

If you want the short checklist instead of the full guide, use the service page.

Related guides

FAQ

Can I export my Slack messages myself?

Not unless you are the workspace owner or an admin. The export tool belongs to the workspace, not to individual accounts. If you are not an admin, ask one to run the export, or file a privacy request at slack.com/trust/privacy-request.

Does the Slack export include direct messages?

Only on paid plans. Free workspaces export public channels only. Standard, Plus, Business+ and Enterprise Grid can include private channels and direct messages, but the admin has to apply to Slack for the expanded export tool first on Standard and Plus.

How long does a Slack export take?

Slack emails you when the file is ready and does not publish how long that takes. For a small workspace it may be minutes. For a large one with years of messages, plan for hours. There is no guaranteed timeline.

Are the files I shared in Slack included in the export?

No. The export contains URLs pointing to the files, not the files themselves. If a file has been deleted or the channel removed, the link no longer works. Save anything important separately.

Last verified: Nov 14, 2026. Steps checked against slack.com. Report an outdated step →

About the author

Charles runs Digital Takeout Day, a twice-yearly reminder (May 8 and November 8) to download and back up your data from every online service you use.

Every guide is cross-checked against the platform's own export documentation and re-verified before each Takeout Day.

Read the full bio, editorial policy, and contact →