Do I ever choose a web server on regular hosting?

On shared and most managed plans, no — the provider chose it, and at most you drop an .htaccess file into Apache. The choice becomes yours on a VPS or dedicated machine, where installing and configuring the web server is part of the job.

nginx or Apache — does it matter for my site?

For a typical site, either serves it well; configuration quality matters far more than the brand. The practical differences are operational: nginx's model handles high connection counts efficiently, while Apache's per-directory overrides make it convenient in multi-tenant shared environments.

What is a Web Server? — Getting Digital glossary

Web Server

Also: HTTP server, nginx, Apache HTTP Server

A web server is the program that listens for HTTP requests and answers them — serving files directly or passing the request to application code — with nginx and Apache as the long-standing workhorses of the role.

Two meanings, one word

Colloquially, 'the web server' often means the machine a site runs on. Precisely, it is software: a program bound to ports 80 and 443 that speaks HTTP. The distinction matters the moment you configure anything, because what people tune, secure and debug is the program — the machine is just where it lives. One physical or virtual server can run several web servers; one web server routinely fronts dozens of sites.

Modern setups usually chain two layers. The web server in front handles what it is uniquely good at: TLS termination, static files, compression, rate limiting and virtual hosts (many domains on one program). Dynamic requests are proxied onward to application processes — PHP-FPM, a Node.js service, Python workers — which is why nginx is so often described as a 'reverse proxy'. On shared hosting this whole arrangement exists too; you simply never see it.

nginx — event-driven architecture built for many simultaneous connections; the default front layer of the modern stack.
Apache HTTP Server — the veteran, prized for per-directory configuration (`.htaccess`) and its module ecosystem; still everywhere in shared hosting.
Caddy and friends — newer servers that automate TLS certificates and aim for minimal configuration.

Key takeaways

→A web server is software, not hardware: the HTTP-speaking program in front of your site, distinct from the machine hosting it.
→In practice it works as a front layer — TLS, static files, routing — proxying dynamic requests to separate application processes.

Related concepts

RelatedShared Hosting
Shared hosting is one web server fronting many tenants — the mechanism behind the model.
RelatedLoad Balancing
The same software fills both roles: a load balancer is a reverse proxy with multiple backends.
RelatedSSL/TLS
TLS terminates at the web server (or CDN edge) — where certificates get configured.

FAQ

Do I ever choose a web server on regular hosting?: On shared and most managed plans, no — the provider chose it, and at most you drop an .htaccess file into Apache. The choice becomes yours on a VPS or dedicated machine, where installing and configuring the web server is part of the job.
nginx or Apache — does it matter for my site?: For a typical site, either serves it well; configuration quality matters far more than the brand. The practical differences are operational: nginx's model handles high connection counts efficiently, while Apache's per-directory overrides make it convenient in multi-tenant shared environments.