New Tigris accounts now serve public content from a dedicated domain:
`t3.tigrisfiles.io`. This separates public content delivery from API infrastructure.

## What's changing?

New Tigris accounts serve public content — both
[public buckets](/content/docs/buckets/public-bucket/index.html) and
[public objects in private buckets](/content/docs/objects/public-objects/index.html) — from `t3.tigrisfiles.io` instead of `t3.storage.dev`.

Public content URLs use the bucket name as a subdomain:

```text
https://my-assets.t3.tigrisfiles.io/logo.png
```

No additional configuration required.

This change only affects how public content is served to anonymous visitors. All
authenticated operations — uploading, listing, deleting, and managing objects
through the CLI, SDKs, or S3 API — continue to use `t3.storage.dev`. When you
use an SDK, every request is authenticated, whether the bucket is public or
private. The only thing that changes is the URL you hand out for public access.

Presigned URLs generated through the Tigris Console now use `t3.tigrisfiles.io`
automatically. Presigned URLs you generate in your own code continue to work on
whichever endpoint you already use.

## What about existing accounts?

Nothing changes. If you already serve public content from `*.t3.storage.dev`,
your URLs continue to work. This change applies only to new accounts.

Organizations, namespaces, and buckets belonging to known partners are also
excluded regardless of account age.

`fly.storage.tigris.dev`, used by many Fly.io users, follows the same rules. New
accounts should use `t3.tigrisfiles.io` for public content instead.

To switch existing content to the new domain, swap the hostname:

```diff
- https://my-bucket.t3.storage.dev/images/photo.jpg

+ https://my-bucket.t3.tigrisfiles.io/images/photo.jpg
```

## Custom domains

If you use a
[custom domain](/content/docs/buckets/custom-domain/index.html) for your
public bucket, it continues to work as before. New custom domain CNAME records
should point to `BUCKET.t3.tigrisbucket.io` as described in the
[custom domain docs](/content/docs/buckets/custom-domain/index.html).

For production public content, we recommend a custom domain. It keeps your URLs
stable regardless of platform domain changes.

## Alternate domains

Two additional domains serve the same public content as `t3.tigrisfiles.io`:

| Domain                           | Example URL                              |
|----------------------------------|------------------------------------------|
| `BUCKET.t3.tigrisbucket.io`     | `https://my-assets.t3.tigrisbucket.io/logo.png` |
| `BUCKET.t3.tigrisblob.io`       | `https://my-assets.t3.tigrisblob.io/logo.png` |

If `t3.tigrisfiles.io` has issues, you can switch to either of these
immediately.

## Getting started

Create a public bucket with a single command:

```bash
aws s3api create-bucket \

--endpoint-url https://t3.storage.dev \

--bucket my-public-site \

--acl public-read
```

Your content is available immediately at
`https://my-public-site.t3.tigrisfiles.io/`.

See the
[public bucket docs](/content/docs/buckets/public-bucket/index.html) for
the full setup guide, and the
[custom domain docs](/content/docs/buckets/custom-domain/index.html) to
set up your own domain.