No connection. Still local.
You are seeing this because the page you asked for was not in the offline cache. The tools themselves still run on your device — no connection is needed once a tool has been loaded and cached.
What usually works offline
- The home page, category pages and this offline page, once the site has been visited.
- Any tool you have opened before, because its page and engine were cached on that visit.
- OCR in a language you have already used, because the language data was cached after the first run.
- Re-processing a file with a cached tool, including downloading a new result.
What still needs a connection
- A tool you have never opened. Its page and processing engine were never downloaded.
- OCR in a language you have not used before; the language data has to be fetched once.
- Email, because the contact form opens your own mail app and sending needs a connection.
- External links in the guides — they point to other websites.
- Site updates. A cached copy can be out of date until you reconnect.
Prepare before you go offline
- Open the tool once while connected.
Let the page finish loading. For a video or OCR tool, run a small test file so the heavy engine and language data are cached, not just the HTML.
- Check the result.
Make sure the output is what you expect. An offline cache is not useful if the tool was never working in the first place.
- Keep the tab or reopen it offline.
The service worker serves the cached page on reload. You can then process files normally; they still never leave the device.
Why a cached page can disappear
Browsers treat site data as disposable. Clearing browsing data, using a private window, switching profiles, or running a storage cleaner can remove the cache. A service-worker update also replaces the old cache. None of these affect your actual files — they only remove the site—s local copy.
If a page behaves strangely after an update, a hard reload (or clearing site data for this domain) fetches the current version. The privacy policy lists exactly what is stored locally.
Try a cached page
If those pages are not cached either, reconnect once and they will be stored for next time.