This guide explains Android proxy configuration for per‑network Wi‑Fi proxies, global proxy via Developer options, and PAC auto‑config. We also cover app‑specific behavior and troubleshooting.
Android proxies are typically set per Wi‑Fi network and affect traffic routed through that network for many apps and browsers. Some apps (e.g., Firefox, certain VPN/proxy clients) use their own proxy settings and may not follow system configuration. Global proxy via Developer options can influence broader traffic but is device/vendor dependent.
Note: This applies to the specific Wi‑Fi SSID. Switching networks requires configuring each network.
If Global HTTP proxy is missing, your device/vendor may not support it. Use per‑Wi‑Fi proxy or an app‑level proxy client.
Some Android builds allow Proxy Auto‑Config (PAC) via Wi‑Fi advanced settings (Proxy → Auto‑config or script address). If available, enter your PAC URL and save, then verify via What's My IP.
Popular Android clients (e.g., V2RayNG, Clash) implement their own proxy stack and routing rules. They may not rely on system Wi‑Fi proxy settings. Configure these apps directly using your node/subscription, and enable their service to route traffic.
Wi‑Fi proxies apply per network. Mobile data does not use Wi‑Fi proxy; use an app‑level client or global proxy (if supported).
Apps may bypass system proxy or pin connections. Configure app‑specific proxy settings or use a client (V2RayNG/Clash) with routing rules.