Slack export to PDF
A Slack workspace export is a .zip of JSON files: one folder per channel, one file per day, people as user IDs and links in Slack's own code. Court Copy reads the .zip in your browser and prints one channel or DM as a page-numbered PDF with a cover sheet, the SHA-256 of each file it used, names in place of IDs, threads under the message that started them, optional page stamps and real redaction. Nothing is uploaded.
1. Get the export
Only a workspace owner or admin can export. If that is not you (in most workplace disputes it is not), ask them, or ask your lawyer to request it.
- In Slack, click the workspace name at the top left, then Tools & settings → Workspace settings.
- Click Import/Export Data at the top right, then the Export tab.
- Pick the date range and click Start Export. Slack emails a link when the .zip is ready; download it from that link while signed in.
- What it holds depends on the plan. On Free and Pro plans a standard export has public channels only. Private channels and direct messages need an owner on Business+ or Enterprise Grid with the “export all” option Slack enables on request (Pro owners can ask for it in limited cases, such as a legal requirement). A PDF can only show what the export contains, and the cover says so.
- On the Free plan, messages older than the plan's history limit are hidden and are not in an export either.
- Keep the .zip exactly as downloaded. Court Copy prints its SHA-256 on the cover, and the SHA-256 of every day file it read.
2. Make the PDF
Open Court Copy, choose LINE, KakaoTalk, Slack, Snapchat or TikTok → Choose .txt, .csv or .zip and pick the export .zip (or drop it, or choose the unzipped folder). Every channel and DM in it is listed with its message count and dates; pick one, set the dates, time zone, page stamps and redactions, then press Make PDF.
- Times are exact: Slack stores each message's time as UTC seconds. Choose the zone to show them in; the cover says which one was used.
- Names. User IDs (
U01ABC…) are replaced by the display name, or the full name, fromusers.json; the cover lists each person with their Slack handle and user ID. - Slack's codes are written out:
<@U01ABC>becomes “@Ana Gómez”,<#C01|general>becomes “#general”,<https://…|the handbook>becomes “the handbook (https://…)”, and&becomes “&”. Emphasis marks (*bold*) and emoji codes (:thumbsup:) are kept as written. - Threads are printed under the message that started them, each reply marked “Reply in thread” and quoting its parent. A reply can therefore be later than the message printed after it; the cover says so.
3. What the PDF contains, and what it cannot
- A cover sheet: the .zip and each day file by path with its SHA-256, the channel type and ID, its topic and purpose, creator and members from the channel list, the participants, dates, counts and how the PDF was made.
- One numbered entry per message: sender, time, text, edited marks with the edit time, reactions with who reacted, joins and leaves, topic changes, link previews and shared messages.
- Files are listed by name, type and size. A standard export links to files on Slack's servers instead of including them;
Court Copy never fetches those links. If your export tool saved the files in the .zip (for example under
__uploads/), they are matched by file ID, pictures are printed and every file gets its own SHA-256.
An export does not hold messages deleted before it was made or the earlier text of edited messages, so the PDF cannot show them. A deleted message that had replies shows as “This message was deleted.”, as Slack wrote it.
Under Redact you can hide a person's name and IDs (on their messages, in reactions and in join lines) and black out single messages; redacted text is left out of the PDF file entirely.
Not affiliated with Slack or Salesforce. Whether a printout is accepted, and in what form, is for the court, the tribunal, the lawyers and the other side to say.
Open Court Copy Full exports free right now, nothing uploaded.