You have a paragraph on your phone. You need it on your laptop. Both devices are right in front of you, and this still somehow takes a minute and leaves debris behind.
The three workarounds, and what each one costs
Emailing yourself. Universal, works everywhere, and permanently pollutes the one inbox you are trying to keep clean. You also now have the text stored in a system you will never deliberately delete it from.
Messaging yourself. Faster than email, and the same problem in a smaller room: your saved-messages thread becomes a junk drawer, and the text sits in a chat history indefinitely.
Platform transfer — AirDrop, Nearby Share, Quick Share. Genuinely good when it works. It requires both devices to be the same ecosystem, physically near each other, with the right radios on. iPhone to Windows laptop, or phone to a remote desktop, and you are back to email.
All three share one trait: they use a storage system to do a transport job. The text is transient but the container is permanent, so you either clean up after yourself or you accumulate.
The one-note method
Open sharenotes.dev on the phone, paste, hit Share. You get a link
made of words — sharenotes.dev/blue-fox-42. Type that on the laptop and
the text is there.
The part that makes this work on a phone-to-laptop hop specifically is that the URL is short enough to retype by hand. There is no channel needed between the devices. You read it off one screen and type it into the other, which means it works when the two devices share no account, no network and no ecosystem.
The note stays live, too — edit on either device and the other updates. Handy when you are reformatting something on the laptop while reading the original off the phone.
Clipboard rooms, when you will do this more than once
If text is going back and forth repeatedly, generating a new link each time is
friction. Clipboard rooms exist for that: go to
sharenotes.dev/clip on both devices, type the same code, and you are in a
shared buffer.
The codes are six characters, drawn from a 31-character alphabet with the ambiguous
glyphs removed — no l versus 1, no O versus
0 — because these get read aloud and typed by hand. You can also just make
one up: any 3–10 character code works.
There is no separate room system under the hood. The room code is the note slug, so a room is a note you reach by typing instead of clicking. We wrote up why we built it that way.
Two things to know before you use a room for anything sensitive. Unlisted is not the same as private — anyone who types your code lands in your room, so short or guessable codes are genuinely guessable. And because rooms are created on join, a typo does not error; it silently drops you into a different empty room. If your text has not appeared, check the code before you re-paste.
Note or room?
| One-off note | Clipboard room | |
|---|---|---|
| Best for | Send it once, move on | Back-and-forth over a session |
| You get | A word-based link | A short code you both type |
| Setup | Paste, share, send link | Both devices type the same code |
| Reuse | New link each time | Same code all session |
Rough rule: if you will do it once, use a note. If you are going to do it four times in the next ten minutes, open a room and leave it open.
It expires, and that is the point
A ShareNotes note is removed 7 days after it was last opened. You can shorten that to 1 hour or 24 hours, or make it single-use so it is destroyed on first read.
This reads like a limitation and is actually the entire reason the method beats emailing yourself. The text was transient — a wifi password, an address, a paragraph being moved between two screens. Email and chat treat it as permanent because that is what they are for. Here the default is that it cleans itself up, and if you want it kept, you keep it somewhere you chose deliberately.
If you want the deeper version of the cross-device workflow, there is a dedicated walkthrough at send text to yourself, and a feature page for transferring text between devices.
Otherwise: open the editor, paste, and read the link off your screen.