SlackVault and slack-archive: Static HTML or a Firebase Copy

SlackVault and slack-archiveAn open-source Node tool that pulls channels, DMs and files with a user token and writes a static HTML archive plus JSON.Last checked November 7, 2026. Check slack-archive for yourselfSlackVault is not affiliated with or endorsed by Slack.Which one suits youChoose slack-archive if you want one free run that leaves you plain HTML files meant to open decades from now, with incremental re-runs when you choose to do them.Choose SlackVault if you want the copy taken every 15 minutes without a manual run, and the result searchable from a web app rather than a folder of files.What each one costs

SlackVault: Forever Free

Open source

$0 / one time

No cloud, free

Their page

Side by side

Saves public channel messages

Yes

Yes Their page

Saves private channel messages

Yes

Yes Their page

Saves direct messages and group DMs

Yes

Yes: DMs and multi-person DMs Their page

Saves thread replies

Yes: A thread that fails to save is skipped, not retried

Not stated on the pages we checked

Saves shared files

Yes: File details always; copies only at a public link on our storage, when switched on

Yes Their page

Runs on its own on a schedule

Yes: Every 15 minutes, while the browser runs

Not stated on the pages we checked

Copy lives in storage you control

Partly: Messages in your Firebase project; file copies are not in your storage

Yes Their page

Search across the saved history

Yes: The most recent page of messages, up to 50 per query

Yes: basic search Their page

Export to open file formats

Yes: JSON, CSV, HTML and Markdown

Yes: static HTML and JSON Their page

Works without workspace admin rights

Partly: No admin scopes, though a workspace can require approval for new apps

Not stated on the pages we checked

Puts records back into Slack

No: No way yet to send records back into Slack

Not stated on the pages we checked

Free plan with no time limit

Yes

Yes Their page

What SlackVault does today, and what it does not

Messages, channels, members and file records go to your own Firebase project. Supabase is not supported yet.

Files do not go to your Google Drive or your Firebase project. When file copying is switched on in our extension build, each file uploads to our file storage with its visibility set to public: the link is hard to guess, but anyone holding it can open the file without signing in. Where no storage key is set in the build, no copy is made, and your archive keeps the file’s details and Slack’s link, which works only while Slack serves that file.

There is no way yet to send records back into Slack.

The sync runs in a browser extension, every 15 minutes, only while that browser is running.

SlackVault can copy only what Slack’s API still returns, so anything older than your plan’s window is out of reach unless an earlier sync already saved it.

If saving one thread fails, the sync logs it and moves on without retrying those replies.

Search checks the most recent page of messages, up to 50 per query, not the whole archive.

The extension and the Android app have no store listing yet, and the source code is in a private repository.

Moving acrossRead the guideAll comparisons