spacedrop.app

Peer-to-peer (P2P) browser file sharing sends a file or clipboard text directly from one device to another over an encrypted WebRTC connection, so the file is never stored on a server. It works when both devices have the sharing page open in a modern browser and can reach each other over the network. SpaceDrop, a browser-based P2P file and text exchange app, describes exactly this model: transfer files or clipboard text between devices "without installing any app or uploading any server."

Server-Upload Sharing vs. Direct Peer-to-Peer

The two models differ in where your file physically goes.

With a server-upload service, the file sits on someone else's disk until it is downloaded or expires. With P2P, the server's role is reduced to helping the two browsers find each other; the content itself moves between the devices.

How WebRTC Enables Browser-to-Browser Connections

WebRTC (Web Real-Time Communication) is the browser standard that lets two browsers open a direct data channel. The general flow:

1. Signaling. The two browsers exchange connection details (session descriptions and network candidates) through a lightweight signaling service. This is metadata, not your file.
2. NAT traversal. Most devices sit behind routers, so WebRTC uses ICE with STUN (and, when needed, TURN relay) to find a workable path between them.
3. Data channel. Once connected, the browsers open a secure channel, and the file or text is sent over it, typically encrypted in transit.

The signaling step is why both devices need the page open at the same time: the connection is live, not a stored link.

Sending a File or Clipboard Text Between Two Devices

The exact buttons depend on the app, but the underlying steps are consistent:

1. Open the sharing page (for example, SpaceDrop) on both devices in a modern browser.
2. On one device, start a transfer or share session and pair the two devices using whatever code, link, or prompt the app provides.
3. Wait for the peer connection to establish. If it stalls, the devices may be on networks that block direct connections.
4. Send the file or paste clipboard text into the transfer area.
5. Confirm on the receiving device that the transfer completed before closing either tab.

Verification: the transfer is complete when the receiving device shows the full file or text and the sending side reports success. For large files, check the file size on both ends.

Common snags:

• One device closed the tab or lost its connection mid-transfer.
• A restrictive corporate or public network blocks the peer connection.
• The browser is outdated or lacks WebRTC support.
• Very large files take time and depend on both devices staying awake and online.

Practical Limits and Privacy Benefits

Limits to plan around:

• Both devices must have the page open and an active connection at the same time.
• Transfer speed depends on both devices' networks, not a data-center link.
• Some networks prevent direct connections, which can slow or block a transfer.

Privacy benefits:

• The file is not stored on a server, so there is no server copy to leak or linger.
• Only the paired peer receives the content.
• No app install means nothing persistent is added to either device.

SpaceDrop's own description frames the appeal this way: files and clipboard text move directly between devices without an app install or a server upload. If your priority is avoiding a stored copy and you can coordinate both devices at once, browser P2P is a good fit; if the recipient can't be online at the same time, a conventional upload-and-link service is the more practical choice.

WebRTC (Web Real-Time Communication) is a browser technology that lets two devices send audio, video, and screen content directly to each other without plugins, downloads, or accounts. It's what makes a site like Share Your Screen Instantly work: you create a room, share a short code, and the other person sees your screen in seconds. The main conditions are a WebRTC-capable browser on both ends and, for the person sharing, a desktop device — the site notes that screen sharing isn't supported on mobile, though mobile users can still join a room to view someone else's screen.

What WebRTC actually is

WebRTC is a set of APIs built into modern browsers. It handles three jobs that used to require separate software:

• Capturing media — grabbing a camera, microphone, or screen as a live stream.
• Transporting it — sending that stream over the network with low latency.
• Securing it — encrypting the connection by default.

Because these capabilities live in the browser, a web page can start a real-time session with a few lines of JavaScript instead of asking users to install an app.

Why there are no downloads or sign-ups

Traditional screen sharing tools often route everything through a vendor's server and tie sessions to an account. WebRTC changes both parts:

No plugin or app. The browser already contains the media and networking stack, so the page just calls it.

No account required. A session is identified by a room code, not a login. On Share Your Screen Instantly, you click "Create Room," get a code, and send it to whoever should watch. They enter the code under "Join a Room" and the stream starts. Identity is handled by the code itself, which is why the whole flow can stay anonymous.

How two browsers find each other: signaling and room codes

WebRTC's peer-to-peer connection can't start on its own — the two browsers need to exchange connection details first. That initial handshake is called signaling, and it's the one part WebRTC doesn't define for you.

A typical flow looks like this:

1. Create — the sharer's browser generates an offer describing its media and network info.
2. Exchange — that offer, and the viewer's answer, are passed between the two sides through a signaling channel (often a small server or a service like Firebase).
3. Connect — once both sides have each other's details, WebRTC opens a direct peer-to-peer link.
4. Stream — screen frames flow over that link, and the room code is simply the human-friendly label that ties the two sides to the same signaling session.

The room code matters because it replaces manual configuration. Instead of copying long connection strings, you share something short like ABC123, and the signaling layer matches the two participants.

What "peer-to-peer" means in practice

Once the connection is established, media travels directly between the two browsers rather than being relayed through the site's servers. That's the source of WebRTC's low latency — the stream doesn't take an extra round trip through a central machine.

In real networks, a direct path isn't always possible (firewalls, NAT, restrictive networks). In those cases WebRTC falls back to a TURN relay server, which forwards the traffic. The connection still works; it just isn't purely peer-to-peer anymore. This is a normal part of WebRTC, not a failure.

Browser and device support

The asymmetry is worth noting: mobile browsers can receive and display a shared screen, but capturing and sending one is generally not available, which is why the site tells mobile users they can join but not share. On desktop, the person sharing will see a browser prompt asking which screen, window, or tab to capture — that permission step is a browser security feature, not something the site controls.

Why this design enables instant sharing

Putting it together, WebRTC makes no-sign-up screen sharing possible because:

• The media stack is already in the browser, so nothing needs installing.
• Room codes replace accounts, so there's no registration step.
• Peer-to-peer transport keeps latency low, so the experience feels immediate.
• Encryption is built in, so the connection is secure without extra setup.

The trade-off is that the experience depends on both browsers supporting WebRTC and on the network allowing a connection — which is why a relay fallback exists. For the common case of two people on desktop browsers sharing a screen for a quick presentation or support call, that's more than enough to make it feel instant.

You can upload to Netu.tv three ways: directly from your desktop, by pasting remote URLs (up to 50 at a time), or over FTP. You don't need an account to start an upload, but you do need to register or log in to manage your videos afterward. Before you begin, check the limits: each video can be no more than 8096 MB and no longer than 500 minutes, and the service recommends mp4 with H.264 (720p, 1500 kb/s) and AAC audio (44100 Hz / 128 kbps).

Before you upload: limits and recommended format

If your file is larger or longer than these limits, re-encode or split it before uploading — the upload will not accept it as-is. Matching the recommended encoding also reduces the chance of playback problems later.

Method 1: Desktop upload

1. Open the upload page. You can do this while logged out — the page shows "Select videos (you are not logged in)."
2. Select your video file(s). The page supports uploading multiple files at once.
3. Click Start upload. You can cancel with Cancel upload or clear the queue with Delete.
4. To manage the videos afterward (rename, organize, track status), register or log in.

Expected result: the file enters the upload queue and, once finished, becomes available to share. If you stay logged out, you can still upload and share, but you lose the management tools.

Method 2: Remote URL upload (beta)

This method pulls a video from a link you already host elsewhere, instead of pushing it from your machine.

1. Paste your URLs into the URL field. You can add up to 50 URLs.
2. To set a title, append ###title to the end of the link — for example, https://example.com/video.mp4###My Title.
3. Click Add to upload queue.
4. Watch the queue table, which tracks File name, URL, Created, Status, File-Code, and Adult?. Use Update list to refresh and Delete Selected From Queue to remove entries.

Expected result: each URL appears as a row with a status you can monitor. This is labeled beta, so expect occasional hiccups on large batches.

Method 3: FTP upload

FTP upload is listed alongside the other two methods on the upload page. It's the practical choice when you're moving many or very large files and don't want to keep a browser tab open. The page confirms FTP is supported but doesn't publish the server credentials here — get those from your account area after logging in.

Common failures and how to fix them

Old videos stop loading after you switch your site to HTTPS. Some older videos may still be requested over HTTP. The page's fix is to add the appropriate reference so those HTTP links resolve — if you don't have HTTP links, you can close that notice.

Videos deleted by robots. If automated crawlers are removing your videos, load the iframe src only after a captcha challenge. You can also put a captcha in front of videos or enable Cloudflare's "I'm under attack!" option to block bot access.

Domain or subdomain blocked on some ISPs. Rotate your domain/subdomain over time, using 301 redirects, so a blocked domain doesn't take your whole library down.

Popunder firing on blank areas. If you use popunder ads, they should fire only when a user clicks an element, not on the blank body — the page links a script for this.

After upload: sharing and webmaster tips

Once a video is processed, share it with friends using its link, or embed the player on your site. If you're monetizing, the page's webmaster tips are worth applying:

• Place the Netu.tv player above other players to get more money.
• Write unique descriptions for each video — the page notes this drives search-engine traffic.
• Use PageSpeed Insights to check load speed, since faster sites get more traffic from Google.

Quick method comparison

If you just want a shareable link fast, use desktop upload. If your files already live on a server, remote URL saves re-uploading. If you're moving a library, FTP is the least babysitting.

File transfer is the process of moving a file from one device to another. The method you choose determines how fast the file arrives, whether it passes through a third-party server, and what size limits apply. For quick sends between two devices you control, a browser-based peer-to-peer tool like SpaceDrop can move files or clipboard text directly over the network without installing an app or uploading to a server. For large archives, offline recipients, or auditable delivery, cloud links, email attachments, or local network transfer fit better.

The four common ways to send a file

The key distinction is whether the file is stored on a server. Cloud and email methods require a copy to live on someone else's infrastructure, at least temporarily. Direct P2P and local transfer aim to avoid that.

How browser-based peer-to-peer transfer works

WebRTC (Web Real-Time Communication) is the browser standard that makes direct P2P possible without plugins. The flow is roughly:

1. Signaling. The two browsers exchange connection details through a lightweight signaling service. This service coordinates the connection but does not carry the file itself.
2. Connection negotiation. The browsers attempt a direct connection. If both devices are behind restrictive NATs or firewalls, a relay (TURN) server may be needed to bridge them.
3. Data channel. Once connected, the file is sliced into chunks and sent over an encrypted data channel directly between the browsers.
4. Reassembly. The receiving browser reassembles the chunks and offers the file for download or saves it to the chosen location.

SpaceDrop describes itself as a peer-to-peer file and text exchange web app that lets you move files or clipboard text between devices "without installing any app or uploading any server." That matches the WebRTC model above: the coordination step exists, but the file payload is intended to travel device-to-device. Because it runs in the browser, it works across operating systems as long as both sides use a compatible browser.

The practical benefit is speed and privacy: no upload wait, and no stored copy on a server. The practical cost is that both devices must be online and connected at the same time, and the connection can fail on locked-down networks.

Step-by-step: sending a file with a web-based P2P tool

1. Open the tool on both devices. Load the site in a modern browser (Chrome, Edge, Firefox, or Safari) on the sending and receiving device.
2. Establish the pairing. Follow the tool's pairing step — typically one device displays a code, link, or room, and the other joins it. This is the signaling step.
3. Grant permissions if prompted. Some tools ask for clipboard access (to send text) or notification permission. Deny anything you don't need.
4. Select and send. Choose the file or paste the text on the sender, confirm the transfer, and watch for a progress indicator.
5. Verify on the receiving side. Confirm the file name and size match, then save it. For text, confirm the pasted content is complete.

Expected result: the file appears on the second device without a full upload cycle. If the progress bar stalls at "connecting," the browsers have not established a direct path — see the failure points below.

Common failure points and quick checks

• Stuck at "connecting." The network is blocking the direct path. Try a different network (for example, switch one device from corporate Wi-Fi to a phone hotspot), or check whether the tool supports a relay fallback.
• Clipboard text won't paste. Browsers restrict clipboard reads to secure (HTTPS) pages and often require a user gesture. Click into the page first, then paste manually.
• Transfer dies midway. Large files over an unstable connection are vulnerable to drops. Keep both tabs in the foreground, disable sleep on both devices, and retry on a steadier network.
• One device can't open the page. Check browser version and whether the network blocks the site. Older browsers may lack the WebRTC data-channel support the tool relies on.
• File arrives corrupted or truncated. Compare file size on both ends. A mismatch usually means the connection dropped before the final chunk was acknowledged — resend.

Choosing a method

Use browser P2P when both people are online at the same time, the file is sensitive enough that you'd rather not store it on a server, and you want to skip app installs. Use a cloud link when the recipient may download later or the file is very large and you want resumable delivery. Use email only for small documents where convenience outweighs size limits. Use local network transfer when both devices are on the same Wi-Fi and you want the fastest path with no internet dependency.

Peer-to-peer (P2P) transfer sends a file or piece of text straight from one device to another through the browser, so the data is not uploaded to and stored on a server in between. On SpaceDrop, a web app for peer-to-peer file and text exchange, you open the site on both devices, connect them, and send files or clipboard text directly. This works without installing an app, but both devices need a modern browser, an internet connection, and the page must stay open until the transfer finishes.

What peer-to-peer transfer means in practice

In a normal upload, your file goes from your device to a server, and the other person downloads it from that server. The file sits in the middle, and a copy may remain there.

In a P2P transfer, the two browsers connect to each other and data flows across that connection. SpaceDrop describes itself as a peer-to-peer file and text exchanging web application that transfers files or clipboard text directly between devices "without installing any app or uploading any server." The practical result: no middle copy is stored as part of the transfer, and the receiving device gets the data from the sending device.

The connection itself is typically established with WebRTC, the browser technology for real-time direct connections. You do not need to configure WebRTC yourself; the app handles the connection step.

Steps to connect two devices and start a transfer

The exact buttons and labels depend on the current SpaceDrop interface, so treat the steps below as the general flow rather than a fixed menu map.

1. Open SpaceDrop on both devices. Use a modern browser on each device (for example, a laptop and a phone). No app install is required.
2. Start a session on one device. One device acts as the sender or session starter. The app presents a way to pair the two devices — typically a code, link, or room identifier.
3. Join from the second device. Enter or open the same pairing information on the other device so the two browsers can find each other.
4. Wait for the connection to establish. The app should show that the devices are connected. If it does not, see the troubleshooting section below.
5. Send the file or text. Choose a file to transfer, or paste clipboard text into the text field, then send.
6. Confirm receipt on the other device. The receiving device accepts or saves the file, or copies the text. Keep both pages open until the transfer reports completion.

Expected result: the file appears on the receiving device, or the text is available to copy there, without the file having been uploaded to a storage server as part of the transfer.

Sending clipboard text as well as files

SpaceDrop is built for both files and text. The text path is useful when you want to move a URL, a password reset code, a snippet of code, or a paragraph from one device to another without emailing it to yourself.

• Files: select the file on the sending device and send it through the connected session.
• Clipboard text: paste the text into the app's text area on the sending device and send it; then copy it on the receiving device.

Because the text travels over the same direct connection, the same conditions apply: both devices connected, both pages open, transfer completed before you close anything.

What both devices need for the transfer to succeed

A practical example: you have a 200 MB video on a laptop and want it on a phone on the same Wi-Fi. You open SpaceDrop on both, pair them, start the send, and leave both screens on until the phone shows the file as received. If you lock the phone or close the tab midway, the transfer can fail and you would need to start again.

Common failure points and how to troubleshoot them

• Devices never connect. Re-check that you entered the same pairing code or link on both devices, and reload both pages before trying again. A stale session on one side is a frequent cause.
• Connection blocked on a restrictive network. Some corporate, school, or public networks block the traffic needed to establish direct connections. If pairing repeatedly fails on one network, try a different network on at least one device.
• Transfer stalls or drops. Keep both tabs in the foreground where possible, avoid locking the screen, and do not switch the sending device to another app for long periods during a large transfer.
• Browser incompatibility. If one device uses an old or unusual browser, switch to a current version of a mainstream browser and retry.
• Text does not arrive. Confirm the send action completed on the sending side and that you are copying from the receiving device's text area, not the sender's.

If a transfer fails partway, the simplest recovery is to start a fresh session on both devices rather than trying to resume the old one.

When to use this approach — and when not to

Peer-to-peer browser transfer fits quick, direct moves between two devices you control or trust: phone to laptop, laptop to tablet, or sharing a snippet of text across devices. It avoids installing software and avoids parking the file on a server as part of the transfer.

It is less suitable when the receiving device cannot keep a browser page open for the duration, when one side is on a network that blocks direct connections, or when you need a durable copy stored somewhere for later download. In those cases, a conventional upload-and-download service is the more reliable choice.