I do a lot of tiny design jobs that don’t deserve a project folder: convert a GIF, embed cover art on an MP3, tweak SVG paths, check a color against a palette, spit out a mockup frame for a PR comment. None of those need a team workspace. Most of them do need me not to paste a client asset into whatever “free online tool” ranked first this week.

This is the tutorial version of that habit — how I pick a local-in-browser path for one-offs, what I check before I trust a tab, and where Uwarp fits when I want a catalog instead of hunting ten different domains.

The job shape that should stay local

I treat something as a one-off design job when:

Input is a file or paste — image, audio, SVG, CSS snippet, hex list

Output is a download — another file, a code block, a screenshot-ready canvas

No collaboration — I’m not co-editing with a PM in the same doc

Sensitivity isn’t zero — staging UI, unreleased brand marks, client audio

If all four hold, a SaaS “workspace” is usually the wrong abstraction.…