Skip to main content
ModPageSpeed 2.0: AVIF, WebP, and critical CSS — up to 69% less page weight on the live demo

mod_pagespeed 1.1

mod_pagespeed, maintained again.

Google released its final release of mod_pagespeed in 2020. We picked it up. mod_pagespeed 1.1 is a drop-in replacement — same config, same filters, same behavior — with ongoing security patches, the new Cyclone Cache, and support from the people who know the codebase best.

Launch pricing — year one at half price on 1.1 and 2.0 · through June 16, 2026
Install mod_pagespeed 1.1 Upgrade Guide

Four web servers. One optimized codebase.

mod_pagespeed 1.1 runs as an in-process module — not a proxy, not a sidecar. Apache, nginx, and IIS ship today; Envoy is experimental.

Apache

Apache

GA

Drop-in replacement for the Google/Apache module

nginx

nginx

GA

Dynamic module — apt/dnf package for Ubuntu 24.04 & AlmaLinux 9

IIS

IIS

GA

Native Windows Server support

Envoy

Envoy

Experimental

HTTP filter for Envoy proxy

Install on Ubuntu 24.04 or AlmaLinux 9 

curl -fsSL https://packages.modpagespeed.com/install.sh | sudo sh

# nginx
sudo apt install nginx-module-pagespeed   # Ubuntu 24.04
sudo dnf install nginx-module-pagespeed   # AlmaLinux 9

# Apache
sudo apt install mod-pagespeed            # Ubuntu 24.04
sudo dnf install mod-pagespeed            # AlmaLinux 9

The signed apt/yum packages target each distro's stock nginx (Ubuntu 24.04 → nginx 1.24.0, AlmaLinux 9 → 1.20.1). On nginx.org stable or mainline, build the module from the source tarball instead.

What's changed since Google's last release

We picked up where Google left off and got to work. Everything below ships in 1.1.

Maintained and supported

Regular updates, security patches, and direct support from the team that knows the codebase best.

Drop-in replacement

Same configuration directives, same filters, same behavior. Swap the binary and you're done.

Cyclone Cache

New cache backend shared with ModPageSpeed 2.0. Fixed-size file, lock-free reads, memory-mapped I/O.

Bazel build system

Rebuilt with Bazel for reproducible builds. Pre-built binaries for major platforms — no more compiling from source.

Security fixes

All known CVEs from the open-source project patched. Ongoing security maintenance included.

Multi-platform

One source tree, four ports. Apache, nginx, and IIS ship today; Envoy is experimental.

Two products. Both maintained.

Both products are actively maintained. Pick the one that fits your situation.

In-process module

mod_pagespeed 1.1

Best for teams already running mod_pagespeed who want a supported, maintained release without changing their setup.

  • ✓ Drop-in compatible with open-source config
  • ✓ Apache, nginx & IIS today; Envoy experimental
  • ✓ In-process — no sidecar needed
Install mod_pagespeed 1.1

See the live admin console →

Out-of-process worker

ModPageSpeed 2.0

Ground-up rewrite in C++23. An async worker behind an nginx reverse proxy. Best for new deployments and teams that want the reverse-proxy or middleware model.

  • ✓ AVIF, SVG, and Jpegli image pipeline
  • ✓ ASP.NET Core middleware + Docker / nginx reverse proxy
  • ✓ Worker process + web console
Explore 2.0

Frequently asked questions

1.1-specific questions below. For the 2.0 architecture and integrations, see the 2.0 FAQ →

What counts as a server?
One license per machine running the module — whether that's nginx + worker (ModPageSpeed 2.0), an Apache, nginx, IIS, or Envoy host (mod_pagespeed 1.1), or an ASP.NET Core process. You can run the module unlicensed to evaluate it in any environment; contact sales@we-amp.com about non-production licensing or multi-server volume pricing.
What happens if I run unlicensed?
The engine keeps optimizing — it never locks you out. Unlicensed installs add an X-PageSpeed-Warn: unlicensed response header, show a notice in the admin console, and write a warning to the startup log. A commercial license is required for production use.
What happens after I cancel?
The engine keeps optimizing after your license expires — it never locks you out. The installation simply returns to the unlicensed state (the X-PageSpeed-Warn: unlicensed header, an admin-console notice, and a startup-log warning). Re-activate any time — your cache contents and configuration aren't touched.
Is there a free tier?
No free tier — a commercial license is required for production use. You can install and run the engine unlicensed to evaluate it: it optimizes fully and just adds an X-PageSpeed-Warn: unlicensed header. Buy a license from the admin console at /pagespeed_global_admin on your server when you're ready for production.
How does the license key work?
You receive an Ed25519-signed token via email. Set it as an environment variable. Signature validation runs offline at startup — no internet dependency in the request path. The product refreshes subscription state with our API every 12 hours; see Terms of Service for details.
mod_pagespeed is free. Why should I pay?
The original mod_pagespeed and ngx_pagespeed are no longer actively developed. We-Amp maintains both mod_pagespeed 1.1 (the drop-in continuation of the open-source project — CVE patches, modern nginx, IIS support) and ModPageSpeed 2.0 (the ground-up rewrite with zero-copy serving, variant-aware caching, and an out-of-process worker). Both come with direct email support.
What's your refund policy?
Subscriptions are billed immediately on purchase via FastSpring (our Merchant of Record). Cancel anytime through the FastSpring customer portal — billing stops at the end of the current period. Refund requests are handled by FastSpring under their standard refund policy. EU/EEA consumers have a 14-day right of withdrawal under EU Directive 2011/83/EU; see Terms of Service for details.
Is mod_pagespeed still maintained?
Yes. Google's final release shipped in 2020 and the GitHub repository was archived in 2025. Active development continued at We-Amp B.V. — a Dutch company founded by one of the former mod_pagespeed maintainers. mod_pagespeed 1.1 is the maintained continuation: drop-in compatible with the open-source release, with ongoing CVE patches, reproducible Bazel builds, and direct support.
Are the known CVEs against Google's last release patched?
Yes. mod_pagespeed 1.1 ships with patches for the known CVEs that accumulated against the archived upstream. Security maintenance is included with every license; if your security team needs a current CVE statement for procurement, contact us.
Will my existing pagespeed.conf keep working?
Yes. mod_pagespeed 1.1 is a drop-in continuation of the open-source project. All existing pagespeed directives work unchanged — swap the binary, keep your config.
How is 1.1 different from Google's last open-source release?
Same filters, same directives, same in-process architecture. What's added: ongoing CVE patches, a native IIS module, a GA nginx dynamic module (signed apt/yum packages for Ubuntu 24.04 and AlmaLinux 9), the Cyclone shared-memory cache (replacing the old file cache, no config change), and direct email support. Google's final release shipped in 2020 and the GitHub repository was archived in 2025; 1.1 is the actively maintained branch.
Which web servers does 1.1 support?
Apache (drop-in replacement), nginx (dynamic module), and IIS (native Windows Server module) all ship as GA packages today. The nginx packages target each distro's stock nginx — Ubuntu 24.04 and AlmaLinux 9 (amd64); for other nginx versions, build from the source tarball. Envoy (HTTP filter) is experimental.
What happens when my license expires?
mod_pagespeed keeps optimizing — it never locks you out. The installation returns to the unlicensed state and adds an X-PageSpeed-Warn: unlicensed response header (plus an admin-console notice and a startup-log warning). Your web server continues to function normally — no downtime, no data loss. A commercial license is required for production use.
Should I run 1.1 or ModPageSpeed 2.0?
Pick by deployment fit. Run 1.1 when you want a native in-process module inside Apache, nginx, or IIS with no separate worker and no added proxy hop, drop-in config compatibility, and the classic combine/sprite/IPRO filters with a built-in admin UI. Run ModPageSpeed 2.0 when you want an out-of-process worker behind an nginx reverse proxy fronting any HTTP origin (or ASP.NET Core middleware), with zero-copy serving, variant-aware caching, and a web console. Both are actively maintained, share the same optimization core and cache, and cost the same.
Is the license heartbeat the same as 2.0?
Yes. Both products share the same offline-validated Ed25519 license token and the same 12-hour heartbeat that refreshes subscription state with our API. No internet dependency in the request path; one license format works across both products.

Your mod_pagespeed. Maintained again.

Install and run it unlicensed — it fully optimizes and adds an X-PageSpeed-Warn: unlicensed header. Same config, same filters — swap the binary and you're optimizing again. A commercial license is required for production use.

Year one at half price — applies at checkout, ends June 16, 2026.
Install mod_pagespeed 1.1 Email the maintainer