Public Gateways

Public gateways are best-effort, with no SLA. They run as a public good and can rate-limit, change, or go offline at any time, so they suit demos and testing only. Production apps that can't run full peer-to-peer and need an HTTP Gateway or Delegated Routing should run a self-hosted IPFS stack end-to-end.

SECURITY NOTES

• For complex websites and apps, only use gateways with ✅ in the Origin column.
  Gateways marked ❌ lack origin isolation: all sites share localStorage, cookies, and session data. A malicious page could access data from every other site you've visited via that gateway. Subdomain gateways also ensure relative links work correctly.
• For wallets and dapps, self-host your gateway on your local machine.
  Third-party gateways can inspect your browsing history or modify deserialized traffic. Run IPFS Desktop (GUI) or Kubo (CLI) for a localhost gateway, and IPFS Companion browser extension to redirect IPFS requests to it automatically.
• No central authority governs this list. Run your own gateway and add it here.
  IPFS Foundation operates only these public good gateways: ipfs.io, dweb.link, and trustless-gateway.link (report abuse).