Setup guide · Updated May 2026

Custom domain file sharing setup guide

Send files from files.youragency.com instead of wetransfer.com or drive.google.com. This guide walks through exactly how custom-domain file sharing works, the DNS setup in plain English, common pitfalls, and which tools actually support it.

Updated May 19, 2026
11 min read

What you'll learn

  • What custom-domain file sharing actually is (and what it isn't)
  • How DNS CNAME records make it work — explained in plain English
  • The exact 5-step setup process with example DNS records
  • Common pitfalls — SSL conflicts, Cloudflare proxy, root-domain issues
  • Which tools support true custom-domain delivery (and which fake it)
  • Pricing reality check — most tools charge enterprise rates

What is custom domain file sharing?

In one sentence

Sending files from a download link on your own domain (files.youragency.com) instead of a vendor's domain (wetransfer.com, drive.google.com).

When you send a client a file via WeTransfer or Google Drive, the link reads wetransfer.com/... or drive.google.com/... — the recipient lands on someone else's branded page. Custom-domain file sharing replaces that vendor URL with your own, so the link reads files.youragency.com/q4-final. Same file, your brand wraps the handoff.

Under the hood, you point a subdomain (e.g., 'files' or 'downloads') at your file-sharing tool's infrastructure via a DNS record called a CNAME. The tool auto-provisions an SSL certificate so the link is HTTPS. Your root domain (the site itself) is untouched — only the subdomain is dedicated to delivery.

Most well-known file services (WeTransfer, Dropbox, Google Drive) don't offer this at any price. The ones that do typically charge enterprise pricing — $200+/mo with annual commits. A few accessible options exist; we cover them below.

How it actually works — DNS, CNAME, and SSL

The technical mechanism is a single DNS record. You don't need to host anything or run a server. The file-sharing tool keeps doing all the work; your domain just acts as the public-facing URL.

Here's the flow when a client clicks your branded link:

The flow

  1. 1

    Client clicks

    files.youragency.com/abc123

  2. 2

    DNS resolves

    Your CNAME → vendor's edge

  3. 3

    SSL handshake

    Cert matches your domain

  4. 4

    Vendor serves

    File served as your brand

  5. 5

    Client downloads

    Branded download page

Step-by-step setup

Setup is genuinely simple — under 10 minutes end-to-end on most platforms. The exact tool UI varies, but the DNS steps are the same everywhere. We'll use 'files.youragency.com' as our example subdomain throughout.

  1. 01

    Pick a delivery subdomain

    Choose a short, memorable subdomain dedicated to delivery. The most common patterns are 'files', 'downloads', 'send', or 'share'. Avoid your root domain — that's reserved for your main website. CNAME records have technical conflicts with root domains, and a dedicated subdomain keeps your delivery URL separate from your marketing site.

  2. 02

    Sign up for a tool that supports true CNAME on an entry tier

    Most well-known file services (WeTransfer, Dropbox, Google Drive) don't support custom-domain delivery at any tier. The accessible options are BulkShare Pro ($29/mo), Jumpshare Plus ($8.25/mo), and Files.com (enterprise tiers starting around $50/user/mo). Set up your account before adding the DNS record so you can verify it immediately.

  3. 03

    Find the CNAME target value from your tool

    Inside your tool's dashboard (usually under 'Custom Domain' or 'Branding'), the platform shows you the exact CNAME target value. It looks something like 'app.bulkshare.cloud' or 'cname.vendor.com'. Copy this exact string — you'll paste it into your DNS provider next.

    Example CNAME target from your tool
    Target: app.bulkshare.cloud# yours will be unique
  4. 04

    Add the CNAME record at your DNS provider

    Log into wherever your domain is registered — Cloudflare, Namecheap, GoDaddy, Vercel, Route 53 all work the same way. Find the DNS management section, add a new record with these exact values, save, and you're done with the DNS side.

    DNS record to add
    Type:CNAME
    Name:files# just the subdomain part
    Target:app.bulkshare.cloud# from step 3
    TTL:Auto# or 300 if you must specify
  5. 05

    Verify in your tool + wait for SSL provisioning

    Back in your tool's dashboard, hit 'Verify' on the custom domain. The tool checks DNS resolution and provisions a free SSL certificate (typically Let's Encrypt) within 1-5 minutes. You'll see a 'Verified ✓' or 'Live' status when it's ready. Total wait time is usually under 30 minutes including DNS propagation.

  6. 06

    Test with a real delivery

    Generate a new link from the tool — it should now read files.youragency.com/[link-slug]. Open in an incognito browser to confirm HTTPS works. Send a real delivery to a client. The brand consistency is immediate, and you'll feel the difference on the very first link.

Common pitfalls to avoid

Setup itself is simple, but a few configuration choices catch people. Knowing these in advance saves 30 minutes of debugging:

  • Trying to use your root domain instead of a subdomain

    CNAME records have technical limitations on root domains (apex records) — they conflict with other DNS entries like MX records for email. Always use a subdomain like 'files.youragency.com' or 'downloads.youragency.com'. This is the standard pattern across every vendor.

  • Cloudflare orange-cloud proxy breaking SSL

    If you proxy your DNS through Cloudflare (orange-cloud), the SSL certificate provisioning from your file-sharing tool can fail. Switch to gray-cloud (DNS only) for the delivery subdomain during initial setup. Some tools work fine with the proxy after verification — check vendor docs.

  • Adding the full subdomain in the 'Name' field

    When adding the CNAME record, the 'Name' field should be just 'files' — not 'files.youragency.com'. The DNS provider automatically appends your root domain. Adding the full name creates an invalid record like 'files.youragency.com.youragency.com'.

  • Expecting the URL to be instantly live globally

    DNS propagation takes time. Most users see the URL live within 5-30 minutes, but in rare cases it can take up to 24 hours for global propagation. Don't panic if your CNAME doesn't resolve immediately — wait an hour before troubleshooting.

  • Not setting up SPF/DKIM/DMARC for email reputation

    Custom-domain delivery improves email deliverability when paired with SPF, DKIM, and DMARC records on your domain. Without these, emails containing your branded links can still hit spam filters. Set up email auth properly if you send delivery links via Mailchimp, Postmark, or any transactional email service.

  • Choosing a subdomain you'll outgrow

    If your domain hosts multiple brands or sub-brands, a generic 'files.youragency.com' might force awkward future migrations. Consider 'downloads.youragency.com', 'send.youragency.com', or even brand-specific subdomains if you have a multi-brand setup.

Tools that support custom-domain delivery

Not every file-sharing tool offers real custom-domain delivery — and many use the term loosely. Here's a brief honest list of the accessible options (full reviews and pricing are linked):

  • BulkShare

    Editor's pick

    True CNAME custom-domain delivery on Pro ($29/mo). Cheapest credible option that doesn't require enterprise sales calls or annual commits. up to 5 seats included (no per-seat upcharge) for small teams.

    Learn more

  • Jumpshare

    Custom-domain delivery on Plus tier ($8.25/mo). Designed around screen capture workflow — good fit if you're already using it for screenshots and recordings.

    Learn more

  • Files.com

    True CNAME on all paid tiers. Enterprise-grade infrastructure with dedicated IPs and SOC2 compliance. Starts around $50/user/mo — overkill for solo agencies but strong for medium-large companies.

  • Smash

    Subdomain (yourstudio.fromsmash.com) on Pro tier. True CNAME on your own root requires Enterprise. Best fit for huge-file transfer workflows.

    Learn more

  • Filemail

    Custom-domain delivery on Business tier. Strong fit for compliance-heavy industries (Norway data residency, GDPR-friendly).

    Learn more

  • WeTransfer / Dropbox / Google Drive

    Not supported at any tier. WeTransfer Ultimate allows custom backgrounds + logo on transfer pages, but the URL stays wetransfer.com. Dropbox and Drive don't offer it at all.

Try it yourself

Set up your branded delivery domain in under 10 minutes.

Start free on Starter to verify the DNS flow without a credit card. Upgrade to Pro ($29/mo) when you're ready to go live with files.youragency.com.

Start freeSee pricing

Frequently asked questions

No. The hardest part is adding one DNS record — every modern domain registrar (Cloudflare, Namecheap, GoDaddy, Vercel, Route 53) has a clear 'Add CNAME' button. The file-sharing tool handles everything else (SSL certificate provisioning, traffic routing). Most setups take under 10 minutes total.

Jumpshare Plus at $8.25/mo is the cheapest, though it's optimized for screen-capture workflows. BulkShare Pro at $29/mo is the cheapest tool purpose-built for branded client delivery. Most other accessible options start at $50+/user/mo (Files.com) or require Enterprise contracts ($200+/mo with annual commits).

No. Modern tools auto-provision an SSL certificate via Let's Encrypt as part of the CNAME setup — no extra cost, no manual configuration. The certificate auto-renews every 90 days. Only legacy enterprise platforms still require you to bring your own SSL certificate.

Technically yes, but practically no. CNAME records have conflicts with root domains (they break MX records for email). The standard pattern is a dedicated subdomain like 'files.youragency.com' or 'downloads.youragency.com'. This is what every vendor supports and what we recommend.

Custom branding adds your logo or background image to the vendor's page (WeTransfer Ultimate does this). The URL still reads wetransfer.com. Custom domain replaces the URL itself — recipients land on files.youragency.com with your brand throughout. Only custom domain delivers a fully on-brand experience.

Often yes, especially to enterprise inboxes with strict filtering. Emails containing links to your own domain (with its own sending reputation) typically clear filters more cleanly than emails containing vendor domains. Pair custom-domain delivery with SPF, DKIM, and DMARC records for maximum effect.

Yes. Most tools tie the custom domain to your workspace, so every team member's deliveries automatically use the same shared domain. BulkShare Pro (up to 5 seats included, no per-seat upcharge) is built specifically for this — one custom domain, multiple team members, no per-user setup.

Existing vendor-URL links (e.g., already-sent wetransfer.com or bulkshare.cloud links) keep working. New links generated after you set up the custom domain automatically use the branded URL. There's no retroactive migration — old links stay valid, new ones brand on.

Most tools support one custom domain per workspace. If you run multiple brands (agency + side studio), you typically need separate workspace accounts — one per brand. Enterprise tiers sometimes support multi-domain workspaces.

No. The CNAME just changes the URL — files are still served from the vendor's CDN at the same speed. Recipients don't notice any difference except the URL on the link. From a performance standpoint, custom-domain delivery is identical to standard vendor delivery.

Every modern DNS provider supports CNAME records — they may just call it something slightly different. Look for 'DNS Records', 'Zone Editor', or 'Add Record'. If you're stuck, your file-sharing tool's docs usually have provider-specific instructions for Cloudflare, Namecheap, GoDaddy, Vercel, etc.

Update the CNAME target at your DNS provider to point to the new tool's infrastructure. Removal from the old tool, addition to the new tool, then update the DNS record. The whole migration takes under 10 minutes plus DNS propagation time. Existing links from the old tool will stop working once you change the CNAME — plan the cutover for a low-traffic moment.