---
title: "Introducing t3.tigrisfiles.io for public content"
description: "New Tigris accounts serve public buckets and objects from t3.tigrisfiles.io. Existing URLs keep working."
date: "2026-04-02"
author: "Katie Schilling"
url: "https://fly.io/changelog/tigris-public-content-domain/"
discussion: "https://community.fly.io/t/introducing-t3-tigrisfiles-io-for-public-content/27511"
---

# Introducing t3.tigrisfiles.io for public content

📣 Announcement

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

If you're signing up today, your public buckets and public objects are served from t3.tigrisfiles.io automatically. All authenticated operations (uploads, SDK calls, CLI) continue to use t3.storage.dev — the only thing that changes is the URL you share for public access.

A few things to know:
- Existing accounts are unaffected; your current URLs keep working
- For production public content, we recommend setting up a [custom domain](https://www.tigrisdata.com/docs/buckets/custom-domain/)
- `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.

Full details: https://www.tigrisdata.com/blog/public-bucket-domains