Digitalization
19. October 2026 6 min
What is NGINX, and do you need to decide anything about it for your website? How to tell if it is your job
NGINX is open-source software that receives requests to a website and either answers them itself or passes them on. Here you get an explanation of what it does, what it is not, and whether you need to make any decisions about it yourself.

NGINX
NGINX is open-source software that sits at the front of a server and receives requests to a website, where it either answers them itself or passes the request on, and it is used as a web server, reverse proxy, cache and load balancer.
Also called: engine x
NGINX is pronounced “engine-x”. It was written by the Russian developer Igor Sysoev and released in 2004 under a 2-clause BSD license, which allows free use. The commercial edition, NGINX Plus, and support come from F5.
Why do you come across NGINX, and what is it not?
You come across NGINX because it runs a large share of the world’s websites and is often mentioned in hosting agreements, on error pages and in conversations with developers. NGINX decides how requests reach your site, but it is not your hosting, your CMS or a CDN.
The word usually turns up in three situations. Your hosting provider says they run NGINX. You see an error page with the text “nginx” at the bottom. Or a developer suggests changing something in the NGINX configuration to make the site faster.
In all three cases, NGINX is a program on the server. It is not something you buy as a separate service, and on most hosting plans it is already installed and maintained by someone else. The table shows what NGINX is most often confused with.
| Term | What it is | How it differs from NGINX |
|---|---|---|
| Hosting | The agreement and the server your website runs on | NGINX is one of the programs that can run on the server. Hosting is the space and the operation itself. |
| CDN | A network of servers around the world that delivers files close to the visitor | A CDN sits in front of your server. NGINX sits on your server. Many sites use both. |
| WordPress and PHP | The application that builds your pages, cart and checkout | NGINX does not build pages. It passes the request on to PHP and delivers the response back. |
| Apache | Another widely used web server | Handles many of the same tasks. The choice depends on setup and needs, and some servers use both. |
| NGINX Plus | The commercial edition from F5 | Built on the same core, but with extra features and support. A typical website rarely needs it. |
What happens when a request reaches NGINX?
When a request reaches NGINX, NGINX decides whether it can be answered directly or must be passed on to the backend. NGINX delivers images, CSS and cached pages itself, while the cart and checkout are passed on to the application that builds them.
Take a WooCommerce shop on a single server. A visitor opens a product page. NGINX receives the request, handles the encrypted HTTPS connection and looks at what is being asked for. If it is an image, it is sent straight from the disk. If the customer adds something to the cart, the request goes on to PHP.
Web server
As a web server, NGINX delivers files straight from the server’s disk: images, CSS, JavaScript and PDFs. In the shop, this means product images can be sent without involving PHP at all.
Reverse proxy
A reverse proxy receives requests on behalf of another server and passes them on. NGINX sits in front of PHP, so the visitor never talks directly to the backend. This is also where HTTPS is usually handled.
Cache
NGINX can store fully built pages in a cache and send them again to the next visitor. A product page that is the same for everyone does not need to be rebuilt every time. The cart and checkout, on the other hand, must not be cached, because the content is personal.
Load balancer
As a load balancer, NGINX spreads requests across several backend servers. This only matters once a site runs on more than one server. A shop on a single server does not use this role.
TCP/UDP and mail proxy
NGINX can also forward traffic other than web pages, such as email and database connections. This is rarely relevant for a typical website, and you can usually ignore it.
What do people usually ask about NGINX?
Is NGINX free?
Do I need to do anything about NGINX myself?
How can I tell if my website uses NGINX?
Is NGINX faster than Apache?
What does “502 Bad Gateway” with nginx at the bottom mean?
What to remember about NGINX
NGINX is open-source software that sits at the front of the server and receives every request to a website.
NGINX answers images, files and cached pages itself, and passes the rest, such as the cart and checkout, on to a backend like PHP.
NGINX is not hosting, a CMS or a CDN, but a program that runs on the server alongside them.
If you have managed hosting, NGINX is usually the responsibility of your hosting provider or developer, and you only need to make decisions about it if you run the server yourself.