Android
Verify checksum
OffBridge moves text and files between your Android phone and Windows PC, device to device. Pair once with a QR code or a 6-digit code, then send over your own Wi-Fi or with no network at all. Everything is sealed with AES-256, and nothing touches a server.
Try it: select any words on this page and tap Copy. Or copy one of these:
On Windows, what you copy reaches your paired phone by itself. Your text stays on this page.
Android doesn't let apps read the clipboard in the background, so the phone sends with one tap: the Push to PC tile, Share → OffBridge, or opening the app. Your text stays on this page.
Photos, videos, documents, whole folders. Big transfers go device to device and pick up where they stopped if the link drops, instead of starting again.
Or press Send in the window and pull the Wi-Fi yourself.
Or press Next on the phone and pull the Wi-Fi yourself.
Pairing runs a key exchange, then both screens show the same 6-digit code. If the numbers match, nobody is sitting in the middle. Or skip the digits and scan a one-time QR code that expires.
Meanwhile, on Pixel 10 Meanwhile, on Windows PC
Same digits? Press Accept on the phone.
Pairing Request
From: Windows PC
Make sure this code matches on both devices
Paired with Windows PC
You can now send files and share the clipboard with it.
OffBridge tries the fastest link first and only steps down when it has to. When there's no network to share, one device shows a QR code and the other scans it to build a private link between just the two of them.
Windows shows the code; an Android phone scans it with the camera. Try QR in the window.
NFC tap and camera scanning are Android-only. Pick a network on the phone, then Next.
or
Your hotspot is on — the other phone scans this to auto-join and receive.
There's no cloud to breach and no account to leak. This is everything a copy passes through between your two devices, and it goes nowhere else.
6-digit code
A fresh ECDH exchange on secp256r1 makes the shared key, and both screens show six digits drawn from it. Confirming they match is what stops anyone sitting in the middle.
A pairing QR carries a one-time key that expires. After that the peer's key is pinned, and a later swap fails closed.
Every copy and file is sealed on the device before it leaves, under the key from pairing. GCM is authenticated, so tampering is caught, not hidden.
Large files are sealed chunk by chunk.
Sealed on every link
Over your Wi-Fi, or with no network at all: QR, NFC, Wi-Fi Direct and hotspot links each use a per-session key.
Off-grid sealing needs Android 3.7.3 and Windows 3.7.7. With an older app on either side the link is authenticated but unsealed, so update both.
Keys stay home
Each pairing's keys are generated on your hardware and kept in the OS keystore. Never uploaded, shared or escrowed.
Unpair a device and its keys are wiped.
What isn't there
The app makes one other request: a version check against GitHub, which sends nothing about you.
Free, with no account. Install it on both devices; your platform is picked out below.
You're on another platform. OffBridge runs on Android and Windows. Grab a build below and install it on a supported device.
Builds are published for Android and Windows.
NFC tap to send, camera QR scanning, the Push to PC quick-settings tile, Share → OffBridge from any app, and a Lite or Pro layout.
Runs from the system tray so it can receive in the background, and ships its own runtime, so there's no Java to install.
No. On the same Wi-Fi it goes direct over your LAN; with no network at all it creates its own link via QR, NFC, Wi-Fi Direct or a hotspot bridge. Your clipboard and files never route through the internet. The app does reach out for one thing, and only if it can: a version check that asks GitHub whether a newer build exists.
It only reaches devices on your local Wi-Fi, and that traffic never crosses onto the internet, so it doesn't count against a data plan. It also can't discover devices over cellular. You need the same Wi-Fi, or an off-grid QR or NFC link.
Never. There are no servers and no account. Clipboard contents and files move straight between your devices, with keys stored only on your hardware. Those bytes are sealed with AES-256-GCM whether they cross your Wi-Fi or an off-grid QR or NFC link. Off-grid sealing needs Android 3.7.3 or later and Windows 3.7.7 or later on both ends; with an older device the off-grid link is still direct and authenticated, but the file bytes are not sealed.
It's a Short Authentication String derived from a secure key exchange. Both devices show the same number, and confirming they match proves you're connected to the right device and not an impostor.
Not on its own. Since Android 10, apps can't read the clipboard while they're in the background, and OffBridge doesn't try to get around that. What you copy on Windows reaches the phone automatically; to send from the phone, tap the Push to PC quick-settings tile, use Share → OffBridge, or open the app, which sends whatever you last copied.
Both apps ship in English, German, Spanish, French, Indonesian, Japanese, Portuguese, Russian, and Simplified and Traditional Chinese.
Multi-gigabyte transfers are supported, with live per-file progress. If the connection drops mid-transfer it resumes rather than starting over.
Android installs from Google Play. The Windows version is a standard installer with a bundled runtime, so there's no Java to set up. It isn't code-signed yet, so Windows may flag it the first time; the next question covers what to do.
That's Windows reacting to the missing code signature, not to anything the app does. It shows up two ways. SmartScreen displays a blue “unknown publisher” notice you can pass with More info, then Run anyway. Smart App Control, a stricter Windows 11 feature that's switched on for some machines, can block it outright with “couldn't verify the publisher,” and by design it has no per-app override.
OffBridge is off-grid and has no account; it's simply an unsigned indie build with no reputation yet. It does sit in the system tray so it can receive transfers, which is the app doing its job rather than anything hidden. You can confirm any download against the SHA-256 on the Windows card.
Two honest caveats. Smart App Control decides per file hash, so clearing one build does nothing for the next one. And the app is not code-signed yet, so we can't promise a date when a given release stops being flagged. If SmartScreen is all that's in your way, More info then Run anyway gets you through. If Smart App Control is on, there's no per-app override, and we'd rather you skip the install than switch the feature off.