← Back to blog

Clips that wait for signal

The moment you decide to keep a page is rarely the moment you have a good connection. You’re underground, or boarding, or standing in the one corner of the office where the signal dies. A clipper that fails there fails at the only time it’s asked to work.

So Clipperjay is built so the save never depends on the network.

The tap that always succeeds

Hitting Save clip writes the clip to a local queue on your device, along with your capture choice and the destination you picked. That’s the whole interaction. You get the confirmation and you put your phone away.

The queue drains on its own the next time you’re online: the clip is rendered, uploaded to OneNote and filed on the page you chose. Nothing to retry, no list of failures to tend to. If you clip six pages on a flight, six pages are in your notebook by the time you’re through the terminal.

Read-mode is your phone’s work, not a server’s

Most pages don’t need a server at all. Read-mode fetches the page on the device and extracts the article there, which is the cheapest thing Clipperjay can do and the most private: for an ordinary article, the page never passes through us.

Some pages can’t be read that way. A site that builds itself with JavaScript hands the device an empty shell, and a full-page screenshot needs a real browser to scroll and stitch. Those go to a renderer — your own, if you run one locally, and otherwise Clipperjay’s hosted one.

That’s also why renders, rather than clips, are the unit that matters to us: an ordinary read-mode clip costs nothing to serve, while a page that needs a browser costs real browser time.

Either way it fits the queue, because the queue holds only small durable facts — the URL, your capture choice, your destination — until there’s signal to act on them.

Filed in the wrong place? Move it

Speed comes from not being asked twice, so Clipperjay defaults to the destination you last used for that site. Occasionally that default is wrong.

The toast that confirms the save carries a Move action, and every clip stays in the clip library where you can move it later — without opening OneNote to do it.

The quiet goal

None of this is visible when it’s working, which is the point. A clipper earns its place by being reliable enough that you stop thinking about it: you share the page, and the page is in your notebook. Whether that happened immediately or twenty minutes later, in a tunnel, isn’t your problem to track.


Clipperjay is on iOS and Android. Get it now.