How to export Slack messages for your records
Slack is where a lot of workplace communication lives - decisions, agreements, disputes, feedback, and the conversations that lead up to all of them. When you need records of what was said and when, Slack's export options range from straightforward to frustratingly limited, depending on your role and your workspace plan. Here's what's available and how to use it.
Workspace-level exports (admin only)
If you're a workspace admin or owner, Slack provides a built-in export tool under Settings and Administration. This produces a JSON export of public channel messages, organized by channel and date.
On free and Pro plans, the workspace export covers public channels only. Private channels and direct messages are not included. On Business+ and Enterprise Grid plans, admins can export all data including private channels and DMs, but this typically requires approval from Slack and may involve a compliance or legal justification.
The export format is JSON - structured data files organized into folders by channel, with each day's messages in a separate file. The data includes message text, sender ID, timestamp, reactions, thread replies, and edit history. It's thorough but not human-readable without processing. You'll need to convert it to something readable, either with a script, a JSON viewer, or a tool designed for Slack export analysis.
Personal message history
If you're not an admin, your options are more limited. Slack does not offer a per-user "download my data" button comparable to what Facebook or Google provides.
What you can do:
Copy individual messages. Right-click or long-press any message and copy the text. This works for grabbing specific exchanges but doesn't scale.
Search and document. Slack's search is powerful. You can search by channel, person, date range, and keywords. Use search to find the messages that matter, then copy them into a document with timestamps and channel context. Tedious for large volumes, but effective for targeted documentation.
Use the Slack API. If you have some technical comfort, the Slack API lets you pull your own message history programmatically. The conversations.history method retrieves messages from any channel you're a member of. This requires creating a Slack app with appropriate permissions, which your workspace admin may need to approve.
What's included in exports (and what's not)
Slack exports generally include:
- Message text and sender
- Timestamps (Unix format, convertible to readable dates)
- Edits (the current version and a flag indicating the message was edited)
- Thread replies
- Reactions (emoji reactions with who added them)
- File references (links to uploaded files, though the files themselves may or may not be included)
- Channel join/leave events
What's typically not included or limited:
- Deleted messages are not included in standard exports. Once deleted, they're gone from the export. If someone deletes a message before the export runs, it won't appear.
- Huddle transcripts may or may not be captured depending on workspace settings.
- Canvas and clip content may be referenced but not fully embedded.
- DMs on free/Pro plans are excluded from admin exports entirely.
Requesting your data under privacy rights
If you're in the EU, UK, or another jurisdiction with data subject access rights (GDPR, UK GDPR, etc.), you have the right to request a copy of your personal data from Slack. This is separate from the workspace export tool.
To make a request, email privacy@slack.com with your workspace URL and the email address associated with your account. Slack is required to respond within 30 days. The data they provide should include your messages, profile information, and activity data.
This route is slower than a workspace export, but it's available to any user regardless of admin status, and it covers DMs and private channels that workspace exports on lower-tier plans don't include.
In Australia, the Privacy Act provides similar (though not identical) rights. In the US, rights vary by state - California residents have rights under the CCPA. Check what applies to your jurisdiction.
Practical approaches for workplace documentation
If you're documenting workplace conversations for a specific purpose - an HR complaint, a performance dispute, a record of agreements - here's a practical workflow:
Identify the relevant channels and DMs. List every Slack space where relevant conversations occurred. Don't forget threads within channels - important context often lives in thread replies rather than the main channel.
Search with date ranges. Use Slack's before: and after: search operators to narrow results. Combine with from: to filter by person and in: to filter by channel.
Preserve context. When documenting individual messages, include the channel name, the full thread (not just one reply), and surrounding messages that provide context. A single message pulled from a thread can mean something different than it does in context.
Note timestamps in a consistent format. Slack shows relative time ("2 hours ago") by default. Hover over the timestamp to see the exact date and time. Record this in your documentation.
Save files and links separately. If relevant conversations reference shared files, download those files. Slack's free plan deletes file access after a certain storage threshold, and even paid plans may have retention policies set by admins.
Retention and deletion policies
Workspace admins can set message retention policies that automatically delete messages after a specified period. On the free plan, Slack limits searchable history to the most recent 90 days and 10,000 messages (whichever comes first). The messages may still exist in Slack's systems, but they're not accessible to users.
If you're on a free workspace and the conversation you need has scrolled past the 90-day window, a GDPR data request may be your best option for retrieving it.
For ongoing documentation needs, don't rely on Slack's retention. Export or document as conversations happen, especially in workplaces where retention policies are aggressive or where messages are routinely deleted.