What it is
HTTP and HTTPS proxies are built for web traffic: the browser asks the proxy to open a tunnel to a host and the proxy resolves the name. SOCKS5 sits lower: it carries any TCP stream, can relay UDP if the provider supports it, and lets the client choose whether the proxy resolves names.
Why it matters
The difference shows up in two places: DNS (who resolves names) and WebRTC (whether UDP travels through the proxy). A provider that does not support SOCKS5 UDP leaves WebRTC to be handled in the browser.
What to do
Use the type your provider documents for its gateway, then run the WebRTC and DNS tests with the proxy on.
In Clout Browser
A saved proxy in Clout Browser has a type (http, https or socks5), host, port and login, and a pasted list may carry optional http://, https:// or socks5:// prefixes.