StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. lighttpd vs nginx

lighttpd vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
lighttpd
lighttpd
Stacks156
Followers133
Votes27

lighttpd vs nginx: What are the differences?

Introduction

In the world of web servers, two popular options that are often compared are lighttpd and nginx. Both are lightweight, high-performance servers that excel in delivering static content efficiently. However, there are key differences that set them apart in terms of architecture, features, and usability. Let's explore these differences in detail.

  1. Architecture: Lighttpd follows a traditional, single-process, event-driven architecture. It relies on multiple processes or threads to handle concurrent connections efficiently. On the other hand, nginx is designed with an asynchronous, event-driven architecture, utilizing a single master process and multiple worker processes, making it highly scalable and capable of handling a large number of simultaneous connections.

  2. Modules and Features: While both lighttpd and nginx provide an extensive collection of modules and features, nginx has gained popularity for its vast array of built-in modules, including load balancing, caching, SSL offloading, and WebSocket support. Lighttpd, on the other hand, focuses more on being a lean server, offering just the essential features, making it suitable for simple setups.

  3. Memory Usage: One major contrast between lighttpd and nginx is their memory usage. Lighttpd is known for its low memory footprint, making it an ideal choice for resource-constrained environments. In comparison, nginx requires more memory due to its advanced feature set and multi-process architecture. It's important to consider the available resources when choosing between the two.

  4. Configuration: When it comes to the configuration syntax, nginx utilizes a declarative and flexible approach, allowing easy customization and readability through its simple directives. Lighttpd, on the other hand, follows a more traditional configuration syntax with more rigid directives, which can be a bit challenging for beginners but provides more granular control for advanced users.

  5. Performance: Both servers are known for their efficient and high-performance nature, but nginx often outperforms lighttpd in handling concurrent connections, especially in scenarios with heavy traffic or under high loads. Its optimized I/O handling and asynchronous architecture greatly contribute to its superior performance characteristics.

  6. Community and Support: Nginx, being widely adopted by large enterprises, has a larger community and a vast amount of documentation and resources available. It offers commercial support from Nginx, Inc., while lighttpd, although having a smaller community, also provides active support and regular updates.

In summary, lighttpd and nginx differ in their architecture, modules/features, memory usage, configuration syntax, performance, and community/support. Choosing between the two depends on the specific requirements of the project, including the expected traffic, available resources, and level of customization needed.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on NGINX, lighttpd

Daniel
Daniel

Co-Founder at Polpo Data Analytics & Software Development

May 25, 2021

Decided

For us, NGINX is a lite HTTP server easy to configure. On our research, we found a well-documented software we a lot of support from the community.

We have been using it alongside tools like certbot and it has been a total success.

We can easily configure our sites and have a folder for available vs enabled sites, and with the nginx -t command we can easily check everything is running fine.

289k views289k
Comments
greg00m
greg00m

Mar 9, 2020

Needs advice

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities.
Ready, aim fire!

766k views766k
Comments
Grant
Grant

Developer at GMS LLC

Sep 5, 2020

Decided
  • Server rendered HTML output from PHP is being migrated to the client as Vue.js components, future plans to provide additional content, and other new miscellaneous features all result in a substantial increase of static files needing to be served from the server. NGINX has better performance than Apache for serving static content.
  • The change to NGINX will require switching from PHP to PHP-FPM resulting in a distributed architecture with a higher complexity configuration, but this is outweighed by PHP-FPM being faster than PHP for processing requests.
  • The NGINX + PHP-FPM setup now allows for horizontally scaling of resources rather vertically scaling the previously combined Apache + PHP resources.
  • PHP shell tasks can now efficiently be decoupled from the application reducing main application footprint and allow for scaling of tasks on an individual basis.
429k views429k
Comments

Detailed Comparison

NGINX
NGINX
lighttpd
lighttpd

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Statistics
GitHub Stars
28.4K
GitHub Stars
-
GitHub Forks
7.6K
GitHub Forks
-
Stacks
115.0K
Stacks
156
Followers
61.9K
Followers
133
Votes
5.5K
Votes
27
Pros & Cons
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
Pros
  • 7
    Lightweight
  • 6
    Easy setup
  • 2
    Simplicity
  • 2
    Full featured
  • 2
    Open source

What are some alternatives to NGINX, lighttpd?

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

Swoole

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Puma

Puma

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Caddy

Caddy

Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase