Wbipfs is a free, open-source command-line tool for saving a copy of a webpage to IPFS, the peer-to-peer content network. It also works as a Go package, so developers can call its saving functions from their own programs. It suits archivists, researchers and developers who are comfortable working in a terminal.
Before you start, note that the last code update dates to January 2022, more than four years ago. The latest listed version is v0.2.0, and no later code changes are recorded. The tool may still handle basic jobs, but expect few or no recent fixes, and check the GitHub repository before relying on Wbipfs for Windows for important work.
What Is IPFS and Why Save Webpages to It?
IPFS, short for InterPlanetary File System, is a peer-to-peer network for storing and sharing files. Instead of asking one server for a page at a web address, a client asks the network for content identified by a cryptographic fingerprint of that content. If the content is identical, the identifier is identical, no matter which node serves it.
That design suits archiving. A saved page keeps its identifier as long as its contents do not change, so a link to the snapshot points to exactly what was saved. Original websites can be edited, moved or removed, but a copy held on IPFS stays addressable while some node keeps holding it.
Who Wbipfs Is For
Wbipfs fits people who already work in a terminal and want to automate a repeatable task. A researcher collecting sources for a report might run it against a list of URLs and keep permanent copies to cite later. A journalist preserving a page before it is edited could use it the same way, though anyone relying on a record for legal purposes should also note when and how each copy was made.
Developers are a second audience. Because the project exposes a Go package, a team can build saving into an internal tool or a larger archiving pipeline. Readers who only want to browse IPFS content, rather than save it, will be better served by a node application or a desktop client.
Practical Scenarios for Archiving Pages on IPFS
Archiving is most useful when a page is likely to change or disappear. Examples include saving a policy document before a revision, preserving a project's documentation at a particular release, or keeping a copy of a public statement that might be quietly edited later.
A snapshot shows what a page looked like when you saved it. It does not confirm that the content was accurate or that the author meant it. Record the source URL, the date and the reason for saving next to each identifier, so the archive stays useful to someone who was not involved in making it.
Pinning, the default mode in Wbipfs, is what keeps a copy available on the network. Without pinning or another node holding the content, a saved snapshot can become hard to retrieve.
Key features
Webpage to IPFS saving
Command-line interface
Go package for programmatic use
Pinner and daemon modes
Tor proxy option for Wayback saving
How to install Wbipfs on Windows
- 1
Get the file from the official source
Open the project's GitHub Releases page at github.com/wabarc/wbipfs and find the latest release, currently v0.2.0. The project builds for Windows, so look for a Windows file among the release assets. Download only from the official website or GitHub Releases.
- 2
Verify the checksum
Compute the SHA-256 hash of the downloaded file using a tool such as PowerShell's Get-FileHash command. Compare it with the value published on the release page. If the hashes do not match, delete the file and do not run it. If a signature is published, check that too.
- 3
Place the executable
Extract the archive if needed and move the wbipfs executable into a folder of your choice, such as a tools folder in your user directory. Add that folder to your PATH environment variable if you want to run the program from any terminal window.
-
Prepare optional dependencies
If you plan to use the Tor proxy option, install a Tor executable and confirm it is reachable from your PATH. If you want daemon mode, start a standalone IPFS daemon before running Wbipfs. Pinner mode, the default, does not need this step.
System requirements
- A Tor executable, only if you use the Tor proxy option for Wayback saving
- A standalone IPFS daemon running on your machine, only if you choose daemon mode instead of the default pinner mode
How to use Wbipfs
Wbipfs runs from a terminal, so open Command Prompt or PowerShell in the folder that holds the program. The steps below describe the general flow. Check the help output of your installed version for exact flags, since options can change between releases.
- Open PowerShell and run the program with its help flag to see which options your version supports.
- Decide between pinner mode, the default, and daemon mode. If you choose daemon mode, start your IPFS daemon first.
- If you want Wayback saving routed through Tor, confirm the Tor executable is available in your PATH.
- Run the tool with the URL you want to save, adding the flags shown in the help output.
- Record the identifier IPFS assigns to the saved content, along with the source URL and the date.
- Test the result by loading the identifier through your local node or a public IPFS gateway to confirm the snapshot is retrievable.
Pros & cons
- Free and open source, with the code publicly available on GitHub
- Simple command-line workflow that suits scripting and repeated jobs
- Can be imported as a Go package inside your own software
- Optional Tor routing for Wayback saving
- The last code update was in January 2022, so recent fixes are unlikely
- Windows is listed as likely rather than guaranteed, so confirm a Windows build exists before installing
- Daemon mode needs a separate IPFS daemon, and Tor routing needs an extra executable
- Command-line only, with no graphical interface for casual users
Is Wbipfs safe?
Wbipfs does not handle wallets, keys or payments, so the main risks are the usual ones for any downloaded executable. Get the program only from the official website or the project's GitHub Releases page at github.com/wabarc/wbipfs. Compare the file's SHA-256 checksum with the value published on the release page, and check a signature if one is available.
Because the last code update was in January 2022, review the source code or the issue tracker before running the tool on sensitive material. Keep your antivirus active while you work with it, and treat any copy of the program from a third-party download site with suspicion. Confirm the latest version on the official release page before installing.
- Official source only. Download from github.com/wabarc/wbipfs. 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
Wbipfs is narrower than most tools in this list. It focuses on saving a single webpage to IPFS from the command line. Kubo is the reference IPFS node, so it is the better choice if you want to run a full node, while Wbipfs does not try to do that. IPFS Desktop places a node in your system tray for people who prefer a graphical interface.
Pinner CLI is closer in spirit, since it is also a command-line tool, but it centers on pinning content you already have rather than capturing a webpage. Peergos and Storj are built for storing and sharing files for personal or team use, so they serve a different purpose from web archiving.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v0.2.0
- Last update
- 16 Jan 2022
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/wabarc/wbipfs
Frequently asked questions
Yes. Wbipfs is free and open source, and its source code is published on GitHub. The optional tools it can use, such as a Tor executable or a standalone IPFS daemon, are separate downloads that you install yourself.
The project builds for Windows, so it can run on Windows, but support is listed as likely rather than guaranteed. Look for a Windows file on the GitHub Releases page before installing. If none is attached, the repository's build instructions are aimed at developers.
Pinner mode is the default and the simpler option. Daemon mode requires a standalone IPFS daemon, which gives you direct control over your node but adds another process to start and maintain. Choose daemon mode if you already run IPFS on your machine.
No. Tor is only needed if you use the Wayback option routed through a Tor proxy. In that case, a Tor executable must be installed and available to the program. You can skip Tor unless your workflow specifically calls for it.
The latest listed version is v0.2.0, and the last code update dates to January 2022. That is more than two years ago, so recent fixes are unlikely. Read the repository's issue list and commit history before depending on it for important work.
Yes. Wbipfs can be imported as a Go package, so your code can call its saving functions directly. You will need a Go toolchain to build your project, and you should review the package's code first, given how long it has been since the last update.
It is reasonably safe if you get it from the official GitHub Releases page and verify the SHA-256 checksum before launching it. Review the code if you handle sensitive material, and keep your antivirus active. The safety section explains these steps in more detail.
Verdict
Wbipfs suits people who are comfortable in a terminal and want a small, scriptable way to save webpages to IPFS. It is a sensible pick for archivists, researchers and developers who might embed it in a Go project. It is less suitable for anyone wanting a polished interface or regular updates, given that the last code change dates to January 2022. Before installing, confirm the current release and that a Windows build is available.