⌨️ Enter Code
📷 Scan QR
—
OR
OR
Works across WiFi, 4G/5G, different countries. PeerJS relay handles NAT & firewalls automatically.
Once connected, data flows directly between devices — no server ever touches your files unless you request a share link.
Host shows QR, guest scans it — connection established automatically.
Convert received files into shareable public download links (via gofile.io).
Connecting to PeerJS server...
Room:
Works from any network
Hold & select all, then copy:
Free, private, peer-to-peer file sharing — no accounts, no servers, no limits.
Yunze Universal Transfer was built with a single goal: to make file sharing as simple and private as handing someone a USB drive — but from anywhere in the world. We believe that sharing files shouldn't require uploading your data to a corporation's servers, creating accounts, or worrying about file size caps.
Yunze was created and is maintained by the Yunze team as part of a growing suite of web-based productivity tools. Every product we build prioritizes simplicity, privacy, and accessibility.
Yunze uses WebRTC (Web Real-Time Communication) technology — the same technology that powers video calls in your browser — to establish a direct, encrypted connection between two devices. Once a connection is made, files travel directly between those two devices without ever passing through our servers.
The connection is brokered through PeerJS, an open-source signaling library. The signaling server only helps two devices find each other — it never sees your file data.
🔒 Your files are never stored on Yunze servers. We have no access to what you share. When the connection closes, everything is gone.
Most file sharing services work by uploading your file to a cloud server, storing it, and giving the recipient a download link. This means your file sits on someone else's computer — sometimes indefinitely. Yunze eliminates this entirely.
Yunze is an independent software team focused on building clean, fast web tools. Our products share a consistent design philosophy: minimal interfaces that get out of your way and let you focus on your work. Follow us on Instagram @yunze_official for updates.
If you encounter issues or have questions, visit our Help & FAQ section within the app. For business inquiries or partnership requests, reach out through our Instagram page.
Last updated: April 2026. This policy explains what data Yunze Universal Transfer collects and how it is used.
Yunze Universal Transfer ("Yunze", "we", "us") is committed to protecting your privacy. This application is designed from the ground up to minimize data collection. We do not require accounts, we do not store your files, and we do not track your transfers.
When you create a room, our app uses PeerJS signaling servers to help two devices discover and connect to each other. During this process, your IP address may briefly be visible to the PeerJS signaling server for the purpose of establishing the connection. Once connected, the data flows directly between devices.
PeerJS is an open-source project. You can review their privacy practices at peerjs.com.
PeerJS / PeerJS Cloud: Used for WebRTC signaling (helping devices find each other). No file data passes through this service.
Gofile.io: Used optionally when you choose "Upload & Get Link". When you use this feature, your file is uploaded to Gofile's servers. Their privacy policy applies. We recommend reviewing it at gofile.io.
Yunze Universal Transfer does not set any cookies.
Yunze Universal Transfer is not directed at children under the age of 13. We do not knowingly collect personal information from children.
We may update this Privacy Policy from time to time. Changes will be reflected on this page with an updated date. Continued use of the service constitutes acceptance of the updated policy.
For privacy-related questions, contact us through our Instagram page @yunze_official.
A complete guide to understanding peer-to-peer technology and how it enables private, fast file sharing.
In a traditional file sharing model, you upload your file to a central server — think Google Drive, Dropbox, or WeTransfer. The server stores your file, and the recipient downloads it from that server. This is simple and widely understood, but it comes with real trade-offs:
Peer-to-peer file transfer eliminates the central server from the data path. Instead, the two devices — the sender and the receiver — establish a direct connection with each other and exchange data without any intermediary holding the file.
Think of it like this: instead of mailing a letter through a post office that opens and reads it, you hand it directly to the person. The post office might have helped you find their address, but they never touched the envelope.
💡 Key principle: In P2P transfer, the server helps devices find each other, but it never touches the actual file data. Everything goes directly between the two devices.
WebRTC (Web Real-Time Communication) is an open standard built into every modern browser that enables real-time audio, video, and data communication without plugins. Originally designed for browser-based video calls (used by Google Meet, Discord, and others), WebRTC's data channels are equally powerful for file transfer.
WebRTC uses ICE (Interactive Connectivity Establishment) to figure out the best path between two devices. It tries direct connections first, and falls back to relay servers (called TURN servers) only when firewalls block direct connections. This is why Yunze can work across different networks — WiFi to 4G, home network to corporate network.
Before two devices can connect directly, they need to exchange some initial information — their network addresses, capabilities, and connection preferences. This exchange happens through a "signaling server." Yunze uses PeerJS's signaling infrastructure for this purpose.
Crucially, the signaling server only sees connection metadata, not your file data. Once the connection is established, the signaling server is no longer involved. Yunze uses the PeerJS signaling server to broker connections, and then all actual data travels directly between devices.
Most devices don't have a direct public IP address — they're behind a router using NAT (Network Address Translation). This can make direct device-to-device connections tricky. WebRTC handles this using a process called NAT traversal, which finds "holes" in firewalls that allow the two devices to communicate directly.
In cases where NAT traversal fails (very strict corporate firewalls, for example), WebRTC falls back to a TURN relay server. Even in this case, the connection remains encrypted end-to-end.
When you share a file through a cloud service, you're trusting that service with your data — their terms of service, their security practices, their compliance with government requests. With P2P transfer, there's nothing to subpoena: the file was never on a server.
WebRTC connections are encrypted using DTLS (Datagram Transport Layer Security), which is the same class of encryption used to secure HTTPS websites. This means your data is protected in transit even when routed through relay servers.
Use P2P (Yunze) when:
Use cloud storage when:
Peer-to-peer technology is becoming increasingly mainstream. As browsers become more capable and WebRTC matures, P2P applications are moving beyond file transfer into collaborative editing, decentralized social networks, and distributed computing. Yunze Universal Transfer is part of this shift toward a more private, user-controlled internet.
Best practices for keeping your files safe when sharing them across the internet — whether you use Yunze or any other service.
Every time you share a file digitally, you're making decisions that have security implications. Who can access the file in transit? Where is it stored? Who can see it? How long does it persist? Most people share files without thinking about these questions — and most file sharing services are designed to keep you from thinking about them.
This guide breaks down the key security concepts behind file transfer so you can make informed decisions about how you share sensitive information.
The most fundamental security requirement for any file transfer is encryption in transit — ensuring that if someone intercepts your data while it's traveling across the internet, they can't read it. There are two main approaches:
TLS/HTTPS encryption: Most cloud services (Dropbox, Google Drive, WeTransfer) use TLS to encrypt the connection between your device and their servers. This protects your file from network eavesdroppers, but the service provider still receives and can access your unencrypted file.
End-to-end encryption (E2EE): With E2EE, the file is encrypted on your device before it leaves, and only the intended recipient can decrypt it. Even the service provider cannot access the file. Yunze's WebRTC data channels use DTLS, which provides strong encryption that even the signaling server cannot read.
🛡️ Yunze uses WebRTC DTLS encryption — your files are encrypted between your device and the recipient's device. No intermediary can read them.
Encryption at rest refers to how files are stored. Cloud services that store your files should encrypt them on their servers — but "encrypted at rest" doesn't mean the service can't read them. It just means someone who steals their hard drives can't. The service provider still holds the encryption keys.
Yunze avoids this problem entirely: your files are never stored on our servers. There's nothing to encrypt at rest because there's nothing at rest.
1. Use end-to-end encrypted transfer methods
For truly sensitive files (legal documents, financial records, medical information), use services that offer genuine end-to-end encryption. P2P tools like Yunze are excellent for this because files never touch a server.
2. Encrypt the file itself before sharing
For an extra layer of protection, encrypt a file before sending it — even through an already-encrypted channel. Tools like 7-Zip allow you to create password-protected archives. Share the password through a different channel (phone call, in-person).
3. Verify the recipient
Before sharing sensitive files, confirm you're communicating with the right person. In Yunze, room codes are short-lived and session-based — they expire when the connection closes. Always share room codes through a trusted channel.
4. Use a secure network
Avoid sharing sensitive files over public WiFi networks without additional protection. While Yunze's WebRTC connections are encrypted, other traffic on your device may not be. Consider using a VPN on public networks.
5. Be careful with cloud-based fallbacks
When using Yunze's "Upload & Get Link" feature, your file is uploaded to a third-party service (gofile.io). This is convenient but doesn't have the same privacy guarantees as a direct P2P transfer. Use this feature only for non-sensitive files.
Security is always a trade-off. The right level of security depends on what you're protecting and who you're protecting it from. A casual user sharing vacation photos has very different needs than a journalist sharing sensitive sources.
For most everyday file transfers, a service like Yunze provides excellent security: direct P2P, encrypted connection, no server storage. For very high-risk scenarios, consider additional measures: file-level encryption, air-gapped devices, or specialized secure communication tools.
Yunze was built because we believe privacy-respecting file transfer should be accessible to everyone — not just people with technical expertise. By building on WebRTC and keeping the interface simple, we've made it possible for anyone to share files with strong security guarantees, no account required, and no file size limits. We believe the future of file sharing is direct, private, and user-controlled.