Android and iOS both have a built-in proxy setting, but it lives inside each Wi-Fi network's configuration, applies only to that network, speaks only HTTP, and is honoured only by apps that choose to — browsers and most system components do, many third-party apps do not, and nothing on cellular data does. That makes the built-in setting fine for testing a website from another location and useless as a way to put a phone's traffic behind a proxy. For that you need a local VPN-based proxy client: an app that registers itself as a VPN, captures every packet the phone sends, and forwards it through your HTTP or SOCKS5 proxy. This guide covers both approaches, per-app routing, and how to check the phone is not leaking around the proxy.

The built-in Wi-Fi proxy: what it is for

Android

  1. Settings → Network & internet → Internet (or Wi-Fi) → tap the gear next to the connected network → Edit (pencil) → Advanced options.
  2. Set Proxy to Manual; enter hostname and port; optionally a bypass list. Save.

Android's Wi-Fi proxy is HTTP only and has no field for a username and password in the standard settings UI. Apps that use the system HTTP stack will prompt for proxy credentials the first time (Chrome does); apps using their own networking may fail silently. SOCKS5 is not supported here at all.

iOS / iPadOS

  1. Settings → Wi-Fi → tap the (i) next to the connected network → scroll to HTTP Proxy → Configure Proxy → Manual.
  2. Enter server and port; toggle Authentication on to enter a username and password. Save.

iOS does accept credentials, and Safari and most apps using the system networking frameworks (URLSession) will honour the proxy. Still HTTP-only, still per-network, still nothing on cellular.

What it is good for

Checking how a site or your own app renders from a specific country while you sit on your home Wi-Fi; quick manual tests; nothing that requires the proxy to be reliably applied to every connection.

What it misses

  • Cellular data. Switch to 4G/5G, or let the phone fall back when Wi-Fi is weak, and every connection is direct. This is the biggest practical leak.
  • Apps with their own networking. Many apps — especially those built on cross-platform frameworks or embedding their own HTTP libraries — never look at the system proxy. Social and marketplace apps often fall in this group.
  • Non-HTTP traffic. Push services, VoIP, games and anything on raw TCP/UDP go direct.
  • Certificate pinning. Unrelated to routing, but if you were hoping to inspect an app's traffic, pinned apps will refuse a MITM proxy regardless.

The reliable way: a local VPN-based proxy client

Both platforms let an app declare itself a VPN. Once the user approves, the OS routes all device traffic — Wi-Fi and cellular, every app, every protocol — into that app's virtual interface. A proxy client of this kind does not tunnel to a VPN server; it takes the captured packets and forwards them through your HTTP CONNECT or SOCKS5 proxy, credentials included, and returns the responses. From the phone's perspective it is a VPN; from your proxy provider's perspective it is an ordinary client; from the destination's perspective the phone is behind your proxy IP.

What you get:

  • Coverage of every app and both radios, including cellular fallback.
  • SOCKS5 as well as HTTP, with authentication.
  • Usually per-app rules: route only chosen apps through the proxy and let the rest go direct (or the reverse), which is exactly what multi-account and testing work needs.
  • Often DNS handling — resolve through the proxy to avoid the DNS leak.

What you do not get: an interception point for TLS contents (it forwards encrypted traffic as-is), and, on iOS, more than one such VPN active at once — the platform allows a single VPN configuration to be connected.

Set-up is the same shape everywhere: install the client, add a profile with proxy type / host / port / credentials, choose which apps (or all), tap connect, approve the VPN prompt. Because these apps run as VPNs, the OS shows the VPN key icon while they are active. Our software catalogue lists mobile proxy clients that have been tested with mobile and residential providers; the antidetect vendors also ship mobile-oriented clients for their profiles.

Per-app routing: the case that actually matters

The reason to proxy a phone is almost never “all my traffic”; it is “this app should look like it is somewhere else, or on a different identity.” Two things follow.

First, use the client's per-app rules rather than routing everything: your banking app, your personal messenger and the app store have no business exiting through a proxy in another country, and routing them there both wastes bandwidth and creates account-security alerts.

Second, match the proxy type to the platform. A mobile app is expected to arrive from a mobile carrier IP; behind a datacenter or even a residential-broadband IP, a phone app is a mild anomaly, and on platforms that check, a noticeable one. This is the strongest use case for mobile (carrier) proxies — see the proxy types comparison and, for platform-specific notes, mobile proxies for marketplaces. The identity logic is the same as on desktop: one persistent identity, one stable IP; see why accounts should not rotate.

Android-specific: developer and enterprise routes

  • ADB global proxy (adb shell settings put global http_proxy host:port) applies an HTTP proxy device-wide including cellular — useful on test devices and emulators, but it persists until cleared (settings put global http_proxy :0) and, like the Wi-Fi setting, is honoured only by compliant apps.
  • Emulators accept a proxy at launch (-http-proxy) or in the emulator settings; combined with a per-emulator proxy this is how testing farms give each virtual device its own IP.
  • Work profiles / MDM can push a proxy or a per-app VPN policy centrally; relevant if you manage a fleet.
  • Multiple users / clones. Android's multi-user feature and app-cloning let one device hold several isolated app instances; pair each with a per-app rule in the VPN client and each instance gets its own exit. Beware that device-level fingerprints (hardware IDs, advertising ID unless reset) are shared across clones — the phone equivalent of the browser-fingerprint problem in the antidetect article.

iOS-specific

  • Only one VPN can be connected at a time, so one proxy client is the practical limit; do per-app selection inside it.
  • iOS's own iCloud Private Relay (Safari and some system traffic) is a two-hop proxy scheme built into the OS. When it is on, Safari's traffic to the destination arrives from Apple's relay egress, not from your proxy — turn it off while testing or your results will be confusing.
  • Configuration profiles (.mobileconfig) can install a global HTTP proxy or a per-app VPN for supervised devices; that is the enterprise route.

Verify on the phone

  1. With the client connected, open a browser and an IP-echo page: the IP and country should be the proxy's.
  2. Turn Wi-Fi off and reload on cellular: still the proxy's IP? If not, only the Wi-Fi setting is active.
  3. Open the specific app you care about and, where it exposes one, check its own idea of your location or use a proxy-side log to confirm its traffic passes through.
  4. Run a DNS-leak test in the browser: resolvers should not be your carrier's.
  5. If the app uses WebRTC (many chat and social apps do), be aware it can disclose local addresses inside the app just as in a browser; a VPN-based client that owns the interface limits what is visible, but a mobile app cannot be configured the way desktop Chrome can.

The general procedure — what to check and how to read it — is in How to test a proxy; the mobile additions are cellular fallback and per-app coverage.

Frequently asked questions

How do I set a proxy on Android?

For a Wi-Fi network only: edit the network's advanced options and set an HTTP proxy. For all traffic including cellular and every app: install a VPN-based proxy client and add your proxy there.

How do I set a proxy on iPhone?

Per Wi-Fi network: Settings → Wi-Fi → (i) → HTTP Proxy → Manual, with optional authentication. For everything: a VPN-based proxy client from the App Store.

Why does the app ignore my proxy settings?

Because the Wi-Fi proxy is advisory: apps using their own networking stack, and all cellular traffic, bypass it. A VPN-based client captures traffic at the interface level so no app can opt out.

Can I use SOCKS5 on a phone?

Not through the built-in Wi-Fi setting (HTTP only). Yes through a VPN-based proxy client, most of which support SOCKS5 with authentication.

Can I use different proxies for different apps?

Yes — VPN-based clients typically offer per-app rules; on Android, combining app clones or multiple users with per-app rules gives each instance its own exit.

Should I use a mobile proxy for phone apps?

Usually yes. Mobile platforms expect carrier IPs, and mobile (carrier) proxies are the closest match; datacenter IPs on a phone app are the most conspicuous combination.