# Bandwidth Usage

Filebase tracks outgoing data transfer (egress) across all services. Upload bandwidth (ingress) is always free. Your dashboard displays a stacked bandwidth chart broken down by the following categories:

## S3

Data downloaded through the S3-compatible API. This includes `GetObject` requests, multipart download reads, and any other egress through the S3 endpoint.

## Gateway

Data served through your dedicated IPFS gateways. Each time a user or application fetches content via a dedicated gateway URL, the response size counts toward this category.

## Public GW

Data served through the shared Filebase public IPFS gateway (`ipfs.filebase.io`). The public gateway is intended for testing and light usage and is subject to [rate limits](https://docs.filebase.com/service-limits#public-gateway-rate-limits).

## Bitswap

Data transferred to other IPFS peers via the Bitswap protocol. When external IPFS nodes request blocks of your pinned content, the outbound transfer is counted here.

## Trustless

Data served via the IPFS Trustless HTTP Gateway protocol. Trustless gateways return content-addressed, verifiable responses that clients can validate independently.

## RPC

Data transferred through IPFS RPC API calls. This covers responses from the [IPFS RPC API](https://docs.filebase.com/api-documentation/ipfs-rpc-api) endpoint.

## Sites

Data served from Filebase-hosted IPFS sites. When visitors load pages on a site you've published through [Filebase Sites](https://docs.filebase.com/sites/sites), the page and asset egress counts toward this category.

## Billing

All categories are summed together and count toward your account's total bandwidth usage. For pricing details, see the [Filebase Pricing page](https://filebase.com/pricing/).