HTTP proxy speaks HTTP/HTTPS only. SOCKS proxy is protocol-agnostic — HTTP, WebSocket, arbitrary TCP. Comparison table and when-to-pick guide.
HTTP proxy for browser traffic that benefits from header inspection (caching, filtering, rewrites). SOCKS5 proxy for anything else — games, custom apps, non-HTTP TCP protocols.
HTTP proxy understands HTTP and HTTPS traffic and can inspect/rewrite headers. SOCKS (specifically SOCKS5) is protocol-agnostic — it forwards any TCP traffic without understanding it. HTTP for browser-focused work with header manipulation; SOCKS for anything else (games, custom apps, non-HTTP).
Side-by-side
Context
The two proxy protocols solve different problems. HTTP proxies grew out of caching and filtering use cases where the proxy needs to understand what it is forwarding. SOCKS grew out of firewall traversal for arbitrary protocols where the proxy just needs to forward bytes.
Pick HTTP proxy when
Pick SOCKS proxy when
What breaks if you pick wrong
Configuring an HTTP proxy for a game connection over UDP or a custom TCP protocol fails — the HTTP proxy does not know how to speak those. Configuring SOCKS5 for a corporate cache scenario means you lose the caching, because SOCKS does not understand HTTP semantics.
FAQ