Empowia
← All posts
slackAugust 23, 2026·Updated October 25, 2026·8 min read

How to Back Up Slack Files, Not Just Their Links

Slack's official export gives you file links, not the files themselves. Here's how to save accessible attachments locally and check that the copies open.

The maker behind Empowia

Read in:Deutsch日本語中文Français

How to Back Up Slack Files, Not Just Their Links

Quick answer

To back up Slack attachments, save the actual files from conversations you can still access, not just links in an export. Slack's official export contains file links rather than the file bytes; on the Free plan, it exports links to files from only the last 90 days. Empowia for Slack can save accessible messages and files to your computer and offers a files gallery. Afterward, open a saved PDF or image from your disk to verify it really downloaded. Already hidden Slack Free files cannot be recovered with Empowia.

Key takeaways

  • A Slack export ZIP is not a backup of the attachment bytes; it contains links to files.
  • Distinguish a file uploaded to Slack from a Google Drive, Dropbox or other external URL pasted into a message.
  • Save Slack-hosted files while your account can still access them and verify that the saved copies actually open from your computer.
  • Empowia backs up accessible Slack files locally and provides a files gallery; its free version covers up to 20 conversations.
  • Slack Free hides older files after 90 days, and Empowia cannot later back up files it can no longer access.

I once went looking for a signed contract someone had shared in Slack. I remembered the thread, the PDF and the relief of getting the paperwork done. What I hadn't checked was whether a copy of that PDF existed anywhere outside Slack. When the link stopped helping, that distinction was suddenly the whole story.

That's why I separate a link to a file from the file itself. If I want to back up Slack attachments, I want to finish with a PDF, image or spreadsheet I can open from my computer. Not a JSON record with a promising filename. Not a link that may stop working when I need it.

the Slack file that looks saved but isn't

A file card in a conversation feels solid. You can see the name, sometimes a preview and the message that introduced it. It's tempting to think that if you save the message, you've saved the attachment too.

But imagine you're reviewing an archive six months later. You find the exact thread. There it is: signed-agreement.pdf, shared by the right person on the right date. You click the URL and it fails. You've preserved a record that the file existed, not the file you needed.

That isn't a problem with JSON itself. JSON is doing its job as structured data. The mistake is asking it to be a downloadable copy of a separate object.

So my definition of success is intentionally unglamorous: I can disconnect from that Slack conversation, open the downloaded file from my disk and read the contents. If I can't, the attachment backup isn't complete.

why Slack's export gives you file links, not files

Slack's official export documentation is explicit: the export contains file links, not the files themselves. The JSON can help identify which files were shared, but it doesn't package the PDFs, screenshots and spreadsheets into the ZIP for you.

There are two separate restrictions worth understanding. On Slack Free and Pro, the standard public-channel export is for workspace owners and admins. And specifically on Free, that export includes links to files from the last 90 days only. Neither rule guarantees that a linked file is still available when you finally try to fetch it.

I treat the official export as a record and a set of pointers. That's useful for some jobs. It isn't the same as an attachment library saved on my own computer. If you're staring at an exported ZIP, how to read and search its JSON is a different guide. Here I'm concerned with the actual file bytes.

first find out whether it was an upload or a link

There are two things people call “files in Slack,” and I ask which one I have before deciding what to back up.

A Slack upload is the PDF, image or spreadsheet someone attached directly in a conversation. Slack hosts that file. While my account can still access it, I can save the actual attachment to my computer. That is what a Slack file backup is for.

A shared external link is a URL to something hosted elsewhere — a Google Drive document, a Dropbox folder or a Figma page. Slack may preserve the address and the message around it, but it doesn't hold the underlying document just because somebody pasted the URL. If I need an offline copy, I have to get it from the service where it lives, subject to the access I'm given there.

This is a small distinction with big consequences. An archive full of shared URLs can be great for finding resources again. It isn't proof that those external resources were downloaded or will remain available forever.

So I make two groups before I start: actual Slack uploads to preserve as files, and external links to revisit or save separately. I don't count the second group as successfully backed-up attachments.

how I back up Slack attachments I can still open

I start with the conversations most likely to contain important uploads: a project channel, a supplier DM, a thread with a signed document. I don't begin by promising myself I'll archive everything. I start with the file I'd regret losing.

If it's just one attachment, I can open it while I still have Slack access and save a copy to my own computer. I give the saved file a recognizable place and check it immediately. That manual route isn't glamorous, but for a handful of critical documents it's perfectly reasonable.

If I have many conversations and want to keep a searchable local copy, Empowia for Slack uses my signed-in Slack session to back up the messages and files my account can access. It doesn't need a workspace admin role, registered app or API token. The resulting backup and files stay on my computer, and there's a files gallery for working with the saved attachments.

I choose a route based on the size of the job, not on how impressive the tool sounds. A single contract may only need one careful download. A growing collection of project conversations is a better reason to maintain an archive.

Whatever the method, normal workplace rules about which information I may keep still apply. Having access to a file is not an automatic license to take company records elsewhere.

prove the file made it onto your computer

This is the part I'd never skip again. It's also the easiest part of the whole process.

First, open the copy from your disk. If it's a PDF, read a page. If it's an image, make sure the image renders. If it's a spreadsheet, check it isn't an empty shortcut or a broken link. The point is to test the saved file, not click the Slack card again.

Second, check the right version. A document named “final” may have a later revision. I compare what I saved with the message around the original attachment: who shared it, when and why. If I need the last approved version, I don't assume the most recent filename tells the whole story.

Third, look at a few different file types. A PDF, an image and a spreadsheet make a quick sanity check for a larger backup. I don't need a complex audit to catch the basic mistake of having links instead of files.

Only after that would I count a file as protected from losing access to that particular Slack copy. This check doesn't promise a perfect backup of every conversation; it proves that the few files I actually tested are real local copies.

keep the attachment and its conversation together

A loose folder of PDFs solves only half the problem. I might have the contract and still have no idea whether it was the approved version or an early draft. The surrounding message can be as important as the document.

That's why an archive of messages and files is more useful than a stack of isolated downloads. Empowia offers local full-text search over backed-up Slack history and a files gallery, so I can work from the saved resource or from words I remember in the conversation. I don't need to claim it searches inside every PDF or invent a particular file-organizing layout to make that useful.

If the real problem is “I know somebody shared that file, but where?”, I've written about finding saved Slack files and links in a personal archive. This article stays on the narrower problem: did the file itself get saved?

what old Slack Free files you can't rescue

The time limit matters most when the workspace is on the Free plan. Slack hides messages and files older than 90 days from view, and data older than one year is subject to permanent deletion under Slack's Free-workspace policy.

Here's the practical point for this tutorial: Empowia cannot back up a file that Slack Free has already hidden from your account. Starting a backup today protects what is still accessible today; it does not reconstruct months of older invisible attachments. That's a reason to start early, not a reason to claim a magic recovery capability.

The policy itself deserves more detail than a file tutorial can provide, so the separate guide to Slack Free's 90-day and one-year history limits covers that distinction. I just need to know whether the file still opens before I try to preserve it.

start with one file you would hate to lose

If I had ten minutes today, I wouldn't spend them comparing every Slack backup feature. I'd find one important attachment that's still reachable, save the actual file, open it on my computer and check its version against the message. Then I'd do the next one.

If that grows into a recurring need, Empowia's free version can back up up to 20 conversations, including their accessible files; the product page explains the app and current pricing covers the one-time unlimited option.

The difference between a Slack file link and a saved file is easy to forget while everything still works. It becomes impossible to ignore when a link doesn't. I would rather make that distinction today, with a PDF I can open, than discover it when the document matters most.

FAQ

Does Slack's official export contain attachments?

It contains links to files, not the actual attachment bytes. Slack Free exports file links from only the last 90 days.

How do I know a Slack file really backed up?

Open the downloaded file directly from your computer. A working PDF or image stored locally is different from a filename or a link that still depends on Slack access.

Can I back up files from Slack DMs?

Empowia for Slack can back up files from DMs and group DMs your signed-in account can access, without requiring a Slack admin role. Applicable workplace data-retention rules still matter.

Will backing up a Google Drive link save the document?

No. A URL pasted into Slack is a link to another service, not the file stored by Slack. To keep the document itself, you need to obtain a copy from the service that hosts it.

Can Empowia recover Slack Free attachments older than 90 days?

It cannot retrieve files the Free plan has already hidden. Start backing up while the attachments are still available to your account.

Comments

Loading comments…

Leave a comment

Comments are reviewed before they appear.