Download
Download Squid Proxy Professional
The trial and the commercial release are the same binary - there is no separate trial build and no feature restrictions. Installing requires a licence key: request a free 30-day key, or activate a commercial licence you have already bought.
Windows installer
Squid Proxy Professional for Windows
Code-signed Windows installer including a Squid build compiled from source.
| Version | Coming soon |
|---|---|
| Squid version | Coming soon |
| Windows versions supported | Coming soon (Windows 10, Windows 11, and supported Windows Server editions) |
| Installer size | Coming soon |
| SHA-256 checksum | Coming soon |
| Code signing | The Windows installer is signed with a commercial code-signing certificate. SmartScreen and group-policy reputation will recognise the publisher once the release is in circulation. |
| Trial limitations | None on features. The evaluation runs the complete product for 30 days, and the 30 days begin when you activate rather than when the key is issued. When the evaluation ends, the Squid service will not start until a commercial licence is activated - a proxy already running is not interrupted, but it will not come back after a restart. Please do not point production traffic at a trial installation. |
| Release notes | Coming soon |
Verifying your download. When the build is published, the SHA-256 checksum will be listed above. On Windows, run
certutil -hashfile SquidProxyProSetup.exe SHA256 in PowerShell or Command Prompt and compare the output to the published value.
Install
Run the code-signed installer with administrator rights. The installer registers Squid as a Windows service with sensible defaults.
Activate
Enter your trial or commercial key in the management console. On a server with no desktop, run
squid-service.exe activate <key> instead. The service will not start without a licence.
Configure and start
Set your listener and ACLs, validate the configuration, then start the service.
Production deployments. Run a quick check against your environment first: confirm the listener port is free, allow the port through Windows Firewall, and configure clients before pointing production traffic at the proxy. The documentation covers each of these steps.