Client software is an application installed directly on your device – your computer, phone, or tablet. A web browser is also client software, but it serves a special purpose: it lets you access and run applications through the internet without installing them individually.
The practical difference? Client software (like Slack's desktop app, Zoom, or Adobe Photoshop) lives on your machine. A web application (like Google Docs, Trello, or Digital Samba) runs inside your browser. Both connect to servers, but they do it differently, and each approach has real trade-offs in performance, security, updates, and ease of access.
Here's the full breakdown.
Table of contents
- What is client software?
- What's a web browser?
- Client software vs web browser: key differences
- When to use a desktop client vs a web app
- The convergence: PWAs, Electron, WebAssembly and WebGPU
- Why browser-based matters for video conferencing
- Frequently asked questions
What is client software?
Client software is any application installed on a device that communicates with a server over a network. The term 'client' comes from the client-server model: your device (the client) sends requests to a remote computer (the server), which processes them and sends back data.
Some everyday examples of client software:
- Slack (desktop app) – installed on your computer, syncs messages from Slack's servers
- Zoom – installed locally, connects to Zoom's cloud infrastructure for video calls
- VS Code – a code editor that runs locally but connects to extensions, remote servers, and cloud services
- Spotify (desktop app) – installed on your machine, streams music from Spotify's servers
- Microsoft Outlook – installed locally, connects to email servers to send and receive messages
Client software depends on your device's operating system (Windows, macOS, Linux, Android, iOS). That's why many applications need separate versions for each OS – the code that talks to your hardware (microphone, camera, GPU, file system) is different on every platform.
Not all client software needs an internet connection to function. Photoshop, for example, works offline once installed. Other applications – like Zoom or Slack – need a connection to do anything useful, because the service they provide lives on the server.
What's a web browser?
A web browser is a specific type of client software designed to request, receive, and display content from web servers. Chrome, Firefox, Safari, Edge, and Brave are all web browsers.
But modern browsers are far more than page viewers. They're platforms in their own right. Thanks to technologies like JavaScript, WebAssembly, and WebRTC, browsers can now run applications that were previously only possible as installed software: video editing (Clipchamp), interface design (Figma), spreadsheets (Google Sheets), and real-time video conferencing (Google Meet, Digital Samba).
When you open a web application in your browser, the server sends the browser instructions (HTML, CSS, JavaScript) on how to build and run the application. The browser executes those instructions locally on your device. The application looks and feels like a native programme, but it's running inside the browser's environment – it doesn't have direct access to your device's hardware or file system the way installed software does.
Client software vs web browser: key differences
| |
Client software (desktop app) |
Web application (in browser) |
| Installation |
Must be downloaded and installed on each device |
No installation – open a URL and it works |
| Updates |
User or IT department must install updates |
Updated automatically on the server; users always get the latest version |
| Offline access |
Can work offline (if designed for it) |
Requires an internet connection (except Progressive Web Apps) |
| Performance |
Direct access to device hardware (GPU, CPU, memory) – generally faster for heavy tasks |
Runs inside the browser sandbox – once limited, now increasingly capable via WebAssembly and WebGPU |
| Security |
Has full access to the device – a malicious app can do serious damage |
Sandboxed by the browser – limited damage potential, but still vulnerable to web-based attacks (XSS, phishing) |
| Cross-platform |
Needs separate builds for each OS (Windows, macOS, Linux) |
Works on any device with a supported browser |
| Deployment |
IT departments must manage installation and permissions |
Users access it immediately – no IT gatekeeping |
| Maintenance cost |
Developers maintain multiple codebases for each platform |
One codebase serves all platforms |
| Hardware access |
Full access to cameras, microphones, GPUs, file system, peripherals |
Selective access through browser APIs (e.g. WebRTC for camera/microphone, WebGPU for the GPU) with user permission |
| Data storage |
Stores data locally on the device |
Stores data on the server (or in limited browser storage) |
When to use a desktop client vs a web app
The choice depends on what the application needs to do.
Desktop clients make more sense when:
- The application needs heavy GPU or CPU access (video editing, 3D rendering, game development)
- Offline functionality is essential (field work, areas with unreliable internet)
- Deep integration with the operating system is required (system tray notifications, file system watchers, background processes)
- Maximum performance is critical (professional audio production, large-scale data analysis)
Web applications make more sense when:
- Ease of access matters more than raw performance (participants joining a video call shouldn't need to install anything)
- Cross-platform support is a priority (one link works on Windows, Mac, Linux, Chromebook, phone, tablet)
- IT deployment is a concern (organisations that restrict software installation on employee devices)
- Automatic updates are important (everyone is always on the latest version)
- Real-time collaboration is core to the product (multiple users working on the same document or canvas)
Many applications now offer both. Slack has a desktop client and a web app. Figma works in the browser and as an Electron-based desktop app. Spotify runs natively and in the browser. Users choose based on preference and context.
The convergence: PWAs, Electron, WebAssembly and WebGPU
The line between client software and web applications has been blurring for years. Four technologies are driving this convergence.
-
Progressive Web Apps (PWAs) let web applications behave more like installed software. A PWA can work offline, send push notifications, and appear in your app launcher – all without being downloaded from an app store. Under the hood, it's still a web app running in the browser, but the user experience feels native.
-
Electron takes the opposite approach. It wraps a web application inside a lightweight browser (Chromium) and packages it as a desktop app. VS Code, Slack, Discord, and Figma's desktop app all use Electron. The developer writes one web-based codebase, and Electron turns it into installable software for Windows, macOS, and Linux. Newer alternatives like Tauri do the same with a far smaller footprint by using the operating system's built-in web renderer.
-
WebAssembly (Wasm) gives browsers access to near-native performance. Code written in languages like C, C++, or Rust can be compiled to WebAssembly and run inside the browser at speeds approaching native applications. This has enabled browser-based applications that were previously unthinkable – from video editors to 3D engines.
-
WebGPU goes a step further, giving web applications direct, GPU-accelerated access for graphics and computation. Now supported across all major browsers and reaching candidate-recommendation status in 2026, it brings desktop-class performance to tasks like machine learning, video processing, and 3D rendering in the browser – narrowing the performance gap that once clearly favoured installed software.
These technologies don't eliminate the distinction between client software and web apps, but they've made it less relevant for many use cases. The question is shifting from 'client or web?' to 'what experience does the user need?'
Why browser-based matters for video conferencing
Video conferencing is a category where the shift to browser-based delivery has been especially significant.
The traditional model required every participant to download and install a client application before joining a call. This created friction: people running into installation errors, IT departments blocking downloads on managed devices, and participants on unfamiliar machines (a hotel business centre, a borrowed laptop) unable to join.
WebRTC (Web Real-Time Communication) changed this. It's a set of protocols built into modern browsers that enables real-time audio, video, and data transmission – directly in the browser, with no plugins or downloads needed. When you join a browser-based video call, your browser uses WebRTC to establish encrypted peer-to-peer or server-mediated connections.
Browser-based video platforms are built entirely on WebRTC, so every participant – host or attendee – joins through the browser. There's nothing to download and nothing to install, and the same link works on a Windows desktop, a MacBook, a Chromebook, an Android phone, or an iPad.
For organisations that want to embed video conferencing into their own platforms – an ed-tech product, a telehealth system, a customer support tool – this browser-based approach is critical. Embeddable video conferencing APIs and SDKs let developers build the full video experience directly into a web application, so users never have to leave the product to install a separate video client.
Curated software platforms like Setapp show that native desktop applications still have strong appeal – offering polished, OS-integrated experiences for users who want them. But for the specific use case of joining a meeting or a video call, the browser-based model wins on accessibility and friction reduction.
For a deeper look at how WebRTC works, see our article on what is WebRTC.
Frequently asked questions
What is client software?
Client software is any application installed on your device that communicates with a server over a network. Examples include email clients like Outlook, messaging apps like Slack, and video tools like Zoom. The 'client' is your device; the 'server' is the remote computer it talks to.
Is a web browser client software?
Yes. A web browser is a specific type of client software – one that's designed to request, receive, and display content from web servers. What makes it different from other client software is that it can also run web applications inside itself, effectively acting as a platform for other software.
What is the difference between a web app and a desktop app?
A desktop app is installed on your device and has direct access to your hardware and operating system. A web app runs inside a browser and is accessed through a URL. Desktop apps typically offer better performance for heavy tasks; web apps offer easier access, automatic updates, and cross-platform compatibility.
Do I need to install software for video conferencing?
Not necessarily. Platforms like Zoom and Microsoft Teams offer desktop clients but also work in the browser. Browser-based platforms like Digital Samba and Google Meet require no installation at all – you join via a link in your browser. For a closer look at browser-based video conferencing security, see our guide to video API security.
What is WebRTC?
WebRTC (Web Real-Time Communication) is a set of protocols built into modern browsers that enable real-time audio, video, and data transmission without plugins or downloads. It's the technology that makes browser-based video conferencing possible. See our full explanation of how WebRTC works.
Will desktop software disappear?
No. Desktop software will continue to exist for tasks that need direct hardware access, offline functionality, or maximum performance – video editing, 3D rendering, software development tools. But for many categories (email, documents, communication, collaboration), web applications have already become the default.
