Status
Check the current state of the local app and its optional network-assisted features.
Paperlane is split into two layers with different dependencies: local tools that run entirely in your browser, and optional network-assisted features that call out to a service. Their availability should be understood separately.
Local tools: work offline#
Once the app shell and a given tool's code have loaded into your browser, local tools (page management, edit and annotate, most convert-to/from-PDF operations, and security utilities that don't require write-side encryption) do not depend on an application server to run. They will keep working on an already-loaded page even if your network connection drops mid-session.
AI and network-assisted features: depend on connectivity#
Features that call a model provider — AI summarization, chat-with-PDF, and similar — need an active network connection to the provider each time they run. If that connection or the provider itself is unavailable, those features fail independently of local tools and should say so clearly rather than hanging silently.
Installed app (PWA) caching#
When installed as a Progressive Web App, Paperlane caches the app shell and recently used tool bundles so they can start without a network round-trip. A tool you have already opened once is more likely to be available offline than one you are opening for the first time on a given device.
The offline indicator in the app reflects your browser's own connectivity signal plus whether the current route's assets are already cached — it is a best-effort indicator, not a guarantee that every feature on the page will work without a connection.
Reporting an outage#
If a network-assisted feature is down, or a local tool that should work offline is failing even with cached assets, please report it through the Contact page with the specific route and what you observed.