Use Proxies in Browser Automation Tools

Many browser automation and profile tools accept one proxy per profile, one proxy per worker, or an imported proxy list. Thunderproxy supports each workflow as long as the tool receives the format it expects.

Quick answer: generate the proxy line in Thunderproxy first, test one line with cURL, then import the same values into your browser tool using its required format.

Choose the right Thunderproxy source

Workflow	Best Thunderproxy source
One browser profile	Quick Access proxy string
Many browser profiles	Exported proxy list
Many workers or scrapers	Exported proxy list or API link
Dedicated static IP per profile	Static ISP proxy table or export

Use Rotating Residential or Rotating Datacenter when you want pool access with location and session settings. Use Static ISP when each profile needs a dedicated static IP from a table row.

Set up one browser profile

1. Open the subscription in the Thunderproxy dashboard.
2. Choose location, protocol, and rotation mode.
3. Copy the proxy string or separate host, port, username, and password fields.
4. Paste the values into the browser tool.
5. Test the profile before scaling the setup.

If the tool has separate fields, do not paste a full URI into the host field. Split the values into host, port, username, and password.

Import many proxy lines

Use Export when a tool accepts a list of proxy lines.

Common import formats include:

host:port:username:password
username:password@host:port
http://username:password@host:port
Copy code

Choose the format required by the tool. If the imported proxies fail, export a small test file with one or two lines and confirm the format before importing a full list.

Use sticky sessions for profile stability

For rotating products, choose Sticky when a browser profile should keep the same exit IP as long as the session remains available.

Sticky sessions are best-effort. The gateway tries to keep requests with the same -sid- suffix on the same exit IP, but residential peers and pool members can go offline. If that happens, the next request may receive a new exit IP while keeping the same session ID.

For hard dedicated-IP requirements, use Static ISP instead of a rotating sticky session.

Re-export after settings change

Re-export proxy lists after:

• Changing country, state, or city.
• Switching rotating or sticky mode.
• Changing sticky session count.
• Switching HTTP or SOCKS5.
• Resetting a password.
• Changing Static ISP quantity or protocol.

Older exported rotating usernames can continue to work while the subscription is active, but they keep the routing settings encoded at export time.

Troubleshooting browser tools

• Test one proxy with cURL before testing inside the browser tool.
• Confirm the tool's proxy format matches the exported format.
• Confirm protocol and port match.
• If every imported line fails, check subscription activity, remaining usage, password, and import format.
• If only one line fails, test a fresh exported line.
• If a sticky session changes exit IP, create a new sticky session or use Static ISP for dedicated-IP workflows.

Next steps

• Choose proxy string formats.
• Test with cURL.
• Troubleshoot sticky sessions.
• Fix exported proxy lists.