Collect event photos from guests on my computer
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.
Last updated on
Run an upload app such as copyparty on your computer with a write-only folder, put one TSLink guest link in front of it, and share that link with your guests for a day or two. Guests upload from their phone's browser with no account and no app to install; the photos land on your own disk, and the link stops working at the deadline or when you revoke it. With the upload app listening on 127.0.0.1:3923:
tslink add photos --proxy localhost:3923 --max-request-body 128MiB --request-read-timeout 2m
tslink guest create photos --for 2d --label "Wedding guests" --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. Turn the printed link into a QR code with an offline generator such as qrencode rather than a website, because the link is the key. TSLink is an independent project, not made by Tailscale.
Set up the upload app
TSLink does not provide an upload page; it puts a time-limited gate in front of an app you run. copyparty fits because its browser uploader sends files in resumable chunks (uploading), which helps on patchy venue Wi-Fi and mobile data.
The copyparty configuration we tested, with measurements, is in receive large files. In short, configure it so that it:
- listens on
127.0.0.1only (copyparty's-i, which defaults to all interfaces;--helpsource); - gives visitors write-only access (copyparty's
wpermission) to one folder, so guests cannot browse or download each other's photos (accounts and volumes); - hides the host name and disk usage with
-nihand-nid(single dash;--helpsource).
TSLink caps each request at 32 MiB by default, below copyparty's default 96 MiB maximum chunk (u2sz). copyparty's README says to raise a proxy's limit to at least 96 MiB or lower its chunk size with --u2sz, so --max-request-body 128MiB is a reasonable ceiling for default chunking; it caps what any one guest request may send. In our test with the default cap every chunk got 413: the page kept showing a transfer rate while nothing was stored. --request-read-timeout 2m gives a phone that pauses more room than the default 30 seconds of read inactivity. 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; if uploads are rejected during your rehearsal, add --preserve-host to tslink add before creating the link (copyparty checks the Origin header, see its cors notes). Let someone upload big files explains the sizing.
Settle the limits before you print the cards. tslink limits set photos --max-request-body <size> can raise the cap later without replacing the link, but it restarts the app's node: uploads in flight are cut and guests have to open the link again. tslink add on an app with guest links is refused, so --preserve-host cannot be added later without removing the app, which revokes the link on your cards.
One shared link, no PIN, short lifetime
Plan on one link for all guests. Skip the PIN: TSLink allows five PIN checks per link in a 15-minute window, and successful checks count, plus ten per source address across links. Thirty guests entering a PIN on one link would lock it out, and guests on the same venue Wi-Fi may share one public address. The link itself carries a 256-bit token, so protect it the way you would protect the QR card: share it only with the guests and keep the lifetime short.
- Pick the window.
--for 2dcovers the day and the morning after; the minimum is 1h and the default maximum is 7d. - If the link leaks, create a new one with the same
guest createcommand, then revoke the old one withtslink guest revoke <id>; every guest then needs the new link. A second link works while the first is still active, so you can also give a late group its own link and revoke it separately. - Restarts are survivable. Links and deadlines persist, but guest sessions live in memory, so after a TSLink restart guests just open the link again.
Before the event
- TSLink installed (installation), a Tailscale account with MagicDNS and HTTPS turned on, and 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. - Enroll the node. The first
tslink addmay returnneeds_loginwith anauth_url; open it once beforeguest create. Ifguest createreportsurl_not_ready, nothing was saved: runtslink url photos --wait=30sand the same command again. - Set it up a day early. A new public name can take up to 10 minutes to appear in public DNS, and you want time to rehearse.
- Rehearse from a phone on mobile data with Tailscale switched off. A device inside your tailnet reaches the private listener, where a guest link only redirects to
/without a guest session, so it cannot test what guests see.tslink statusandtslink doctorconfirm Funnel is active;doctorwarns when it cannot verify it. - Keep the computer awake, online and with enough free disk for the whole window.
During and after
tslink guest list
tslink access log --app photos --since 24h
tslink guest revoke <id>
tslink remove photosguest list shows uses per link; access history records guest decisions by link ID, not by person, and is bounded. Revoking or reaching the deadline cancels uploads in progress, so revoke after the last guest has finished. tslink remove also revokes every link the app still has. Then stop the upload app. The photos stay in the upload folder.
On v0.3.1 and earlier
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 before the event. 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
- Anyone with the link can upload until it expires, including people it was forwarded to. Write-only access limits the damage to unwanted uploads; it does not stop them.
- TSLink does not resume uploads or manage files. Resuming, file names, duplicates and storage are the upload app's job.
- Your computer must stay online. If it sleeps, the link is unavailable until it wakes.
- Funnel is slow. Tailscale says traffic over Funnel is subject to 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
curlupload and 0.8 to 1.5 MB/s sustained for a browser upload, on one day; at about 1 MB/s one connection moves roughly 3.5 GB per hour. We did not measure many guests uploading at once. - Guest links work only for HTTP proxy apps, so the upload app is required.
When something else is the better choice
| Option | Choose it when | What you give up |
|---|---|---|
| Dropbox file requests | You want the simplest guest experience, or your computer cannot stay online. Guests need no Dropbox account. | Photos go to Dropbox storage. Basic, Plus and Family plans accept files up to 2 GB; deadlines need a higher plan. |
| copyparty on its own | You are happy with copyparty's own share links, which can have a password, an expiry and allow uploads, and you already have a way to publish it. | You publish it yourself. TSLink adds a ts.net address through Funnel with no router port, and a deadline and revocation in front of the app that also cut uploads in progress. |
| Tailscale Serve | Everyone uploading is already in your tailnet. | Guests would need Tailscale, which rules it out for most events. |
| Cloudflare Quick Tunnel | You do not want a Tailscale account. | Each visitor must verify an email in a browser with --allowed-mail, or the link is open; testing and development only; access ends when cloudflared stops. |
Let your coding agent do it
Paste this into Claude Code, Codex or Cursor:
Set up photo collection from about 30 wedding guests onto this computer for 2 days, through one TSLink guest link shared by all guests. Guests have no accounts. Follow these rules:
1. Use copyparty, configured from its official README; do not write your own upload server. Listen on 127.0.0.1 only, port 3923, one folder ~/wedding-photos 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 photos --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. Show me the guest command and wait for my yes before making anything public. Then run: tslink guest create photos --for 2d --label "Wedding guests" --public --print-link --json. No PIN, because many guests share one link. Never use a lifetime above 7d and never use never. If guest create fails with url_not_ready, run tslink url photos --wait=30s and try once more; never retry without --print-link.
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>. Make the QR code with an offline tool such as qrencode, never a website. Ask me to test an upload from a phone with Tailscale off. If an upload gets HTTP 413, raise the cap with tslink limits set photos --max-request-body <size>; if uploads are rejected otherwise, the fix is tslink remove photos, then add again with --preserve-host and create a new link.
5. After the event, when I say so: tslink guest revoke <id> first, then stop copyparty and run tslink remove photos. Never delete or move anything in ~/wedding-photos.Related pages
- Let someone upload big files to my Mac: request limits and the one-uploader version.
- Guest links: PIN limits, sessions and revocation in detail.
- Send a Mac download link that expires in 3 days: share the best photos back.
- Comparisons: TSLink next to other ways of publishing an app.
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.
Upload big files to a 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.
http.server link expiry
python3 -m http.server has no notion of time and a tunnel only carries traffic. What an expiring link needs you to write yourself, and what TSLink guest links and other tools already provide.