The URL is part of the deliverable
If you send HTML to clients, a proposal, a report, a dashboard, an interactive mockup, the link itself does real work before anyone reads a word. A random string of characters tells the recipient "this is a temporary upload". A readable, branded path tells them "this is the document, prepared for you". The difference is the same gap between a file dumped on a free host and a finished deliverable, and for consultants and agencies it is often the detail that makes the work look worth what it cost.
There are two distinct meanings of "custom link" worth separating, because they have very different setup costs:
- A custom path on a shared domain, such as
livesend.io/yourname/acme-proposal. Readable, branded to you, near-zero setup. - A custom domain you own, such as
reports.youragency.com. Maximum control, but it requires hosting and DNS work.
Option 1, a branded path on LiveSend (lowest setup)
LiveSend gives every account a username, chosen once. On Pro, each document can take a custom slug under that username, so the link reads yourname/q3-report rather than a random code. The workflow is three steps:
- Upload or paste your HTML to create the document.
- On the Access tab, set the custom slug (must be unique in your account).
- Send the branded link. The original random URL keeps working too.
The branded link carries everything else with it: view tracking, optional password, expiration, inline editing without changing the URL. Honest limits: it lives under the LiveSend domain (no fully custom domain yet), there is a 3MB (6MB for Pro) cap per file, and the custom slug is a Pro feature.
Option 2, a custom domain on Vercel, Netlify, or Cloudflare Pages
If the link absolutely has to be on your own domain, deploy the HTML as a static site and point a subdomain at it, for example reports.youragency.com. This is the right answer when the domain itself is part of the brand promise.
The cost is setup and maintenance: a Git repository or drag-and-drop deploy, DNS records for the subdomain, and a redeploy every time the document changes (which also tends to change the path unless you manage it carefully). None of these platforms include per-recipient view tracking, password protection, or expiration out of the box, so you would build or bolt those on yourself.
Option 3, a URL shortener with a custom alias
Tools like Bitly or Dub let you create a short link with a custom alias that redirects to wherever the HTML is hosted. This cleans up the visible link but does not change where the file lives, you still need a host underneath, and the recipient's address bar shows the real destination URL once redirected. Shorteners also add a hop that some corporate email filters flag. Useful as a cosmetic layer, not a hosting solution.
Which one fits your work
If you want a readable, branded link in under a minute and you also want to know when the client opened it: a custom slug on LiveSend. If the link must be on a domain you own and you have the appetite for hosting and DNS: deploy on Vercel or Netlify. If you only need to tidy up an existing link cosmetically: a shortener with a custom alias. For most client deliverables, the branded path plus built-in tracking is the shortest path to something that looks finished.
Already generating the HTML with an AI tool? See how to share an AI-generated report with a client.