6 min read · updated 2026-07-29
Building a toolkit you can carry to any computer
Start with the things you would notice losing
Do not begin by collecting tools. Begin by listing the five things you did on a computer last week that you would be stuck without: writing something, editing an image, opening a PDF, moving a file to someone, looking something up. Fill those five, then stop.
A toolkit of five things you use is worth more than forty bookmarks you have to search through, and search-through-your-own-bookmarks is the failure mode every large collection eventually reaches.
Split it into the account layer and the open layer
The account layer is where your state lives — notes, documents, files, tasks. Pick as few of these as you can, because each one is a login to remember on a machine that will not have your password manager.
The open layer is everything else: converters, editors, calculators, checkers. These should need no account at all, so they work identically on any machine, including one you have thirty seconds on.
Prefer tools that work offline where you can
Anything doing its processing on-device usually keeps working when the connection does not. On patchy hotel wi-fi or a train, that is the difference between finishing something and not. It is also the strongest privacy property available in a browser, so you are picking up two benefits from one choice.
Several such tools are installable as progressive web apps, which gives you an icon and an offline cache without an actual installation — the closest thing to having your software with you.
Solve the transfer problem once
The recurring friction in a browser-only setup is moving a file between the machine you are on and the one you own. Pick one method and learn it properly: a browser-to-browser transfer for large files, an expiring link for anything you need to hand to someone else, and a self-destructing note for a credential you have to move.
Email attachment limits are what most people fall back on and are the worst option available on every axis.
What still genuinely needs installing
Sustained heavy video work, large-scale local development, anything needing deep operating-system access, and any professional workflow with a colour-managed or hardware-accelerated pipeline. Browser tools have closed a remarkable amount of this gap, but they have not closed all of it, and pretending otherwise wastes an afternoon.
The honest framing: a browser toolkit covers everything up to the point where the work becomes your full-time job. Past that, install something.
In short
- Fill the five things you would be stuck without, then stop.
- Keep the account layer as small as possible; make the rest need no login.
- On-device tools give you offline capability and privacy from the same choice.
- Pick one file-transfer method and learn it properly.
- Heavy video, real development and colour-managed work still need an installation.