Custom domains

Serve a bucket's public files from your own hostname, with HTTPS included.

Released November 2026.

You can now give a bucket an address on your own domain. A file that was at https://idr01.zata.ai/my-bucket/photo.jpg can be opened at https://files.example.com/photo.jpg, over HTTPS, with a certificate Zata issues and renews for you.

Set it up in Bucket Settings → Custom Domains: enter the hostname, add the two DNS records the console shows (a TXT record to prove you own the domain and a CNAME record to send traffic to the bucket), and wait for the status to become Active.

What to know

• Custom domains serve public downloads only. Uploads and S3 tools keep using the regional endpoint.
• The bucket's files must be publicly readable. The console offers Allow public read if they are not.
• Available on paid plans, for the account owner. Each bucket can have 1 custom domain and each account 5.
• Use a subdomain such as files.example.com. Root domains and wildcards can't be used.

Learn more

• Custom domains: the full guide, including what to do when a domain shows an error.
• Make files public: how public access works.
• Bucket settings: where the section lives.