{"post":{"slug":"what-is-a-client-2026","title":"What Is a Client in 2026: the requester half of the web","excerpt":"In computing, a client is the program that asks a server for something, like a browser requesting a web page. Here is what a client is and how it works in plain language.","category":"code","date":"June 1, 2026","author":"ByteLedger Team","content":"<span class=\"dropcap\">A</span> client, in computing, is a program that requests something from another program called a server, then uses whatever comes back. The web browser you are reading this in is a client: it asked a server for this page, the server sent it, and the browser displayed it. That request-and-response pattern is the heart of the client-server model, and it describes most of how the internet actually works. A client always starts the conversation; the server waits and answers. Understanding which side is which clears up a surprising amount of confusion about how apps and websites operate.\n\n## How the client-server model works\n\nThe model has two roles. The client initiates a request, the server processes it and sends a response. Picture ordering at a counter: you, the client, place an order; the kitchen, the server, prepares it and hands it back. The client does not need to know how the kitchen works, only how to ask and what to expect.\n\nOn the web, this happens over HTTP. Your browser sends an HTTP request to a server identified by a URL, the server runs whatever logic it needs, and it returns HTML, data, or a file. The same shape repeats for a mobile app talking to an API, a database tool querying a database, or one microservice calling another. If you want the other half of the picture, the companion guide on [what a server is](/blog/what-is-a-server-2026) covers the responding side in detail.\n\n## Types of clients\n\nClients are not all browsers. The term covers any software that makes requests.\n\n| Client type | Example | Notes |\n|---|---|---|\n| Web client | A browser like Chrome or Firefox | Requests and renders web pages |\n| Mobile or desktop app | A banking app, an email app | Talks to a backend API |\n| Command-line client | A tool that hits a REST API | No graphical interface |\n| Another server | A service calling a payment API | A server can be a client too |\n\nThat last row matters: client and server are roles, not fixed identities. A program can be a server to one party and a client to another at the same time.\n\n## Thin clients vs thick clients\n\nA common distinction is how much work the client does on its own.\n\nA thin client keeps most logic and data on the server and does little beyond displaying results, which makes it lightweight and easy to update centrally. A thick, or fat, client does more processing locally, which can feel faster and work offline but is harder to keep consistent across devices. Most modern web apps sit somewhere in between, doing meaningful work in the browser while relying on the server for data and security.\n\nWhen a client talks to a server, it usually does so through an interface the server exposes. To understand that contract, read [what a REST API is](/blog/what-is-a-rest-api-2026), since that is the most common way clients and servers communicate today.\n\n## Common misconceptions\n\n- **The client is the device.** Not quite. The client is the requesting program; the device just runs it.\n- **Clients are always browsers.** Apps, scripts, and other servers are clients too whenever they make requests.\n- **The server always knows more.** The server holds shared data and rules, but a client can hold plenty of its own state and logic.\n- **Client and server are fixed labels.** They are roles in a given exchange, and one program can switch between them.\n\n## FAQ\n\n**What is a client in simple terms?**\nA program that asks a server for something and uses the response, like a browser requesting a web page.\n\n**What is the difference between a client and a server?**\nThe client makes the request and the server answers it. They are roles in a conversation, not necessarily different machines.\n\n**Is my phone a client?**\nYour phone is a device, but the apps and browser running on it act as clients when they request data from servers.\n\n**What is a thin client?**\nA client that does little processing itself and relies on the server for most logic and data, which makes it light and easy to manage centrally.\n\n## Where to go next\n\n[What is a server](/blog/what-is-a-server-2026), [What is a REST API](/blog/what-is-a-rest-api-2026), and [What is a web browser](/blog/what-is-a-web-browser-2026).","hue":195,"metaTitle":"What Is a Client in 2026? Client vs Server Explained","metaDescription":"What is a client in 2026? A plain-language guide to clients in computing, how the client-server model works, types of clients, and common misconceptions.","keywords":["what is a client 2026","client explained","client server model","what is a client in computing","client vs server","web client","thin vs thick client","client for beginners","what does client mean in tech","http client"],"tldr":["**A client requests, a server responds** — the client asks for data or an action and waits for the server to answer.","**Your browser is the classic client** — it sends requests for web pages and renders what the server sends back.","**Clients come in many forms** — web browsers, mobile apps, desktop apps, and even other servers can act as clients.","**Thin vs thick describes how much it does** — a thin client offloads work to the server, a thick client does more on its own.","**Skip:** confusing the client device with the client software; the client is the program making the request, not just the machine."],"readTime":"3 min read","wordCount":722},"related":[{"slug":"what-is-a-server-2026","title":"What is a server in 2026? The program that answers requests explained","excerpt":"A server is a program or machine that listens for requests and sends back responses, like serving web pages. This guide explains how servers work, the client-server model, and common types.","category":"code","date":"June 18, 2026","author":"ByteLedger Team","readTime":"4 min read","hue":195},{"slug":"what-is-a-database-schema-2026","title":"What Is a Database Schema in 2026: the blueprint for data","excerpt":"A database schema is the blueprint that defines how data is organized: the tables, columns, types, and relationships. Here is what a schema is and why it matters.","category":"code","date":"June 22, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":222},{"slug":"what-is-a-boolean-2026","title":"What Is a Boolean in 2026: true, false, and why it matters","excerpt":"A boolean is a data type with only two possible values, true or false. It is how programs make decisions. Here is what a boolean is and how it works in plain language.","category":"code","date":"June 17, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":212}],"sameCategory":[{"slug":"bazel-build-explained-2026","title":"Bazel Explained: What Hermetic Builds Actually Cost","excerpt":"Bazel delivers reproducible, precisely cached builds and demands that you describe everything. Here is what you get, what it costs, and who should say no.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":145},{"slug":"graphql-federation-2026","title":"GraphQL Federation: One Graph, Many Teams","excerpt":"Federation composes independently-owned subgraphs into a single API. Here is what it solves, the operational cost it adds, and when a simpler gateway is enough.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":300},{"slug":"hermetic-builds-explained-2026","title":"Hermetic Builds Explained: Same Inputs, Same Output","excerpt":"A hermetic build depends only on declared inputs. Here is what that property gives you, the common leaks that break it, and how to move toward it incrementally.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":130},{"slug":"monorepo-tooling-compared-2026","title":"Monorepo Tooling Compared: What You Actually Need","excerpt":"Monorepo tools solve task orchestration and caching, not repository layout. Here is what each tier provides and how to tell when you have outgrown the simple option.","category":"code","date":"August 19, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":150}],"newer":{"slug":"what-is-a-chatbot-2026","title":"What is a chatbot in 2026? A plain-language explainer","excerpt":"A chatbot is software that holds a conversation in text or voice. Here is what a chatbot is, how it works, where it helps, and where it still falls short.","category":"ai","date":"June 1, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":216},"older":{"slug":"what-is-a-cookie-in-web-2026","title":"What is a cookie in web in 2026? Browser cookies explained","excerpt":"A cookie is a small piece of data a website stores in your browser to remember things between requests. Here is what it does, the types, and the privacy angle.","category":"code","date":"June 1, 2026","author":"ByteLedger Team","readTime":"3 min read","hue":240}}