kubo/docs/gateway.md

Gateway

An IPFS Gateway acts as a bridge between traditional web browsers and IPFS. Through the gateway, users can browse files and websites stored in IPFS as if they were stored in a traditional web server.

More about Gateways and addressing IPFS on the web.

Kubo's Gateway implementation follows IPFS Gateway Specifications and is tested with Gateway Conformance Test Suite.

Local gateway

By default, Kubo nodes run a path gateway at http://127.0.0.1:8080/ and a subdomain gateway at http://localhost:8080/.

Caution

For browsing websites, web apps, and dapps in a browser, use the subdomain gateway (localhost). Each content root gets its own web origin, isolating localStorage, cookies, and session data between sites.

For file retrieval, use the path gateway (127.0.0.1). Path gateways are suited for downloading files or fetching verifiable content, but lack origin isolation (all content shares the same origin).

Additional listening addresses and gateway behaviors can be set in the config file.

Public gateways

IPFS Foundation provides public gateways at https://ipfs.io (path), https://dweb.link (subdomain), and https://trustless-gateway.link (trustless only). If you've ever seen a link in the form https://ipfs.io/ipfs/Qm..., that's being served from a public goods gateway.

There is a list of third-party public gateways provided by the IPFS community at https://ipfs.github.io/public-gateway-checker/

Configuration

The Gateway.* configuration options are (briefly) described in the config documentation, including a list of common gateway recipes.

Debug

The gateway's log level can be changed with this command:

> ipfs log level core/server debug

Running in Production

When deploying Kubo's gateway in production, be aware of these important considerations:

Important

Reverse Proxy: When running Kubo behind a reverse proxy (such as nginx), the original Host header must be forwarded to Kubo for Gateway.PublicGateways to work. Kubo uses the Host header to match configured hostnames and detect subdomain gateway patterns like {cid}.ipfs.example.org or DNSLink hostnames.

If the Host header is not forwarded correctly, Kubo will not recognize the configured gateway hostnames and requests may be handled incorrectly.

If X-Forwarded-Proto is not set, redirects over HTTPS will use wrong protocol and DNSLink names will not be inlined for subdomain gateways.

Example: minimal nginx configuration for example.org

server {
    listen 80;
    listen [::]:80;

    # IMPORTANT: Include wildcard to match subdomain gateway requests.
    # The dot prefix matches both apex domain and all subdomains.
    server_name .example.org;

    location / {
        proxy_pass http://127.0.0.1:8080;

        # IMPORTANT: Forward the original Host header to Kubo.
        # Without this, PublicGateways configuration will not work.
        proxy_set_header Host $host;

        # IMPORTANT: X-Forwarded-Proto is required for correct behavior:
        # - Redirects will use https:// URLs when set to "https"
        # - DNSLink names will be inlined for subdomain gateways
        #   (e.g., /ipns/en.wikipedia-on-ipfs.org → en-wikipedia--on--ipfs-org.ipns.example.org)
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host  $host;
    }
}

Common mistakes to avoid:

• Missing wildcard in server_name: Using only server_name example.org; will not match subdomain requests like {cid}.ipfs.example.org. Always include *.example.org or use the dot prefix .example.org.

• Wrong Host header value: Using proxy_set_header Host $proxy_host; sends the backend's hostname (e.g., 127.0.0.1:8080) instead of the original Host header. Always use $host or $http_host.

• Missing Host header entirely: If proxy_set_header Host is not specified, nginx defaults to $proxy_host, which breaks gateway routing.

Important

Timeouts: Configure Gateway.RetrievalTimeout based on your expected content retrieval times.

Important

Rate Limiting: Use Gateway.MaxConcurrentRequests to protect against traffic spikes.

Important

CDN/Cloudflare: If using Cloudflare or other CDNs with deserialized responses enabled, review Gateway.MaxRangeRequestFileSize to avoid excess bandwidth billing from range request bugs. Cloudflare users may need additional protection via Cloudflare Snippets.

Directories

For convenience, the gateway (mostly) acts like a normal web-server when serving a directory:

1. If the directory contains an index.html file:
2. If the path does not end in a /, append a / and redirect. This helps avoid serving duplicate content from different paths.^†
3. Otherwise, serve the index.html file.
4. Dynamically build and serve a listing of the contents of the directory.

_{^†This redirect is skipped if the query string contains a go-get=1 parameter. See PR#3963 for details}

Static Websites

You can use an IPFS gateway to serve static websites at a custom domain using DNSLink. See Example: IPFS Gateway for instructions.

Filenames

When downloading files, browsers will usually guess a file's filename by looking at the last component of the path. Unfortunately, when linking directly to a file (with no containing directory), the final component is just a CID (bafy.. or Qm...). This isn't exactly user-friendly.

To work around this issue, you can add a filename=some_filename parameter to your query string to explicitly specify the filename. For example:

https://ipfs.io/ipfs/QmfM2r8seH2GiRaC4esTjeraXEachRt8ZsSeGaWTPLyMoG?filename=hello_world.txt

When you try to save above page, you browser will use passed filename instead of a CID.

Downloads

It is possible to skip browser rendering of supported filetypes (plain text, images, audio, video, PDF) and trigger immediate "save as" dialog by appending &download=true:

https://ipfs.io/ipfs/QmfM2r8seH2GiRaC4esTjeraXEachRt8ZsSeGaWTPLyMoG?filename=hello_world.txt&download=true

Response Format

An explicit response format can be requested using ?format=raw|car|.. URL parameter, or by sending Accept: application/vnd.ipld.{format} HTTP header with one of supported content types.

Content-Types

Majority of resources can be retrieved trustlessly by requesting specific content type via Accept header or ?format=raw|car|ipns-record URL query parameter.

See trustless gateway specification and verifiable retrieval documentation for more details.

application/vnd.ipld.raw

Returns a byte array for a single raw block.

Sending such requests for /ipfs/{cid} allows for efficient fetch of blocks with data encoded in custom format, without the need for deserialization and traversal on the gateway.

This is equivalent of ipfs block get.

application/vnd.ipld.car

Returns a CAR stream for a DAG or a subset of it.

The dag-scope parameter controls which blocks are included: all (default, entire DAG), entity (logical unit like a file), or block (single block). For UnixFS files, entity-bytes enables byte range requests. See IPIP-402 for details.

This is a rough equivalent of ipfs dag export.

application/vnd.ipfs.ipns-record

Only works on /ipns/{ipns-name} content paths that use cryptographically signed IPNS Records.

Returns IPNS Record in Protobuf Serialization Format which can be verified on end client, without trusting gateway.