In computing and telecommunications, the terms "online" and "offline" indicate whether a device, service, or person can communicate over a network. If a computer or user is attached to the Internet, it is typically described as "online". A website accessible to others is also called online. Conversely, a device or service that cannot reach the network is considered "offline." Beyond connectivity, these words are used more broadly to mean operational or non‑operational in context: a system may be online but idle, or offline but powered on for maintenance.
Characteristics and common states
Being online usually implies network reachability, the ability to send and receive data, and visibility to other systems. Offline implies no network reachability, limited functionality, or intentional disconnection. Intermediate or related states include:
- Connected/Disconnected: basic link status at the network level.
- Available/Unavailable: application or service-level readiness to serve requests.
- Idle/Away: presence indicators used by communication platforms.
- Air‑gapped: physically isolated from networks for security.
History and development
The online/offline distinction grew with telecommunication networks and early computer dial‑up services, where users physically connected to remote systems. As always‑on broadband and mobile networks became common, "online" shifted from occasional connections to a default expectation. At the same time, software that can operate without continuous network access—such as email clients, desktop applications, and later progressive web apps—revived attention to offline capability.
Uses, examples and importance
Practical examples help illustrate the difference. A web page is online when a server responds to requests; a laptop is offline if airplane mode is active; a smartphone can be online for messaging while some apps work offline because they cache data. Offline functionality is important for resilience, user experience in poor networks, and privacy. Services that synchronize when reconnected (file sync, mail clients, note apps, maps) bridge the two states.
Distinctions and notable considerations
Several important distinctions affect security, reliability, and design. Air‑gapped systems provide high security by staying offline. Offline modes reduce latency and dependency on networks but require conflict resolution when syncing. Presence indicators on social platforms represent subjective availability rather than strict connectivity. Legal or contractual definitions sometimes distinguish "online" availability from scheduled maintenance or degraded service.
Designers and administrators must weigh tradeoffs between always‑online convenience and the robustness of offline operation. Approaches such as offline‑first application design, caching, and explicit sync policies help applications remain useful when connectivity is intermittent. Understanding the technical and human meanings of online and offline helps architects build more resilient, secure, and user‑friendly systems.