How to Export Slack DMs Without Admin Access

Most people picture their Slack DMs as something locked in a company vault that only IT can open. They aren't. Every direct message you can scroll to right now, your own account is already reading — and that's the whole trick. You don't need admin rights to export your Slack DMs. You need a tool that saves what you can already see.

The confusion comes from finding the wrong door first. Search "export Slack" and you land on Slack's built-in export, which really is admin-only. So people conclude the whole idea is off-limits to them. But that export was built to hand an entire workspace to a compliance officer. It was never the only way to keep your own conversations, and for one person, it's usually the wrong one.

quick answer

• Slack's official export — owner/admin only. On the free plan it covers public channels only; DMs and private channels come through an admin-run corporate export on paid plans (per Slack's export help docs, as of 2026-08). A regular member can't run it.
• Copy-paste by hand — works for a short DM, no admin needed, but it loses files, threads, and timestamps, and there's no search afterward.
• Slackdump — free, open-source, command-line. Reaches your own DMs and private channels with no admin. You read the result in a separate viewer (github.com/rusq/slackdump).
• Backupery for Slack — a paid Windows desktop app that backs up your accessible Slack data, no admin.
• Empowia for Slack — a Windows 10/11 app that reuses the session you're already signed into and saves your DMs and private channels locally, with search and cited AI. No admin, no tokens. Windows-only for now, and it can't recover already-deleted messages.

what the official export actually gives you

The actual shape of Slack's own export is worth spelling out, because half the frustration comes from not knowing it. It's a workspace-level tool, so Slack gates it behind an owner or admin. On a free plan, an admin running it gets public channels as raw JSON — no DMs, no private channels. On paid plans, an admin can request a corporate export that does include DMs and private channels, but that's still an admin action, often behind an approval step, and it dumps the whole organization rather than your one conversation.

Notice what's missing from that list. There's no button, anywhere, that lets a normal member export their own DMs through Slack. That gap is exactly why people assume it can't be done at all.

why your own DMs sit behind an admin wall

Think about what Slack is protecting. If any employee could ask Slack to spit out messages, the company's whole private history would leak one download at a time. So Slack draws a hard line — exporting the workspace is an administrative act, and it belongs to whoever runs the workspace.

But reading a conversation and exporting the workspace are two different things. Your account can open your DMs because they're yours. A local archiver leans on that fact and nothing more. It doesn't ask Slack for a special export or a broader permission. It just walks the same conversations your app already shows you and writes them to disk. No wall gets climbed, because the archive never reaches past what you can already see.

the ways that don't need admin

So what actually works when you're not an admin? A few things, and they're not equal.

Copying messages by hand is the zero-tool option. Fine for pulling one important exchange out of a DM. Useless for a year of history — you lose threading, files turn into dead links, and you can't search what you saved. I've done it in a pinch and regretted it every time.

Opening Slack in a browser and poking at DevTools doesn't count, by the way. It shows you the page's guts, but it saves nothing you can keep. Refresh and it's gone.

The real answers are tools that read your signed-in session and write a proper local copy. Here's how the ones that do that compare.

the no-admin methods, side by side

Facts as of 2026-08. Every row says where it stops, not just where it wins.

Method	No admin?	Your DMs & private channels?	Local copy?	Searchable later?	Cost
Copy-paste by hand	Yes	Only what you scroll	Wherever you paste	No	Free
Slack official export	No — owner/admin only	Free plan: no. Paid: admin-run corporate export	Download	No	Free / paid plan
Slackdump	Yes	Yes — your own access	Yes	In a separate viewer	Free, open-source
Backupery for Slack	Yes	Yes — your own access	Yes	Basic, no AI	Paid Windows app
Empowia for Slack	Yes	Yes — your own access	Yes	Yes — local search + cited AI	Free to 20, one-time ~€19.90

There's no all-green row, and I'm not going to pretend there is. Slackdump is free and reaches everything you can see, but you're in a terminal and then a separate viewer. Empowia gives you search and cited answers on top, but it's a paid app past twenty conversations and Windows-only right now. Pick the row that's green in the columns you actually care about.

how the desktop-session route works

Since Empowia for Slack is the one I make, let me be plain about how it does this so you can judge it. It reuses the Slack session already signed in on your computer — the same login the desktop app uses. From there it copies the DMs, group DMs, private channels, and files your account can open, straight to your own machine. No admin approval, no app registration, no pasting API tokens.

On top of the archive you get instant local search, and AI answers that cite the exact source message, using your own API key. It's free for the first twenty conversations, then a one-time purchase (around €19.90) lifts the cap — no subscription.

And the limits, because you should hear them before you download. It's Windows 10 and 11 only at the moment (a Mac version is coming). It makes a copy you keep and read outside Slack — it can't push messages back into Slack. It's a personal archive, too, not legal hold or disaster recovery — that's an admin-run enterprise job, a different product for a different buyer. And like every tool on this page, it can't recover a message Slack has already permanently deleted. It reads your live history the way the app does. If it's gone from Slack, there's nothing left to save.

what you can reach, and what stays off-limits

This is the line that matters, so I'll say it flatly. You can archive what your own account can already open. Your DMs. Your group DMs. Private channels you're a member of. The files in them. That's a lot, and for most people it's everything they were worried about losing.

What you cannot do is reach past your own access. You can't export a DM between two colleagues. You can't pull a private channel you were never added to. No personal tool hands you that, and wanting it would mean stepping around Slack's access controls, which is a different thing entirely — and one you shouldn't do. If a message is genuinely across other people's accounts, that's an admin's corporate export, under company rules, not a job for a personal archiver.

And you can't turn back the clock. On the free plan especially, old history gets hidden and then aged out for good — the Slack free plan limits piece walks through exactly when. Once Slack has deleted it, no archiver invents it back.

before you archive a work Slack

Quick but important, because technical access and permission aren't the same thing. Your account can see the conversations, sure. That doesn't automatically mean you're allowed to keep a copy.

Work Slack and everything in it usually belongs to the company, not to you. Plenty of employers have policies about exporting or retaining messages, especially when clients, contracts, or personal data are in the thread. So before you archive anything from a workplace workspace, check your employee agreement or just ask IT. It's a two-minute question that saves a much worse conversation later. Archiving your own personal or community Slack is a far simpler case — but even then, only ever save what's actually yours to save.

a few things people get wrong

The mistakes I see most aren't technical. They're timing and scope.

Waiting is the big one. People plan to back up "before I leave" and then leave on a Friday with the account already switched off. Once you're deactivated, the conversations go with the access — do it while you can still open them, not on the way out.

Over-reaching is the other. Someone decides that because they can technically grab something, they should. Keep it to your own DMs and channels, and keep it to what you're cleared to keep. A clean, allowed archive beats a complete one that gets you in trouble.

And skipping the files. Messages without their attachments are half a record — the PDF someone dropped, the screenshot that settled an argument. A good archive pulls the files down too, not just links that expire.

your two-minute exit checklist

Three steps and you're done.

• Pick the conversations that would actually sting to lose — the DMs, the one or two private channels, the files inside them.
• Confirm you're allowed to keep them.
• Save them while your account can still open them.

Empowia for Slack handles that last step on Windows — no admin, no API tokens, free for your first twenty conversations. Use whatever tool you like. Just remember which part has a deadline. It's not the software. It's your access, and access is the thing with an expiry date.