Harness the power of IPFS in your browser!
 Firefox | Firefox for Android |
 Chrome |  Brave |  Opera |  Edge |
|---|---|
 |
 |
IPFS Companion harnesses the power of your locally running IPFS node (either through the IPFS Desktop app or the command-line daemon) directly inside your favorite Chromium-based or Firefox browser, enabling support for ipfs:// addresses, redirecting content-addressed websites and file paths to your local Gateway, easy IPFS file import and sharing, and more.
IPFS is a peer-to-peer hypermedia protocol designed to make the web faster, safer, more resilient, and more open. It enables the creation and dissemination of completely distributed sites and applications that don’t rely on centralized hosting and stay true to the original vision of an open, flat web. Visit the IPFS Project website to learn more.
IPFS Companion detects and tests requests for IPFS-like paths ( such as /ipfs/{cid} or /ipns/{peerid_or_host-with-dnslink}) on any website. If a path is a valid IPFS address, it is redirected to load from your local gateway. The gateway at localhost will also automatically switch to a subdomain to provide a unique origin for each website:
https://ipfs.io/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR
→http://localhost:8080/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR→http://bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi.ipfs.localhost:8080
IPFS Companion detects DNSLink info in the DNS records of websites. If a site uses DNSLink (a few examples are https://docs.ipfs.io, https://ipld.io, and http://tr.wikipedia-on-ipfs.org), IPFS Companion redirects the HTTP request to your local gateway:
http://docs.ipfs.io
→http://localhost:8080/ipns/docs.ipfs.io→http://docs.ipfs.io.ipns.localhost:8080/
IPFS Companion also upgrades transport to IPFS if it finds the x-ipfs-path in any HTTP response headers; this also acts as a fallback for cases when an IPFS path is not present in the URL. Learn more.
You can disable and re-enable local gateway redirects by several means:
- Suspend redirects globally in IPFS Companion's preferences
- Suspend redirects per site using the toggle under "Current tab" (illustrated below) or in IPFS Companion's preferences
- Add
x-ipfs-companion-no-redirectto the URL itself as a hash (example) or query parameter (example)
IPFS Companion enables you to quickly and easily access common actions from your browser bar with just a few clicks:
- See how many peers you're connected with a glance at the cube icon in your browser bar
- Check your IPFS API and gateway status by clicking the cube icon to reveal the main menu
- Right-click images and other page assets to easily add them to IPFS (including the option to preserve file names)
- Choose the Import option in the main menu for quick drag-and-drop import from a browser tab
- Pin or unpin IPFS resources (via API) directly from the main menu
- Copy shareable public gateway links, IPFS content paths, or CIDs of IPFS resources directly from the main menu
- Launch the IPFS Web UI dashboard from the main menu with a single click
- Toggle gateway redirects or switch all IPFS Companion features on/off quickly and easily from the main menu (illustrations below)
You can toggle redirects (of any IPFS sub-resources) for an individual website under the Current Tab section of the main menu. If that site uses DNSLink, toggling off will restore the site's original URL, too.
To temporarily suspend all IPFS integrations (redirects, API status content scripts, protocol handlers, etc.), use the on/off button at the top of the IPFS Companion menu.
IPFS Companion ships with a variety of experimental features. Some are disabled by default, so be sure to check out IPFS Companion's Preferences to see them all.
-
Make plaintext IPFS links clickable (demo)
-
Re-route requests made via the following experimental protocols to an HTTP gateway (public or custom):
ipfs://$cidipns://$cid_or_fqdndweb:/ipfs/$ciddweb:/ipns/$cid_or_fqdn
-
Switch between the external HTTP API of your local IPFS node (default setting) and a js-ipfs node embedded in your browser (note that this has some functionality limitations)
| Firefox | Firefox for Android |
Chrome | Brave | Opera | Edge |
|---|---|
|
|
Important! Make sure you have IPFS installed on your computer as well. Because IPFS Companion (in its standard configuration) talks to your computer’s local IPFS node to work its browser magic, you’ll need to have IPFS running on your computer, too.
It's also possible to grab vendor-specific packages for each release,
but these builds are not signed, nor will automatically update. .zip bundles are meant only to be manually loaded via chrome://extensions (Chromium) or about:debugging (Firefox) for smoke-testing.
To work on IPFS Companion's code, you'll need to install it from source. Quick steps are below, but see the full developer notes for more detailed instructions and tips.
- Clone https://github.com/ipfs-shipyard/ipfs-companion.git
- Run this all-in-one dev build to install dependencies, build, and launch in the browser of your choice:
- Chromium
$ npm run dev-build chromium - Firefox
$ npm run dev-build firefox # firefox:nightly works too!
- Chromium
All are welcome to help make IPFS Companion even better!
- Check out the contribution guide for how to get started as a developer
- Open an issue
- Make sure you read and abide by the IPFS Code of Conduct
The best place to ask about IPFS Companion (or IPFS in general!) is in the official IPFS Forums, where you can search past discussions for others who may have had the same questions, too. There's also an active #ipfs community on IRC.
These frequently encountered troubleshooting situations may be helpful:
- Import via right-click does not work in Firefox: See this workaround.
- HTTP-to-HTTPS redirects fail when using Ghostery: Ghostery is known to toy with HTTP-to-HTTPS redirect, which in some setups breaks websites utilizing public gateways (more details). Until this is fixed upstream, a workaround is to whitelist affected sites.
- NoScript breaks IPFS Companion: By default, NoScript breaks IPFS Companion by blocking assets loaded from an IPFS gateway running on localhost. To fix this, extend the SYSTEM ruleset and prepend it with IPFS whitelist (feel free to modify this, but get familiar with ABE rule syntax first):
# Enable IPFS redirect to LOCAL
Site ^http://127.0.0.1:8080/(ipfs|ipns)*
Anonymize
# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Deny
- IPFS Companion Privacy policy
- The IPFS logo belongs to the IPFS Project and is licensed under a CC-BY-SA 3.0 license
- is-ipfs, js-multihash, and other npm dependencies are under MIT license, unless stated otherwise
- IPFS Companion itself is released under CC0; to the extent possible under law, the author has waived all copyright and related or neighboring rights to this work, effectively placing it in the public domain