Overview

Web3 Storage (now operating as Storacha) lets you upload files to a decentralized storage network built on IPFS and Filecoin, receiving a content-addressed CID for each upload. Files are permanently retrievable via any IPFS gateway using their CID, making this ideal for NFT metadata, open datasets, or any content that must be publicly verifiable. The free tier provides up to 5 GB of storage with no egress fees.

Beginner Tip

After uploading, you can immediately access your file at `https://YOUR_CID.ipfs.w3s.link/` — no extra steps needed. Copy the CID from the upload response and paste it into that URL pattern to confirm the file is live.

Available Data

space mission data
celestial body information
launch schedule
astronomical images

Example Response

JSON Response
{
  "file_id": "f_abc123",
  "filename": "document.pdf",
  "size_bytes": 1048576,
  "mime_type": "application/pdf",
  "download_url": "https://example.com/files/f_abc123",
  "created_at": "2025-01-15T10:00:00Z"
}

Field Reference

cid Content identifier (CID) for the uploaded file — use this to retrieve the file from any IPFS gateway.
size Size of the uploaded content in bytes.
created Timestamp when the upload was recorded.
type MIME type of the uploaded content as detected or declared.
name Filename associated with the upload, if provided.

Implementation Example

Request
const url = "https://web3.storage/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized The API token is missing or has been revoked.
Create a new API token at web3.storage (or storacha.network) and pass it as `Authorization: Bearer YOUR_TOKEN`.
CID not found immediately after upload IPFS propagation can take a few seconds to several minutes before the CID is resolvable on public gateways.
Wait 30–60 seconds and retry the IPFS gateway URL. Use the w3s.link gateway first as it has the fastest access to freshly uploaded content.
Upload body too large (413) Single-request uploads are limited; very large payloads exceed the HTTP body limit.
Use the CAR (Content Addressable Archive) upload endpoint or the official w3up-client library which handles chunking automatically.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth API Key
HTTPS REQUIRED
CORS YES
Difficulty Intermediate
Verified: 2026-04-07

Similar APIs

View All →