ProxyJam Connector switches proxies without leaving the page. Save your proxy servers, pick one from the toolbar, or write rules that send each site through the one it should use. No account, no ads, and no network request until you turn a feature on. It works with proxies you already have; it does not supply them, and it is not a VPN.
This extension is a separate product from the ProxyJam proxy service. Installing it signs you in to nothing, and it works with whatever proxies you configure — other providers' or your own. Firefox installs a build of its own from Firefox Add-ons.
Chrome and Microsoft Edge install the same package from its Chrome Web Store listing, ProxyJam Connector — Proxy Manager; Edge asks once to allow extensions from other stores. Firefox installs a build of its own, with SOCKS5 passwords and per-container proxies, from Firefox Add-ons. Nothing is unlocked by paying, because there is nothing to pay for.
Chrome 116 or later, or a current Microsoft Edge. The Firefox build needs Firefox 128 or later.
In short: ProxyJam Connector is a free proxy manager and proxy switcher extension for Chrome, Microsoft Edge and Firefox, built on Manifest V3. It switches proxies from the toolbar, routes each site through its own proxy by rules, imports FoxyProxy and SwitchyOmega profiles, and fails over to a backup proxy you choose. It needs no account and makes no network request until you turn a feature on.
ProxyJam Connector is a free proxy manager extension for Chrome, Microsoft Edge and Firefox: it stores your proxy profiles, switches between them from the toolbar in one click, and routes individual sites through specific proxies using rules you write. Chrome and Edge install it from the same Chrome Web Store listing, and Firefox installs its own build from Firefox Add-ons. It is a Manifest V3 extension, the only kind Chrome still runs: since Chrome 138, in July 2025, Manifest V2 extensions are disabled for every user with no way to turn them back on, as Chrome’s own timeline records. It is free, it has no account, and it is offline by default: it makes no network request until you turn on one of its optional checks or sign in to its account tab, and every destination is listed below.
No. The original Proxy SwitchyOmega is a Manifest V2 extension, so current Chrome has disabled it and cannot turn it back on. ZeroOmega is its Manifest V3 fork, and FoxyProxy rebuilt its own extension for Manifest V3 as version 8. ProxyJam Connector is another Manifest V3 proxy switcher, and its importer reads SwitchyOmega and FoxyProxy backup files directly, so profiles and rules move over in one step, with a report of every entry accepted, skipped or rejected. What Manifest V3 changed, what an import leaves behind and how to check the result are covered in SwitchyOmega and Manifest V3.
Whichever switcher you choose, Chrome’s own limits apply to all of them: a rule on an HTTPS address sees only the hostname, and Chrome’s proxy API cannot supply a SOCKS5 username and password. Choose ProxyJam Connector for rules with nine condition types, health checks that fail over to a backup proxy you nominate, and a published list of every network request the extension can make.
The two Chrome limits in the table below come from Chromium itself. Its notes on proxy support say that a PAC script sees only the scheme, host and port of an HTTPS address, and that Chrome supports no SOCKS5 authentication method, a gap Chromium issue 256785 tracks. The other ways to send only some sites through a proxy in Chrome, without an extension, are compared in using a proxy only for certain sites, and the sign-in dialog Chrome shows for a password-protected proxy is explained in why Chrome keeps asking for a proxy password.
Open the toolbar popup and pick Direct, a saved profile, Auto for rule-based routing, or your system proxy. A route diagram shows where traffic actually goes and changes shape with the mode, and the badge says which is active at a glance — green for a single proxy, blue for rules, red when something failed.
Nine condition types — exact domain, subdomain, host wildcard, URL wildcard, regular expression, exact URL, prefix, suffix and contains. First match wins with an explicit fallback, so the outcome is always predictable. Group them into named sets and move between a work configuration and a personal one with one switch.
HTTP, HTTPS, SOCKS4, SOCKS5 and QUIC, each with credentials, notes, remote DNS, a colour tag and a favourite flag. Search, sort, filter and duplicate them. Import drops in a file and detects the format — ProxyJam, FoxyProxy, SwitchyOmega, TXT or CSV — and reports exactly what was accepted, skipped or rejected.
Probe the active proxy every 5, 15, 30 or 60 minutes and nominate a backup per profile. When a check finds the active proxy unreachable the extension switches to the backup you chose and says so in the popup. It never switches silently, never picks a replacement you did not nominate, and is off until you turn it on.
Reachability, external IP, geo and ASN, and a WebRTC leak test. Every one of them is off by default, because every one of them makes a network request. The DNS-leak test reports unavailable rather than a verdict, because detecting a DNS leak needs a reflection service and the extension ships none.
Add it from the Chrome Web Store, then open the browser's Extensions menu — the puzzle-piece icon — and pin ProxyJam Connector so its button stays in the toolbar.
Open Manage profiles and enter a host, port and protocol, with a username and password if the proxy needs them — or import a FoxyProxy, SwitchyOmega, TXT or CSV file.
Choose the profile in the popup to send all traffic through it, or choose Auto and add rules that send each site through its own proxy.
The popup's route strip and the toolbar badge show what is active: green for one proxy, blue for rules, red when something failed.
| Chrome / Edge | Firefox | |
|---|---|---|
| Minimum version | Chrome 116; Edge installs the same package | Firefox 128 |
| Permissions asked for at install | proxy, storage, webRequest, webRequestAuthProvider, alarms | proxy, storage, alarms, contextualIdentities |
| How rules are applied | Compiled to a PAC script | Evaluated per request |
| SOCKS5 username and password | No — Chrome's proxy API cannot supply them (Chromium issue 256785) | Yes |
| URL and path rules on HTTPS | Hostname only — Chrome strips the path before a PAC script sees it | Yes, the full URL |
| A different proxy per container | No — Chrome has no containers API | Yes |
Testing geo-specific behaviour, or moving between staging environments without editing system settings every time.
Running your own proxies and not wanting the list of them handed to anybody. Profiles and rules stay in local extension storage and leave only if you export them.
The importer reads FoxyProxy and SwitchyOmega backup files, plus plain TXT and CSV, and reports which entries it accepted, skipped or rejected. Check that report before you remove the old extension.
External IP check
Geo and ASN lookup
WebRTC leak test
Scheduled health check
ProxyJam account tab
Everything else
No. The extension has no account and no billing, and every feature is available the moment you install it. It works with whatever proxies you configure, including ones you bought elsewhere or run yourself. There is one optional tab where you can sign in to a ProxyJam account to buy a proxy and connect to it in a click, and that tab makes no request at all until you do.
Yes, and there is nothing to unlock. No licence server, no paid tier, no advertising. The extension exists because the people who buy proxies from us needed a proxy manager, and one that talks to nobody until you ask it to is the only kind worth shipping.
Neither. It is a proxy manager: it sets your browser's proxy to servers you already have, from any provider, and switches between them. It supplies no proxies of its own, and it changes only the browser's traffic, not the rest of your computer's.
Chrome 116 or later and Microsoft Edge install the same package from the Chrome Web Store listing, ProxyJam Connector — Proxy Manager. Firefox 128 or later gets a build of its own, from Firefox Add-ons. There is no Safari build. Per-container proxies and SOCKS5 usernames and passwords work only in Firefox, because Chrome's extension APIs provide neither.
Open the Chrome Web Store listing in Edge. Edge shows a banner offering to allow extensions from other stores; allow it once, then choose Add to Chrome — the button's name, though it installs into Edge. Edge runs the same package as Chrome, with the same features and limits.
Yes. It does the same job — storing proxies, switching between them and routing sites by pattern — as a Manifest V3 extension that runs on current Chrome. Drop a FoxyProxy, SwitchyOmega, TXT or CSV file into the importer and it detects the format, reads profiles and rules, and reports exactly which entries were accepted, skipped or rejected. It adds health checks that fail over to a backup proxy you choose, and it has no account and no telemetry.
Offline by default, which is a narrower claim than offline. Four destinations exist and each one is off until you turn it on: api.ipify.org for the external IP check, ipwho.is for the geo lookup, Google's public STUN server for the WebRTC test, and api.proxyjam.com for the optional account tab. Two things can then repeat without you pressing anything: the health check, which reuses the ipify request on the interval you schedule, and, while you are signed in and a proxy from your account has been added to the extension, an hourly refresh of your orders. Turning the health check off or signing out stops them. ProxyJam Connector — Privacy Policy
Chrome's proxy API provides no way to supply SOCKS5 credentials, so the browser will not use them even though the extension stores them. Use an IP allowlist on the proxy instead, or run that profile in Firefox, where it works. The profile shows a warning when this applies rather than failing quietly. Proxy password prompt
At install on Chrome and Edge: proxy to set the browser's proxy configuration, storage to save your profiles locally, webRequest and webRequestAuthProvider to answer proxy authentication without a dialog, and alarms for the scheduled health check and order refresh. Firefox asks for proxy, storage and alarms, plus contextualIdentities to list your containers by name and colour; it answers proxy authentication without webRequest. Access to all sites is optional and never requested at install — it is asked for only when you configure an authenticated proxy or turn on the network checks — and signing in to the account tab asks for api.proxyjam.com alone. There are no content scripts, so it never reads or changes the pages you visit.
No. They are separate products. The service sells proxies and has accounts, billing and a dashboard; the extension has none of those and works with any provider's proxies. Each has its own privacy policy, and the extension's covers only the extension.
