Skip to main content

Configuring Your Custom Domain

Set up your primary custom domain by creating a DNS record and entering the domain in Files.com. By default, Files.com obtains and renews the SSL certificate for you, so you do not need to purchase or upload one.

You need Site Administrator access in Files.com and access to your domain's DNS provider. Choose an address on a domain you control, such as files.example.com, then complete these two steps:

  1. At your DNS provider, create a CNAME record pointing your chosen address to your Files.com subdomain, [subdomain].files.com. For example, to use files.example.com for the Files.com site yourcompany.files.com, set the record's name to files within the example.com DNS zone and its target to yourcompany.files.com. Use the hostname alone as the target, without https:// or a path. Select DNS-only mode if your provider offers proxying, so connections reach Files.com directly. Use the lowest available TTL, ideally 30–60 seconds, so later DNS changes take effect promptly.
  2. In Files.com, enter your chosen address, such as files.example.com, in the site-wide Primary Custom Domain setting. Keep the default option for Files.com to manage the SSL certificate, then save. This associates the address with your site and lets Files.com issue the certificate needed for encrypted connections.

Once the DNS record resolves correctly and the certificate is active, open your custom domain in a browser, such as https://files.example.com, to access your site. Your existing Files.com subdomain remains available. This setup also provisions dedicated IP addresses for your site.

For DNS-provider options and troubleshooting, see Custom Domain DNS Records. Custom Domain Settings covers the available site settings, including HTTP Strict Transport Security (HSTS).

Using Your Own SSL Certificate

If you need to provide your own SSL certificate, select Use my own certificate in the Custom Domain settings, then upload and activate your certificate. In the SSL Certificates settings, copy the exact CNAME target shown for your domain under DNS Configuration into your DNS record. This routes connections to the addresses serving your certificate. Targets can differ between domains on the same site, so use the value displayed for the specific domain you are configuring.

Selecting a Custom Domain Name

You can use any subdomain of any domain that you control as your primary custom domain. We recommend not using "ftp" as the first part of your domain (such as ftp.<your-domain>), since this will cause some browsers to improperly access the Files.com web interface. Instead, we suggest using something like files.<your-domain>. For instance, if you control the example.com domain, you might use the custom name files.example.com.

Custom Domain and SSO

Adding a custom domain does not affect your Single Sign-On (SSO) integrations, and no change is needed in your IdP. If the Relay State field in your IdP names your Files.com subdomain, Files.com still identifies your site from it, because the subdomain is still one of your site's hostnames. You can change the field to your custom domain if you prefer, because both hostnames identify the same site.

If the Relay State field names a custom domain that you later change or remove, IdP-initiated logins fail until you update the field, and SP-initiated logins are not affected.

Adding Multiple Custom Domains

Once you've configured your primary custom domain, you can define additional custom domains. The other custom domains can be used just for specific purposes, like rebranding your S3-compatible API endpoint, or changing the domain used for Public Hosting.