Send and receive files, text and links between an Android phone and your computer, using the same Quick Share your phone already has.
It adds Windows support and transfers that work without a shared Wi-Fi network (see How devices connect). It started as a fork of Martichou/rquickshare by Martin André and is now developed separately; see Credits.
Download the installer for your system from the latest release. To build it yourself instead, see BUILD.md.
Versions look like 1.26.298.42: the major version, the year and the day of the year the release was built (26.298 is October 25, 2026), then a build number that goes up with every release.
The installers aren't code-signed yet, so Windows and macOS will warn you the first time - see below.
Run r-quick-share-main_v<version>_x64-setup.exe. It asks whether to install for you only or for everyone on the computer (in Program Files). Either way Windows asks for administrator permission.
Earlier releases also had an .msi installer. If you installed from the .msi, uninstall it first (Settings > Apps > Installed apps), or you'll end up with two copies.
- Windows SmartScreen may say it "protected your PC", because the installer isn't signed. Click More info, then Run anyway.
- Windows Firewall will ask whether to allow rquickshare the first time it runs. Allow it on Private networks, otherwise your phone can't reach it over Wi-Fi.
- Bluetooth is needed for transfers with a phone that isn't on your Wi-Fi network.
Open r-quick-share-main_v<version>_aarch64.dmg and drag the app to Applications. There is no Intel build at the moment.
Because the app isn't signed, macOS will block it the first time. Go to System Settings > Privacy & Security, scroll down to the message about rquickshare, and click Open Anyway.
The packages are built on Ubuntu 24.04, and the minimum GLIBC version they need is part of the file name (for example glibc-2.39). Check yours with ldd --version.
RQuickShare also needs one of these libraries; the package manager normally installs it for you:
libayatana-appindicatorlibappindicator3
sudo apt install ./r-quick-share-main_v*_amd64.debapt install with a local file also installs any missing dependencies, which dpkg -i doesn't.
sudo dnf install ./r-quick-share-main_v*.rpmsudo rpm -i r-quick-share-main_v*.rpmEvery release lists the SHA-256 of each installer in SHA256SUMS, and GitHub keeps a signed record (an attestation) that this repository's Release workflow built each one. This shows the file is the one the release published. It doesn't stop the Windows and macOS warnings above, which only code signing does.
To check the attestation, use the GitHub CLI, signed in with gh auth login:
gh attestation verify r-quick-share-main_v<version>_x64-setup.exe --repo asulwer/rquickshareTo check only the checksum, compare the hash with the file's line in SHA256SUMS:
- Windows (PowerShell):
Get-FileHash .\r-quick-share-main_v<version>_x64-setup.exe - macOS:
shasum -a 256 r-quick-share-main_v<version>_aarch64.dmg - Linux, with
SHA256SUMSdownloaded next to the package:sha256sum -c --ignore-missing SHA256SUMS
- Same Wi-Fi network: devices find each other over mDNS and transfer directly over the network. This is the fastest path and works on every platform.
- No shared Wi-Fi (Windows): the transfer starts over Bluetooth LE, then moves to Wi-Fi - your local network if the phone can reach it, otherwise a hotspot rquickshare brings up on your PC (Windows Mobile Hotspot). Your PC needs Bluetooth, and a Wi-Fi adapter for the hotspot.
- Bluetooth on Linux is newer: receiving from a phone over Bluetooth works, and the transfer moves to Wi-Fi when both devices are on the same network.
Bluetooth support is still being refined; see KNOWN_ISSUES.md for the problems we know about.
- Make sure rquickshare's visibility (top of the side menu) isn't Hidden from everyone.
- On the same Wi-Fi network, mDNS has to be allowed on that network; public networks (coffee shops, airports, etc.) often block it. On Windows, also check the firewall note above.
- Without a shared network, your computer needs Bluetooth turned on.
Android doesn't advertise itself all the time, even in "Everyone" mode. A few ways around that:
- Scan the QR code. When you pick something to send, rquickshare shows a QR code. Scanning it with your phone makes the phone show itself to rquickshare, even when it isn't set to "Everyone".
- Bluetooth. On Windows and Linux, rquickshare broadcasts a Bluetooth advertisement that makes nearby Android devices reveal themselves, if your computer has Bluetooth.
- Open the receive screen on the phone. In the "Files" app, open the "Nearby Share" tab. If that isn't there, use a shortcut maker (see here) to create a shortcut to either:
- Activity:
com.google.android.gms.nearby.sharing.ReceiveSurfaceActivity - Action:
com.google.android.gms.RECEIVE_NEARBYwith Mime type*/*
- Activity:
Note: Samsung changed Quick Share on its devices, so the shortcut workaround may not work there.
This is normal when your computer is relying on Bluetooth to find the phone: Android periodically withdraws its advertisement and only reappears when it sees the Bluetooth message again.
To notify you when a nearby phone is sharing, rquickshare listens over Bluetooth. Unless BlueZ offers a passive monitor, that means scanning, and while a scan runs the Bluetooth controller can't take a reconnection from a mouse or keyboard. Turn off Notify me when a nearby device is sharing in the settings to stop it. See docs/ble-nearby-alert.md for the details, including the passive mode and its trade-offs.
Copy the text (or URL) to your clipboard, then press Ctrl+V (or Cmd+V) inside the rquickshare window and pick the target device. URLs are sent so the receiving Android device can open them in a browser. You can also enable Auto-stage clipboard text in Settings to have newly copied text staged for sending automatically.
Text, links and Wi-Fi networks sent to your computer show up as a notification, with a Copy button (and Open, for links).
No - Quick Share only sends individual files. Dropping a folder on the window shows a message asking you to send the files inside it instead.
Open Settings and set Device name. Leave it empty to use your computer's name.
That's by default: closing the window keeps rquickshare running in the system tray so it can still receive. To quit when the window closes, turn off Keep running on close in Settings.
On Linux, if your desktop has no system tray, you can check whether it's still running with:
ps aux | grep r-quick-shareYou can give rquickshare a fixed port to allow in your firewall. Close the app, then add a "port" entry to its settings file:
- Windows:
%APPDATA%\dev.mandre.rquickshare\.settings.json - Linux:
~/.local/share/dev.mandre.rquickshare/.settings.json - macOS:
~/Library/Application Support/dev.mandre.rquickshare/.settings.json
Warning
The json must stay valid after your modification; for example, if "port" is the last item of the JSON it must not have a comma after it, otherwise the config will be reset.
{
...existing_config...,
"port": 12345
}By default the port is random (the OS will decide).
- Windows:
%LOCALAPPDATA%\dev.mandre.rquickshare\logs - Linux:
~/.local/share/dev.mandre.rquickshare/logs - macOS:
~/Library/Logs/dev.mandre.rquickshare
To capture a problem, set Logging level to trace in Settings, reproduce it, and attach the log to an issue.
This happens for some users running Linux + NVIDIA cards. Start rquickshare with:
env WEBKIT_DISABLE_COMPOSITING_MODE=1 rquicksharerquickshare is still in development. Windows 11 and Linux are the main targets; macOS should work but is less tested. Expect the design to change between versions.
Got feedback or suggestions? Feel free to open an issue.
This project wouldn't exist without these amazing open-source projects:
- https://github.com/Martichou/rquickshare by Martin André, the original project this one grew out of
- https://github.com/grishka/NearDrop
- https://github.com/vicr123/QNearbyShare
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. See BUILD.md to get a development build running; pull requests must pass the checks in .github/workflows/check.yml (rustfmt, cargo test, lint, type-check).