Custom Domains

Serve your uploads from your own branded domain with automatic TLS certificates.

Custom domains are available on embrly.ca, and on self-hosted instances running in cloud mode.

Custom domains let you share files and short links from your own domain, like files.yourbrand.com, with HTTPS set up for you.

How Many You Can Add

Everyone gets the same number of domains; see Limits. You can get more by:

Contributing to Emberly on GitHub: +1 to +5, see Contributor Perks
Boosting the Emberly Discord server: +1 to +3, see Discord Perks
Asking for a limit increase

Setting Up a Custom Domain

Step 1: Add Your Domain

Go to Dashboard → Domains
Click "Add Custom Domain"
Enter your domain (e.g., files.yourdomain.com)
Click "Add Domain"

The domain is created with status awaiting_cname.

Step 2: Configure DNS

Add a CNAME record at your DNS provider:

Type	Target / Value	TTL
CNAME	`cname.emberly.site`	300

For a root domain (@), use a CNAME-flattening provider (Cloudflare supports this natively).

Cloudflare users

Set the record to DNS only (grey cloud) during verification. You can enable proxying (orange cloud) after the domain is active.

If your domain's DNS is on Cloudflare, click Set up with Cloudflare on the domain instead and paste a Cloudflare API token with Zone → Zone → Read and Zone → DNS → Edit permission for that domain. Emberly creates the records for you. The token is used once and isn't stored.

Step 3: Verify

Return to Dashboard → Domains
Click "Verify" next to your domain
TLS is automatically provisioned — verification usually completes within a few minutes

Setting a Primary Domain

Your primary domain is used for new uploads and short links, unless you've chosen a different upload domain in Profile → Uploads:

Open your domain list
Click the ⋯ menu next to a verified domain
Select "Set as Primary"

Upload tools such as ShareX follow the same rule. From the API, pass a domain field with an upload to choose one yourself.

Troubleshooting

Status	Meaning
`awaiting_cname`	DNS record not yet detected
`pending`	Cloudflare is provisioning TLS
`active`	Domain is live and serving files
`error`	Verification failed — check DNS

CNAME not detected?

DNS changes can take up to 24 hours to propagate
Verify the target is exactly cname.emberly.site
Use dig CNAME yourdomain.com to check the current value

Certificate errors?

Ensure the domain is verified (active) before enabling Cloudflare proxying
If using Cloudflare, temporarily set to DNS-only and re-verify

For more detail see the Domain API reference.