Step by step guide to exporting conversations from Slack, across different types of messages and channels and between Slack's various plans (Free, Pro, Business+, Enterprise+).
slack.com/services/exportNon-admins: See alternative methods below.
Whether you need to export Slack conversations for compliance, legal holds, moving to another platform, or just want a permanent record, this guide explains how to export Slack data across all plans—Free, Pro, Business+, and Enterprise Grid.
We'll also cover the limitations of each Slack plan, non-admin workarounds, and how to actually read the exported data (spoiler: Slack exports in JSON, which isn't human-readable without tools).
What you can export depends on your Slack plan:
| Plan | Public Channels | Private Channels | Direct Messages (DMs) | Requires |
|---|---|---|---|---|
| Free | ✅ Yes | ❌ No | ❌ No | Workspace Owner/Admin |
| Pro | ✅ Yes | ❌ No | ❌ No | Workspace Owner/Admin |
| Business+ | ✅ Yes | ✅ Yes* | ❌ No | Workspace Owner/Admin + Member consent |
| Enterprise Grid | ✅ Yes | ✅ Yes* | ✅ Yes* | Org Owner + Discovery API approval |
*Requires explicit approval or legal justification in most regions due to privacy laws.
These plans use Slack's Standard Export:
slack.com/services/export (must be signed in as Owner/Admin)
Limitations:
Enterprise Grid has two export options:
Use slack.com/services/export to export public channels.
For private channels and DMs, use the Discovery API:
When to use:
Note: Discovery API access is not automatic. Slack reviews requests and may deny access without proper justification.
If you receive a subpoena or court order demanding Slack data, proper export and preservation is critical. You'll need to export private channels, DMs, and metadata that may not be included in standard exports - and you must do it immediately to avoid spoliation sanctions. Our Slack subpoena response guide covers the complete legal process, including objections, review workflows, and production formats that courts will accept.
If you're not an admin, your options are limited but not zero:
Slack exports in JSON (JavaScript Object Notation):
Example JSON snippet:
{
"type": "message",
"user": "U1234ABCD",
"text": "Hey team, the Q4 report is ready.",
"ts": "1672531200.000000"
}
When to use JSON:
Some third-party tools (like ViewExport) convert JSON to plain text or HTML:
When to use TXT/HTML:
Raw Slack exports are not human-readable. Here's how to view them:
.zip fileWhy ViewExport:
Limitations:
Solution: Ask your Workspace Owner/Admin to grant you export permissions or request the export on your behalf.
Solution: JSON files aren't meant to be "opened" like documents. Use ViewExport or a JSON viewer.
Possible causes:
Solution: Slack exports contain links to files, not the files themselves. Download files separately before they're deleted.
Why: Large workspaces with years of data can take hours.
Solution: Break exports into smaller date ranges.
Solution: Check your email spam folder. The link expires after 7 days, so download promptly.
| Method | Who Can Use | What's Exported | Format | Best For |
|---|---|---|---|---|
| Slack Standard Export | Workspace Admin | Public channels only | JSON | Compliance, audits, backups |
| ViewExport | Anyone with export file | Whatever's in the export | JSON → PDF/HTML/CSV | Reading, searching, eDiscovery |
| Discovery API | Enterprise Grid Org Owner | Public, private, DMs | JSON | Legal holds, investigations |
| Slackdump | Any user (tech-savvy) | Channels you're in | JSON | Personal backups |
| Backupery | Any user (paid) | Channels you're in | Multiple formats | Automated backups |
| Copy-Paste | Anyone | Visible messages only | Text | Small, one-off exports |
For official exports: Yes, you need to be a Workspace Owner or Admin.
No. Only Business+ and Enterprise Grid support private channel exports (with restrictions).
Usually yes, if the export was created after the message was posted. But if a message was deleted before the export, it won't be included.
Use ViewExport, a free JSON viewer, or a text editor. JSON isn't human-readable on its own.
No (not via Standard Export). Slack exports the entire workspace. Use the Discovery API (Enterprise Grid) for granular control.
Not natively. Use third-party tools like ViewExport or build a custom solution with the Slack API.
Yes, if you use the Discovery API (Enterprise Grid). Standard exports show only the latest version of edited messages.
Yes, Slack's native export is free. Third-party tools may charge.
None (functionally). The names differ by region for regulatory reasons.
Don't wait until you need the data. Export quarterly or before major events (layoffs, audits, litigation).
Slack exports contain sensitive data. Encrypt and store them in secure locations (encrypted drives, secure cloud storage).
If exporting for legal reasons, document:
Run a test export to ensure you understand the process and can access the data when needed.
If subject to regulations (GDPR, HIPAA, etc.), understand your data retention and export requirements. Work with legal counsel.
You should consider ViewExport if:
ViewExport vs. Slack's native export:
Exporting Slack conversations is straightforward if you're an admin on Free/Pro/Business+ (public channels only) or Enterprise Grid (full access with Discovery API).
Key takeaways:
slack.com/services/exportNeed help managing Slack exports? Contact us or start a free trial of ViewExport.
