Receive big files on your Mac with an expiring link
Receive files from a person without a Tailscale account: copyparty's resumable upload page behind a TSLink guest link that expires. Measured speed, limits and cleanup.
Last updated on
Someone needs to send you files: camera footage, a client's raw assets, a batch of photos. They should need only a browser, the files should land on your own disk, and the link should stop working on a date you choose. TSLink has no upload page of its own. This guide pairs it with copyparty (MIT), a file server whose browser uploader splits files into chunks and resumes after interruptions. TSLink adds the public, expiring, revocable guest link.
Measured on 2026-11-11 with a TSLink build from main shortly after v0.3.1 and copyparty 1.20.26, uploading from a second machine through the public Funnel edge. Read Speed before you promise anyone a 40 GB transfer.
Set it up
You need TSLink v0.4.0 or later and a running, enrolled TSLink node with Tailscale HTTPS and Funnel permission. Then:
pipx install copyparty # or: python3 -m pip install --user copyparty
mkdir -p ~/inbox
copyparty -i 127.0.0.1 -p 3923 -v ~/inbox:/:w -nih -nid --name inbox --bname inboxLeave it running in its own terminal. In another:
tslink add inbox --proxy localhost:3923 --max-request-body 128MiB
tslink guest create inbox --for 3d --label "camera footage" --public --print-linkSend the printed message. The recipient opens the link, drops files on the page and confirms.
What each choice does:
| Setting | Why |
|---|---|
-i 127.0.0.1 | copyparty listens on loopback only; the guest link is the only way in |
-v ~/inbox:/:w | write-only volume: visitors can upload but cannot list or download anything, including each other's files |
-nih -nid | single dash. By default copyparty shows every visitor your machine's hostname and free disk space |
--max-request-body 128MiB | copyparty's browser uploader sends each chunk as its own request, aiming for 64 MiB and never above 96 MiB. TSLink's default 32 MiB cap rejects those chunks with 413. 128 MiB covers them; you do not need a multi-GiB cap |
Set the request limit before sending the link where you can. To change it later, run tslink limits set inbox --max-request-body <value>: it changes only the limits and restarts the app's node, so uploads in flight are cut and the recipient must reopen the link. tslink add on an app with guest links is refused.
On a new installation the first guest link also takes the app off the portal gateway and says so (removed_gateway_route). If guest create refuses with portal_route_guest_refused, someone else depends on that route, for example a person you granted the app to; the message names the next command. If it reports url_not_ready, nothing was saved: run tslink url inbox --wait=30s and the same command again. The first public request after creating a link can fail for about 30 seconds while Funnel comes up.
What the recipient sees
A copyparty upload page with a progress bar. Closing the tab, losing Wi-Fi or a restart on your side does not lose progress: they reopen the same link, pick the same file, and copyparty skips the chunks it already stored. We tested three interruptions: browser killed, copyparty restarted, and a 60-second network block on the uploader's side. Each upload continued from where it stopped; the block needed no action at all. A 300 MB file arrived with a matching SHA-256.
Speed
Funnel relays public traffic through Tailscale's servers, and Tailscale's Funnel documentation states that it is subject to non-configurable bandwidth limits. Measured upload speed into the receiving Mac:
| Path | Speed |
|---|---|
| Public guest link (Funnel), browser upload, sustained | 0.8 to 1.1 MB/s |
Same, single curl upload | 0.65 to 0.84 MB/s |
| Same node and app over the tailnet | 35 MB/s |
The uploader had a 1.5 Gbit/s uplink, so the relay is the bottleneck, not TSLink or the connection. At about 1 MB/s, 1 GB takes 15 to 20 minutes and 40 GB takes more than 11 hours. For a few GB a guest link is fine. For tens of GB, prefer giving the person tailnet access to the same app: they install Tailscale once and get tailnet speed.
Revoke and clean up
tslink guest list
tslink guest revoke <grant-id>
tslink remove inboxAfter revocation, both the link and existing browser sessions get a generic 401, and an upload in progress stops. tslink remove revokes every link the app still has. When the last link expires, TSLink also closes the public Funnel edge: in our test a running upload stopped within a second of the deadline and later requests could not connect at all. Stop copyparty yourself. Interrupted uploads stay as *.PARTIAL files in ~/inbox; delete the ones you do not want.
Known limits
- In v0.3.1 and earlier,
guest createdid not remove the gateway route (runtslink portal route remove inboxfirst), request limits could not be changed on an app with guest links, and a secondguest create --print-linkfor the same app failed withurl_not_readywhile its guest gate was active. - A guest link is a bearer link. Anyone holding it can upload until it expires. Add
--pinand send the PIN separately if that matters. - copyparty enforces no quota in this setup. Watch your free disk space or read copyparty's volume options for size limits.
Sources: copyparty README and Tailscale Funnel, accessed 2026-11-11.