IPFS Companion is a free, open source browser extension for people who want to open IPFS content in Chromium-based or Firefox browsers on Windows without leaving their everyday browser. It is released under the MIT license, and its code is hosted on GitHub, where the latest version is v3.4.0 and the last code update is dated September 17, 2026.
The extension does not replace an IPFS node. Instead, it connects your browser to a Kubo node already running on your computer, either through the IPFS Desktop app or a command-line daemon. Once connected, ipfs:// addresses and content-addressed websites can be routed to your local gateway, and you can import and share files straight from the browser. It suits developers, researchers and curious users who want a hands-on look at the distributed web.
What Is IPFS Companion Used For?
Most people meet IPFS links on forums, project pages or documentation that point to content by address rather than by server name. Without a helper, a browser does not know what to do with an ipfs:// link. IPFS Companion closes that gap by passing the request to your own node.
A few realistic scenarios show how it fits in:
- A researcher opens a dataset published on IPFS and wants the copy served from their own machine.
- A developer builds a static site, adds the output to a local node, and checks the links in the browser they already use.
- A small team shares design files by importing them through the extension and sending the resulting address in a chat.
In each case the extension is a thin layer. The data moves through your Kubo node, so that node's configuration and free disk space matter as much as the extension itself.
How Content Addressing Changes the Way Links Work
Ordinary web links point to a location: a domain name on a particular server. If the server goes offline or the page changes, the link may break or show something different. IPFS uses content identifiers instead, which are derived from the data itself.
Because the identifier depends on the content, the same file always produces the same address, and any change produces a new one. That makes it easier to confirm that you received exactly the bytes that were published. It also means a file can be retrieved from any node that holds a copy, not only from the original host.
IPFS Companion makes these addresses usable in a normal browser session. It does not change the underlying model, so understanding content identifiers helps you read the links it handles.
Local Node or Public Gateway: Which Should You Use?
A public gateway is convenient. You open a link and the page loads, with nothing to install. The tradeoff is that availability and policies depend on a third party you do not control.
A local node works differently. Your own Kubo instance fetches and serves the content, and it can keep a copy of anything you pin. The cost is that the node must be running, and it uses your bandwidth and disk space. Content you have not pinned may take longer to load if few peers hold it.
IPFS Companion is built around the local option. If you only want to glance at an occasional IPFS link, a public gateway may be enough. If you work with IPFS regularly, a local node gives you more control over what you keep and how it is served.
Key features
ipfs:// address support
Redirects to your local gateway
File import and sharing
Works with IPFS Desktop or the daemon
Supported coins
IPFS Companion is not a wallet and does not handle coins. Its scope is content on the IPFS network: ipfs:// addresses, content-addressed websites and files you import through your node.
How to install Ipfs Companion on Windows
- 1
Set up a local Kubo node
Install IPFS Desktop or run the Kubo command-line daemon on your PC. Start it and confirm it is running before you open the browser, because the extension depends on the node being available.
- 2
Get the extension from the official source
Download only from the official website or the project's GitHub Releases page at github.com/ipfs/ipfs-companion. Avoid copies offered on other sites, even if they look identical.
- 3
Verify the file
Compare the SHA-256 checksum of the downloaded file with the value published alongside the release, or check the signature if one is provided. Do not install a file that does not match.
- 4
Install in your browser
Open the extensions page of your Chromium-based or Firefox browser and add the package. Menus change between browser versions, so follow the prompts your browser shows for installing an extension from a file.
-
Connect to your node
Open the extension settings and confirm that it points to your running node. Then test the connection with a known ipfs:// link.
System requirements
- A Windows PC with a supported Chromium-based or Firefox browser
- A local Kubo node, running through IPFS Desktop or the command-line daemon
- Enough free disk space for the content you choose to store or pin
How to use Ipfs Companion
Once the extension is installed and connected, using it takes only a few minutes. The steps below assume your node is already running.
- Start IPFS Desktop or the Kubo daemon and wait until it reports that it is online.
- Open the IPFS Companion settings and check that the node address matches your local setup.
- Paste an ipfs:// address into the browser's address bar and press Enter.
- Confirm that the page or file loads through your local gateway.
- To share a file, use the import option in the extension, then copy the address it generates.
- Send that address to the person who needs it. They will need their own IPFS node or a gateway to open it.
- Pin the content you want to keep on your machine so it remains available after you close the page.
Pros & cons
- Free and open source under the MIT license
- Routes ipfs:// addresses through your own Kubo node
- Recently updated, with a tagged release at v3.4.0
- Works with either IPFS Desktop or the command-line daemon
- Keeps everyday browsing in the browser you already use
- Requires a local Kubo node to be running before it is useful
- Storage and bandwidth come from your own machine
- File handling is limited to import and sharing, not full file management
- Offers little value for people who only browse regular websites
Is Ipfs Companion safe?
IPFS Companion is open source and maintained, with its last code update dated September 17, 2026, so it is not deprecated. Still, a browser extension can see the pages you visit, so treat installation with care. Download only from the official website or the GitHub Releases page, and compare the SHA-256 checksum or signature before installing. Review the permissions the extension asks for and decline anything that does not match its purpose. Never enter a seed phrase or other private key on a third-party website, whatever the site claims to offer. If you are unsure whether you have the newest build, check the latest version on the official website.
- Official source only. Download from github.com/ipfs/ipfs-companion. 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
IPFS Companion is not a node and not a browser. It sits between your browser and an IPFS node. Kubo is the reference node that stores and serves the data, and IPFS Desktop is a tray app that runs Kubo for you; both are needed before the extension does anything. Agregore takes a different path: it is a minimal browser for the distributed web, so it handles IPFS content itself rather than through an extension. Peergos focuses on end-to-end encrypted peer-to-peer storage and sharing, while Storj is a decentralized cloud storage network aimed at larger storage needs. Pinner CLI suits anyone who prefers pinning from the command line. Choose IPFS Companion if you want ipfs:// links in your current browser.
Specifications
- Price
- Free
- Type
- Open source
- License
- MIT
- Latest version
- v3.4.0
- Last update
- 17 Sept 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/ipfs/ipfs-companion
Frequently asked questions
Yes. IPFS Companion is free and open source under the MIT license, so you can use and inspect its code without paying for the extension. Running a local node uses your own disk space and bandwidth, which are the real costs of the setup.
No. IPFS Desktop is one option for running a local node. The extension can also connect to a Kubo node started with the command-line daemon. In either case, the node must be running on your computer before the extension can route requests to it.
Yes, in the sense that it runs inside a Chromium-based or Firefox browser, and a Kubo node can run on Windows as well. Because the project is distributed through its releases, check the GitHub Releases page for the build that matches your browser.
Once the extension is connected to a running node, paste or click an ipfs:// address in your browser. The extension passes it to your local gateway, and the content loads in the same tab. If nothing loads, confirm that your node is online first.
Kubo is the reference IPFS node that stores, fetches and serves data. IPFS Companion is a browser extension that talks to Kubo. Without a running node, the extension cannot do much, so the two are usually used together.
The project is not deprecated. Its latest version is v3.4.0, and the code was last updated on September 17, 2026. Recent activity like this is a good sign for a small open source tool, though you should still review changes before relying on it for important work.
Verdict
IPFS Companion suits people who already run, or plan to run, a local IPFS node and want ipfs:// links to work in their everyday browser. It is free, open source and recently updated, which matters for a niche tool. It is less useful for casual browsing or for anyone who does not want to keep a node running. If you are new to IPFS, start by setting up Kubo or IPFS Desktop, confirm it works, and then add this extension.