Compared honestly
Octopin vs web3.storage / Storacha
The Protocol Labs-backed IPFS host that has closed.
Verdict
Storacha is no longer an option: storacha.network now redirects to fil.one, a separate S3 storage product, and the w3s.link gateway redirects to dweb.link, which stopped serving apps in September 2026. If you had content there, re-pin it somewhere active. Octopin keeps the same CIDs, so nothing on-chain changes.
Side-by-side
| Feature | Octopin | web3.storage / Storacha |
|---|---|---|
| Service status | Active | Closed (site redirects to fil.one) |
| Gateway | gateway.octopin.app, works for apps | w3s.link redirects to dweb.link (browser only since Sept 21, 2026) |
| Free storage | 1 GB | None |
| Bandwidth | Unlimited on paid plans | None |
| Re-pin existing CIDs | Yes (import by CID or CAR, paid plans; re-upload on free) | Not applicable |
| Wallet required | No, Google sign-in | Not applicable |
When to pick web3.storage / Storacha
There is no Storacha service to pick anymore. If you want Filecoin storage deals with on-chain proofs, look at Filecoin Pin. If you want a simple IPFS pinning service with a free tier and no wallet, use Octopin.
- • Was the Protocol Labs / Filecoin ecosystem's own IPFS host, with a generous free tier.
- • Stored data in Filecoin deals, so some content may still be retrievable from Filecoin storage providers.
Where we differ
- • Active service with a gateway that works for apps, not only browsers.
- • No wallet needed: Google sign-in like a normal SaaS.
- • Same CIDs after re-pinning, so contracts and tokenURIs stay as they are.
- • Unlimited bandwidth on every paid plan.
How to switch from web3.storage / Storacha to Octopin
- Create a free Octopin account with Google sign-in. No wallet, no card for the free plan.
- List the CIDs you have pinned on web3.storage / Storacha. If you still have the original files, upload them to Octopin: the same bytes always produce the same CID.
- On a paid plan you can skip the re-upload and import content directly by CID, or upload a CAR export of your data.
- Check a few CIDs on gateway.octopin.app and a public gateway like ipfs.io. If your contract uses
ipfs://URIs, nothing on-chain changes. - Keep the old pins until everything resolves from Octopin, then remove them from web3.storage / Storacha.
Moving a whole collection? Read the IPFS migration playbook and why contracts should use ipfs:// URIs, not gateway URLs.
FAQ
My w3s.link URLs stopped working. What do I do?
w3s.link now redirects to dweb.link, which only serves browsers since September 21, 2026. Pin the content on Octopin (same CIDs) and replace the host with gateway.octopin.app. If your contract stores ipfs:// URIs, it needs no change.
Will my existing CIDs work without changes?
Yes. IPFS CIDs are content addressed. As long as someone keeps the bytes pinned, the CID resolves. Upload the original files to get the same CIDs, or on paid plans import by CID or CAR file.
I no longer have the original files. Can I still recover them?
Maybe. If the content is still on any IPFS node or in a Filecoin deal, importing the CID on Octopin can fetch it from the network. If nobody has a copy anymore, it cannot be recovered, so move content you care about soon.
More IPFS pinning comparisons
Try Octopin for free
1 GB free. Unlimited bandwidth from $5/mo. No credit card.