How Do You Use SessionBox to Run Multiple Accounts?

What Does a Working SessionBox Setup Look Like End to End?

You install SessionBox One on Windows or macOS, connect it to Chrome, Edge or Firefox through the SessionBox extension, create one profile per account, attach a proxy to each profile, and verify the IP before you sign in. That is the whole shape of how to use SessionBox: the app manages sessions, the extension opens them in your browser, and the proxy decides which IP each session presents to the site.

What SessionBox One Is and Why Old Tutorials Confuse People

SessionBox creates separate browser sessions on top of a browser you already use, so two windows can hold two different logins to the same website at the same time. The current product, SessionBox One, is a desktop app for Windows and macOS that opens profiles in Chrome, Edge or Firefox through a SessionBox extension.

The standalone extension era is over. A 2024 walkthrough reported the original SessionBox extension was no longer available on Chrome, Edge or Firefox, replaced by SessionBox One. Guides that still describe a single extension button describe a product you cannot download today. Most of the confusion about how to use SessionBox comes from mixing those two eras. If you are checking whether the tool still behaves the way older reviews claim, this look at does SessionBox multi-login still work covers what changed.

SessionBox One separates three profile types, and picking the wrong one is the most common early mistake.

The three types are documented in the SessionBox knowledge base if you want the vendor’s own wording before you commit.

Step 1: Install SessionBox One and Connect Your Browser

1. Download the desktop app for Windows or macOS and install it. SessionBox One runs on those two platforms, so a Linux-only machine needs a different tool.
2. Open the app and sign in. A first install includes a one-week trial with access to all features, which is enough to finish the setup before you pick a plan.
3. Install the browser extension for the browser you actually work in — Chrome, Edge or Firefox — and leave that browser open.
4. Return to the app and confirm it lists the connected browser. That connection is what lets the app launch profiles as real browser windows rather than tabs.

Then test it: create one throwaway profile and open it. You should get a clean window with none of your everyday cookies. If your personal logins are already there, the extension is not controlling that window and the profile is not isolated.

A browser-specific walkthrough of the connection step, including the extension prompt, is in this SessionBox Edge setup guide.

Step 2: Create One Profile per Account

1. Open My Profiles and create a new profile.
2. Name it after the account, not the site. “Store A – Amazon seller” survives a year of growth; “Amazon 1” does not.
3. Choose the type: local for a machine-bound daily login, temporary for a one-off check, cloud if a second device or a teammate needs it.
4. Open the profile and log in to the account you own or are authorised to manage.

One profile per account is not bureaucracy. Two logins sharing a profile share one cookie jar and one set of local storage, so the second sign-in replaces the first session and the site sees both accounts arriving from identical client state.

Keep the naming symmetric with your proxies. If the profile is “Client A – Meta”, call the proxy “Client A – Meta – DE residential”. At thirty profiles, that repetition is the only thing standing between you and a login attempt from the wrong country.

The rest of how to use SessionBox follows from that split: profile first, proxy second, login last.

Step 3: Attach a Proxy to Each Profile

1. Open My Profiles and select the profile you want to route.
2. Click Manage proxies, then Add proxy.
3. Fill in host, port, protocol, and username and password if your provider issued them.
4. Click Test proxy and wait for it to pass before you save. A failed test at this point is a typo, not a mystery.
5. Select that proxy entry for the profile so every window it opens starts behind that IP.

The unit that matters is the entry, not the profile. One entry attached to five profiles means all five share an exit IP. To give each profile its own IP, add one entry per profile and use a distinct session id in the username field where your provider supports sticky sessions.

Protocol choice decides whether this step works at all. SessionBox does not send a username and password to SOCKS5 proxies, so a credentialed SOCKS5 entry fails authentication however carefully you type it. Use HTTP proxies with credentials, or a SOCKS5 endpoint that authorises you by whitelisted IP. If you are setting this up for the first time, this guide to browser profiles with proxies walks through the same fields in another tool.

Bulk import and automatic assignment — assign strategies that distribute proxy entries across profiles — start at Professional. On Hobby you add entries one at a time, which is fine for a handful of accounts and painful at ten.

Step 4: Match Timezone, WebRTC and Location to the Proxy

This is the step most guides skip, and it decides whether the proxy does anything useful. A site can read your time zone from the browser and, through WebRTC, discover the local network path your machine takes — both independently of the HTTP request that arrives from the proxy. If one part of how to use SessionBox rewards patience, it is this one.

On Hobby, fingerprint protection, WebRTC protection and proxy-location matching are not included. In practice a site can still see your real IP through WebRTC, and the clock stays on your computer’s zone while the request claims another country. On Professional and above, switch on WebRTC protection and proxy-location and timezone matching for each profile.

If you bring your own proxies, treat the three settings as one unit: IP, time zone and locale should describe the same place. A profile exiting in Frankfurt with a browser clock set to Los Angeles and an en-US locale is a combination a site’s risk checks can spot without any fingerprinting at all.

Step 5: Verify the Profile Before You Log In

Order matters. Verify first, log in second. If you sign in, discover the IP is wrong, then change the proxy, the platform now holds a session that started in one country and continued in another, and no settings edit undoes that.

1. Open the profile with no site loaded and visit a geolocation checker. The IP, city and country should match your proxy, not your connection.
2. Read the time zone the browser reports. It should match the proxy’s region when matching is enabled.
3. Run a WebRTC test. If it surfaces a local address alongside the proxy address, WebRTC protection is off.
4. Only then open the target site and sign in.
5. Repeat after every proxy change, every move between networks, and every handover to a teammate.

Log the result for the profiles that matter: profile name, proxy entry, exit country, verified date. That short note makes a client question about “where does this account log in from” answerable in seconds.

Step 6: Switch, Share and Run Profiles Day to Day

Switching is a click per profile in My Profiles. Open the one you need, close it when you are done, and keep the rest closed — the app slows noticeably when many sessions run at once, a point reviewers raised in early 2026, so there is no benefit to leaving fifteen windows open.

Sharing splits into two models. Direct 1-1 shares work when the recipient has at least a Hobby seat. Shared spaces, where several people work inside one set of profiles, require Professional or Teams — and there the proxies travel with the profiles, so a colleague opening “Client A” inherits the IP that profile is supposed to use. For agency work the second model is the one you want, because it removes proxy setup from the handover.

One workflow trap: older guides show adding a proxy from the extension’s session settings, Other tab, with the Proxy dropdown set to Add new. That belongs to the extension era, and the proxy only applied for the lifetime of that session. In SessionBox One, do it from My Profiles → Manage proxies so the entry stays attached after the window closes.

What SessionBox Costs and What Each Tier Unlocks

The tiers differ in ways that change your setup, not just your bill. Prices below are the monthly rates from the SessionBox pricing page, with the annual-billing monthly equivalent in the next row.

Professional and above also expose a Local API on localhost:54789 with a key issued inside the app, and the documentation covers a Selenium workflow and a Node.js SDK for profile creation. That matters if your team already automates browser testing, and it is not a reason to buy if you do not.

Common SessionBox Pitfalls and How to Fix Them

1. SOCKS5 with a username and password. It will not authenticate. Switch to an HTTP proxy with credentials, or ask your provider for IP whitelisting and use SOCKS5 without credentials.
2. The proxy passes the checker but the site still refuses the login. Check the time zone and WebRTC result next, then the locale. If all three line up and the site still blocks you, the problem is the account, not the network — use the platform’s own verification or appeal process rather than rotating another IP.
3. The real IP shows up on Hobby. WebRTC protection and timezone matching start at Professional, so no proxy entry fixes this on the entry tier.
4. Every profile shows the same IP. You reused one proxy entry. Add one entry per profile with a distinct session id in the username.
5. A teammate cannot join a shared space. Shared spaces need Professional or Teams on their side too; a Hobby seat can only receive a 1-1 share.
6. You learned how to use SessionBox from an old tutorial. Most SessionBox content still online describes the deprecated extension. Trust the desktop app’s own menus over a 2023 blog post.

When a Dedicated Profile Manager Fits Better Than an App Plus Extension

SessionBox’s model assumes Chrome, Edge or Firefox is already on the machine and layers sessions on top of it. A dedicated browser profile manager ships its own Chromium build, so profiles do not inherit your everyday browser’s version, extensions or settings, and there is no extension to keep connected.

The differences that matter day to day are narrow but real: whether fingerprint protection is on every plan or starts at a mid tier, whether cloud profiles count against a small allowance, how SOCKS5 credentials are handled, and whether the tool carries an automation layer you will either use or pay for unnecessarily.

Send.win takes the second approach. Sendwin Browser is a native desktop app for Windows 10/11 (64-bit), macOS 12 and later on Apple Silicon and Intel, and Linux, built on Chromium; a cloud browser option runs profiles on an EU server in Helsinki, which helps when a teammate must check an account from a device with nothing installed. Each profile keeps its own fingerprint protection and proxy, and timezone, locale, WebRTC and geolocation follow the proxy’s exit IP. Sharing a profile with a paid teammate opens it already signed in, without a password changing hands. There is no API, SDK or headless mode on any plan, so a workflow built on SessionBox’s Local API has no equivalent here. The direct comparison is in Send.win vs SessionBox.

Whichever tool you pick, the rules do not move. Use it only with accounts you own or are authorised to manage. Where a platform caps how many accounts one person may hold — Amazon requires approval for an additional seller account, and agencies on Meta are expected to work through Business Manager roles — that limit applies to your browser choice, not around it.

Frequently Asked Questions

How do I install SessionBox One on Chrome?

You install the desktop app first, then add the SessionBox extension to Chrome when the app prompts you. That order is the first thing to get right when you learn how to use SessionBox on any browser. The extension alone is not the product — it is the bridge that lets the app open profiles as Chrome windows. Keep Chrome open during setup and confirm the app lists the browser before creating profiles.

How do I add a proxy to a SessionBox profile?

Open My Profiles, select the profile, click Manage proxies, then Add proxy and fill in host, port, protocol and credentials. Click Test proxy and save only after it passes, then select that entry for the profile. Adding the entry is not enough on its own — it has to be assigned before it takes effect.

How much does SessionBox cost?

Hobby is $12.99/month with one seat and up to 10 cloud profiles, Professional is $59.99/month with two seats, and Teams is $99.99/month with five assignable seats and unlimited cloud profiles. Billed annually the three work out to roughly $6.99, $29.99 and $49.99 per month. A first install includes a one-week trial with all features unlocked.

What is the difference between local, temporary and cloud profiles?

Local profiles live on the machine where you created them and open fastest. Temporary profiles are discarded when you close them, which suits one-off checks and testing a page as another user. Cloud profiles are stored with your account and sync across devices, and they count against your cloud profile allowance.

Does SessionBox work with SOCKS5 proxies?

Yes, but only through IP whitelisting. SessionBox does not send a username and password to SOCKS5 proxies, so a credentialed SOCKS5 entry fails authentication. Use an HTTP proxy with credentials, or ask your provider to whitelist your IP and connect to SOCKS5 without a login.

Can I share a SessionBox profile with a teammate?

Yes, in two ways. A direct 1-1 share works as long as the recipient has at least a Hobby seat. Shared spaces, where a team works inside one set of profiles with the proxies included, require Professional or Teams for the members joining.

Why does a site still see my real IP or timezone on Hobby?

Because WebRTC protection and proxy-location timezone matching start at Professional. On Hobby the browser can still expose a local address through WebRTC, and the clock stays on your computer’s zone even when the request arrives from another country. Upgrading, or using a tool that includes those settings on every plan, is the fix.

How do I verify my SessionBox proxy is working?

Open the profile and load a geolocation checker before visiting any site you care about. A working proxy shows its own city and country as your IP, and the browser’s reported time zone should match that region. Run a WebRTC test in the same window to confirm no local address appears alongside it.

How Send.win Helps With How To Use Sessionbox

Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.

• Isolated profiles – separate cookies, storage and sessions per profile
• Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
• Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
• Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
• Team sharing – share a signed-in profile with a teammate without sharing the password

Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).

Related Products & Resources

• Download
• Demo Browser
• Pricing
• Use Cases
• Fingerprint Checker