A Cross-Device Clipboard That Respects Permissions and Privacy
Design a clipboard handoff between computer and phone with browser permissions, receipts, separate queues, offline behavior, conflict handling, history cleanup, and safe analytics.
uCopy Technical Blog
Clear explanations for connections that work in real life
Practical uCopy guides to WebRTC, P2P file transfer, STUN and TURN, LAN discovery, resumable transfers, screen sharing, privacy, and security.
WebRTCP2P transferSTUN / TURNPrivacy & security
FIELD NOTES
Subscribe via RSSLatest articles
How Browser Device Discovery Works on a Local Network
See why a page cannot freely scan a LAN, how same-exit discovery differs from ICE, and what a complete flow needs from presence and consent through expiry, blocking, and reconnect.
P2P vs Cloud File Transfer: Choose by File Lifecycle, Not Hype
Choose browser P2P, a cloud link, or a hybrid by asking whether both sides are online, how long the file must remain, who needs access, how recovery works, and which copies are acceptable.
Can a Browser File Transfer Resume After a Page Refresh?
Learn what survives receiver or sender refresh and network loss, why the sender may need to reselect the source, and which manifests and terminal states make resume reliable.
Browser Screen Sharing: Fullscreen, Mobile Gestures, and Refresh
Build a usable WebRTC screen share from source selection and sender controls to fullscreen, landscape, pinch and pan, viewer refresh, reconnect, stop behavior, and privacy.
Is Browser File Sharing Safe? A 12-Point Practical Checklist
Review device approval, temporary codes, WebRTC encryption, TURN metadata, file digests, download risk, feature permissions, error reports, and analytics before trusting a browser transfer.
How to Send Large Files Between a Phone and Computer
Compare a cable, local sharing, cloud storage, and browser P2P for multi-gigabyte transfers, then check speed, mobile data, resume support, free space, and verification before you start.
STUN vs TURN: What Each Server Does in a WebRTC Connection
Use home routers, office firewalls, and mobile networks to understand STUN, TURN, ICE candidates, and direct paths, including the real effects on latency, relay cost, and privacy.
Why WebRTC File Transfer Is Slow: A Layer-by-Layer Checklist
Troubleshoot fast direct transfers but slow TURN, or healthy screen sharing beside a crawling DataChannel, by checking the route, backpressure, acknowledgement windows, storage, and CPU.
WebRTC NAT Traversal: Why Direct Works Here but TURN Is Needed There
Follow ICE gathering, checks, pair selection, and network change to see how home routers, strict NAT, firewalls, IPv6, VPNs, and guest Wi-Fi affect direct WebRTC.
WebRTC P2P File Transfer: Direct Paths, STUN, TURN, and Safety
Follow a browser file transfer from pairing to verification, including direct WebRTC paths, STUN discovery, TURN fallback, backpressure, resume behavior, and the security checks that matter.
No install. No account.
Start for freeConnect two devices now
Send files, sync a clipboard, chat, and share a screen securely from the browser.