A custom domain replaces the defaultDocumentation Index
Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt
Use this file to discover all available pages before exploring further.
share.streampixel.io URL with one of your own — for example play.yourgame.com or demo.yourcompany.com. This is useful for branding, embedding without third-party cookie restrictions, and keeping your CSP rules tight.
Why use a custom domain
Branding
Visitors see your domain in the address bar, not Streampixel’s.
Embed-friendly
Same-origin embeds bypass third-party cookie blocking in modern browsers.
CSP compatibility
Tight Content Security Policies that disallow
streampixel.io still work.Trust
Users recognize your domain and are less likely to bounce.
Add a custom domain
Open Project Settings
Navigate to the project that should serve from a custom domain and open Project Settings.
Add the DNS record
Streampixel shows a
CNAME (or A record for apex domains) value. Copy it and add it at your DNS provider — Cloudflare, Route 53, GoDaddy, Namecheap, etc.Click Verify
Once the DNS record is live, click Verify in the dashboard. Streampixel checks resolution and provisions HTTPS.
DNS setup
Use aCNAME for subdomains (recommended) and an A record for apex domains.
| Record type | When to use | Example |
|---|---|---|
CNAME | Subdomains like play.example.com | play.example.com → cname.streampixel.io |
A | Apex domains like example.com (some registrars do not allow CNAME at the apex) | example.com → 203.0.113.10 |
DNS changes can take a few minutes to several hours to propagate globally, depending on your provider’s TTL and your registrar. If verification fails immediately after adding the record, wait 5-10 minutes and try again.
HTTPS / TLS
Streampixel handles certificate provisioning automatically as soon as DNS verification succeeds. There is no need to upload a certificate, generate a CSR, or renew anything. Certificates are renewed before expiry without any action on your side. The stream is only served over HTTPS — there is no HTTP fallback.If your DNS provider has CAA records, make sure they permit Streampixel’s certificate authority. Most defaults are permissive enough; if certificate issuance fails, removing the CAA record temporarily is the easiest fix.
Multiple domains per project
You can add more than one custom domain to the same project. This is useful when:- Migrating from an old domain to a new one (run both for a transition period).
- Serving the same experience under regional domains (
play.example.com,play.example.de). - Supporting both the apex and a
wwwsubdomain.
Remove a domain
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Verification fails | DNS record not propagated yet | Wait 5-10 minutes, then click Verify again. |
| Verification fails | DNS record points at the wrong target | Re-copy the exact value shown in the dashboard. |
| Verification fails | A pre-existing record is still cached | Lower the TTL on your DNS, wait, then retry. |
| HTTPS shows a warning | Certificate is still provisioning | Wait a minute or two after a successful verification. |
| Stream loads on the streampixel.io URL but not the custom domain | DNS resolves but is pointed at the wrong host | Use dig +short play.example.com to confirm it resolves to the value the dashboard expects. |
| Embedding still shows third-party cookie warnings | Browser is caching the old origin | Hard-refresh the embedding page after switching the embed URL to the custom domain. |
Next steps
Sharing and embedding
Use your custom domain in embed iframes.
Security control
Whitelist your custom domain alongside
share.streampixel.io.Branding
Pair the custom domain with custom logo and splash screens.
Webhooks
Receive events when builds tied to this domain are updated.