Offline

Use tools locally, with clear offline limits

Learn how LocalKit prepares browser resources, what offline reuse depends on, and which browser settings can remove cached tool files.

LocalKit is designed so supported tools process your files in the browser. Some tools work immediately, while AI and media tools may need one online setup before they can run smoothly later.

What stays local

  • Supported tools process selected files inside the current browser tab or local worker.
  • Generated previews and downloads are created locally by the browser.
  • The app does not need to upload your source files or generated files to run local workflows.

First-use setup

  • Tools that use AI or heavier media processing may ask the browser to prepare models, WASM modules, or runtime files.
  • Keep the page online and the tab open during the first setup so those files can be prepared correctly.
  • After setup, the same browser profile can reuse cached files while the browser keeps them available.

What can affect offline use

  • Private browsing, storage cleanup, or strict browser settings can remove cached tool files.
  • A different browser, device, or user profile will need its own setup.
  • Large files and AI tools still depend on device memory and browser support, even after files are cached.

What offline does not mean

  • The first visit still needs the app shell, tool code, and any required resources to load successfully.
  • Remote catalog refreshes and resource plan checks may need a network connection.
  • Some tools are catalog-only until a local implementation is bundled, and some features may remain device-limited.