SOCKS5 Proxies: Residential and Mobile IPs
ProxyField runs SOCKS5 on 412M+ residential and 10.2M+ mobile IPs in 195+ countries at the same price as HTTP, per GB and not per IP: residential traffic costs $2.95/GB for 1 GB, $2.79 from 10 GB, $2.65 from 50 GB, $2.49 from 100 GB, $2.29 from 250 GB, $2.09 from 500 GB and $1.95 from 1,000 GB, so 100 GB is $249.00 whether it runs through 10 IPs or 10,000; the tier rate applies to the whole purchase, there is no subscription and the traffic never expires. Mobile traffic costs $3.45/GB for 1 GB down to $2.45 from 1,000 GB. Start with the Easy Trial: 1 GB for $2.95.
- Country
- United States
- City
- New York
- Rotation
- per request
- Protocol
- HTTP · HTTPS · SOCKS5
$ curl -x socks5h://<login>:<password>@gate.proxyfield.io:7000 \
https://api.ipify.org - SOCKS5
- HTTP
- HTTPS on one gateway
- 412M+ residential / 10.2M+ mobile IPs
- 195+ countries, 21,000+ cities
- sticky sessions up to 36 h
- from $1.95/GB
UDP: yes on residential and on dedicated ISP IPs. ProxyField residential SOCKS5 relays UDP, such as HTTP/3 over QUIC, on gate.proxyfield.io:7000, the same port as every protocol, and a dedicated ISP IP relays UDP on its own SOCKS5 port; web pages, APIs and scrapers need only TCP, which SOCKS5 relays with its CONNECT command. Sticky sessions over SOCKS5: yes. Keep one residential IP for an hour with <login>-session-he9f2qga-ttl-3600 in the username, if you send a request at least every 2 minutes; sessions run from 30 s to 36 h, and for one IP over days, a dedicated ISP IP costs from $2.29 for 30 days.
SOCKS5 is a proxy protocol (RFC 1928) that relays your app's connections through the proxy's IP, with optional username/password authentication (RFC 1929); unlike an HTTP proxy, it does not read or rewrite the HTTP request. Every ProxyField residential and mobile IP works over SOCKS5, HTTP and HTTPS on one gateway, with a 99.6% success rate, according to our service data (the protocol among the proxy types: Types of Proxies: Residential, Datacenter, ISP and Mobile).
How much does a SOCKS5 proxy cost: per GB or per IP?
Per GB, a residential SOCKS5 proxy at ProxyField costs $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB, the same as HTTP, with no per-IP or per-port fee: 10 GB is $27.90, 100 GB $249.00 and 1,000 GB $1,950.00, whether the traffic runs through 10 IPs or 10,000. Paying per IP instead, a dedicated ISP IP costs from $2.29 for 30 days. The smallest purchase is 1 GB for $2.95; many providers make you buy 2 GB or more to start, and with ProxyField you can buy just 1 GB.
What the per-GB price buys: SOCKS5, HTTP and HTTPS on the same balance; 195+ countries and 21,000+ cities at one price per GB; a 99.6% success rate, according to our service data, on the same pool at 1 GB as at 1 TB; and traffic that never expires.
| Volume in one purchase | Residential per GB | Example | Total |
|---|---|---|---|
| 1–9 GB | $2.95 | 1 GB | $2.95 |
| 10–49 GB | $2.79 | 10 GB | $27.90 |
| 50–99 GB | $2.65 | 50 GB | $132.50 |
| 100–249 GB | $2.49 | 100 GB | $249.00 |
| 250–499 GB | $2.29 | 250 GB | $572.50 |
| 500–999 GB | $2.09 | 500 GB | $1,045.00 |
| 1,000+ GB | $1.95 | 1,000 GB | $1,950.00 |
Read moreShow less
Cheaper than the big brands' $4/GB at every volume: residential proxies cost $2.95/GB for 1 GB and fall to $1.95/GB from 1,000 GB, with no subscription. The tier rate applies to the whole purchase. From 1 TB, the price is individual: contact sales.
Mobile SOCKS5, on 5G, 4G and LTE carrier networks, costs $3.45/GB for 1 GB down to $2.45/GB from 1,000 GB.
What sets the price of a SOCKS5 proxy here:
| Factor | Effect on the price |
|---|---|
| Protocol: SOCKS5, HTTP or HTTPS | none: the same price per GB |
| IP type | residential $2.95 down to $1.95/GB; mobile $3.45 down to $2.45/GB |
| Volume in one purchase | 7 tiers; the tier rate applies to the whole purchase |
| Country, region or city targeting | none: the same price per GB |
| Number of IPs, threads or sessions | none: no per-IP or per-port fee, unlimited concurrent threads |
What a GB is, and what a month costs. You pay for traffic through the proxy, not for time or addresses. At an assumed 0.5 MB per page, 1 GB is about 2,000 pages, so a scraper that loads 20,000 pages a month uses about 10 GB ($27.90) and one that loads 200,000 uses about 100 GB ($249.00). Billed traffic counts both directions (upload and download), including a site's error responses; a connection the gateway refuses (407, 402, 502) costs nothing. Traffic never expires, so a month you don't use carries over.
What a GB is worth depends on the success rate. A request that fails and is retried uses traffic twice, so compare the success rate with the per-GB price: ProxyField's is 99.6%, according to our service data.
Per GB or per IP? Per GB buys traffic through the whole pool; per IP rents fixed addresses for a term.
| Item | Per GB (residential, mobile) | Per IP (dedicated ISP, dedicated datacenter IPv4) |
|---|---|---|
| You pay for | Traffic: 10 GB costs $27.90 whether it runs through 10 IPs or 10,000 | Each address for 30 days: ISP from $2.29, datacenter IPv4 $1.39 |
| IPs | A new IP on every request, or sticky 30 s to 36 h, in 195+ countries | The same IP for the whole 30 days |
| Best for | Many IPs with modest traffic each: scraping, SERP and price checks | One address used for days: one account per IP |
| Renewal | No subscription; traffic never expires | You renew in the dashboard; nothing renews automatically |
One way to compare: a dedicated ISP IP costs from $2.29 for 30 days, and residential traffic $2.95/GB. If one address moves less traffic in a month than the price of one ISP IP buys, or you need many addresses, per GB costs less; if you need the same address for weeks, per IP is the product. Dedicated datacenter and ISP IPs run over HTTP, HTTPS and SOCKS5. Rotating datacenter proxies run over HTTP, HTTPS and SOCKS5 on gate.proxyfield.io:7000.
What common jobs cost each way (residential per GB; dedicated ISP per IP for 30 days):
| Job | Per GB | Per IP | Which fits |
|---|---|---|---|
| A first test on your own target | 1 GB: $2.95 | 1 ISP IP: from $2.29 | Per GB: you test the whole pool, not one address |
| Scraping through thousands of IPs, 10 GB | $27.90 | Thousands of IPs: not practical | Per GB |
| 10 accounts, each on one fixed IP for 30 days | Not possible: a sticky session lasts at most 36 h | 10 ISP IPs at $2.29–$2.79: $22.90–$27.90 | Per IP |
| A monthly scraper, 100 GB | $249.00 | – | Per GB |
| 100 accounts, one fixed IP each | – | 100 ISP IPs at $2.29–$2.79: $229.00–$279.00 | Per IP |
| A large crawl, 1,000 GB | $1,950.00 | – | Per GB |
Easy Trial: 1 GB for $2.95
Easy Trial: 1 GB for $2.95 (mobile $3.45). No minimum purchase, no subscription, and the traffic never expires. You get the same pool and the same quality at 1 GB as at 1 TB: there is no separate trial pool. All purchases are final. In return, your traffic never expires: what you buy stays on your balance until you use it.
Easy Trial: 1 GB for $2.95.
Try for the price of 1 GB, no subscription, traffic never expires.
Does SOCKS5 support UDP, and do residential proxy providers allow it?
Yes. SOCKS5 relays UDP through its UDP ASSOCIATE command (RFC 1928, section 7), and ProxyField residential SOCKS5 relays UDP, such as HTTP/3 over QUIC, on gate.proxyfield.io:7000, the same host, port and login as HTTP and HTTPS. Providers differ: a provider's SOCKS5 can be TCP-only on some products, so ask which product relays UDP, and run the PySocks test below before you buy more than 1 GB (the Easy Trial, $2.95).
SOCKS5 and UDP by ProxyField product:
| Product | SOCKS5 | TCP (CONNECT): web pages, APIs, scrapers | UDP (UDP ASSOCIATE) |
|---|---|---|---|
| Residential (rotating) | Yes | Yes | Yes, on port 7000 |
| Mobile (5G/4G/LTE) | Yes | Yes | |
| Rotating datacenter | Yes, on gate.proxyfield.io:7000 | Yes | – |
| Dedicated ISP | Yes | Yes | Yes, on the IP's own SOCKS5 port |
| Dedicated datacenter IPv4 | Yes | Yes | – |
Read moreShow less
What to do, by the traffic you send:
- Web pages, APIs, scrapers, headless browsers: they need only TCP (CONNECT), which ProxyField SOCKS5 relays on every residential and mobile IP. You can buy for this today.
- HTTP/3 and QUIC, or other UDP such as DNS over UDP: you need a UDP relay. ProxyField residential SOCKS5 relays UDP on
gate.proxyfield.io:7000, and a dedicated ISP IP on its own SOCKS5 port; your client must send its UDP over SOCKS5 too, and whether a call or game app does depends on the app. Check it with the test below on the Easy Trial (1 GB for $2.95); the result table tells you what each answer means. - Over a TCP-only SOCKS5 proxy, browsers fall back from HTTP/3 to HTTP/2 over TCP and pages still load; what you lose is UDP traffic such as WebRTC through the proxy.
What needs UDP, and what does not:
| Traffic | SOCKS5 command | Needs UDP relay? |
|---|---|---|
| Web pages, APIs, scrapers, any TCP connection | CONNECT | No: every SOCKS5 client and server does this |
| DNS lookups | CONNECT with a hostname (socks5h://) | No: the proxy resolves the name, so no DNS packet leaves your machine |
| HTTP/3 (QUIC) | UDP ASSOCIATE | Browsers fall back to HTTP/2 over TCP when UDP is not relayed |
| WebRTC, voice and video calls, STUN | UDP ASSOCIATE | Yes |
| Online games, DNS over UDP to a chosen resolver | UDP ASSOCIATE | Yes |
WebRTC in browsers. A browser can send WebRTC traffic around a SOCKS5 proxy that relays only TCP, so a page may see your own IP through WebRTC. In a scraping or multi-account browser, turn WebRTC off or set it to proxied traffic only (Firefox: media.peerconnection.ice.proxy_only set to true; antidetect browsers have a WebRTC setting per profile).
Test UDP on any SOCKS5 proxy. Send one DNS query over UDP through the proxy with PySocks:
# pip install PySocks
import socket
import socks
s = socks.socksocket(socket.AF_INET, socket.SOCK_DGRAM)
s.set_proxy(socks.SOCKS5, "gate.proxyfield.io", 7000, username="<login>", password="<password>")
s.settimeout(10)
# DNS query for example.com (type A), sent over UDP to 1.1.1.1:53
query = bytes.fromhex("abcd01000001000000000000076578616d706c6503636f6d0000010001")
s.sendto(query, ("1.1.1.1", 53))
data, addr = s.recvfrom(512)
print(len(data), "bytes from", addr)What the result means. These are the generic replies of any SOCKS5 server (reply codes from RFC 1928, section 6; the messages are PySocks'), not a list of ProxyField gateway responses:
| What you see | Meaning | What to do |
|---|---|---|
... bytes from ('1.1.1.1', 53) | The proxy relays UDP | Use it for UDP traffic |
socks.SOCKS5Error: 0x07: Command not supported, or protocol error | The server does not offer UDP ASSOCIATE | UDP is refused; use the proxy for TCP only |
socks.SOCKS5Error: 0x02: Connection not allowed by ruleset | The server supports the command, but its policy blocks this request | Ask the provider which UDP destinations or ports it allows |
socket.timeout (TimeoutError in Python 3.10+) | The relay opened, but no datagram came back | Retry once before you conclude; a firewall on your side can drop UDP too |
Sticky sessions over SOCKS5: one residential IP for an hour
Yes: put -session-<id>-ttl-3600 in the username, as in <login>-session-he9f2qga-ttl-3600, and one residential IP holds for up to an hour over SOCKS5, if you send a request at least every 2 minutes. Traffic, not time, is billed: an hour as one visitor that loads 200 pages of 0.5 MB uses about 100 MB, about $0.30 at $2.95/GB. A session can be set to any length from 30 s to 36 h. Three limits decide whether it holds the whole hour:
Read moreShow less
- Default: a session set without
ttllasts 20 min. - Idle: a sticky IP that stays idle for 120 s is replaced.
- Node: the IP is held while its exit node is up; if the node drops, the gateway retries once with a new session and the IP may change.
# The same sticky username twice: both calls should print the same IP
curl -x "socks5h://<login>-session-he9f2qga-ttl-3600:<password>@gate.proxyfield.io:7000" https://api.ipify.org
curl -x "socks5h://<login>-session-he9f2qga-ttl-3600:<password>@gate.proxyfield.io:7000" https://api.ipify.orgExpected output: one IP address, the same on both lines (for example 203.0.113.24, an address from the documentation range, not a real exit IP). A new session id, such as -session-k7m2x9pq-, gets a new IP.
More username lines in the same format:
| You want | Username |
|---|---|
| One IP for an hour, any country | <login>-session-he9f2qga-ttl-3600 |
| A US IP for an hour | <login>-country-us-session-he9f2qga-ttl-3600 |
| A New York IP for 10 minutes | <login>-country-us-region-new_york-city-new_york-session-he9f2qga-ttl-600 |
| A Canberra IP for 36 h (the maximum) | <login>-country-au-region-australian_capital_territory-city-canberra-session-he9f2qga-ttl-129600 |
| A new IP on every request in Germany | <login>-country-de |
Every part after the login is optional, and SOCKS5 and HTTP set sessions the same way, in the username. The 1 h preset is one of seven (1, 5, 10 and 30 min, 1, 3 and 6 h), so "an hour or so" has a preset on either side: 30 min and 3 h.
| Preset | Typical use |
|---|---|
| New IP on every request | Crawling many independent pages |
| 1 min, 5 min, 10 min | A search with a few result pages; a short form |
| 30 min | A checkout or a multi-step flow from one region |
| 1 h | A login session or an hour of work as one visitor |
| 3 h, 6 h | A long app test or one account's working session |
| Longer than 36 h, or one IP for days | Not a session: a dedicated ISP proxy, from $2.29 per IP for 30 days. Dedicated datacenter and ISP IPs run over HTTP, HTTPS and SOCKS5. Rotating datacenter proxies run over HTTP, HTTPS and SOCKS5 on gate.proxyfield.io:7000. |
How long the IP holds. You set the session's length; the IP is not promised for every second of it. If a node slows down, traffic automatically moves to the next one, so a long job should check its exit IP now and then with the script below. A connection that breaks is not restored: your client reconnects with the same username, and the session keeps its IP while the exit node is up.
Check that the IP holds for the hour. Reuse one sticky username, send a request every minute (an IP idle for 120 s is replaced) and print the exit IP every 5 minutes:
# pip install "requests[socks]"
import time
import requests
STICKY_USER = "<login>-session-he9f2qga-ttl-3600" # one IP for up to 1 h
proxy = f"socks5h://{STICKY_USER}:<password>@gate.proxyfield.io:7000"
for minute in range(0, 61):
ip = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=30).text
if minute % 5 == 0:
print(minute, "min:", ip)
time.sleep(60) # stay under the 120 s idle limitThe same IP on every line means the session held. More: Rotating and sticky SOCKS5 sessions.
How a SOCKS5 connection works
It forwards your app's connection through the proxy's IP, so the destination sees the proxy's address, for any TCP traffic and not only web pages. It takes 4 steps:
-
Connect
Your client opens a TCP connection to the proxy and lists the authentication methods it supports.
-
Authenticate
The proxy picks one: username and password (RFC 1929), or no authentication when it accepts your IP.
-
Request
The client sends the destination host and port with the CONNECT command, or asks for a UDP relay with UDP ASSOCIATE.
-
Relay
The proxy opens the connection from its own IP and copies the bytes in both directions until one side closes it.
SOCKS5 on residential and mobile IPs
SOCKS5 is included on every tier, at no extra cost, on both residential and mobile IPs: one dashboard, one balance. The price is per GB of traffic, the same as for HTTP and HTTPS.
Volume tiers
residential from $1.95/GB · mobile from $2.45/GB
| Volume in one purchase | Residential, per GB | Mobile, per GB |
|---|---|---|
| 1–9 GB | $2.95 | $3.45 |
| 10–49 GB | $2.79 | $3.29 |
| 50–99 GB | $2.65 | $3.15 |
| 100–249 GB | $2.49 | $2.99 |
| 250–499 GB | $2.29 | $2.79 |
| 500–999 GB | $2.09 | $2.59 |
| 1,000+ GB | $1.95 | $2.45 |
| Item | Residential | Mobile (5G/4G/LTE) |
|---|---|---|
| IPs | 412M+, from real home internet providers (ISPs) | 10.2M+, on mobile carrier networks |
| Protocols | SOCKS5, HTTP, HTTPS | SOCKS5, HTTP, HTTPS |
| Targeting | Country, region (state), city | Country, region (state), city |
| Typical response | Under 1 s, according to our service data | Under 1.5 s, according to our service data |
| Sessions | New IP per request, or sticky from 30 s to 36 h | New IP per request, or sticky from 30 s to 36 h |
| Authentication | Username:password; IP whitelist | Username:password; IP whitelist |
| Price | $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB | $3.45/GB for 1 GB down to $2.45/GB from 1,000 GB |
The pool is clean for Google, checked and segmented. If a node slows down, traffic automatically moves to the next one. 24/7 live chat helps with setup.
More on Residential proxies, Mobile SOCKS5 proxies, Rotating and sticky SOCKS5 sessions, SOCKS5 proxies by country and SOCKS5 at the same price per GB.
How to use a SOCKS5 proxy
Use the gateway host and port with your username and password, and the socks5h:// scheme if you want the proxy to resolve hostnames.
-
Get your credentials
Once your payment is confirmed, your gateway, username and password, or IP allowlist, are in your account.
-
Set the proxy URL
Use
socks5h://<login>:<password>@gate.proxyfield.io:7000in your tool. The general format issocks5://login:password@host:port. SOCKS5 takes the same username and password; with the IP allowlist, use the port you set up in the dashboard. -
Test it
Use the Proxy checker: test a SOCKS5 proxy, or request api.ipify.org and check that the IP shown is not yours.
Read moreShow less
# cURL: proxy-side DNS with socks5h
curl -x socks5h://<login>:<password>@gate.proxyfield.io:7000 https://api.ipify.org
# The same with a US city in the username
curl -x socks5h://<login>-country-us-city-new_york:<password>@gate.proxyfield.io:7000 https://api.ipify.org# pip install "requests[socks]"
import requests
proxy = "socks5h://<login>:<password>@gate.proxyfield.io:7000"
r = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.text)Country, region, city, session and session time go in the username, as in the sticky-session table above; the targeting in the username works the same over SOCKS5. The targeting parameters and a quick start are in the docs in your account.
Port. SOCKS5 uses port 1080 by convention, but a provider can use any port; ProxyField's SOCKS5 runs on gate.proxyfield.io:7000, the same port as HTTP and HTTPS. More in What Is a Proxy Port?
Apps and browsers that take a SOCKS5 proxy
Most tools accept a SOCKS5 proxy: SOCKS5 in cURL, SOCKS5 in Firefox (a SOCKS v5 option with "Proxy DNS when using SOCKS v5"), SOCKS5 in antidetect browsers, Python libraries, Playwright and Puppeteer. Chrome takes no SOCKS5 username and password, so use an extension or a local forwarder, or IP whitelisting, which works over SOCKS5: SOCKS5 in Chrome. To build the settings for a tool, see the SOCKS5 configurator.
SOCKS5, HTTP and HTTPS on one gateway
Use SOCKS5 when your tool only speaks SOCKS or the traffic is not HTTP; use HTTP or HTTPS for web scraping and browsers. On ProxyField all three run on the same IPs at the same price per GB: see HTTP proxies. The protocols compared, including UDP, encryption and socks5 vs socks5h, are in SOCKS5 vs HTTP Proxy; the older protocol in SOCKS4 vs SOCKS5.
- UDP The SOCKS5 protocol can relay UDP, but each provider decides whether to; see Does SOCKS5 support UDP?.
- Encryption SOCKS5 itself does not encrypt traffic; use HTTPS to the website, so the TLS session runs end to end through the proxy.
- DNS With
socks5h://the proxy resolves the hostname; withsocks5://your client does.
What to check when you buy SOCKS5 proxies
Check 6 things. Here is ProxyField's answer for each.
- IP type Residential and mobile IPs are on home internet and carrier networks; datacenter IPs are on hosting networks. ProxyField also sells Datacenter proxies and Static residential (ISP) proxies. Dedicated datacenter and ISP IPs run over HTTP, HTTPS and SOCKS5. Rotating datacenter proxies run over HTTP, HTTPS and SOCKS5 on
gate.proxyfield.io:7000. - Authentication Many tools need username and password. ProxyField takes username:password or an IP whitelist; for SOCKS5 see the setup note above.
- UDP The protocol allows it; providers differ (see Does SOCKS5 support UDP?).
- Country targeting over SOCKS5 Choose a country, a region or a city, as with HTTP, across 195+ countries and 21,000+ cities. The targeting in the username works the same over SOCKS5.
- Price per GB or per IP Residential and mobile are priced per GB, with no subscription; the tier rate applies to the whole purchase, and traffic never expires.
- Session length Sticky from 30 s to 36 h (presets 1, 5, 10, 30 min and 1, 3, 6 h), or a new IP on every request.
What is SOCKS5 used for?
SOCKS5 carries traffic from tools that speak SOCKS but not HTTP proxying, scraping libraries, headless browsers and non-web TCP clients.
Typical lawful work: web scraping and public data collection, SEO and SERP monitoring across regions, price monitoring, ad verification, social media monitoring and regional website checks.
Payment, verification and acceptable use
- Payment USDT, BTC, ETH or 10 other coins, in US dollars; access opens once the payment is confirmed.
- Verification No identity verification for ordinary purchases, including crypto: sign up with an email address and buy. We may ask for verification if an account shows signs of abuse or breaks our Acceptable Use Policy.
- Data We don't record the content of your traffic or the pages you visit. We keep only the service data we need to count your traffic, keep the network running and handle abuse reports. Connection metadata is kept for up to 30 days.
- Use You may not use SOCKS5 to send spam or open mail ports, spread malware or attack systems.
SOCKS5 Proxies FAQ
24/7 support by live chat, including help with setup and integration.
How much does a SOCKS5 proxy cost?
ProxyField SOCKS5 proxies cost the same as HTTP: residential $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB, and mobile $3.45/GB down to $2.45/GB. The tier rate applies to the whole purchase, there is no subscription, and the traffic never expires.
How much does a SOCKS5 proxy cost if I buy residential traffic per GB instead of paying per IP?
Per GB you pay for traffic, with no per-IP or per-port fee: ProxyField residential SOCKS5 costs $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB, so 10 GB is $27.90, 100 GB $249.00 and 1,000 GB $1,950.00 whether it runs through 10 IPs or 10,000 (all tiers in the price table). Per IP, a dedicated ISP IP costs from $2.29 for 30 days. The smallest purchase is 1 GB ($2.95), the same price covers HTTP and city targeting, and the traffic never expires.
Which providers offer the best SOCKS5 residential proxies?
ProxyField runs SOCKS5 on all 412M+ residential IPs in 195+ countries, with a 99.6% success rate, according to our service data, at no extra cost over HTTP. When you compare providers, check SOCKS5 authentication, UDP support, targeting over SOCKS5 and session length, then test on your own target.
Where can I buy SOCKS5 proxies with residential IPs in a specific country?
From ProxyField: choose a country, a region or a city across 195+ countries, and all 50 US states, for SOCKS5 as for HTTP. Residential SOCKS5 traffic costs from $1.95/GB, and the Easy Trial is 1 GB for $2.95. The country goes in the username, as in the setup section above.
Do residential proxies support SOCKS5, or only HTTP?
ProxyField's residential and mobile proxies support both: every IP works over SOCKS5, HTTP and HTTPS on the same plan and at the same price per GB, from $1.95/GB.
When should I use SOCKS5 instead of HTTP?
Use SOCKS5 when your tool only speaks SOCKS, or the traffic is not HTTP, such as other TCP clients. For web scraping and browsers, HTTP or HTTPS is usually simpler. ProxyField gives you all three on the same IPs at the same price.
Do residential proxy providers allow UDP over SOCKS5?
ProxyField does: its residential SOCKS5 relays UDP, such as HTTP/3 over QUIC, on gate.proxyfield.io:7000, the same host and port as HTTP. Other providers differ, often by product: SOCKS5 relays UDP through the UDP ASSOCIATE command (RFC 1928), each provider decides whether its servers allow it, and a server that refuses answers with reply code 0x07, "Command not supported". Check your own client with the UDP test in the section above on the Easy Trial, 1 GB for $2.95.
What is a UDP proxy?
A UDP proxy relays datagrams, such as DNS queries, QUIC or voice traffic, instead of a TCP stream. A SOCKS5 client asks for a relay over TCP with UDP ASSOCIATE and then sends each datagram to it with a short header; a server that refuses answers with reply code 0x07.
How do I set up a SOCKS5 proxy in my tool?
Set the proxy URL in your tool as socks5h://<login>:<password>@gate.proxyfield.io:7000, or socks5:// if your client should resolve hostnames itself. Then request api.ipify.org and check that the IP shown is not yours.
How do I buy SOCKS5 proxies?
Sign up with an email address and buy residential or mobile traffic from 1 GB in USDT, BTC, ETH or 10 other coins; SOCKS5 is included on every tier. Once the payment is confirmed, your gateway and credentials are in the account.
Show 8 more questionsShow fewer questions
Do you offer HTTP, HTTPS and SOCKS5 support?
Yes: HTTP, HTTPS and SOCKS5 on residential and mobile IPs, on every tier, through one gateway, gate.proxyfield.io:7000.
Is SOCKS5 a residential proxy?
No. SOCKS5 is a protocol, and the IP type is separate: a SOCKS5 proxy can run on a residential, mobile or datacenter IP. ProxyField runs SOCKS5 on 412M+ residential and 10.2M+ mobile IPs.
Is SOCKS a good proxy?
For tools that speak SOCKS or carry non-web TCP traffic, yes: SOCKS5 relays any TCP connection and supports username and password authentication. It does not encrypt traffic by itself, so keep HTTPS to the site.
Is there a proxy app that uses SOCKS5?
Most tools take a SOCKS5 proxy: Firefox, cURL, Python libraries, Playwright, Puppeteer and most antidetect browsers. Chrome takes no SOCKS5 username and password, so use an extension or a local forwarder there.
Can I use SOCKS5 proxies in the terminal?
Yes. With cURL, pass the proxy URL: curl -x socks5h://<login>:<password>@gate.proxyfield.io:7000 https://api.ipify.org. More options are on the cURL proxy page.
Do sticky sessions work over SOCKS5, so I can keep one residential IP for an hour or so?
Yes: ProxyField keeps one residential IP for up to 1 hour over SOCKS5 with <login>-session-he9f2qga-ttl-3600 in the username, as for HTTP; sessions run from 30 seconds to 36 hours, and 20 minutes when no ttl is set. Send a request at least every 2 minutes, because a sticky IP idle for 120 s is replaced, and the IP is held while its exit node is up. An hour of 200 pages at 0.5 MB uses about 100 MB, about $0.30 of traffic; for one IP over days, a dedicated ISP IP costs from $2.29 for 30 days.
What port does a SOCKS5 proxy use?
Port 1080 by convention, but a provider can run SOCKS5 on any port. ProxyField runs SOCKS5 on port 7000 of gate.proxyfield.io, the same port as HTTP and HTTPS; test the line with cURL before you plug it into a tool.
Are free SOCKS5 proxies worth using?
Rarely. Free public SOCKS5 lists are open to anyone, often slow or dead, and you cannot tell who runs the server. ProxyField has no free plan; its smallest purchase is 1 GB for $2.95.
Related pages
Easy Trial: 1 GB for $2.95.
Try for the price of 1 GB, no subscription, traffic never expires.