WhatsApp has no in-app proxy setting. That is the first thing to get straight, and it is the reason this article exists. Neither the Android app, the iPhone app, the Windows desktop app, the macOS desktop app, nor WhatsApp Web exposes any proxy toggle, hidden URL bar, or developer flag that lets you route its traffic through a different IP.

That sounds limiting, but it actually points at the right solution. If WhatsApp will not do it for you, the device has to. Setting a SOCKS5 proxy at the device level routes every app on the phone — WhatsApp included — through Snowpad. Your exit IP becomes a real Indian mobile IP from a Jio, Airtel, or Vi radio, and rotates on each new connection.

This guide walks through the three device-level paths: Android, iOS, and desktop. All of them use the same Snowpad endpoint.

Host:     gw.snowpad.io
Port:     9999
Protocol: SOCKS5
Username: your 32-character Snowpad API key (the SOCKS5 username)
Password: anything — for example "x"

Snowpad does not check the password. Your API key is the real credential.

Android — SocksDroid (no root)

SocksDroid is the simplest path on Android. It uses Android's VPN API to create a virtual network interface, so it does not need root and works on Android 5.0 and newer.

  1. Install SocksDroid from the Play Store.
  2. Open the app and tap Add Proxy.
  3. Protocol: SOCKS5.
  4. Server: gw.snowpad.io.
  5. Port: 9999.
  6. Username: paste your Snowpad API key.
  7. Password: anything (e.g. x).
  8. Tap Connect and accept the VPN permission prompt.

From that moment, every app on the phone — WhatsApp, the Play Store, your browser — exits through a Snowpad Indian mobile IP. SocksDroid also supports per-app routing if you only want WhatsApp to use the proxy. The full SOCKS5 setup on Android walks through the same pattern in more detail.

iOS — Wi-Fi proxy, Wi-Fi only

iOS does not have a no-root VPN-API app that is as easy as SocksDroid. The supported path is the Wi-Fi system proxy, with one honest limitation: it only works while the device is connected to that specific Wi-Fi network. Cellular traffic is not proxied.

  1. Open Settings → Wi-Fi.
  2. Tap the i next to your connected network.
  3. Scroll to HTTP Proxy → Manual.
  4. Server: gw.snowpad.io.
  5. Port: 9999.
  6. Authentication: on. Username = API key, Password = anything.
  7. Leave the Wi-Fi network and reconnect for the proxy to apply.

If you switch to cellular, turn the proxy back off in Settings, or iOS will keep trying to apply it on Wi-Fi reconnects only and your WhatsApp traffic will leak via cellular. For a longer write-up of iOS proxy caveats, see the iOS proxy setup guide.

Windows and macOS — system proxy for WhatsApp Desktop

WhatsApp Desktop on Windows and macOS respects the system HTTP/SOCKS proxy. Setting it at the OS level routes WhatsApp Desktop through Snowpad while the proxy is on, and reverts to direct when you turn it off.

On macOS: System Settings → Network → Details → Proxies → check SOCKS Proxy, set server and port, then OK and Apply.

On Windows: Settings → Network & internet → Proxy → Manual proxy setup → set the SOCKS proxy host and port. Windows handles SOCKS5 natively for apps that opt in, including WhatsApp Desktop.

Be aware: this also routes your browser and most other apps that respect the system proxy. If you only want WhatsApp Desktop proxied, set the system proxy, restart WhatsApp Desktop, then turn the system proxy back off when you are done. There is no per-app proxy toggle on either OS without third-party tooling.

What this does NOT do

A device-level proxy through Snowpad changes your exit IP. That is all it does.

  • It does not change your registered phone number or account. Your WhatsApp account, contacts, chats, status, and profile are unchanged. The service still knows your number is your number.
  • It does not unblock WhatsApp in countries where it is banned at the network layer. Snowpad Indian mobile IPs reach WhatsApp's servers normally. In a country that blocks WhatsApp server IPs themselves (China, Iran, North Korea), a Snowpad exit IP cannot reach those endpoints either. For banned-region access you need a working tunnel into an unblocking country first.
  • It does not affect the WhatsApp Business API. Business API traffic comes from Meta's servers, not your device. A SOCKS5 proxy on your machine has nothing to do with that surface.

If any of those are what you actually need, device-level proxying is the wrong tool.

Wrapping up

If your goal is to make WhatsApp traffic leave from a real Indian mobile IP, device-level SOCKS5 with Snowpad is the supported way. Pick Android if you can — it is the most flexible. On iOS, accept the Wi-Fi-only trade-off. On desktop, expect to toggle the system proxy on and off.

For background reading on the underlying mechanics, see What Is a Proxy Server and SOCKS5 vs HTTP Proxy. If you are brand new to Snowpad credentials, the console credentials page walks through where to find your API key.