Branded File Delivery for Freelancers and Consultants
Add your logo and a one-line note to the receiver page so client deliveries do not look like a generic file-tunnel link. A small detail with disproportionate effect on perceived quality.
When you bill a client ₩2,000,000 for a deliverable, the moment they actually open the package matters. A bare WeTransfer link or a generic shared-folder URL feels like the file came from a commodity logistics service. A receive page with your logo and a single-line message — "Final deliverables for Acme Corp, please review by Friday" — feels like the file came from a professional who curated the moment.
File Tunnel's branded delivery is a 30-second setting on the send screen that turns the receiver page into your packaging.
What changes for the receiver
Without branding, the receiver page is a clean monochrome surface — the file name, size, and a download button. With branding enabled, the same page gets a header band that displays:
- Your logo (any image URL — your website's favicon or a hosted PNG works fine)
- A short note (up to 240 characters) that you write per transfer
The rest of the page is unchanged. The transfer is still peer-to-peer, still time-limited, still passwordable. The branding is purely visual — a frame around an unchanged painting.
Where the branded receiver page earns its keep
- Final deliverables to a paying client. Logo + "Final files for Acme Corp — review by Friday, reply with questions." Sets the tone for the close-out.
- Sales proposals or proposal decks. The first impression matters; a branded receive page reinforces that you treat the proposal as a finished artifact, not a draft thrown over a wall.
- Vendor invoices or contracts. "Invoice #2026-04 from Cheol Studio" on the receive page makes it obvious to the recipient's accounting team what they are opening.
- Press kits. Journalists who get the link know immediately whose press kit it is, before they even download.
- Workshop / course materials. Branded handoffs to participants reinforce the workshop identity.
What to put in the note
The note is short — 240 characters, about three lines. The templates that work in practice:
"Final deliverables for Acme Corp. Please review by Friday and reply with any revision notes. Invoice attached separately."
"Workshop slides + recording. Slides are PDF, recording is MP4 (~1.2 GB). Reach out at hello@cheol.studio if anything looks broken."
"Press kit v3 — updated headshots, logo files, fact sheet. Embargoed until 2026-06-01 09:00 KST."
Notice the structure: what it is, what action is expected, where to follow up if something is off. Three sentences max.
Logo image — what works, what doesn't
- Works: a hosted PNG, JPG, SVG, or WebP at any public URL. Your own website's favicon, a logo on your portfolio, an image on your CDN.
- Works: images with transparent backgrounds — they sit cleanly against the dark or light theme.
- Avoid: images requiring login (private Drive links, Dropbox previews). The receive page is public; if the image URL needs auth, the logo simply won't load.
- Avoid: very wide logos. The header caps display at ~160 px wide, ~48 px tall. Square or moderately wide rectangles look best.
How to enable per transfer
- Activate Pro Pass on the device you send from.
- On the Send tab, scroll the settings panel to Branded delivery. Toggle it on.
- Paste the logo URL and write your note. The character counter shows you the 240-char limit live.
- Send normally. The receiver sees the branded header above your file the moment they open the receive link.
Why we let you choose per transfer instead of setting it once
Different deliveries deserve different framing. The proposal you send to a brand-new lead wants a different note from a midnight deliverable to a long-term client. A per-transfer field is a small bit of friction (re-typing a similar note) but it's what keeps the channel from feeling automated. If you do find yourself reusing the same exact note often, paste it from a text snippet manager — it's 30 seconds either way.