{"id":280,"date":"2026-06-23T18:31:17","date_gmt":"2026-06-23T18:31:17","guid":{"rendered":"https:\/\/documentlibrary.pro\/docs\/document-library-pro-hosted-custom-domain\/"},"modified":"2026-06-25T11:39:20","modified_gmt":"2026-06-25T11:39:20","slug":"document-library-pro-hosted-custom-domain","status":"publish","type":"doc","link":"https:\/\/documentlibrary.pro\/es\/docs\/document-library-pro-hosted-custom-domain\/","title":{"rendered":"Use a custom domain with your hosted document library"},"content":{"rendered":"

Out of the box, your hosted document library sits at a documentlibrary.app address (something like your-library.documentlibrary.app<\/code>). If you would rather it lived on an address of your own, for instance docs.yourcompany.com<\/code>, you can hook up a custom domain. Here is how the process works.<\/p>\n

What a custom domain gives you<\/h2>\n

Connect a custom domain and both your library and the links you share point to your own branded address rather than the default documentlibrary.app one. That makes sense if you send your library link around a lot, or if you want it to sit alongside the rest of your website. A subdomain works best for this, for example docs.yourcompany.com<\/code> or library.yourcompany.com<\/code>.<\/p>\n

How to request your custom domain<\/h2>\n

Open your hosted dashboard and head to your library settings. (You will also come across this step in the setup wizard the first time you create a library.) Type the domain you want, such as docs.yourcompany.com<\/code>, into the custom domain<\/strong> field, then choose Request Domain<\/strong>.<\/p>\n

What happens next<\/h2>\n

Custom domains are something we configure by hand, which keeps everything correctly and securely set up. Once your request comes in, we will get in touch inside two working days<\/strong> to finish the setup together.<\/p>\n

You will need to be able to reach your domain’s DNS settings<\/strong>, which are typically handled wherever you bought the domain or with your hosting provider. We will give you the precise DNS record to add, usually a CNAME record<\/strong> aimed at our platform. After that record is in place and has had a little time to take effect, we point your domain at your library and a secure SSL certificate is issued automatically, so the library loads over HTTPS.<\/p>\n

The DNS record you will add<\/h2>\n

The record we ask for is always a CNAME<\/strong> that points your domain at our platform:<\/p>\n