Docs Use Basalt

Devices nearby

Send files to a phone or computer that isn't on your host, before any drive is set up, even with no Wi-Fi in common.

Share with a device nearby sends files to devices around you that aren’t on your host: a guest’s phone, a friend’s laptop, two phones in a café. No drive is needed, and the two devices don’t need a Wi-Fi in common. From version 1.6.4.

Be found

On the device that receives, turn on Receive from devices nearby: on a computer in Settings, Nearby; on a phone under More, Sharing. Nothing arrives without your yes.

Devices nearby see it by its name and a short code, such as Pixel 8 · K7HM, so two phones of the same model can be told apart. The switch says what others see.

Send

  • Before any drive is set up: on the first screen, choose Share with a device nearby.
  • From a drive: choose Share on a file or folder, and pick the device under Nearby, not in this home.

The person there sees what you’re sending, with Accept and Decline. Never more than they accepted arrives.

No shared Wi-Fi needed

  • On the same Wi-Fi, the files go over it.
  • With no Wi-Fi in common, the devices find each other by Bluetooth. The one receiving opens a small Wi-Fi of its own only for that transfer, the sender joins it, and both go back to their own Wi-Fi after. Being ready to receive costs your Wi-Fi nothing: that Wi-Fi is opened only when someone sends.
Same Wi-Fi No Wi-Fi in common
Android Yes Yes, by Bluetooth
Windows Yes Yes, by Bluetooth, where the computer’s Bluetooth can be found. One that can’t still receives from a device that is sharing, by listening for it
Linux Yes Not yet: Bluetooth comes to Linux in a later version

Some phones have Wi-Fi for 2.4 GHz only. With no Wi-Fi in common, they can’t yet send to a Windows computer, whose own Wi-Fi is 5 GHz. On the same Wi-Fi they can, and sending to them works either way.

A code, for busy places

Always ask for a code makes every share to or from this device need a six-digit code: the receiver sees it once they accept, and the sender types it. It applies if either device has it on. Two devices showing the same name and short code always need it.

A wrong code counts as a guess, and after five the offer ends.

Safe by design

  • Every share between devices nearby is encrypted.
  • With a code, only the device that typed it can take the files, and someone listening learns nothing to try codes with.
  • A device can’t send more than you accepted, or flood you with offers.
  • A file arrives under its own name only once it is whole.

What it needs

The Nearby page says what is missing, with the button that puts it right.

  • Android: Bluetooth on, the Nearby devices permission, and, to reach devices that aren’t on your Wi-Fi, Location on: Android needs it to look for Wi-Fi. Basalt never reads where you are.
  • Windows: if Windows Firewall turns devices nearby away, the Nearby page shows Allow, which lets them in once Windows asks you.
  • Linux: if ufw or firewalld turns them away, Allow asks for your password to let them in.
  • If another app, or another copy of Basalt, is using Basalt’s nearby port, the Nearby page says so and tries again by itself.

If a share doesn’t arrive

On a computer, Settings, Nearby, Show the nearby log has the steps of each share. It is kept on that computer only, and has the names and network addresses of devices nearby: look at it before you send it to anyone. See Troubleshooting.

Something unclear, or not covered here? Ask in Help and setup, where the community and Refora Technologies answer, or write to us, and we will improve this page.