IPFS unlocks a ton of value at the data layer, but its peer-to-peer nature means reading data from the network isn’t always performant by today’s web standards. w3link marries IPFS content IDs with CDNs to provide a much more performant read experience - and is especially fast for content stored on the web3.storage platform - while still taking advantage of the benefits of IPFS.

In addition, like other IPFS HTTP gateways, w3link takes requests over HTTP, making it easy to integrate with today’s existing web infrastructure.

2-3x

Faster than other public IPFS Gateways for average reads

1PiB+

Served per month

270+

Points of Presence

The most common way for users to read data available on the public IPFS network is via IPFS HTTP gateways like w3link, which are generally run as public services.

Since they use IPFS, you’re never locked into a single gateway and its infrastructure - just swap the domain name. In addition, you can always fetch data from web3.storage using your own IPFS nodes instead or as a backup.

Soon, you’ll be able to use w3link’s SuperHot feature to perma-cache data of up to 5GB per content ID on the edge. Guarantee your users the fastest possible read performance on the web for less than pennies a month.

Perma-cache data up to 5GB per CID

100 ms time-to-first-byte for 95% of the world’s Internet-connected population

Centralized URL support (cache even non-IPFS data)

Perma-cache files of any size

Image resizing in the web3.storage Gateway. Great for thumbnails, etc.

Auto-cache updates to IPNS records for fast updates to mutable content.