
WebShare
Use WebShare-issued proxy endpoints and credentials with individual Social Browser Profiles.
Proxy integrations
Assign a different proxy to each Social Browser Profile. Keep provider credentials, location, session mode, and rotation policy under your control — without being locked to one vendor.
Proxy partners
These are current proxy partners enabled in the Social Browser partner directory. Provider services, pricing, IP pools, and policies are operated by the providers themselves.

Use WebShare-issued proxy endpoints and credentials with individual Social Browser Profiles.

social_browserDedicated residential and ISP proxy options that can be assigned to individual Social Browser Profiles.
SOCIALMobile proxy endpoints backed by carrier networks, with provider-side rotation controls.

SOCIALBROWSERMobile and residential proxy options with rotating or sticky session modes.

SOCIALBROWSERA proxy marketplace where purchased endpoints can be assigned to Social Browser Profiles.

Thor20dResidential, mobile, ISP and datacenter proxy endpoints with rotating and sticky session options.
Residential, static residential and datacenter endpoints configured at the Profile level.
Residential and static ISP endpoints with provider-side geo and session controls.
Partner disclosure: some external provider links are referral or sponsored links. Social Browser may receive a commission when you use them. This does not determine technical compatibility, and you can use any supported third-party proxy provider.
Complete setup guide
You normally need four values from your proxy provider: protocol, host, port, and authentication. Keep any session or location parameters exactly as the provider generated them.
Open the Profile that should use the proxy. Configure proxies per Profile instead of treating them as a browser-wide setting.
Get the host, port, username, password, and protocol from the provider dashboard. If the username contains country, city, session, or sticky-ID parameters, keep them unchanged.
Open Proxy Manager, select HTTP/HTTPS or SOCKS as required, enter the endpoint and credentials, then save it to the selected Profile.
Open the Profile and confirm the public IP, location, DNS behavior, and WebRTC behavior before using the Profile for important work.
Connection formats
Provider dashboards use different labels, but the underlying values are usually the same.
Typical endpoint fields:
proxy.example.com 8000Enter credentials in their dedicated fields:
username passwordSelect the protocol supported by the endpoint.
Verification
A successful connection is not enough. Confirm that routing and browser network behavior match what you intended.
Troubleshooting
Re-copy the username and password from the provider dashboard. Do not remove geo/session suffixes from the username. Confirm the provider allows username/password authentication for that endpoint.
Check the host and port, confirm the proxy is active, verify your firewall or network is not blocking the destination port, and try the protocol listed by the provider.
Review the provider-side location configuration and session parameters. Rotating pools can change IPs by request or time depending on the provider plan.
Compare protocol, credentials, and endpoint values Profile-by-Profile. Each Profile keeps its own proxy configuration, so fixing one Profile does not automatically change another.
Ready to configure
Add the provider endpoint to the Profile that needs it, verify the result, and keep the rest of your Profiles independent.