Wayback is a free, open-source web archiving tool for developers, researchers and community moderators who want to capture pages before they disappear. You give it a link, and it saves a copy of the web content to one or more archive services, so the page can still be read later even if the original is changed or removed. The project is written in Go and combines a command-line interface with a long-running daemon that can listen to chat platforms.
The official documented platforms are Linux and Docker, while the project also publishes builds for Windows. Windows users should check the GitHub Releases page for a current build before installing. The latest release is v0.21.1, and the code was last updated in July 2026, so the project is active. The sections below cover what Wayback does, what it needs, how to install it safely, and how it compares with similar developer tools.
What Link Rot Means for Web Research
Link rot is the gradual disappearance of web pages. A site is redesigned, a news article is removed, or a company shuts down, and the links that pointed to that content start returning errors. For researchers, journalists and documentation writers, this is a real risk, because a citation that worked last year may now lead nowhere.
Web archiving tools address this problem by saving a snapshot of a page at the moment it matters. A snapshot records the content as it appeared, so the citation stays verifiable even after the source changes. Wayback focuses on that capture step and on sending the result to services where it can be found later.
The value of a snapshot depends on timing. Capturing a page right after you cite it is far more useful than trying to recover it months later, which is why automation and batch tools matter for busy workflows.
Who Benefits Most from Automated Archiving
Wayback fits best with people who already work with links at volume. Open-source maintainers who reference external documentation, developers tracking changes in APIs, and community moderators who collect shared sources all face the same challenge: the more links they handle, the harder it is to save them manually.
Technical users are the main audience. Because Wayback is driven by a command-line interface and a daemon mode, it suits people comfortable with terminals, configuration files and chat bot setup. A non-technical user would likely find the initial configuration more demanding than a browser extension or a hosted archiving service.
For teams, the bot integrations offer a shared workflow. A group chat can become an intake point for sources, with each link archived automatically and returned to the thread. This reduces duplicated effort and gives the group a common record of what was referenced.
How a Capture Moves Through the System
In practical terms, a capture starts with a URL. Wayback takes that address, fetches the content, and sends the result to the destinations you have configured. The same request can produce several copies, one for each target, which makes the archive more resilient.
The project also describes a search and playback service for retrieving archived pages that were saved earlier. This means the tool is not only about writing records but also about finding and viewing them later, which is important when a team needs to revisit a source months after it was first captured.
When Wayback runs as a daemon, the flow becomes continuous. Incoming messages from chat platforms trigger captures, and results can be published back to channels. Understanding this pipeline helps you decide which destinations to enable and where to store copies, because each choice affects how easily others can access the material.
Key features
Free and open source
Batch archiving
Built-in command-line interface
Multiple archive destinations
Chat and bot daemon mode
Publishing results to channels
Local storage for offline use
Streaming media download and privacy options
Supported coins
Wayback does not work with coins, tokens or blockchain networks. Its destinations are web archive and publishing services. Captures can be sent to Internet Archive, archive.today, IPFS and Telegraph, and results can be shared on Telegram channels, Mastodon and GitHub Issues. IPFS needs a reachable daemon host, which defaults to 127.0.0.1 and matters only when IPFS is enabled.
How to install Wayback on Windows
- 1
Get the program from an official source
Download only from the official website or the project's GitHub Releases page at github.com/wabarc/wayback. Documentation is available at docs.wabarc.eu.org. Pick the latest release, which is v0.21.1 at the time of writing, and choose a Windows build if the release lists one for your system.
- 2
Verify the file before running it
Compare the SHA-256 checksum published with the release against your downloaded file. On Windows, you can calculate it in PowerShell with Get-FileHash, or with the certutil command. If the release includes a signature, verify it as well. Do not run the file if the checksum does not match.
- 3
Place the executable in a folder
Extract the archive if needed and move the wayback executable to a folder you control, such as a tools directory. Adding that folder to your PATH lets you run wayback from any terminal. Keep the configuration files in a separate location so updates do not overwrite your settings.
- 4
Confirm the command runs
Open a terminal, run wayback with its help option, and confirm that the command prints usage information. If it does not start, check the release notes for your platform, since the documented platforms are Linux and Docker.
-
Add optional components
Install FFmpeg only if you plan to archive streaming media. Configure the IPFS daemon host only if you enable IPFS as a destination. You can skip both steps if you only need to archive regular web pages.
System requirements
- Documented platforms are Linux and Docker; Windows builds are listed on the GitHub Releases page
- FFmpeg is required only for downloading streaming media
- An IPFS daemon host is needed only when IPFS is enabled, with a default of 127.0.0.1
- Chat integrations need accounts and tokens for the services you connect
How to use Wayback
Wayback is designed to be run from a terminal, and the workflow is simple once it is installed. Start with a single test page so you can see how the output looks before you archive larger batches.
- Open a terminal in the folder where wayback is installed, or make sure it is on your PATH.
- Run wayback with a single URL that you want to preserve, such as a documentation page you cite often.
- Check the output to confirm the capture completed and note which destination received the copy.
- Add several URLs in one run to test batch archiving on a small set before using it on a long list.
- If you want local copies, enable storage to disk and choose a folder with enough space for the files.
- For media-heavy pages, confirm that FFmpeg is installed and available to the program before starting the download.
- To use Wayback from a chat group, configure the daemon with the platform you need and start it.
- Send a test link through the connected chat, then confirm the archived result appears where you expect.
- Keep a record of the destinations you enabled, so you know where to look when you need a capture later.
Pros & cons
- Free and open source, with the full code available on GitHub
- Batch archiving handles many links in one run
- Built-in command-line interface suits scripts and scheduled tasks
- Multiple archive destinations provide redundancy
- Daemon mode works with several chat platforms
- Stores archived files locally for offline access
- Exposes Prometheus metrics for monitoring
- Documented platforms are Linux and Docker, so Windows users should confirm support on the releases page
- Streaming media archiving requires a separate FFmpeg installation
- Daemon mode means you manage bot tokens and accounts yourself
- Initial configuration takes time, especially for chat integrations
- Aimed at technical users rather than casual browsing
Is Wayback safe?
Wayback does not hold funds or private keys, but it does act on your behalf and may use bot tokens and service accounts. Download only from the official website or the project's GitHub Releases page, and check the SHA-256 checksum or signature before running the file. Store tokens for Telegram, Discord, Mastodon or other services in a private configuration file rather than in shared code or chat messages. Never enter a seed phrase on any website or into any bot, even one that claims to help with Wayback. If your antivirus flags a new executable, verify its checksum first rather than disabling protection. Check the latest version on the official website before you update.
- Official source only. Download from github.com/wabarc/wayback. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Wayback sits apart from most tools in this catalog. Remix Desktop, Visual Studio Code with Solidity extensions, Solidity and Foundry help you write, compile and test smart contracts. Tenderly CLI focuses on debugging and monitoring contracts after deployment. Postman and RPC providers such as Alchemy, Infura and QuickNode are for sending requests to blockchain nodes. Wayback has no role in contract code. Its job is capturing web pages and sending them to archive services or chat channels. A Web3 team might use Foundry for development and Wayback only to preserve documentation, audit reports or discussions that support a project.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v0.21.1
- Last update
- 5 Jul 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/wabarc/wayback
Frequently asked questions
Yes. Wayback is free and open source, and its source code is published on GitHub. You can download the program, read the code and use it without paying a license fee. Costs may come from hosting a daemon or from services you connect, such as bot accounts or storage, but the program itself has no price.
Windows support is likely but should be confirmed for your version. The project lists Linux and Docker as its documented platforms and states that Windows builds exist. Check the GitHub Releases page for a Windows build of the latest version before installing, and read the release notes for any platform limitations.
Wayback is safe when you get it from the official source and verify the file. Download it from the project's website or GitHub Releases, compare the SHA-256 checksum, and keep your bot tokens private. The safety section explains the steps in more detail, including what to avoid when connecting chat accounts.
Open a terminal and run the wayback command followed by the URL you want to preserve. The program fetches the page and sends a copy to the destinations you have configured. Start with one test link so you can confirm the result before archiving longer lists.
No, FFmpeg is needed only for downloading streaming media. Regular web pages can be archived without it. If you plan to preserve video or audio streams, install FFmpeg and make sure the program can find it before you start a media capture.
Wayback can send captures to Internet Archive, archive.today, IPFS and Telegraph. It can also publish results to Telegram channels, Mastodon and GitHub Issues. You choose which destinations to enable in your configuration, so you can keep copies in one place or spread them across several services.
No. The Wayback Machine is a service run by the Internet Archive, while Wayback is a separate client tool. Wayback can send captures to the Internet Archive, but it is not part of that service and does not replace it. Think of Wayback as a tool that works with archives rather than the archive itself.
Verdict
Wayback suits technical users who archive web pages regularly and want the work automated. If you maintain documentation, follow sources for research, or moderate a community that shares many links, its batch mode, command-line interface and chat integrations can save significant time. Its free, open-source model keeps costs low, and local storage gives you control over your copies.
It is less suitable for casual users who want a point-and-click browser experience. Windows users should confirm build availability on the releases page before committing to it.