Skip to content
RU

Web server shares in 2026: why nginx is 14% and 44% at the same time

TL;DR. Within a single Netcraft report for July 2026, nginx’s share is 14.45%, 20.37% and 43.92%.

Within a single Netcraft report for July 2026, nginx’s share is 14.45%, 20.37% and 43.92%. All three are correct — they answer different questions. W3Techs, the same month, says 31.3%, and that is not an error either.

Below: what each source actually counts, why they differ fourfold on LiteSpeed, and what is known about the Russian segment, where nginx holds 85.9% of the .ru zone.

Check your site's headers →

Why nginx has five different shares at once

Netcraft’s July 2026 survey publishes five populations, and nginx looks different in each — inside one report:

PopulationSizenginxApacheCloudflare
All hostnames1,494,915,62820.37%11.50%16.67%
Active sites14.45%12.10%23.46%
Domains305,348,45917.57%15.51%14.02%
Top million busiest1,000,00020.02%15.56%28.29%
Web-facing computers14,772,04843.92%18.82%

From 14.45% to 43.92% — a threefold spread, and every figure is correct. They answer different questions: on how many names, on how many live sites, on how many physical machines. Any lone "nginx share is X%" without a named population is meaningless.

Worth remembering separately: in the all-names view the "other" bucket holds 34% — more than any named vendor. A four-slice pie chart implies a completeness that does not exist.

A second source gives figures twice as large — and it is not wrong

W3Techs as of 27 August 2026:

ServerW3TechsNetcraft, all names
Nginx31.3%20.37%
Cloudflare Server29.7%16.67%
Apache22.6%11.50%
LiteSpeed14.8%3.88% (top million)
Node.js7.0%
Microsoft-IIS3.1%5.73% (computers)
Caddy0.8%not broken out

The causes are methodological, not errors:

  • Different universes. Netcraft probes 1.49 billion hostnames, most of them parked or machine-generated. W3Techs deliberately excludes those and works with 20M+ sites that carry content. Apache and LiteSpeed sit mostly on live shared-hosting sites and therefore roughly double in W3Techs.
  • LiteSpeed is the sharpest divergence (3.88% vs 14.8%). It concentrates in cPanel hosting: dense in W3Techs’ population, near-invisible across Netcraft’s sea of names.
  • W3Techs allows several servers per site — its column sums to about 111%, so it is not a partition of a whole at all. Netcraft assigns one server per name.
  • Both count reverse proxies as servers. An Apache site behind Cloudflare is recorded as Cloudflare. What runs at the origin is measured by nobody.

No single honest "web server market share" can be derived from these sources. The correct presentation is both, side by side, with populations named — not a winner.

Russia: nginx takes almost everything

W3Techs offers two Russian cuts as of 27 August 2026, and they are different populations rather than two estimates of one:

Server.ru zoneSites hosted in Russia
Nginx85.9%89.2%
Apache6.8%7.0%
Node.js4.1%4.1%

A .ru domain on German hosting lands in the first column and not the second; a .com run from Moscow, the reverse. The denominator for both is sites whose server could be identified, not all sites in the segment.

Source limitation: only the top three positions per segment are published free. There is no open figure for LiteSpeed, IIS, Cloudflare or Angie in Russia — not from W3Techs, not Netcraft, not Cloudflare Radar.

On Angie, the Russian nginx fork: W3Techs tracks it but shows it in the tail below 0.1%. No more precise public figure exists, despite the project’s visibility in the trade press.

Two traps when reading surveys like these

Jumps that are not growth. In the domains view OpenResty gained 9.01 percentage points in a single month — from 15.1 to 42.7 million domains. Organic growth does not look like that: almost certainly one large host changed a header. Narrating it as a trend is a mistake.

Both figures move. W3Techs updates daily, Netcraft monthly. Any share without a retrieval date goes stale silently. That is exactly how statistics turn wrong: a figure from two years ago keeps circulating through listicles labelled "2026".

And one note on what these data do not contain at all: contrary to common belief, HTTP Archive and the Web Almanac have no web server chapter. Raw Server headers exist in their dataset, but no published statistic does.

To see what your own site sends, use the response header check.

Learn more

Frequently Asked Questions

nginx or Apache — which one?

nginx — for high-concurrency (reverse proxy, static files). Apache — for CMS with .htaccess (WordPress, Drupal) and legacy PHP apps. For a new 2026 project — nginx default.

Is Caddy a serious competitor?

Yes, for small-mid projects. Automatic Let's Encrypt, simple config. Downsides: smaller community, fewer docs, slower for extreme scale.

Is IIS still relevant?

Only for Windows-specific workflows (Exchange, SharePoint, legacy .NET). On Linux no reason to use IIS.

How to tell my server?

Enterno HTTP checker shows Server header + Via + X-Powered-By. Or curl -I https://example.com.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.