Click a phone number in Chrome. It rings your Android phone.
Google killed Chrome's own "Click to Call" feature back in 2023, citing low usage — despite people saying they used it a hundred+ times a day. That explanation never sat right, so I rebuilt it.
BrowserToPhone detects phone numbers on any webpage and, with one click, dials them on your paired Android phone — wakes it, waits for your thumbprint if it's locked, dials, and switches to speakerphone automatically. It runs entirely locally over ADB, no Google account or cloud relay involved.
For phones without developer mode set up, there's a fallback: a free push notification via ntfy.sh with a tappable Call button, using a private topic you generate yourself — still no login, no account.
Free, open source, MIT licensed. Fork it, tweak it, run it yourself.
Does it send my data anywhere?
Nothing is collected by me as the developer. Numbers you click go either to a small local server running on your own Mac, or to a private notification topic you generate yourself through ntfy.sh — never to me, never logged anywhere I can see.
Do I need ADB / developer mode on my phone?
Only for the fully automatic path (auto-unlock-aware, auto speakerphone). Without it, the free push-notification fallback still gets you a tap-to-call button — just one extra tap, no dev mode required.
Will this work with my iPhone?
No — the direct-dial path talks to Android over ADB, which iPhones don't support. The Chrome extension itself runs fine on Mac, Windows, or Linux either way, but the paired phone needs to be Android.
