What this article covers
About ZumiLabs. See all the tools.
Our homepage says: Local-first tools and practical guides. You control where your data goes. Lots of products say something similar, and the words can mean anything from "works offline sometimes" to "we promise not to look". So this article spells out what they mean here, tool by tool, including where they don't apply.
What "local-first" means
The term comes from a 2019 essay by the research lab Ink & Switch, which set out ideals for software where your data lives on your own device first and in the cloud only as a copy, if at all. Our version is narrower and easier to check. A ZumiLabs tool is local-first when:
- The work happens on your computer. Your files, recordings, captures and images are processed by your own processor and graphics chip, in your browser or a small app.
- Your data stays where you put it: in your folders, or in your browser's own storage. We don't have a copy.
- There's no ZumiLabs account and no ZumiLabs server in the path. We can't lose, leak, sell or switch off what we never receive.
- Anything that leaves is your choice, made visibly. If a tool can use a cloud service, you choose the service, you supply your own key, and the tool says what it sends.
Why "by default" matters
Several of our tools can use cloud services. A local speech or image model is sometimes slower or less capable than the best cloud one, and pretending otherwise would make the tools worse.
"By default" is the promise that you start local. A tool works without signing up and without a key, and nothing goes anywhere until you set it to. When you do choose a cloud service, it's your account with that service, paid by you, under its terms. ZumiLabs isn't in the middle and doesn't add a fee on top.
Tool by tool
| Tool | Runs on your computer | Can reach the cloud when you choose |
|---|---|---|
| ZumiFiles | Browsing, previews, video trimming, folder comparison and tags, using the browser's File System Access API on your own folders | Direct transfers to another browser over WebRTC |
| OmniCapt | Screenshots, recordings and responsive captures, stored on your machine | Sending captures to Jira, GitHub, Slack or cloud storage |
| OmniBrief | Summaries with Chrome's built-in Gemini Nano, and a search index built in your browser | A cloud language model with your own key |
| CABE | Bookmark workspaces and indexes, in your browser's storage | Nothing |
| ZumiScribe | Transcription with a local engine; transcripts in your browser or folder | A cloud speech service of your choice, with your own key |
| ZumiForge | Image and video models on Apple silicon | Cloud image and video models with your own keys, kept in the Mac's Keychain |
| Audio Splitter | Separating songs into stems with Meta's Demucs model, saved to your folder | Nothing |
The engineering behind most of these rows has its own article: using your folders from a web app, running Gemini Nano locally, a vector search database in the browser, transcription that never uploads and image generation on a Mac.
Where it doesn't apply
A promise is only useful if its limits are clear. These parts of ZumiLabs are not local-first, and don't claim to be:
- The Content Hub. The video courses are streamed from a server like any website. There's no account and nothing to sign up for, but the videos come from the internet.
- CloudSend. Its job is to send files to cloud services. It's a small server you run, so other tools can deliver files without exposing API keys in the browser.
- This website. It uses Cloudflare Web Analytics to count visits. That doesn't use cookies, but it is a request to a third party.
- Usage reports. Where a tool sends a usage report, we say exactly what's in it instead of calling it "anonymous". Saying exactly what leaves your computer explains why.
What it costs you
Local-first has trade-offs, and you should know them before choosing it:
- Your hardware does the work. A recent computer makes a big difference. Some features need a capable graphics chip, or simply run faster on a newer machine.
- Backups are yours. If your data is only on your computer, it's only as safe as your backups.
- Sharing takes a step. Nothing is "already in the cloud", so sending something to a colleague is a deliberate action.
- The best model isn't always local. For some jobs a cloud model is still better, and we'd rather tell you than hide it.
How to check us
You don't have to take this on trust. Open your browser's developer tools, go to the Network tab and use a tool. With a local default, you'll see the app load and then go quiet while it works. If you've chosen a cloud service, you'll see requests to that service and nobody else. If you ever see something that doesn't match this page, tell us.
Local-first tools and practical guides
Browser tools, Mac apps and free courses. No account, and you control where your data goes.
Explore the tools