OpenLiteSpeed is the open-source edition of LiteSpeed Web Server, an event-driven HTTP server released under the GPLv3 license by LiteSpeed Technologies. Among web servers, it is known for efficient PHP execution through its own LSAPI interface, a built-in page cache and native support for HTTP/2 and HTTP/3.
OpenLiteSpeed understands Apache-style rewrite rules and is managed through a browser-based WebAdmin console as well as plain-text configuration files. It is popular for WordPress hosting and is the web server behind several free control panels, while the commercial LiteSpeed Enterprise edition targets hosting companies that need full Apache compatibility.
How OpenLiteSpeed handles requests
OpenLiteSpeed uses an event-driven architecture: a small number of worker processes each handle thousands of connections through non-blocking I/O, rather than dedicating a process or thread to every connection. This keeps memory use stable under high concurrency, similar to Nginx and unlike the classic Apache prefork model.
Dynamic content is passed to external applications. For PHP, OpenLiteSpeed starts lsphp processes and talks to them through LSAPI, a protocol designed by the same vendor as a lighter alternative to FastCGI. The server can spawn PHP processes on demand and stop them when idle, which suits servers hosting many small sites.
The main components of an installation are summarized below.
| Component | Function | Notes |
|---|---|---|
| Listener | Binds IP addresses and ports, handles TLS | Mapped to one or more virtual hosts |
| Virtual host | Configuration for one or more domains | Defines document root, contexts and rewrite rules |
| External app | Backend process such as lsphp | Communicates through LSAPI, FastCGI or a proxy |
| Script handler | Maps file suffixes to an external app | Routes .php requests to lsphp |
| LSCache | Built-in full-page cache | Controlled by response headers and plugins |
| WebAdmin console | Browser-based management | Listens on port 7080 by default |
OpenLiteSpeed compared with other web servers
OpenLiteSpeed competes with Nginx, Apache and Caddy, and with its own commercial sibling. The table highlights the differences that most affect hosting decisions.
| Server | Architecture | Apache .htaccess support | PHP integration |
|---|---|---|---|
| OpenLiteSpeed | Event-driven | Rewrite rules only | LSAPI with lsphp |
| LiteSpeed Enterprise | Event-driven | Broad, reads Apache configuration | LSAPI with lsphp |
| Nginx | Event-driven | None | FastCGI to PHP-FPM |
| Apache | Process, thread or event MPM | Full | PHP-FPM via proxy_fcgi or mod_php |
| Caddy | Event-driven, written in Go | None | FastCGI to PHP-FPM |
The most frequent misunderstanding concerns .htaccess. OpenLiteSpeed reads only the rewrite directives from these files, and other directives such as access control or PHP settings are ignored. Changes to .htaccess may also require a graceful restart to take effect, depending on version and settings.
LSCache and performance settings
The built-in LSCache module stores complete rendered pages and serves them without running PHP. Applications control it through response headers, and official plugins for WordPress and other systems handle cache purging when content changes.
The following settings have the largest effect on performance and stability.
| Setting | Where | Effect |
|---|---|---|
| Max connections | Server tuning | Upper limit of concurrent client connections |
| PHP_LSAPI_CHILDREN | External app environment | Number of PHP worker processes per pool |
| Memory soft and hard limit | External app | Caps memory per PHP process group |
| Max idle time | External app | Stops idle PHP processes to free memory |
| Enable cache | Cache module, server or virtual host | Turns full-page caching on or off |
| QUIC or HTTP/3 | Listener and server settings | Enables HTTP/3 over UDP port 443 |
Most performance gains for content sites come from LSCache hit rates, not from raw server speed. A page served from cache costs a fraction of the CPU time needed to run PHP and database queries.
When OpenLiteSpeed is a good choice
OpenLiteSpeed fits best where PHP applications dominate and the operator controls the whole server. The decision table summarizes typical situations.
| Situation | Fit | Reason |
|---|---|---|
| WordPress on a VPS | Strong | LSCache plugin and LSAPI work together |
| Many small PHP sites | Strong | On-demand PHP processes save memory |
| Apps relying on full .htaccess | Weak | Non-rewrite directives are ignored |
| Reverse proxy for non-PHP apps | Adequate | Works, but Nginx or Caddy are more common |
| Shared hosting with cPanel | Weak | LiteSpeed Enterprise is the supported option |
Migration from Nginx or Apache is usually straightforward for standard PHP applications, because document roots, TLS certificates and rewrite rules carry over with little change. The work lies in translating custom server rules and testing cache behavior. Running the new server on a staging copy first and comparing response headers, redirects and error pages catches most differences before the switch.
Limitations and common mistakes
Administrators moving from Apache or Nginx often run into the same configuration surprises.
- Leaving WebAdmin exposed: port 7080 should be restricted by firewall or bound to a private address.
- Expecting Apache directives to work: only rewrite rules are honored in .htaccess files.
- Forgetting restarts: configuration changes in WebAdmin apply only after a graceful restart.
- Caching personalized pages: carts, account pages and logged-in views need correct no-cache or private cache rules.
- Mixing PHP versions incorrectly: each virtual host must point to the intended lsphp binary.
Stripped to the essentials
A web server is the program that receives requests from browsers and sends back web pages. OpenLiteSpeed is a free, fast web server built to serve many visitors at once without using much memory.
Its special strength is that it keeps ready-made copies of pages, so it can answer most visitors instantly instead of rebuilding each page from scratch. Think of a bakery that keeps popular bread on the shelf rather than baking every loaf only after a customer asks.
Where it is applied
A freelance developer manages twelve small WordPress sites for local businesses on one VPS with 4 vCPUs and 8 GB of memory. Under Apache with mod_php, memory regularly ran out during busy hours.
The developer migrates the sites to OpenLiteSpeed with lsphp 8.3, creates one virtual host per site, installs the LSCache plugin on each WordPress installation and restricts WebAdmin to a VPN address. Idle PHP processes now stop after a few minutes, so quiet sites consume almost no memory.
After the move, most page views are served directly from cache, average memory use falls noticeably, and the server no longer swaps during traffic peaks. The developer postpones a planned upgrade to a larger plan.