Our Apps

Sharing files on a local network with HeyDrop: setup and troubleshooting

Understand HeyDrop’s Android and Windows sharing workflow, local-network requirement, integrity checks and HTTP limitations.

What HeyDrop is designed to do

HeyDrop focuses on local-network transfers between Android and Windows or between two Android devices. The product page describes the Google Play release as being prepared. This guide does not present a store download or purchase as available; check the product page for current distribution status.

A typical journey sends a phone photo to a computer on the same network. Choosing the device, receiving approval and checking the result are separate steps. Local file transfer does not require uploading the file to a central cloud server. Additional services such as advertising and Google Play purchases have separate internet requirements.

Prepare a small first transfer

Connect both devices to the same trusted Wi-Fi network or an appropriate phone hotspot. Open the application on both sides, select the file and confirm that the receiver is expecting it. Begin with a small, non-sensitive sample so you can check connectivity and the save location before a larger transfer.

A receiver name is not proof of identity. Confirm that the destination is the intended nearby device. The product page describes local-address or QR access for supported browsers too. Share that session destination only with the intended recipient rather than posting it publicly.

When the other device is missing

The same Wi-Fi name does not guarantee that devices can reach each other. Guest networks and client isolation can prevent communication. Check whether the connection is a guest network first. Follow administrator policy on managed networks; disabling the entire firewall is not an appropriate default troubleshooting step.

VPNs and multiple network adapters can affect which local address is used. Compare the displayed address with the intended receiver and retry with a small file while keeping the screen active. A useful report includes device type, OS, app version and the exact failing step. Do not attach private files or session links to a public issue.

Integrity, privacy and transfer time

According to the current product description, HeyDrop uses local HTTP and does not provide end-to-end encryption. SHA-256 checks transfer integrity; it does not mean that third parties on the network cannot read the file. Use a trusted private network and separately assess the protection required for sensitive material.

Transfer time depends on Wi-Fi conditions, device storage and network load as well as file size. One gigabyte at an effective ten megabytes per second takes roughly 100 seconds in ideal arithmetic. This is an example, not a measured HeyDrop benchmark. The calculator below estimates units and time only. Open the received file and check its size and contents after completion.

Transfer time estimate

Decimal MB and MB/s. Real transfers include overhead and interruptions.

Sources & further reading

Sources checked: 6 November 2026. Workflows and examples are editorial suggestions; they are not product benchmarks.