English
ProxyJam Connector is a Manifest V3 proxy manager for Chrome, Microsoft Edge and Firefox. Pick a proxy from the toolbar, or write rules that send each site through the one it should use. It is free, it has no account, and it makes no network request until you ask it to.
This extension is a separate product from the ProxyJam proxy service. Installing it does not create an account or sign you in to anything, and it works with whatever proxies you configure — including other providers' or your own.
In short: ProxyJam Connector is a free proxy manager for Chrome, Microsoft Edge and Firefox that stores your proxies, switches between them from the toolbar and routes sites by rules you write. It makes no network request until you turn a feature on, and it needs no ProxyJam account.
ProxyJam Connector is a browser extension that manages proxies for you: it stores your profiles, switches between them from the toolbar in one click, and can route individual sites through specific proxies using rules you write. It runs on Chrome, Microsoft Edge and Firefox as 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. It is also a separate product from the ProxyJam proxy service: installing it signs you in to nothing and works just as well with proxies you bought somewhere else or run yourself.
The two Chrome limits in the table 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.
Chrome and Edge take the same build; Firefox has its own, and gets the features Chrome's API cannot offer. Nothing is unlocked by paying, because there is nothing to pay for.
Chrome 116 or later, Firefox 128 or later. The extension is not listed in any store yet, so until each listing is published these buttons open the stores themselves.
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.
| 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 |
| One-click switching, rules, bypass list | Yes, compiled to a PAC script | Yes, evaluated per request |
| HTTP and HTTPS proxy authentication | Yes, with no dialog | Yes, with no dialog |
| 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 a proxy that is not active | Check shows n/a rather than a made-up number; Measure switches to it, times it and switches back | Check shows n/a rather than a made-up number; Measure switches to it, times it and switches back |
| WebRTC leak test | Yes, off until you turn it on | Yes, off until you turn it on |
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.
Import reads both formats directly, and what they land in is a Manifest V3 extension, the only kind Chrome still runs.
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.
Chrome 116 or later and Microsoft Edge, which install the same package, and Firefox 128 or later, which has a build of its own. There is no Safari build. Per-container proxies and SOCKS5 usernames and passwords work only in Firefox, because Chrome's extension APIs provide neither.
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.
Yes. Drop the file in and the importer detects the format — ProxyJam, FoxyProxy, SwitchyOmega, plain TXT or CSV — and reads profiles, bypass entries and rules. You get a report of exactly which entries were accepted, skipped or rejected, because malformed input that silently disappears is worse than input that is refused.
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.
