Upgrade your browser with IPFS super powers
 Firefox / Firefox for Android |
 Chrome /  Brave /  Opera /  Edge |
|---|---|
 |
 |
This add-on enables everyone to access IPFS resources the way they were meant: from locally running IPFS node :-)
IPFS is a new hypermedia distribution protocol, addressed by content and identities. IPFS enables the creation of completely distributed applications. It aims to make the web faster, safer, and more open.
Learn more at ipfs.io (it is really cool, we promise!)
Requests for IPFS-like paths (/ipfs/{cid} or /ipns/{peerid_or_host-with-dnslink}) are detected on any website.
If tested path is a valid IPFS address it gets redirected and loaded from a local gateway, e.g:
https://ipfs.io/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR
→http://127.0.0.1:8080/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR
Companion will detect presence of DNSLink in DNS records of visited websites and redirect HTTP request to a local gateway.
http://docs.ipfs.io
→http://127.0.0.1:8080/ipns/docs.ipfs.io
This means if you visit websites with a valid DNSLink (eg. https://docs.ipfs.io, https://ipld.io, http://tr.wikipedia-on-ipfs.org) browser will load them from IPFS.
More details: DNSLink Support in IPFS Companion
Companion will upgrade transport to IPFS if the header is found in any HTTP response headers. This is a fallback for edge cases when IPFS path is not present in URL.
More details: x-ipfs-path Header Support in IPFS Companion
It is possible to opt-out from Gateway redirect by:
- a) suspending redirect via global toggle (see Disable All Redirects below)
- b) suspending redirect for via per website opt-out (in Active Tab section of Browser Action or Preferences)
- c) including
x-ipfs-companion-no-redirectin the URL (as a hash or query parameter).
Your IPFS node is exposed as window.ipfs on every webpage.
Websites can detect if window.ipfs exists and opt-in to use it instead of creating their own js-ipfs node.
It saves system resources and battery (on mobile), avoids the overhead of peer discovery/connection, enables shared repository access and more!
Make sure to read our notes on window.ipfs, where we explain it in-depth and provide examples on how to use it your own dapp.
The Browser Action pop-up provides handy toggles for often used operations.
Active Tab actions include option to opt-out current website from Gateway redirect of any IPFS subresources.
Disabling redirect for DNSLink website will restore original URL as well:
A handy toggle to disable all gateway redirects while keeping all other features enabled:
The "power" icon can be used to temporarily suspend all IPFS integrations (redirects, API status, content scripts, protocol handlers etc). Useful during testing. Extension can be re-enabled with a single click:
- IPFS API and Gateway status
- Add local (quick import) or remote files (context menu) to IPFS with option to preserve filename
- Easy access to WebUI and add-on Preferences
- Toggle redirection to local gateway (automatic by default, manual mode can be enabled in Preferences)
- Additional actions for pages loaded from IPFS
- Pin/Unpin of IPFS resources (via API)
- Copy canonical IPFS address
- Copy shareable URL to resource at preferred public gateway
(some are disabled by default, use Preferences screen to enable)
- Requests made via experimental protocols are re-routed to HTTP gateway (public or custom):
ipfs://$cidipns://$cid_or_fqdndweb:/ipfs/$ciddweb:/ipns/$cid_or_fqdn
- Make plaintext IPFS links clickable (demo)
- Switch between External HTTP API and Embedded js-ipfs node. Read about differences at docs/node-types.
We recommend installing the stable release via your browser's add-on store.
| Firefox / Firefox for Android |
Chrome / Brave / Opera / Edge |
|---|---|
|
|
Note: ipfs-companion is designed to retrieve content from a locally running IPFS daemon.
Make sure IPFS is installed on your computer.
Developers and enthusiasts can opt-in for Beta-quality channel with hand-picked Dev Builds:
- Beta for Firefox: Self-hosted Signed Dev Build
- Beta for Chromium-based browsers: Dev Build at Chrome Web Store
It is also possible to grab the last successful build from master,
but these builds are not signed nor will automatically update:
.zip bundles are meant only to be manually loaded via chrome://extensions (Chromium-based) or about:debugging (Firefox) for the purpose of quick smoke-testing.
To work on the extension you need to install it from source rather than from the add on store.
- Clone https://github.com/ipfs-shipyard/ipfs-companion.git
- Run all-in-one dev build:
$ npm run dev-build - Switch
add-on/manifest.jsonto the browser of your choice:$ npm run bundle:firefox # for Firefox (build default) OR $ npm run bundle:chromium # for Chromium-based browsers
- Load it into browser:
-
Chromium-based
- Enter
chrome://extensionsin the URL bar - Enable "Developer mode"
- Click "Load unpacked extension..."
- Pick the directory
add-on
- Enter
-
Firefox
- Enter
about:debuggingin the URL bar - Check "Enable add-on debugging"
- Click "Load Temporary Add-on"
- Pick the file
add-on/manifest.json
- Enter
-
See docs/developer-notes.md for more detailed instructions
Want to ensure prebuilt bundle does not include any additional code?
Don't want to install JS dependencies such as NodeJS and yarn?
Do an isolated build inside of Docker!
Run the following command for ending up
with a built extension inside the build/ directory:
npm run release-buildIt is an alias for running ci:build script inside of immutable Docker image, which guarantees the same output on all platforms.
Legacy versions 1.x.x were based on currently deprecated Add-On SDK (Firefox-only).
While it is not maintained anymore, one can inspect, build and install it using codebase from legacy-sdk branch.
For historical background on the rewrite see Issue #20: Move to WebExtensions.
Feel free to join in. All welcome. Open an issue!
If you want to help in developing this extension, please see CONTRIBUTING page ✨
The browser extension team hangs out at the #ipfs-in-web-browsers channel on Freenode.
This repository falls under the IPFS Code of Conduct.
The best place to ask your questions about IPFS in general, how it works and what you can do with it is at discuss.ipfs.io.
We are also available at the #ipfs channel, where most of IPFS community hangs out.
Questions specific to this browser companion can be asked directly at #ipfs-in-web-browsers
See this workaround.
Ghostery is known to toy with HTTP-to-HTTPS redirect, which in some setups breaks websites utilizing public gateways. More details in #466. Until it is fixed upstream, a workaround is to whitelist affected site.
By default NoScript breaks this addon by blocking assets loaded from IPFS Gateway running on localhost.
To make it work, one needs to extend the SYSTEM Rulset and prepend it with IPFS whitelist:
# 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
Feel free to modify it, but get familiar with ABE rule syntax first.
IPFS logo belongs to The IPFS Project and is licensed under a CC-BY-SA 3.0.
is-ipfs, js-multihash and other NPM dependencies are under MIT license, unless stated otherwise.
The add-on 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.