Clipcroft

I like that a shared computer doesn't need any login, which makes this handy for library or office PCs. One thing I'd wonder about: when I close the tab on the receiving device, does the clipboard disappear right away or stay alive for some time? A small "clipboard expires in X minutes" indicator near the code would make it clearer for people moving sensitive files.

Building on mpopper's question about signalling: the case that decides the architecture for a lot of users is symmetric NAT and CGNAT, which is most mobile carriers. The direct path simply won't establish there, so either the transfer fails or it falls back to a relay - and at that point "never touches a server" stops being true for exactly the users who need it most. Worth saying which one happens instead of letting people discover it mid-transfer. Same for joining: if the clipboard name is short, joining wants either high entropy in the code or a rate limit, otherwise someone can sit in a session and read whatever gets pasted. A password doesn't help after the fact - whoever joined before it was set already saw the plaintext. The no-caps claim is the real differentiator, by the way. Most of these tools cap at 100-500 MB precisely because the relay bill arrives.

The use case that stands out to me is getting a file onto a computer that isn't yours without logging in to anything — that solves a real friction point. One suggestion: a QR-code join option for phones would make the two-step linking even smoother, since typing a clipboard name on a phone keyboard is the one slightly awkward part. Great call making the transfer peer-to-peer so nothing sits on a server.

The no-caps file size plus peer-to-peer transfer is a strong combo — most browser tools cap free transfers well below what you offer here. Two practical questions: how long does a clipboard stay alive if the receiving device opens it an hour later, and if a very large transfer drops mid-way, does it resume or restart from zero? That edge case is where browser-based transfer tools usually cost me the most time.

P2P with nothing stored on a server, across different networks, with no install - that combination is rare. Snapdrop-style tools usually require same Wi-Fi, so the relayless cross-network angle is the interesting bit. How do devices find each other across networks - is there a lightweight signaling step, and does the optional password gate that signaling too? Either way, this replaces my habit of emailing files to myself.

Peer-to-peer with no server storage is exactly what I want for moving client files from phone to laptop. Since nothing is stored, what happens if the receiving device goes to sleep halfway through a large file? Does the transfer resume, or does it restart once both devices are back online?

No size cap is the strongest part of this. A practical question on the receiving side: for a multi-gigabyte file, does the browser stream it straight to disk, or hold it in memory until the transfer finishes? That usually decides whether a 5 GB video works on a phone or an older laptop, and Safari handles it differently from Chrome. A short note on tested file sizes per browser would help set expectations.

Handy for moving a long link from phone to laptop. Since clipboard names are short, what stops someone from guessing one and joining?

Hey Fazier 👋 I'm Víctor, Clipcroft's developer. I needed a real-time way to link two devices, and I wasn't happy with anything that existed. Every tool I tried wanted something first: an app on both devices, an account, the same Wi-Fi. And almost all of them had caps. Online clipboards limited how much text I could paste, and file senders limited the file size or how much I could send in a day. I wanted to open a page on each device and have whatever I put in one show up on the other, whatever its size. So I built Clipcroft, a real-time online clipboard: 1. Open clipcroft.com and create a clipboard. You get a short name, like coolfox42. 2. Open clipcroft.com on the other device and enter that name. 3. Type, paste, or pick files. Text and links appear in real time, and files start transferring right away. That's it. Linking the two devices takes two steps and it's done in seconds. What you get: • No signup, nothing to install. It runs in any browser. • Any network. The devices don't need the same Wi-Fi or the same brand. • No limits. No file size limit, and no per-day or per-month caps. • Peer-to-peer. Files travel directly between your devices and are never uploaded to or stored on any server. • Always encrypted. Files use DTLS and text uses TLS, and an optional password adds end-to-end encryption on top. It's free and supported by advertising. Which two devices do you move things between the most, and how do you do it today? Try that pair and tell me whether your first send worked. I read and reply to every comment.

Browser-only transfer across iPhone and desktop is a practical use case. On mobile Safari, a transfer can be interrupted when the screen locks or the browser goes into the background. Does Clipcroft show an explicit paused or disconnected state to both devices? A clear warning before sending a large video would help users avoid mistaking an interrupted transfer for a completed one.

Sending files peer-to-peer so nothing is uploaded or stored on a server is a nice privacy angle, and needing no signup makes it quick for moving something onto a computer that isn't yours. How does it behave when the sending device closes its browser tab before the transfer finishes? A resume option or a clear warning would be reassuring for large files.

Love that files go peer-to-peer and aren't stored on a server. That's exactly what makes me comfortable sending stuff from a work laptop to my phone. Is there a size limit for files, and does the transfer still work if one device is on mobile data?

The peer-to-peer, no-upload approach is a strong privacy angle. When the two devices are on different networks and a direct connection fails, does Clipcroft fall back to a relay server, and if so does the "never stored on any server" claim still hold for those transfers?

The two-step linking is the part I like most — most tools in this space still make you create an account just to move one file. A couple of questions on how the shared clipboard itself works: how does the second device find the clipboard (a short code, a link, a QR scan?), and how long does a clipboard stay alive if both devices disconnect — since transfers are peer-to-peer and nothing is stored on a server, does the clipboard simply disappear? Also, when several devices join the same clipboard, does everyone see text updates in real time, or only the device that created it?

The two-step linking with no account is exactly the right design for this — nobody wants to sign up just to send a link from phone to laptop. The P2P, never-uploaded approach is a genuinely strong privacy story too, especially compared to cloud-based transfer tools. Question: how does pairing work when the devices are on different networks — a short code or QR? And do clips expire automatically after some time? An auto-expire option would be a natural fit for the privacy angle. Congrats on the launch!

The peer-to-peer detail is the part that matters to me: files never sit on a server, and the optional password adds end-to-end encryption, which is a clearer privacy story than tools that just promise to delete uploads later. I'm curious how pairing holds up when a phone is on cellular and the desktop is behind a strict office NAT. Does the clipboard still connect, or do you fall back to a relay?

The use case that stands out to me is getting a file onto a computer that isn't yours without logging into anything — that's exactly where cloud drives force an account sign-in you'd rather avoid, and the two-step clipboard linking sidesteps it completely. One question on the multi-device side: if several devices join the same clipboard and two people paste different text at nearly the same time, how does it resolve — last write wins, or is there a short history to recover the overwritten text?

Peer-to-peer with no server storage is a nice promise. What happens when two devices can't connect directly, for example behind a strict corporate NAT or on mobile data? Do transfers fall back to a relay server, and if so, does the relay only see encrypted data?

The two-step pairing with a short clipboard name is a nice touch, especially for getting a file onto a computer that isn't yours. Since transfers are peer-to-peer, what happens if one device sleeps partway through a large file: does it resume where it left off or start over?

Peer-to-peer clipboard sync is something I'd use daily when moving test strings between my laptop and an Android device. Do you have any plan for a "sensitive mode", where copied items that look like passwords or OTPs are excluded or auto-cleared? That would make me much more comfortable leaving it running all day. Nice work!

Tested it between two tabs. Joining by name alone worked, and the first device got an "A device joined this clipboard" notice, which partly answers the guessable-name worry above. One bug: I sent a link followed by a few words, and the whole line became a single link with the spaces encoded into the URL, so clicking it opens a broken address. Splitting the URL from the trailing text would fix it, since "link plus a note" is probably the most common thing people paste.