# Decentralized and Web3 S3-Compatible Storage (Storj, Filebase, and More)

> S3-compatible object storage backed by decentralized networks: Storj, Filebase, 4everland, Akave, and the gateway pattern that lets standard S3 tools write to IPFS, Sia, and node networks.

Decentralized storage spreads your data across a network of independent nodes instead of one company's data centers. What makes them usable day to day is the S3-compatible gateway: it puts a standard S3 API in front of the decentralized backend, so your existing S3 tools write to IPFS, Sia, or a node network without touching the underlying protocol. This page lists the decentralized and Web3 S3-compatible providers and how to connect each one.

This is one category in our [complete list of S3-compatible storage providers](/kb/articles/s3-compatible-storage-providers-complete-list/). These connect to Blober through the generic [S3-Compatible connector](/kb/docs/providers/s3-compatible/) when the gateway supports the common S3 operations Blober uses: you point it at the gateway endpoint with the keys the network issues.

## Storj

Storj is decentralized cloud storage where files are encrypted, split, and erasure-coded across thousands of independent nodes worldwide. Its S3-compatible hosted gateway makes all of that invisible to S3 tools.

* **Endpoint format:** `gateway.storjshare.io`, with regional gateways `gateway.eu1.storjshare.io`, `gateway.us1.storjshare.io`, and `gateway.ap1.storjshare.io`.
* **Addressing:** virtual-hosted.
* **Notes:** S3 credentials are generated from an access grant in the Storj console. Storj is globally distributed by default; when an S3-compatible tool requires a region, set it to `global`[\[1\]](https://storj.dev/dcs/buckets/data-location "Source: storj.dev/dcs/buckets/data-location"). Use a large multipart cutoff for very large files. Storj also appears on our [object storage specialists page](/kb/articles/best-s3-compatible-object-storage-specialists/).

## Filebase

Filebase is an S3-compatible gateway that stores objects on decentralized networks (IPFS, and historically Sia and Storj) while presenting a familiar S3 API and console.

* **Endpoint format:** `s3.filebase.io`.
* **Addressing:** both path-style (`https://s3.filebase.io/<bucket>/<key>`) and virtual-hosted (`https://<bucket>.s3.filebase.io/<key>`) are supported.
* **Notes:** Filebase uses a single global endpoint and region `auto`; public-bucket reads should use the virtual-hosted URL served by the Filebase CDN[\[2\]](https://filebase.com/docs/s3-api/overview "Source: filebase.com/docs/s3-api/overview").

## 4everland

4everland is a Web3 infrastructure platform whose Bucket service offers an S3-compatible API backed by IPFS and Arweave.

* **Endpoint format:** `endpoint.4everland.co`.
* **Addressing:** virtual-hosted.
* **Notes:** designed for hosting and pinning assets to decentralized networks while keeping the S3 workflow. Generate keys in the 4everland dashboard; the documented S3-compatible endpoint is `https://endpoint.4everland.co`[\[3\]](https://docs.4everland.org/storage/bucket/bucket-api-s3-compatible.md "Source: docs.4everland.org/storage/bucket/bucket-api-s3-compatible.md").

## Akave

Akave provides decentralized object storage with an S3-compatible interface (Akave O3) aimed at data availability for AI and Web3 workloads.

* **Endpoint format:** the S3-compatible gateway endpoint issued in your Akave account.
* **Addressing:** virtual-hosted.
* **Notes:** confirm the current endpoint host and credentials in the Akave console, as the production gateway address is account-specific. Akave's docs list `akave-network` as the region value for its decentralized S3 interface and show hosted endpoints such as `https://o3-rc2.akave.xyz` for specific environments[\[4\]](https://docs.akave.xyz/akave-o3/introduction/akave-environment/ "Source: docs.akave.xyz/akave-o3/introduction/akave-environment/").

## How the Gateway Pattern Works

Most decentralized networks were not designed around the S3 API. What makes them usable from ordinary tools is a gateway that translates S3 calls into the network's native operations: pinning to IPFS, contracts on Sia, erasure-coding across Storj nodes, and so on. From your side, it is just an endpoint and a pair of keys.

That is the same reason Blober can treat a decentralized gateway like a normal S3 target for common object operations. You do not interact with the network protocol; you point the [S3-Compatible connector](/kb/docs/providers/s3-compatible/) at the gateway and transfer as usual.

A few practical points for decentralized targets:

* **Server-side copy may be limited.** Some gateways do not implement S3 server-side copy. Blober falls back to streaming the copy through, so transfers still work.
* **Listing and metadata can differ.** Treat these stores as S3-compatible for the common operations (browse, upload, download) and confirm any advanced behavior with the provider.
* **Encryption is often built in, but check where it happens.** Networks like Storj encrypt and erasure-code data before it leaves the hosted gateway, but the gateway still handles the upload. Add client-side encryption if your threat model requires the gateway itself not to see plaintext.

## Frequently Asked Questions

**Is decentralized storage really S3-compatible?** The storage networks themselves are not S3, but their gateways are. You connect to the gateway endpoint with S3 keys, and standard S3 tools work. That is what "S3-compatible" means here.

**Can I move data from AWS S3 to Storj or Filebase?** Yes. Because the gateways speak S3, Blober copies directly from an S3 bucket to the decentralized gateway by setting the source and destination endpoints.

**Do these keep my data private?** Several encrypt data before it is distributed (Storj is a notable example). Check each provider's encryption model, since the details differ between networks.

**Why might a transfer behave differently than to AWS?** Some gateways limit server-side copy or return listings differently. Blober handles the copy fallback automatically, so the transfer completes even when native copy is unavailable.

## Related Guides

* [The Complete List of S3-Compatible Providers](/kb/articles/s3-compatible-storage-providers-complete-list/)
* [Object Storage Specialists](/kb/articles/best-s3-compatible-object-storage-specialists/)
* [Self-Hosted and Open-Source S3 Storage](/kb/articles/self-hosted-open-source-s3-compatible-storage/)
* [What S3-Compatible Really Means](/kb/articles/what-s3-compatible-really-means/)

## Get Blober

Connect Blober to a decentralized S3 gateway by URL and move data between Web3 storage and the rest of your clouds directly, without filling your local disk.

**[Download Blober at blober.io](https://blober.io)**