Use your own domain for shared links.

A link is part of how your work reads. A client opening files.yourstudio.com trusts it more than a generic URL from a host they have never heard of, and the link stops advertising someone else's brand on your behalf. That is what a custom domain does. It swaps the nudgehost.com part of every link for an address you own, while the file and everything around it stay exactly the same. The background on what changes and what does not is in branded share links.

Setup is one DNS record, not a migration. Add your domain or a subdomain in the dashboard, then create a CNAME record at your registrar pointing it at NudgeHost. Once the record resolves, your links use your address. If the words CNAME and registrar are unfamiliar, how DNS works explains how the domain name system turns a name you typed into the server that answers, which is the whole mechanism a custom domain relies on.

The part people expect to be painful is the security certificate, and there is nothing to do. NudgeHost issues and renews one for your domain automatically, so the connection is encrypted from the first request and the padlock shows in the browser without you buying or uploading anything. For what that certificate actually is and why the browser checks it, SSL certificates covers it.

A custom domain also tidies up how links look when shared, since the link preview in Slack and iMessage that unfurl in Slack and LinkedIn now carry your address in the URL line. Custom domains live on the Pro and Team tiers, so the paid tier is where the feature starts. For a single personal share the default link is fine. For anything client-facing, your own domain is the difference between looking like a vendor and looking like yourself.