What can work offline
Local project browsing, supported file work, notes, tasks, project organization, and connected local-model workflows can remain available when they do not depend on an online service.
What requires a connection
Cloud providers
Web apps and API calls need internet access.
Account and billing
Sign-in, subscription changes, and billing management require a connection.
Cloud storage and connected apps
Online drives, websites, and remote services need access to their servers.
License refresh and downloads
Periodic validation, installer downloads, and account changes may require the internet.
Switch modes
Use the online/offline control in the app header. LobeWork should make the current state visible so you know whether online actions are available.
If you attempt an online action while offline, reconnect before continuing.
Use a local model
Start the supported local runtime, confirm the model is installed, and connect it through Models. Local inference can still require substantial memory, storage, and processing power.
Prepare before going offline
Open the project
Confirm the needed files are stored locally.
Start the local runtime
Load the model before disconnecting when required.
Finish account changes
Complete downloads, billing, or license updates while online.
Capture work locally
Save important results into the project before closing the session.
Ask LobeWork about this guide.
The question will be placed into the support widget so you can continue from the exact topic.