# Container & Extension Proxy > Assign a proxy to a container and extensions Canonical page: [https://chrome-stats.com/d/container-extension-proxy](https://chrome-stats.com/d/container-extension-proxy) ## Overview - **ID:** `container-extension-proxy` - **Platform:** Firefox - **Type:** Firefox add-on - **Status:** Available - **Publisher:** alpine Q - **Category:** privacy-security - **Daily users:** 15 - **Weekly downloads:** 3 - **Version:** 0.2.3 - **Last updated:** 2026-07-12 - **First published:** 2026-07-09 - **Size:** 183 KB - **Data as of:** 2026-09-07 - **Store listing:** [Firefox Add-ons Store](https://addons.mozilla.org/firefox/addon/container-extension-proxy/) - **Website:** [https://github.com/alpineQ/firefox-container-proxy](https://github.com/alpineQ/firefox-container-proxy) ## Description Container & Extension Proxy is a fork of the original "Container proxy" extension by Aleksey Bekh-Ivanov (original code: https://github.com/bekh6ex/firefox-container-proxy — original listing: https://addons.mozilla.org/firefox/addon/container-proxy/). All credit for the original extension goes to its author. This fork does not claim any originality or priority — it simply adds one feature on top of the existing extension. Like the original, it lets you assign a proxy (SOCKS4, SOCKS5, HTTP or HTTPS) to each Firefox container, so that traffic in a given container goes through the proxy you choose. What this fork adds: the ability to route another browser extension's own traffic through one of your already-configured proxies. Some extensions — SponsorBlock, for example — send their network requests from their own background context, which is not tied to any container. With container-only routing, that traffic went out directly and bypassed the proxy. A new "Extensions" settings page lets you map such an extension to a proxy, so its traffic follows the proxy as well. Why a separate listing: the original project has had no activity for about five years, so the change was not submitted upstream. Published under the same BSD 2-Clause license as the original. ## Rankings - #28,192 — Overall - #82 — contain - #135 — proxy - #187 — wifi proxy - #213 — contact ## Permissions and access ### Permissions - `` - `webRequest` - `webRequestBlocking` - `storage` - `contextualIdentities` - `cookies` - `proxy` ## Safety - **Risk impact:** High risk impact - **Risk likelihood:** High risk likelihood ### Analysis details - Allows access to all websites, posing a significant security risk as it can monitor and modify data from any visited site. - This extension has low user count. Unpopular extensions may not be stable or safe. > Some risk analysis details are omitted from this free response. [Upgrade to view the full analysis](https://chrome-stats.com/pricing). ## Similar extensions and apps - [Container proxy](https://chrome-stats.com/d/container-proxy) — 5,878 users, 4.78 / 5 - [Container Proxy v1.0.3](https://chrome-stats.com/d/container-proxy-v1-0-3) — 10 users - [Containers Socks Proxy Helper](https://chrome-stats.com/d/containers-proxy-helper) — 12 users, 4.00 / 5 - [ProxyContain](https://chrome-stats.com/d/proxycontain) — 6 users, 5.00 / 5 - [Lightweight Container Proxy](https://chrome-stats.com/d/lightweight-container-proxy-02) — 1 users - [Contained Proxy](https://chrome-stats.com/d/contained-proxy) — 1 users - [Container Session Proxy](https://chrome-stats.com/d/container-session-proxy) - [ProxyFlow Containers](https://chrome-stats.com/d/proxyflow-containers) — 2 users - [ProxyFire](https://chrome-stats.com/d/proxyfire) — 5 users - [Domain Socks Proxy Helper](https://chrome-stats.com/d/domain-socks-proxy-helper) — 3 users, 5.00 / 5 - [Container Redirect](https://chrome-stats.com/d/container-redirect) — 39 users, 5.00 / 5 - [Phoenix Proxy FF](https://chrome-stats.com/d/phoenix-proxy-ff) — 1 users --- Source: [Chrome-Stats](https://chrome-stats.com/d/container-extension-proxy)