Add Proxy to Any Send.win Session: Step-by-Step Setup (2026)

How to Add a Proxy to a Send.win Session

To add a proxy to any Send.win session, create the proxy once under Browser → Proxies with its host, port, protocol, and login credentials, then attach it to a session either at creation time or later from the Sessions list — you never re-enter proxy credentials twice. This works identically whether you run the profile locally through the Send.win desktop app or spin it up as a cloud browser session with zero install. Below is the complete step-by-step workflow, proxy-type guidance, verification steps, and fixes for the errors that trip up most new users.

Why Proxy-Per-Session Matters

Every Send.win session (also called a profile) is already isolated at the browser level — separate cookies, separate local storage, a unique canvas/WebGL/font fingerprint. A proxy adds the missing piece: a separate IP address and geolocation per session. Without it, ten isolated profiles can still all share your one real IP, which is exactly the pattern platforms like Amazon, Meta, and TikTok flag as “linked accounts.” Pairing one proxy with one session closes that gap.

• Ban avoidance: platforms link accounts primarily through shared IP + device fingerprint, not just cookies
• Geo-testing: a session with a UK residential proxy renders UK pricing, UK ads, and UK-locked content correctly
• Client separation: agencies running ads or SEO for multiple clients need each client’s session to look like it originates from that client’s own location
• Team accountability: when a proxy is tied to a specific session, you always know which IP a given login or action came from

What You’ll Need Before You Start

1. An active Send.win account — the 30-day free trial (no credit card required) is enough to follow along
2. A proxy from your provider of choice: host/IP, port, protocol, username, and password
3. A target website or URL to test against once the proxy is live

Send.win doesn’t force you into one proxy vendor. Any HTTP or SOCKS5 proxy from a residential, datacenter, mobile, or ISP provider can be pasted straight into the proxy form — this is one of the more flexible parts of the setup compared to tools that lock you into a bundled proxy marketplace.

Step-by-Step: Adding and Assigning a Proxy

Step 1: Add the Proxy to Your Send.win Account

1. Log in to Send.win and open Browser.
2. Go to Proxies → New Proxy.
3. Fill in the form:
   • Name — use something descriptive (see naming tips below), not “Proxy 1”
   • Host/IP and Port — copied exactly from your provider’s dashboard
   • Protocol — HTTP or SOCKS5, depending on what your provider issued
   • Username and Password — the proxy’s authentication credentials
4. Click Save. The proxy now appears in your Proxies list, ready to attach to any session.

You only do this once per proxy. From here on, assigning it to a session — or reassigning it to a different one — is a dropdown selection, not a re-entry of credentials.

Step 2: Assign the Proxy When Creating a Session

1. In Browser, click New Session.
2. Fill in the session details:
   • URL/Domain you’ll be working with
   • Session Name — again, be specific (e.g., “Client A — US East”)
   • Server — leave on Default unless you have a specific reason to change it
   • Proxy — select the proxy you added in Step 1
3. Click Create. The session launches already routed through the selected proxy — there is no separate “apply” step.

Step 3: Verify the Proxy Is Actually Applied

1. Open the session and load any page.
2. Refresh once or twice — proxy connections occasionally need a beat to establish.
3. Open a plain IP-checker page in that same session tab and confirm the reported IP and location match your proxy, not your real connection.
4. If you’re running several sessions side by side, check each one’s IP checker tab independently — they should all report different addresses.

Changing a Proxy on an Existing Session

You don’t have to rebuild a session just to swap its proxy — useful when a proxy goes stale or you want to rotate a client onto a fresh IP.

1. Go to Sessions.
2. Open the session’s settings/edit panel.
3. Pick a different proxy from the dropdown.
4. Click Save, then reopen or refresh the session to confirm the switch took effect.

This is also the fastest way to test whether a “broken proxy” issue is actually the proxy or something else — swap in a known-good proxy on the same session and see if the problem follows the proxy or stays with the session.

Desktop App vs Cloud Browser Sessions: Where the Proxy Lives

Send.win gives you two separate ways to actually run a proxied session, and it’s worth being precise about which one you’re using:

Mode	How it runs	Best for
Desktop app	Native Windows/macOS/Linux client installed on your machine; the proxy routes traffic for the local browser instance	Users who want full local control, existing dedicated hardware, or offline session management
Cloud browser sessions	The profile — proxy included — runs entirely on Send.win’s servers; you connect through a browser tab with no local install	Working from a shared/locked-down machine, switching devices mid-task, or teams that need instant access without provisioning laptops

Cloud sessions are metered by monthly “cloud browsing time” and are included on paid plans alongside cloud sync, profile sharing, and team seats — it’s a genuinely separate, billed mode from the desktop app, not just a marketing label for the same thing. If you’re setting up proxies for a team that needs to create sessions in Send.win’s cloud browser without installing anything locally, the proxy assignment flow above is identical — you’re just choosing “Cloud” instead of running the desktop client.

Assigning Proxies Programmatically (Automation API)

If you’re managing proxies across dozens or hundreds of sessions, doing it by hand in the UI stops scaling. Send.win’s Automation API, available on the Team plan, lets you drive session and proxy creation directly from Selenium, Puppeteer, or Playwright scripts — so a script can spin up a session, attach a specific proxy, run a scripted flow, and tear it down, all without a human clicking through the dashboard. This is the right tool when you’re rotating proxies on a schedule, provisioning sessions for QA test suites, or managing proxy assignment at a volume the UI wasn’t built for. It connects through the profile’s local automation endpoint rather than a public REST URL you’d hardcode, so the exact call pattern follows your existing Selenium/Puppeteer/Playwright driver setup rather than a separate API you learn from scratch.

Choosing the Right Proxy Type for Your Sessions

Not every proxy is equal, and the type you pick changes how believable your session’s IP looks to the site you’re accessing.

Proxy Type	Speed	Detection Risk	Best Use Case
Residential	Medium	Low	Social media, e-commerce, marketplaces that flag datacenter IPs
Mobile (4G/5G)	Medium-Low	Very Low	High-risk platforms with aggressive fingerprinting (dating apps, some ad networks)
ISP (static residential)	High	Low	Long-lived accounts that need a stable IP over weeks/months
Datacenter	Very High	Medium-High	Testing, scraping, or sites that don’t actively flag datacenter ranges

Protocol matters too: HTTP proxies (what Send.win’s form defaults to) cover most session-browsing needs, while SOCKS5 is preferable if your provider issues it and you need broader protocol support beyond plain web traffic. And if you’re deciding between address formats, our breakdown of IPv6 vs IPv4 proxies covers when the newer, cheaper IPv6 pools are safe to use and when a platform’s fingerprinting still expects IPv4.

Proxy + Fingerprint Matching: The Mistake That Gets Accounts Flagged Anyway

A proxy alone doesn’t protect a session if the rest of the fingerprint contradicts it. Sites cross-check the IP’s geolocation against the browser’s reported timezone, language headers, and system locale — a session showing a German IP but a US timezone and English-only Accept-Language header is a mismatch that’s trivial for fraud systems to catch. When you assign a proxy in Send.win, take thirty extra seconds to check that the session’s timezone and language settings line up with the proxy’s country. This single habit fixes more “account got flagged despite using a proxy” reports than any other single change.

Verifying Your Setup Beyond the Basic IP Check

An IP checker confirms the proxy is active, but it doesn’t confirm the session is fully leak-free. Two more checks worth running on any session you’re relying on for account safety:

• WebRTC leak test: WebRTC can expose your real local IP even when a proxy is correctly routing your HTTP traffic — see our WebRTC leak protection guide for how to confirm this isn’t happening
• DNS leak check: confirm DNS queries are resolving through the proxy’s network path, not leaking to your ISP’s resolver

Run both checks once per new proxy/provider combination — you don’t need to repeat them every session, just when you change providers or protocols.

Common Proxy Errors and How to Fix Them

Symptom	Likely Cause	Fix
Proxy added but session shows no change in IP	Session wasn’t refreshed after the proxy was applied, or wrong proxy selected in dropdown	Reselect the proxy, Save, then reopen and refresh the session
Same IP across multiple sessions	Two sessions accidentally assigned the same proxy	Open each session’s settings and confirm a unique proxy is assigned to each
“Authentication failed” on proxy	Typo in username/password, or provider account inactive for that IP/port	Re-copy credentials directly from your provider’s dashboard; confirm the plan is active
Proxy works, but site still flags the account	Timezone/language mismatch, or IP type (datacenter) too easily detected by that platform	Match timezone/locale to proxy country; switch to residential or mobile proxy
Connection times out	Wrong port, provider-side outage, or IP whitelisting required on the provider’s end	Verify port and whitelist settings with your proxy provider directly

Best Practices for Managing Proxies at Scale

• Name proxies by client/region, not number: “US-East-ClientA-Residential” tells you more at a glance than “Proxy 7” ever will, especially once you’re past a dozen entries
• One proxy per session, always: resist the temptation to reuse a proxy across two “just for now” sessions — that’s exactly the shortcut that causes linked-account flags later
• Keep a rotation spare: for any session tied to a revenue-generating account, keep one backup proxy from the same region ready so a dead proxy doesn’t stall the account
• Refresh after every proxy change: Send.win applies the new proxy on session reload, not instantly mid-session
• Audit proxy-to-session mapping monthly if you’re running more than a handful of accounts — it’s easy to lose track of which proxy belongs to which client

Teams managing this at volume typically split the work: one person maintains the proxy inventory while others just pick from a pre-vetted list per session. If your team needs to hand off already-configured, proxied sessions to teammates without re-doing any of this setup, you can share sessions with your team directly inside Send.win — the proxy assignment travels with the session, so a colleague opening a shared session gets the same IP and fingerprint you configured, not a blank slate.

Proxy vs VPN: Why Session-Level Assignment Wins for Multi-Account Work

A VPN changes the IP for your entire device — every tab, every app, one location at a time. That’s the wrong tool the moment you need five sessions on five different IPs simultaneously, which is the normal case for anyone managing multiple accounts or clients. Assigning a proxy per session instead means each Send.win profile keeps its own persistent IP regardless of what your other tabs or sessions are doing. For a deeper look at where each tool actually fits, our proxy vs VPN comparison breaks down the practical differences for marketers and account managers specifically.

Frequently Asked Questions

Can I run multiple sessions with different proxies at the same time?

Yes. Each Send.win session is independently isolated, so you can run as many sessions as your plan allows, each assigned its own proxy, all active simultaneously without one affecting another’s IP or fingerprint.

Which proxy protocol should I choose, HTTP or SOCKS5?

HTTP covers the vast majority of session-browsing use cases and is what Send.win’s proxy form is built around. If your provider issues SOCKS5 and you need it for a specific workflow beyond standard web traffic, follow your provider’s connection instructions when entering the details.

Do I need to recreate a session to change its proxy?

No. Open the session from the Sessions list, edit its settings, choose a different proxy from the dropdown, save, and refresh — the session keeps its cookies, fingerprint, and history while only the proxy changes.

Does adding a proxy work the same on the desktop app and cloud browser sessions?

Yes, the proxy assignment steps are identical in both modes. The difference is only where the session itself runs: locally through the installed desktop app, or entirely in the cloud with no install, metered by cloud browsing time on paid plans.

What happens if I don’t add a proxy to a session?

The session still gets its own isolated cookies and browser fingerprint, but it will share your real IP address with every other session that also has no proxy assigned — which defeats the purpose if the goal is keeping multiple accounts from looking connected.

Can I use free proxies with Send.win?

Technically yes, since any HTTP or SOCKS5 proxy can be entered into the form, but free proxies are typically shared among many users simultaneously, slow, and frequently already flagged by major platforms — for anything account-sensitive, a dedicated residential, mobile, or ISP proxy is worth the cost.

How do I know if my proxy is actually working versus just added?

Open the session, load an IP-checker page, and confirm the displayed IP and location match your proxy provider’s assigned address rather than your real connection. Refresh once or twice first, since proxy connections can take a moment to establish after a change.

Can I assign proxies through code instead of the dashboard?

Yes, on the Team plan. The Automation API lets Selenium, Puppeteer, and Playwright scripts create sessions and attach proxies programmatically, which is the practical option once you’re managing proxy assignment across more sessions than makes sense to configure by hand.