Tools That Run on a USA 5G Proxies Line, and the Settings That Keep Them Fast
Everything on this page connects to a USA 5G Proxies line the same way: with the host, ports and login printed on the line's card at fast.usa5gproxies.com, or, on server-based lines, with the card's VLESS link when a whole device should go through the line. The tools are the ones our customers ask about most, each with the settings that matter and one extra line per tool: the setting that stops the tool from throwing away the line's download speed. Browsers for separate identities come first, then the tunnel clients, a router recipe, media and automation tools, and the speed test to check it all.
Undetectable.io
Profile browserThe browser we recommend first for keeping identities apart on Windows and Mac: every profile carries its own fingerprint, storage and proxy, the proxy manager keeps one line entry shared by many profiles, and a pre-launch test reports the carrier and city. The free tier is enough for a few profiles on a few lines.
- Install the browser, sign in, open its proxy manager and add an entry of type SOCKS5 with the host, SOCKS5 port and login from the line's card, named after the metro and carrier.
- Run the entry's test and read the country, carrier and city it reports.
- Make a new profile, pick the operating system it should present, and point it at the stored entry.
- Let time zone and geolocation follow the proxy; set the language to US English.
- Start the profile, load an IP lookup page to see the carrier address, then run a download test inside it.
- Keep hardware acceleration switched on; video inside the profile needs it to use the 5G speed.
- Two or three live profiles on one 5G line is comfortable, more once 5G+ is attached.
GoLogin
Profile browserThe alternative we recommend, and the natural pick on Linux or in a team: profiles are stored in GoLogin's cloud with their proxy, open from any desktop or the Android app, and a pre-launch check shows the line is up and in the right city.
- Install GoLogin on your platform and sign in.
- Add a profile, keeping the fingerprint GoLogin generates for the chosen operating system.
- Under Proxy pick SOCKS5 and fill in host, port and login, or drop in the host:port:login string from the card.
- Press Check proxy and read the US flag, the carrier and a city in the line's state.
- Keep time zone and geolocation on Based on IP, set language to en-US, save, run.
- One folder per line, named for its metro, keeps related profiles together and unrelated ones apart.
- Launching a profile from the Android app routes that phone through the same line.
v2rayN
VLESS client, WindowsA free Windows client for the Xray protocol family. It imports the line's vless:// link from the clipboard and routes the whole PC, or only chosen applications, through the 5G line.
- Copy the VLESS link from the line's card in the dashboard.
- In v2rayN choose Import from clipboard; the server appears in the list.
- Select it, set the system proxy mode you want, and connect.
- Open an IP lookup page in any browser and confirm the carrier and metro.
- Run a download test to see the 5G figure through the tunnel.
- Use the routing rules to send only US-bound applications through the tunnel so local traffic stays direct.
- The link does not change on rotation; the client reconnects by itself.
Hiddify
VLESS client, Android, macOS, LinuxA free, open-source client that imports a vless:// link and carries the whole device through the line. The Android build is the simplest way to put a test phone on a US 5G address.
- Copy the VLESS link from the line's card.
- In Hiddify choose Add profile and paste the link.
- Connect, then open an IP lookup page on the device and confirm the carrier and metro.
- Run a download test in a browser on the device.
- Turn on per-app routing so only the apps under test use the tunnel; it keeps the rest of the phone fast.
- Keep the link private; reissue it from the dashboard if it may have been shared.
Shadowrocket
VLESS client, iOSThe usual iPhone and iPad client for the Xray family. It imports the line's vless:// link and routes the device through the 5G line with per-app and per-domain rules.
- Copy the VLESS link from the line's card.
- In Shadowrocket tap Add Server and paste the link.
- Connect and open an IP lookup page in Safari to confirm the carrier and metro.
- Run a download test from Safari to see the figure through the tunnel.
- Set the global routing to Proxy for a full-device test, or add rules for the US apps only.
- Streaming apps tested through Shadowrocket play at the line's own speed, so a 5G+ line shows its difference here.
OpenWrt router with sing-box
Whole-office routingA router running OpenWrt can run sing-box or Xray as a client, so every device on a Wi-Fi network leaves on the 5G line without any per-device setup. The right shape for a small QA lab or an office that wants one US exit.
- Install the sing-box or Xray package on the OpenWrt router.
- Convert the line's VLESS link into the client configuration using the fields in the link.
- Add a routing rule that sends the test network's traffic through the tunnel.
- From a device on that network, confirm the carrier address on an IP lookup page and run a download test.
- A router CPU can be the bottleneck for encryption; test the figure from a laptop on the same line before blaming the line.
- Everyone on the network shares one public address, so use it where that is intended.
ffmpeg and ffprobe
Media tools, command lineThe standard command-line tools for probing and recording streams. Through the line they measure what a US 5G player receives: bitrate ladders, segment timing, and stalls, with no browser in the way.
- Export the line's HTTP proxy as an environment variable in the shell: http_proxy and https_proxy set to http://user:pass@host:port.
- Run ffprobe against the stream manifest you are entitled to test to list its variants and bitrates.
- Record a short segment with ffmpeg and watch the throughput it reports.
- Note the achieved bitrate and how steady it stays.
- Use the SOCKS5 port through a wrapper such as proxychains when the tool's HTTP proxy support is not enough.
- Only probe streams you are licensed to test; the tool does not change what you are allowed to access.
Playwright
Browser automationPlaywright drives Chromium, Firefox and WebKit from Node, Python, Java or .NET, with a proxy set per browser context, and is the usual choice for scripted QA on a US 5G address.
- Launch the browser with a proxy option of the form socks5://host:port and pass the username and password as proxy credentials.
- Set the context's timezoneId to the metro's zone and locale to en-US.
- Open an IP lookup page first and assert the carrier before the test proceeds.
- Run the scripted flow and capture screenshots, videos or traces as needed.
- Keep hardware acceleration enabled in headed mode when recording video playback.
- Run several contexts on one 5G line only when they belong to the same identity.
Python requests and curl
Scripts and quick checksFor single requests and collection scripts. Both accept an authenticated SOCKS5 or HTTP proxy and are the quickest way to confirm a line is live from a terminal.
- With curl, add -x socks5h://login@host:port and fetch an IP lookup endpoint; the h in socks5h sends DNS through the line.
- With requests, install the socks extra and put socks5h://login@host:port in the proxies mapping for both schemes.
- Read the organisation and country in the reply before the script goes further.
- Keep the request pace within the target site's rules; a fast line is not a licence to hammer a site.
- A collection script waits on the target site, not on the line; the 4G tier is usually enough for it.
- Call the rotation link between batches and re-check the address before continuing.
Speedtest CLI
MeasurementOokla's command-line speed test, run through the line, gives you a figure from your own side of the connection. It is the simplest way to see what the 5G tier and 5G+ deliver from your side.
- Route the terminal through the line with proxychains and the SOCKS5 port, or run the test from a device on a VLESS tunnel.
- Choose a server in the line's metro so the measurement does not include a cross-country hop inside the US.
- Run the test three times and take the middle figure.
- Subtract the effect of your own connection to the US, visible as the gap between a direct test and the tunnelled one.
- A test from a slow local connection measures that connection; test from a fast one or compare trends.
- Your figure includes the distance to the metro as well as the line.
Two rules for every tool
Two things hold for every entry below. One: the line changes where your traffic exits and nothing else. Clock, language, screen and location permission belong to the tool or the device, and they should agree with the metro the line sits in, Central for Houston and Chicago, Eastern for New York, Boston, Miami and North Carolina, Mountain for Phoenix, Pacific for Los Angeles. Two: when a tool offers SOCKS5 or a tunnel, take it over the plain HTTP port. SOCKS5 carries UDP and resolves names inside the line, a VLESS tunnel moves the entire device, and neither relies on the tool's own HTTP plumbing. One login serves both proxy ports.
Where speed is lost, and how not to lose it
A fast 5G line can feel slow inside a badly configured tool. The usual culprits are a browser profile with hardware acceleration off, a VLESS client with routing rules that send local traffic through the tunnel too, a download tool with a single connection where the server allows several, and a speed test run from a laptop on hotel Wi-Fi that is itself the bottleneck. Each tool entry below names its own fix. Remember your own path to the US metro is part of any figure you measure.
Rotation, moves and 5G+ with these tools
Rotation is invisible to every tool here. Fire it from the dashboard, the rotation link, the API or a schedule, and whatever connects next simply exits on the new address; close browser profiles first. After a free move to another metro, edit the stored proxy once and the clock setting beside it. Adding 5G+ touches no setting anywhere; it changes what arrives through the line.
Integration questions
Where should a newcomer begin?
A browser profile in Undetectable.io for identity work, Hiddify or Shadowrocket to put a test phone on the line, and curl to prove the line is up from a terminal.
Are the logins different for HTTP, SOCKS5 and VLESS?
The two proxy ports share one username and password; the VLESS link carries its own identity inside the link itself.
May several tools run on one line together?
Yes, up to the line's connection limit, all exiting on the same carrier address. A 5G line has room for several.
My tool measures less than the dashboard says. Why?
The dashboard measures at the device in the US; your tool also crosses your own connection to that metro. Check the tool's settings first and compare trends rather than single figures.