I work on a company laptop that is, by design, a fortress. No personal Google accounts allowed. No random browser sign-ins. No syncing anything to anything. Which is great for the security team and terrible for a very specific, very mundane problem: I read something on my phone and I want it open on my work PC.
If you've never hit this wall, here's what it looks like in practice.
The problem with the "obvious" solutions
Chrome has a built-in "Send to your devices" feature. It works beautifully — as long as you're signed into the same Google account on both ends. On a managed work PC, that's exactly the thing you're not allowed to do.
Pushbullet and similar tools solve the cross-device problem in general, but they solve it by asking you to create an account, sign in on both devices, and often grant notification or contacts permissions along the way. On a locked-down machine, "please sign in with your personal account" is a non-starter, and honestly, even when it's technically allowed, I don't love handing a third-party account keys to my browsing habits just to move a URL from A to B.
I wanted something that needed zero accounts, zero installs on the PC side beyond a browser extension, and zero trust in a company I'd have to remember the password for.
The design: a QR code as the entire pairing protocol
The idea I landed on is small enough to describe in one sentence: a Chrome extension on the PC shows a QR code, your phone scans it once, and after that, copying a URL on your phone and tapping a button opens it on the PC.
Here's the flow in more detail:
- You install the QR Send Chrome extension on your work PC.
- The extension displays a QR code containing a link to a web page — no app store, no APK, just a URL.
- You scan it once with your phone's camera. The page that opens has a long, random "channel ID" baked into it.
- You add that page to your phone's home screen, so it behaves like a lightweight app from then on.
- From that point on: copy a URL on your phone, open the "app," tap send. The PC's Chrome extension (which is listening on that same channel) receives it and opens the page.
The whole trick is that the QR code isn't just a shortcut — it's the pairing mechanism. The random channel ID it encodes is the only thing that links your phone to your specific PC. There's no login, no username, no password, nothing to type. Scan once, and the pairing is done for good (or until you decide to re-pair by generating a new code).
Why a web page instead of a native app
I went back and forth on this. A native iOS/Android app would feel more "real," but it comes with real costs: app store review, update friction, and — more importantly for this use case — the implicit expectation that an app wants accounts, push notification permissions, and analytics SDKs.
A plain web page added to the home screen gets you 90% of the native-app feel (its own icon, full-screen, no browser chrome) with none of that baggage. It's also just a URL, which means the whole "install" step is literally scanning a QR code. No app store approval needed on a locked-down corporate device that might not even allow installing apps from an app store account you don't have permission to use.
That constraint — "the phone side can't require an account or an app store login either" — is honestly what pushed the whole architecture toward being accountless end to end, not just on the PC.
How the data actually moves
Under the hood it's intentionally boring:
- The channel ID from the QR code is the only identifier in the system. It's random and long enough to not be guessable, and it's never tied to an email, a name, or any login.
- When you send a URL, it's relayed over HTTPS through a pub/sub service (I'm using ntfy.sh) keyed on that channel ID.
- The PC extension is subscribed to that channel and picks up the URL when it's listening.
- Once the PC receives the message, it's gone. If nothing picks it up, it's automatically deleted after 24 hours regardless.
- There's no server-side account, no persistent history, no logging of what URLs you've sent, and no collection of personal information at all. The relay is a dumb pipe with an expiry timer.
That last point matters to me as much as the account-free part. I didn't want to build a system where I have to ask you to trust me with your browsing history in exchange for not asking you to trust Google or Pushbullet with it.
The honest limitations
I'd rather list these than have someone discover them the hard way:
- The PC's Chrome needs to be running (with the extension active) to receive a URL immediately. If it isn't, the message waits on the relay for up to 24 hours and gets delivered whenever Chrome comes back online — but if you close that window, it's gone.
- URLs only, no files. This is a link-passing tool, not a file-transfer tool. If you need to move a PDF or a photo, this isn't it.
- One-way by default. It's built for phone-to-PC delivery; it's not a general bidirectional sync tool.
- It's a small, single-purpose tool. It doesn't do reading lists, history, or cross-device tab sync. It does one job.
If any of those are dealbreakers for your use case, this probably isn't the right tool — and that's fine, it wasn't trying to be everything.
Try it / links
- Site: https://qrsend.app/en/
- Setup guide: https://qrsend.app/en/guide/
- Chrome Web Store: https://chromewebstore.google.com/detail/nmbdkmipjmgaieegnghbndibpmdceenh
It's a small tool built to solve a small, specific annoyance, and I'd genuinely like to know how other people have solved this. If you're also stuck behind a managed corporate PC: how do you get a link from your phone onto your work machine? Curious whether there's a cleverer pattern I'm missing, or whether "QR code as pairing key" is a wheel other people have already reinvented in a different shape.
Top comments (0)