Routing a 5G line through your media and QA stack
A line from 5G Proxies USA presents itself to software as a plain proxy: one host, an HTTP port, a SOCKS5 port, a username and a password. Any tool that can speak to a proxy can send its traffic over a US carrier's 5G. The catch with throughput-heavy work is that the tool has to be set up so the heavy part actually goes through the line, not just the first request. This page covers the tools media and QA teams ask us about most, with the setup for each, starting with the two profile browsers we recommend, Undetectable.io and then GoLogin, and moving on to system-wide proxies, phones, scripts, media command-line tools, browser automation and streaming QA.
Undetectable.io
Anti-detect browserThe profile browser we recommend first. Each profile has its own fingerprint, its own storage and its own proxy, and the built-in check reports the carrier, city and connection type before the profile opens. For media QA it means a reviewer can keep one profile per carrier line and compare how a player or an ad slot renders on T-Mobile versus Verizon from the same desk. The free tier is enough to prove the pairing with a 5G line before you commit to a team plan.
- Install Undetectable.io on Windows or Mac and sign in.
- In the 5G Proxies USA dashboard open the line and note the host, the HTTP or SOCKS5 port, the username and the password.
- Create a new profile, open the proxy tab, pick the protocol that matches the port, enter the four values and run the check.
- When the check reports your carrier and city, match the profile's time zone and language to that city and save.
- Open the profile, load an IP check page to confirm the address, then start the session you want to test.
- Keep one profile per line. Two profiles sharing a line look like one device to the sites you visit.
- Trigger rotation between sessions from the dashboard, not while a profile is mid-flow.
GoLogin
Anti-detect browserOur second recommendation, and the better fit when the team runs Linux, wants profiles on an Android phone, or shares profiles between reviewers. The proxy is stored with the profile and checked before launch, so nobody opens a Verizon profile on a T-Mobile line by mistake. GoLogin also exposes a local API, which lets a QA pipeline launch a profile on a specific 5G line, run a scripted check and close it, without a person clicking anything.
- Install GoLogin on Windows, Mac, Linux or Android and create an account.
- Add a profile and let GoLogin generate a fingerprint for the operating system you want the site to see.
- Open the profile's proxy section, choose HTTP or SOCKS5, paste the line's host, port, username and password, and press check.
- Set time zone and language to the line's city, or let GoLogin derive them from the proxy.
- Launch the profile, confirm the address on an IP check page, and run the test.
- Use the local API to pair a profile with a line in automated runs; it removes the most common human error.
- Name profiles after the line and carrier so the mapping is obvious in a shared team.
FoxyProxy
Browser extensionA browser extension for Chrome and Firefox that switches proxies per tab, per site or by pattern. It is the quickest way to put a normal browser on a 5G line for a one-off check: watch a stream, load a landing page, measure a page from a US cellular address, then switch back. Patterns let you send only certain domains, say a CDN under test, through the line while everything else stays on your office connection.
- Install FoxyProxy from the Chrome Web Store or Firefox add-ons.
- Add a proxy with the line's host, the HTTP port, and the username and password from the dashboard.
- Choose the mode: use the proxy for all URLs, or add a pattern for the domains you want to route.
- Open an IP check page to confirm the carrier address, then run your check.
- Extensions do not control other applications. For system-wide routing use Proxifier instead.
Proxifier
System-wide proxy clientProxifier intercepts the network traffic of any application on Windows or Mac and sends it through a SOCKS5 or HTTP proxy, including software that has no proxy setting of its own. For media work that is the way to put a desktop streaming client, a download manager or an encoder on the 5G line without touching the application. Rules decide which programs go through the line, so a test tool can ride the carrier while your mail client stays local.
- Install Proxifier and add a proxy server using the line's host, SOCKS5 port, username and password.
- Run the built-in check to confirm the proxy answers.
- Create a rule that names the applications to route, for example the player or encoder under test, and set it to use the line.
- Start the application and confirm in Proxifier's log that its connections are going through the proxy.
- Use SOCKS5 for anything that needs UDP; HTTP proxies carry TCP only.
- Leave the default rule on direct so unrelated traffic does not count against your line's fair use.
Shadowrocket
iPhone and iPad proxy clientA paid iOS app that routes the whole device, or selected apps and domains, through a SOCKS5 or HTTP proxy. QA teams use it to test how an iPhone app or a mobile web player behaves on a US carrier's 5G when the device itself is somewhere else. Rules can be set by domain, so only the app under test uses the line.
- Install Shadowrocket from the App Store.
- Add a server of type SOCKS5 or HTTP with the line's host, port, username and password.
- Choose global routing to send everything through the line, or add rules for specific domains.
- Enable the connection, open an IP check page in Safari, and confirm the carrier address before testing.
- Turn the connection off when the test ends so background app traffic does not use the line.
Android Wi-Fi proxy
Built into AndroidAndroid can route a Wi-Fi connection's browser and most app traffic through an HTTP proxy with no extra software. It is the fastest way to point a test phone at a 5G line to check an Android app, a mobile site or an in-app video from a US cellular address. Some apps ignore the system proxy, so confirm with an IP check inside the app itself where possible.
- Open Wi-Fi settings, long-press the connected network and choose modify or advanced options.
- Set proxy to manual, enter the line's host and HTTP port, and save.
- Open the browser; when prompted, enter the line's username and password.
- Load an IP check page and confirm the carrier address, then open the app under test.
- For apps that bypass the system proxy, a per-app proxy client from the Play Store or a rooted test device is needed.
curl
Command lineThe standard command-line HTTP client, present on every Mac and Linux machine and on recent Windows. With one flag it sends a request through the line, which makes it the tool for a quick throughput check, for confirming what a server returns to a US cellular address, or for pulling a large file to measure how the 5G line performs. Its timing output shows connect time and time to first byte, the numbers that separate 5G from 4G in practice.
- Run curl with the proxy flag set to the line, for example --proxy http://user:pass@host:port, against an IP check URL.
- Confirm the carrier address in the response.
- Add the write-out option to print time to first byte and total time, then fetch a large file to see the line's throughput.
- Use --socks5-hostname instead of --proxy when the test needs DNS resolved on the carrier side.
- Run the same command from two lines in different cities to compare gateways for the same target.
Python requests
ScriptingThe usual HTTP library for Python scripts. A proxies dictionary with the line's credentials sends every call in a session through the carrier. For QA that means a script can fetch a video manifest, walk its segment list, time each download and flag stalls, all from a US 5G address, and then call the rotation link and repeat from a new one. Sessions keep cookies and connections, so logins and multi-step checks work as they would in a browser.
- Install requests and build a proxies dictionary with http and https entries pointing at the line's URL with credentials.
- Create a Session, assign the proxies, and request an IP check endpoint to confirm the carrier address.
- Write the check: fetch the resource, time it, assert on status and size.
- Call the rotation link from the dashboard between runs when a fresh address is needed.
- Use the socks extra and a socks5h scheme when DNS should resolve on the carrier side.
Command-line media tools
Media QAEncoders, stream probes and segment downloaders of the kind that take an HTTP proxy from an environment variable or a flag. Pointing one at a 5G line lets you probe a live stream, fetch a manifest and its segments, or measure a player's download pattern exactly as a US phone on that carrier would see it. Because these tools can move a lot of data quickly, they are the clearest demonstration of what the 5G tier adds over 4G, and also the tools most likely to brush against fair use if left running as a download pipe.
- Set the http_proxy and https_proxy environment variables to the line's URL with credentials, or pass the tool's proxy flag.
- Probe the stream or manifest first to confirm it loads from the carrier address.
- Run the measurement you need: segment timing, bitrate ladder, stall count, or a timed download of a fixed-length sample.
- Stop when the measurement is complete rather than leaving a stream running.
- Measure samples, not whole libraries. A continuous relay of a stream is bulk transfer and outside fair use.
Playwright
Browser automationA browser automation framework for Chromium, Firefox and WebKit that accepts a proxy per browser or per context. QA teams use it to script a page load, a login, a video play or a checkout on a 5G line and to capture timings, screenshots and network traces from a US cellular address. One browser can hold several contexts, each on a different line, so a single run can compare carriers or cities side by side.
- Launch the browser or create a context with the proxy option set to the line's server, username and password.
- Open an IP check page in the context and assert the carrier address before the real test.
- Script the flow, record network events and timings, and take screenshots at the checkpoints you care about.
- Close the context, rotate the line if the next run needs a new address, and repeat.
- Set the context's locale and time zone to the line's city so the browser and the address agree.
Streaming QA tools
Live streaming QADesktop broadcasting software of the OBS kind and the players used to verify a live feed do not usually have a proxy setting, but they run under Proxifier or behind a system proxy. Teams verifying that a live stream reaches viewers on a US carrier use a 5G line to receive the feed in a player, check latency and dropped frames, and confirm that geo-restricted content behaves as expected. Receiving a sample is QA; relaying a stream through the line for an audience is bulk transfer and is not what the line is for.
- Route the player or test client through the line with Proxifier or the operating system's proxy setting.
- Open the stream and confirm the viewer address is the carrier address.
- Record the metrics you need, such as startup time, buffering events and frame drops, for a fixed sample period.
- Stop the player at the end of the sample.
- Keep test windows short and scheduled; the 5G tier's headroom is for measurement, not for serving viewers.
The four values and the two ports
Every tool above asks for the same things: the line's host, a port, a username and a password. The dashboard shows two ports per line, one HTTP and one SOCKS5. Use HTTP for browsers and most HTTP libraries. Use SOCKS5 where the application needs UDP, where DNS should resolve on the carrier side, or where you are routing a whole program with Proxifier. The credentials are the same for both. Nothing changes when you rotate the address, so a configuration done once keeps working for the life of the plan.
Getting the heavy part onto the line
The mistake we see most in media QA setups is a proxy that catches the page but not the media. A browser extension routes the HTML, while the player's segment requests go out another way; a script sets the proxy on one session and a helper library opens its own. Always confirm from inside the thing that moves the data: an IP check in the app, a packet count in Proxifier's log, or a curl of a segment URL with the same proxy flag. When the check is right, the 5G tier's throughput shows up in your numbers; when it is wrong, you are measuring your office connection.
Fair use with fast tools
Our lines carry unlimited data, and the 5G tier can move a lot of it. That is for measuring, testing and verifying. Tools that can relay a live stream, mirror a library or run as a download pipe cross from QA into bulk transfer, which the fair-use rule in our terms does not allow, and such lines may be slowed, paused or suspended. The practical habit is simple: sample, measure, stop. If you are unsure whether a workload is on the right side of the line, describe it to [email protected] before you run it.
Integration questions
Which port should I use in a media tool?
HTTP for anything that is plain web requests; SOCKS5 when the tool needs UDP, wants DNS resolved on the carrier side, or is being routed whole by Proxifier. Both ports use the same username and password.
Can I compare two carriers in one test run?
Yes. Buy two lines, one per carrier, and give each its own profile, Playwright context or Proxifier rule. Run the same check through both and compare the timings.
Is streaming a video through the line allowed?
Watching and measuring a sample for QA is what the line is for. Relaying a stream to viewers, mirroring a library or running a continuous download is bulk transfer and falls outside fair use.