Skip to main content

Pick your integration. Install in a few minutes.

Open source under the Apache License 2.0 — free to install and run, in development and in production.

After install, open the admin console at /pagespeed_global_admin on the server itself. The Apache package serves it to localhost out of the box; on nginx, turn it on first.

Apache, nginx, Docker, Helm, IIS & ASP.NET Core

Every way to run it, in one place. mod_pagespeed's native module installs on Apache and nginx from the signed apt/yum repository, or runs as a Docker container fronting nginx — deploy that with Helm on Kubernetes. Windows/IIS gets a signed installer from the GitHub release, and ASP.NET Core apps get a NuGet middleware or a Linux sidecar. Each card shows which package it comes from and how it integrates.

v2.5.2 see release notes

Apache

mod_pagespeed 2.5.2

Native module

Prebuilt signed package from the apt/yum repository — apt-get on Debian and Ubuntu, dnf on Enterprise Linux. Drop-in replacement for the open-source build.

Debian 12/13, Ubuntu 22.04/24.04 (amd64 + arm64); RHEL/AlmaLinux/Rocky 9 (x86_64 + aarch64) & 10 (x86_64); Apache 2.4+.

Repo setup guide

nginx

mod_pagespeed 2.5.2

Native module

Prebuilt signed dynamic module from the apt/yum repository, pinned to each distro's stock nginx. Loads alongside your existing nginx binary — no rebuild, no traffic detour.

Debian 12/13, Ubuntu 22.04/24.04 (amd64 + arm64); RHEL/AlmaLinux/Rocky 9 (x86_64 + aarch64) via dnf, EL10 (x86_64). Each module is pinned to its distro's exact stock nginx — running a different nginx version? Contact us for a matching build.

Repo setup guide

nginx (Docker)

mod_pagespeed 2.5.2

Reverse proxy

Run the optimizer worker and an nginx with the thin nginx module as Docker containers in front of your origin. The image brings its own nginx and module, so your nginx binary and config stay as they are.

Any host with Docker 24+ (Linux, macOS, Windows). Images: ghcr.io/we-amp/pagespeed-nginx:2.5.2 and ghcr.io/we-amp/pagespeed-worker:2.5.2.

Install guide

Helm

mod_pagespeed 2.5.2

Kubernetes

Official Helm chart deploys nginx and the worker as a two-container pod, sharing a Cyclone cache volume. Pulls the public images directly — no registry credentials required.

Kubernetes 1.28+, Helm 3.12+. Chart: pagespeed (https://modpagespeed.com/charts).

Helm guide

IIS

mod_pagespeed 2.5.2

Native module

MSI installer for Windows Server. Enable in IIS Manager, iisreset, and the optimization pipeline is live.

Running IISpeed? Uninstall it first — both modules cannot coexist on the same host. The installer takes every IIS site on the server down while it runs; see the maintenance-window note in the install guide.

Windows Server 2016 or later, IIS 10, x64

Install guide

ASP.NET Core

mod_pagespeed 2.5.2

NuGet middleware

Two lines in Program.cs add the optimization pipeline to any ASP.NET Core app. Runs in-process — no sidecar, no Docker.

.NET 8 or .NET 10 on Windows, Linux, or macOS.

Install guide

ASP.NET Core Sidecar

mod_pagespeed 1.15

NuGet · Linux

WeAmp.PageSpeed.Sidecar adds the 1.15 module to your Kestrel app via middleware, with a bundled nginx optimizer on loopback behind it. One dotnet add package pulls the native binaries.

Now GA. Want the classic 1.x nginx-module behavior under .NET? Start here.

.NET 8 or .NET 10 on Linux (linux-x64, linux-arm64).

Sidecar guide

Also available: the Envoy HTTP filter (experimental, built from source) and the WordPress plugin.

The Apache and nginx packages keep their existing 1.15-line names — your apt/dnf upgrades them in place, no rename needed.

Direct downloads

The supported way to install is the signed package repositories; for IIS, download the Windows installer (2.5.2, hosted on the module's GitHub release beside its SHA256SUMS) and follow the install guide; the installer takes every IIS site on the server down while it runs, so read its maintenance-window note first. The worker packages (deb, rpm and Windows zip, with a checksum list) of every release are on the project's release listing.

Verifying the Windows installer. The release's SHA256SUMS.asc is a GPG signature of its SHA256SUMS, made with the release signing key (fingerprint 411D EFDB 5713 51D2 B25A EFCC 9C02 B5BD CCE7 5313): the signature verifies the checksum file, and the checksum file then verifies the MSI. The steps are in Verifying a Release. On Windows, the MSI's own Authenticode signature, publisher "We-Amp B.V.", remains the check for the installer itself.

The apt and dnf repositories are signed with a different key, the repository signing key (fingerprint DF00 E296 BE91 41CE A541 1346 F50D 6054 F107 12A0), which the apt/yum page sets up; it does not sign the GitHub release files.

An older key, fingerprint A358 2703 1804 5B75 C552 FEA8 DA8F EBD5 000B C194, signed the 1.x direct downloads (per-file .asc) and the source tags v2.1.0 to v2.4.0. It signs nothing new from 20 October 2026 and is being revoked: use it only to check those older signatures, and treat any signature it made after that date as not ours.

Versions

The version each artifact carries, per release. The current release is mod_pagespeed 2.5.2.

Release Date apt/yum packages (module + optimizer worker) Container images Helm chart (app version) NuGet WeAmp.PageSpeed.AspNetCore IIS installer
2.5.2 current 2026-10-222.5.22.5.20.3.11 (2.5.2)2.5.2pagespeed-iis-2.5.2-win-x64.msi
2.5.0 2026-10-192.5.02.5.00.3.9 (2.5.0)2.5.0pagespeed-iis-2.5.0-win-x64.msi
2.4.0 2026-10-141.19.02.4.00.3.8 (2.4.0)2.4.0not on a public release
2.3.0 2026-10-121.18.02.3.00.3.7 (2.3.0)2.3.0not on a public release
2.2.0 2026-10-061.17.02.2.00.3.6 (2.2.0)2.2.0not on a public release
2.1.0 2026-09-171.16.0nonenone2.1.0not on a public release

From 2.5.0 on, one number names the release on every artifact; only the Helm chart keeps its own chart version and carries the release as its application version. The ASP.NET Core Sidecar (WeAmp.PageSpeed.Sidecar) is versioned on its own; the current package is 1.17.0.

Other integration paths

Running nginx specifically? ngxpagespeed.com has the nginx install walkthrough.

IISpeed customer? Contact us about moving to mod_pagespeed — IIS deployments run on the native Windows module, a signed installer on the mod_pagespeed GitHub release. Arrange your no-cost transfer.

How licensing and support work

Pricing
Free — open source under the Apache License 2.0, with no usage registration. What We-Amp sells is support; Priority and Enterprise add a private package repository (being set up). No per-request fees, no bandwidth metering.
Evaluation
There is nothing to evaluate against a clock — the software is free, in full, under Apache-2.0. Install it, measure the results on your own pages, and add a support plan when you want support from the people who build it.
Hosting
Runs on your servers. No third-party proxy, no CDN dependency, no external service in your request path. The software is open source under the Apache License 2.0.

Search