Open the page
Open the same address on both devices. Nothing to install or sign into.
Open a tab. Close the distance.
No app. No account. From iPhone to Windows, from Android to Mac.
Sending a presentation to the next laptop should not mean uploading to a drive, creating an account, and managing permissions. StarShare lets different operating systems exchange files, text, and links directly through the browser.
Take a quick practice run.
Interactive demo. None of your files are sent.
Open the same address on both devices. Nothing to install or sign into.
Nearby devices on the same network appear in the list. Otherwise, pair with a four-character room code, QR code, or invitation link.
Select the sample file
Tap the other device to choose a file, or drag a file onto it. Here, we only use a small preset sample text.
A real transfer starts when the receiver accepts. Every block is checked with SHA-256; the sender shows delivered only after verification.
Pass a file to one person. Leave something for the whole room.
Pick a device and send a file. Direct connections have no product-imposed file limit; practical capacity depends on the browser, storage, and network.
Devices on the same network can discover each other. If yours do not, share a four-character code, an invitation link, or scan a QR code.
Offer a file for 30 minutes. People in the room can download it themselves, up to four at once. Optional burn after one download; 500 MB per file.
No need to save it as a file first. Send a note or a URL straight to another device.
The receiver checks each SHA-256 block. Only after all bytes arrive and match does it confirm delivery to the sender.
Reconnecting within 30 seconds can preserve your identity and room. File resume needs OPFS support and usable local temporary data. Keep both tabs open during transfer.
On a direct connection, file content travels between browsers over WebRTC. When a relay is needed, the server forwards encrypted data without storing file content.
To coordinate a transfer, the signaling server handles the file name, size, type, and pairing information. This service does not promise that file names are invisible to the server.
The group cloud lets people in your room download from your device. It is not a cloud backup: closing the sender’s tab ends sharing. Recipients may keep downloaded files or local temporary data. Group-cloud image previews remain in signaling-server memory while shared.
Connection and security logs may include IP addresses, with retention depending on service settings. Read the full privacy policy and support information (Traditional Chinese) for data use, local storage, and deletion choices.
Large-file receiving and resume depend on the browser’s OPFS local storage and available space. If OPFS is unavailable or cannot be created, receiving falls back to memory; a large file may exhaust the tab’s memory and resume is not guaranteed. Switching apps or the system reclaiming a tab can still interrupt a transfer.
StarShare fits temporary, cross-platform sharing while both sides are online. For long-term backups or collecting files later, a cloud drive may be a better fit.
| Method | Best suited to | What you need |
|---|---|---|
| StarShare | Live, cross-platform sharing | Both devices keep a WebRTC-capable browser open |
| Built-in sharing | Devices with compatible systems | A supported AirDrop / Quick Share system and version |
| Cloud drive | Long-term storage, later pickup | Usually an account, storage, and sharing permissions |
| Messaging | Notes and small files in a conversation | A shared service; size limits and compression vary |
About sharing. And about your files.
Complete files are not stored on a server. Direct connections transfer between browsers; relays forward encrypted data. Signaling handles the file name, size, type, and pairing information. Group-cloud image previews remain in server memory while shared. Necessary connection and security logs are also retained.
Direct connections have no product-imposed limit, but capacity depends on the browser, local storage, and network. Relays and the group cloud allow 500 MB per file. Large-file receiving depends on OPFS; without it, the memory fallback can exhaust the tab’s memory.
If the receiver supports OPFS and its complete temporary blocks are still available, resending can continue from that data. Without OPFS, or if temporary data is cleared or a tab is reclaimed, you may need to start again.
Use a four-character room code, QR code, or invitation link. IPv4 and IPv6 devices may appear in different discovery lists. If different networks cannot connect directly, a relay is required; this site gates relay use with a passphrase.
Yes. Open StarShare on both devices, use the device list or room code to pair, and choose a file. The receiver accepts to begin. No Apple ID or extra app is needed.
No. StarShare works in your browser, with no registration or sign-in step.
The receiver calculates SHA-256 for every 4 MiB block. It sends confirmation only after all bytes arrive and the hashes match. Only then does the sender show delivered.
It lets people in your room download a file from your device for up to 30 minutes, with a 500 MB per-file limit and up to four simultaneous downloads. You can enable burn after one download. The sender must keep the tab open.
Reconnecting within the 30-second grace period can preserve your name and room. A phone may still suspend or reclaim the tab; the grace period does not guarantee that transfers keep running in the background.
Desktop Chrome, desktop Safari, Android Chrome, and iOS Safari are the primary targets. Other modern WebRTC-capable browsers may also work. OPFS support, available storage, and background behavior affect large files and resume.
Pick up a second device, open StarShare on both, and try a small file.
Open StarShare