Let someone upload big files to my Mac
Run an upload app such as copyparty on localhost, raise TSLink's 32 MiB request limit, and send a guest link that expires. Fine for photos and documents; Funnel is too slow for tens of gigabytes.
Last updated on
TSLink does not provide an upload page, so run an upload-capable web app on your Mac, such as copyparty, listening only on localhost, and put a TSLink guest link in front of it. The uploader opens the link in a browser with no account until the deadline you set or until you revoke it. Set TSLink's request limit above the app's largest request, or bigger requests fail with HTTP 413. With the upload app already listening on 127.0.0.1:3923:
tslink add uploads --proxy localhost:3923 --max-request-body 128MiB --request-read-timeout 2m
tslink guest create uploads --for 3d --label "Footage from Sam" --public --print-linkThis needs TSLink v0.4.0 or later; on a new installation the first guest link also takes the app off the home gateway. Files land wherever the upload app writes them on your disk. TSLink is an independent project, not made by Tailscale.
Big means gigabytes, not tens of gigabytes. Guest links go through Tailscale Funnel, which Tailscale says has non-configurable bandwidth limits. In upload tests through Funnel on 2026-11-11 we measured 0.65 to 0.84 MB/s for a single curl upload and 0.8 to 1.5 MB/s sustained for a browser upload, against about 35 MB/s over the tailnet on the same path; at about 1 MB/s, 1 GB takes 15 to 20 minutes, 10 GB about 3 hours and 40 GB more than 11 hours. That is one day of measurements, not a guarantee. For very large transfers, use a transfer service or a private path: the sender installs Tailscale and you give them access as a named person to a second, private app for the same upload server:
tslink add uploads-private --proxy localhost:3923 --max-request-body 128MiB --request-read-timeout 2m
tslink people add sam@example.com --apps uploads-private --for 3d --print-linksWhile its guest gate is up, an app cannot take new people grants (people_service_unsupported), hence the separate name. people add checks the login against your tailnet's user directory and, for someone outside your tailnet, creates a device invitation; both need a stored user-owned Tailscale API token (tslink login), otherwise setup reports incomplete. The sender installs Tailscale, signs in and accepts the invitation you send them.
Set the request limits
Every TSLink HTTP app without its own settings keeps a 32 MiB cap on a single request body, a 30-second read inactivity window and a 10-second header timeout. An oversized request gets HTTP 413 and a stalled upload gets HTTP 408. The cap applies to each request, not to the whole transfer:
- Chunked uploaders send one request per chunk. copyparty's default chunk size is 64 MiB with a 96 MiB maximum, and its u2sz notes say to raise a proxy's request limit to at least 96 MiB or lower the chunk size with
--u2sz(it calls 32 still acceptable).128MiBis a reasonable ceiling for default chunking; it caps what any one guest request may send. In the test above, with TSLink's default 32 MiB, every chunk got 413: the page kept showing a transfer rate while nothing was stored. Raise the cap or set--u2szbelow it. - A plain HTML form sends the whole file in one request, so the cap must exceed the largest file plus its form metadata.
--request-read-timeout 2mtolerates a phone that pauses longer than 30 seconds. It measures time without progress, not total upload time.- Removing the cap takes both
--max-request-body unlimited --ack-unlimited-request-body.
Choose these with tslink add where you can. To change a limit after the link exists, use tslink limits set, which changes only the limits and keeps the target, access, routes, health check, --preserve-host, guest gate and enrolled node:
tslink limits set uploads --max-request-body 256MiB
tslink url uploads --waitIt restarts the app's node: uploads in flight are cut and the uploader must reopen the link (and enter its PIN again). The command returns before the restart; wait for tslink url before telling them to retry. tslink add on an app with guest links is refused. guest create prints the app's current cap, and an upload over the cap gets a JSON 413 naming the limit, and tslink status and tslink doctor count those refusals with the command that raises it. More in health and request limits.
Choose and set up the upload app
TSLink forwards requests; the upload app receives the files, decides where they go and handles interrupted transfers. copyparty is one option: a single program whose browser uploader splits files into checksummed chunks and resumes after network interruptions, according to its uploading documentation.
The copyparty configuration we tested, with measurements, is in receive large files. In short, configure the app with these properties:
- Listen on localhost only. copyparty's
-ioption sets the listen address and defaults to all IPv4 and IPv6 interfaces (--helpsource);127.0.0.1keeps other devices on your network from bypassing TSLink. - Upload without browsing. copyparty's
wpermission lets a visitor upload into a folder without seeing its contents (accounts and volumes). - Hide machine details.
-nihremoves the host name from the interface and-nidhides disk usage, the same as--du-who no(single dash;--helpsource).
copyparty rejects uploads whose Origin header does not match the server's domain unless they carry a password header (cors), and TSLink normally forwards the backend's own Host. In our test with copyparty 1.20.26 and a TSLink build from main shortly after v0.3.1, browser uploads through a guest link worked without --preserve-host: TSLink sets X-Forwarded-Host to the public name, and copyparty's log shows it reads the host from that header. The occasional HTTP 400 in the test was copyparty answering a resent chunk it already had (its log says already got that); it does not affect the upload. If uploads are rejected, add --preserve-host to tslink add, which forwards the app node's own external name as Host. Unlike the limits, it cannot be changed once the app has guest links: tslink remove uploads (which revokes its links), add it again with the flag and create a new link.
Before you start
- TSLink installed (installation) and a Tailscale account with MagicDNS and HTTPS turned on.
- Funnel permission. Tailscale Funnel needs a
funnelnode attribute in your tailnet policy file. TSLink provisions it by default for an explicitly public service when it has usable API access and policy permissions; otherwise add it yourself. - The first run enrolls the node.
tslink addmay returnneeds_loginwith anauth_url; open it once beforeguest create, which otherwise stops withenrollment_required.guest createwaits up to 8 seconds for the app's address; if it still reportsurl_not_ready, nothing was saved, so runtslink url uploads --wait=30sand the same command again. - A PIN is set at creation. For a single uploader a PIN is reasonable: add
--pintoguest create, type a 6 to 64 digit PIN at the hidden prompt and send it separately. Adding one later means creating a new link, which works while the first is still active. - Check before sending.
guest createsaves configuration; runtslink statusandtslink doctorto confirm Funnel is active. A new public name can take up to 10 minutes to appear in public DNS. Test from a device outside your tailnet, such as a phone on mobile data with Tailscale switched off; inside the tailnet a guest link only redirects to/without a guest session. - Free disk space and a Mac that stays awake for the whole upload window.
Watch, revoke and clean up
tslink guest list
tslink access log --app uploads --since 24h
tslink guest revoke <id>
tslink remove uploadsRevoking is permanent for that link ID and cancels uploads in progress. tslink remove revokes every link the app still has, so an app added later under the same name cannot bring them back. The default guest lifetime ceiling is 7d; never is refused.
New links on older versions
In v0.3.1 and earlier, guest create did not remove the gateway route (run tslink portal route remove <app> first), request limits could not be changed on an app with guest links, and a second guest create --print-link for the same app failed with url_not_ready while its guest gate was active. Upgrade instead of starting the app over. On any version, do not retry a failed guest create without --print-link: it succeeds but saves a link nobody can retrieve, so revoke any such grant.
Limits to know
- TSLink does not resume uploads. If a connection drops, resuming is the upload app's job; copyparty's uploader does it, a plain HTML form does not. Revocation and the deadline also cut uploads in progress, and the app must cope with partial files.
- The link is public and forwardable. Anyone holding it, plus the PIN if set, can upload until the deadline, which is why the folder should be write-only. A label does not identify the uploader.
- Guest links work only for HTTP proxy apps. Folders registered with
tslink add --dirstay private, so TSLink cannot receive files without an app behind it. - Funnel throughput is limited, as described at the top of this page.
When something else is the better choice
| Option | Choose it when | What you give up |
|---|---|---|
| copyparty on its own | You are happy with copyparty's own accounts and its own share links (--shr), which can have a password, an expiry and allow uploads, plus a per-volume upload lifetime; cleaning up expired shares needs e2d. | You still need your own way to make it reachable from the internet. TSLink adds a ts.net address through Funnel with no router port, and a deadline and revocation enforced in front of the app that also cut requests in progress. |
| Tailscale Serve or a TSLink people grant on a separate, un-gated app | The uploader is on your own devices, already in your tailnet, or willing to install Tailscale (outsiders also need you to have a stored API token). Nothing becomes public and the tailnet path is much faster. | The uploader needs Tailscale. |
| Cloudflare Quick Tunnel | No Tailscale account; --allowed-mail limits access to email addresses verified in an interactive browser. | Testing and development only, up to 200 in-flight requests, access ends when cloudflared stops, new hostname each run. |
| A named Cloudflare Tunnel | You want a permanent public upload address. | You manage the account, domain and access policy; no built-in expiry. |
| Dropbox file requests or a transfer service | Uploader convenience or speed matters most, or your Mac cannot stay online. Dropbox uploaders need no Dropbox account. | Files go to the provider's storage. Dropbox Basic, Plus and Family accept files up to 2 GB; higher plans up to 250 GB and can set a deadline. |
Let your coding agent do it
Paste this into Claude Code, Codex or Cursor:
Let one outside person upload files (photos or documents, not tens of gigabytes) to this Mac for 3 days through a TSLink guest link. Follow these rules:
1. Use an existing upload app; do not write your own upload server. Prefer copyparty and configure it from its official README: listen on 127.0.0.1 only, port 3923, one folder ~/incoming that visitors can write to but not browse, -nih and -nid to hide the host name and disk usage. Keep it running in the background.
2. Check that tslink --version reports v0.4.0 or later. Register the app: tslink add uploads --proxy localhost:3923 --max-request-body 128MiB --request-read-timeout 2m. If the result says needs_login, show me the auth_url and wait. Do not remove the gateway route yourself; the first guest link does that.
3. Before creating anything, ask me whether I want a PIN; it can only be set now. Show me the guest command and wait for my yes before making anything public. If I want a PIN, ask me to run the command with --pin myself and type it at the hidden prompt; never put a PIN in a command argument. Otherwise run: tslink guest create uploads --for 3d --label "<uploader>" --public --print-link --json. Never use a lifetime above 7d and never use never.
4. Confirm with tslink status and tslink doctor that Funnel is active, then give me the link, the grant id, the expiry and the revoke command: tslink guest revoke <id>. Test an upload from outside the tailnet. If uploads are rejected, tell me; the fix is tslink remove uploads, then add again with --preserve-host and create a new link.
5. If an upload gets HTTP 413, raise the cap with tslink limits set uploads --max-request-body <size> and tell me the uploader must reopen the link. For a new link, run guest create again. If guest create fails with url_not_ready, run tslink url uploads --wait=30s and try once more; never retry without --print-link.
6. When I say we are done: tslink guest revoke <id> first, then stop the upload app and run tslink remove uploads. Do not delete anything in ~/incoming.Related pages
- Collect event photos from guests on my computer: the same setup for many uploaders.
- Send a Mac download link that expires in 3 days: the other direction.
- Guest links: the gate, PINs and revocation in detail.
- Health and request limits: upload limits and warnings.
Official Tailscale, Cloudflare, Dropbox and copyparty sources linked above: accessed 2026-11-11 (copyparty README and source pinned to commit 1af7efe). TSLink behavior checked against v0.4.0; the throughput and copyparty observations come from one test with copyparty 1.20.26 and a TSLink build from main shortly after v0.3.1. TSLink is an independent project by anydoor7, not made or endorsed by Tailscale.
Expiring download link
Serve the file from a localhost-only web server, then put a TSLink guest link with a 3-day deadline in front of it. The recipient needs only a browser, and you can revoke the link early.
Collect event photos
Wedding or party photos from 30 guests, no accounts: run an upload app with a write-only folder, put one TSLink guest link in front of it, and let it expire after the event.