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:

  1. 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.
  2. Your data stays where you put it: in your folders, or in your browser's own storage. We don't have a copy.
  3. 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.
  4. 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

ToolRuns on your computerCan reach the cloud when you choose
ZumiFilesBrowsing, previews, video trimming, folder comparison and tags, using the browser's File System Access API on your own foldersDirect transfers to another browser over WebRTC
OmniCaptScreenshots, recordings and responsive captures, stored on your machineSending captures to Jira, GitHub, Slack or cloud storage
OmniBriefSummaries with Chrome's built-in Gemini Nano, and a search index built in your browserA cloud language model with your own key
CABEBookmark workspaces and indexes, in your browser's storageNothing
ZumiScribeTranscription with a local engine; transcripts in your browser or folderA cloud speech service of your choice, with your own key
ZumiForgeImage and video models on Apple siliconCloud image and video models with your own keys, kept in the Mac's Keychain
Audio SplitterSeparating songs into stems with Meta's Demucs model, saved to your folderNothing

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:

What it costs you

Local-first has trade-offs, and you should know them before choosing 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.

ZumiLabs

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