Polipo vs Squid vs Privoxy is a comparison people make when they want a proxy at home, in a lab or on a small server. All three sit between clients and the web, yet they were built for different jobs. Knowing those jobs makes the choice much easier than comparing feature lists alone.
This guide focuses on purpose, caching, filtering, resource use and maintenance. It avoids invented benchmarks, because performance depends heavily on hardware, traffic and configuration.
What Each Proxy Was Built For
The small caching proxy covered on this site was designed to be light and simple, using a single-threaded event loop. Squid is a long-established caching proxy built for anything from small offices to large networks, with extensive access control. Privoxy is a filtering proxy aimed at privacy and ad blocking, and it does not focus on caching.
| Aspect | Polipo | Squid | Privoxy |
|---|---|---|---|
| Main role | Lightweight caching proxy | Full-featured caching proxy | Filtering, privacy proxy |
| Caching | Yes, disk and memory | Yes, highly configurable | Not its focus |
| Content filtering | Basic URL blocking | Extensive ACLs | Rich filter and action rules |
| Resource use | Very modest | Varies with configuration | Modest |
| Maintenance | Archived, not maintained | Actively developed | Actively developed |
Caching Compared
Both caching proxies store HTTP responses and respect freshness headers. The lightweight option offers a compact set of cache controls that are easy to understand. Squid offers far more control over storage layouts, replacement policies and cache rules, which suits larger or more demanding deployments.
Privoxy is usually placed in front of or behind another proxy when caching is also needed. On its own, it modifies and filters traffic rather than storing responses for reuse.
Filtering and Privacy
For blocking trackers and adjusting headers, Privoxy is the specialist. It uses action and filter files to change requests and pages. The lightweight caching proxy can remove selected headers and refuse listed URLs, which covers simple needs, while Squid's access control lists handle policy rules at network scale.
- Header control: all three can alter or strip headers to different degrees.
- Ad and tracker blocking: Privoxy's main strength.
- Policy by user or network: Squid's access control lists.
Resource Use and Hardware
The single-threaded design of the smallest option made it a favourite on older hardware and small boards. Privoxy is also light. Squid can run on modest machines, though large caches and many rules naturally need more memory and disk.
For a single user or a few devices, any of them will run comfortably on current hardware. The deciding factor is usually features and maintenance rather than raw resource use.
Maintenance and Security
This is the biggest practical difference. The lightweight caching proxy's repository is archived and the author states it is no longer maintained. Squid and Privoxy continue to receive updates. For anything exposed to other users or the internet, an actively maintained proxy is the responsible choice.
The older project still has value for learning, testing and private experiments, where its small codebase is an advantage. Read our safety article for precautions if you decide to run it.
Setup Effort
The lightweight proxy has a short configuration file and works with a few lines, as shown in the configuration guide. Privoxy also starts easily, with most effort going into filter rules. Squid's configuration is longer because it exposes many more options.
| Need | Best fit |
|---|---|
| Learn how caching proxies work | Polipo, thanks to its small codebase |
| Office or campus caching with policies | Squid |
| Block ads and trackers at home | Privoxy |
| Long-term, maintained production proxy | Squid or Privoxy, depending on the goal |
Combining Proxies
Proxies can be chained. A filtering proxy can forward to a caching proxy, or a caching proxy can use an upstream through its parent settings. Chaining adds complexity, so do it only when each layer has a clear job, and test the full path carefully.
Making the Decision
Start from the problem you want to solve. If you need caching for a network with rules, choose Squid. If you need privacy filtering, choose Privoxy. If you want to study a compact caching proxy or experiment on a private machine, the lightweight option remains an interesting choice.
Learning Value
For students, the smallest of the three offers something the others do not: a codebase that one person can read and understand in a reasonable time. Reading how it parses requests, manages connections and stores objects teaches core HTTP caching ideas that apply to every proxy.
Squid's source is far larger and reflects decades of features and platforms. It is excellent for production but harder to study as a first example. Privoxy's code is approachable too, though it teaches filtering rather than caching.
Matching Proxies to Hardware
| Hardware | Reasonable choice | Notes |
|---|---|---|
| Small board or old laptop | Polipo or Privoxy | Both are modest; prefer maintained software for exposed roles |
| Home server | Any of the three | Choose by purpose: caching or filtering |
| Office or campus server | Squid | Access control and maintained releases matter |
Hardware rarely decides the question on its own. Even a small board runs any of these proxies for a handful of users, so purpose and maintenance status should carry more weight than raw resource figures.
Proxy Comparison FAQs
Privoxy focuses on filtering and privacy rather than caching. It is often combined with a caching proxy when both are needed.
Both the lightweight caching proxy and Privoxy are modest. Actual usage depends on configuration and traffic.
Squid has a longer configuration because it offers many more options, but simple setups are still manageable.
Yes. Proxies can be chained through parent or forwarding settings, as long as each layer has a clear purpose.
Conclusion
Polipo vs Squid vs Privoxy is really a choice between three purposes: compact caching for study and small setups, full-featured maintained caching, and privacy filtering. Match the tool to the task and weigh maintenance heavily for anything others depend on.
If you still want to try the lightweight option, the installation guide shows how to get it running quickly.
