How to Use a Proxy in BlueStacks, for All Instances or One at a Time
By the ProxyV4 Engineering Team · Updated:
BlueStacks proxy setup works in one of two ways: route the whole emulator through Proxifier on Windows, or run a proxy helper app inside each instance. Recent BlueStacks versions show no proxy option in their own settings, and Android's built-in proxy settings have no login fields, so neither suits a proxy that needs a username and password. Proxifier gives every instance the same IP; a helper app per instance gives each one its own.
BlueStacks proxy settings: what the emulator offers
Older BlueStacks releases had a network option in their settings, and guides written for them still circulate. In BlueStacks 5 and later, the emulator's own settings have no proxy field (labels and menus vary by version), so the proxy has to live either on the Windows side or inside Android.
Inside Android, BlueStacks behaves like any emulator: apps that honor the system proxy use it, many games do not, and the system proxy has host and port fields only. The Android proxy setup guide covers those limits in general. ProxyV4 proxies use username and password login, so the routes that work are the ones that can carry a login.
| Route | Username and password | One IP per instance? | Notes |
|---|---|---|---|
| Proxifier on Windows | Yes | No, all instances share the player process | Captures app traffic the guest would otherwise send directly |
| Proxy helper app inside an instance | Yes, if the app supports it | Yes | Uses Android's VPN interface; app availability varies |
| ADB global proxy | No login fields | Yes | Only apps that honor the system proxy |
| Android Wi-Fi proxy fields | No login fields | Yes | May not be editable in every BlueStacks build |
Route BlueStacks through Proxifier
Proxifier intercepts the connections of the Windows processes you name and sends them through your proxy, login included. It is the simplest route when one IP for the whole emulator is enough, for example a QA machine testing one market. The general walkthrough is in the Proxifier setup guide; the BlueStacks-specific parts follow.
Add the proxy server
In Proxifier's proxy server list, add the IP and port from your ip:port:user:pass line, choose SOCKS5 or HTTPS to match the mode your order is in, enable authentication and enter the username and password. Use Proxifier's built-in check before you write any rule; if it fails here, nothing in BlueStacks will work either.
Write a rule for the BlueStacks player
Create a rule whose application list contains HD-Player.exe, the player process in BlueStacks 5, and set its action to the proxy you just added. Start BlueStacks and watch Proxifier's connection log. If the log shows other BlueStacks processes opening outside connections, add those names to the same rule.
Every instance from the same installation runs as HD-Player.exe, so this rule gives all of them one IP. Renaming executables to tell instances apart is fragile and breaks on updates; for separate IPs, use the in-instance route below.
Resolve names through the proxy
Proxifier has a name resolution setting that decides whether hostnames are looked up on your computer or through the proxy. Choose resolution through the proxy so lookups match the exit country; the exact label differs between Proxifier versions.
BlueStacks multi-instance IP: a helper app per instance
For one IP per instance, install a proxy helper app inside each instance. These apps start a local VPN through Android's VpnService and forward traffic to your proxy with the username and password you enter. Android asks you to approve the VPN connection the first time.
App availability changes, and some well-known proxy apps are no longer maintained. Choose one that is currently updated, states support for authenticated SOCKS5 or HTTP, and comes from a developer you trust, since it sees all of that instance's traffic.
Use the Multi-Instance Manager to create or clone instances, then give each one its own line. A clone copies the helper app and its saved profile, so change the proxy in the clone before opening any app. Name instances after their job and IP, such as qa-uk-01, and keep a sheet that maps names to lines.
Separate IPs keep test, client and team environments apart and let you see how an app behaves in another country. Follow each game's and platform's rules on multiple accounts; the online games proxy page explains what a game server sees and how to choose a location close to it.
ADB global proxy: host and port only
BlueStacks can expose ADB through a toggle in its advanced settings, which then shows the local address to connect to. The global proxy setting is useful for host-and-port proxies such as a local relay you run yourself, not for a proxy that needs a login.
# Connect to the instance (use the address BlueStacks shows next to the ADB toggle)
adb connect 127.0.0.1:5555
# Set and check a host:port proxy
adb -s 127.0.0.1:5555 shell settings put global http_proxy IP:PORT
adb -s 127.0.0.1:5555 shell settings get global http_proxy
# Remove it
adb -s 127.0.0.1:5555 shell settings put global http_proxy :0If you set an authenticated ProxyV4 proxy this way, expect a 407 response or no connectivity, because Android has nowhere to put the credentials.
When a ProxyV4 IP suits BlueStacks, and when it does not
ProxyV4 sells private datacenter IPv4 in the United States, Vietnam, Japan, South Korea, Singapore, the United Kingdom and Hong Kong, plus static ISP IPs registered to consumer internet providers in the United States and Vietnam. Each IP has one tenant for the whole term. Traffic on both is unmetered, so game updates and downloads inside BlueStacks do not add to the bill, and renewing before expiry keeps the same IP.
Every proxy supports HTTP(S) and SOCKS5 with username and password, which is what both Proxifier and helper apps need. On the order's page you choose HTTP only, SOCKS5 only, or both on the same port; switching can move the proxy to a new port, so copy the line again.
It is the wrong product if an app accepts only mobile carrier IPs, since ProxyV4 sells no mobile proxies, or if you need a new IP on every request, since rotating proxies are waitlist-only. IPv6 proxies are a separate product that only works on IPv6-ready sites. If your game relies on UDP, ask support through a ticket before ordering. Live per-IP rates are on the pricing page; order one IP and test it in one instance first.
Verify the exit IP and fix common problems
Open a browser inside the instance and load the my IP tool. It should show the proxy's IP and country rather than your own. For a game that never displays an IP, check the login history in the account.
- Still your own IP with Proxifier: the rule does not match the process that opens the connections. Check the connection log and add the missing BlueStacks process name.
- 407 or no connection after an ADB or Wi-Fi proxy: those fields have no login. Clear the value and use Proxifier or a helper app.
- Wrong country in lookups: set Proxifier to resolve names through the proxy, then reload.
- Connection stalls: the protocol in Proxifier or the app does not match the order's mode, or the port changed after a mode switch. Copy the line again.
- Browser works, game does not: the game may use traffic the route does not carry, such as UDP. Ask support before you assume a fix exists.
Frequently asked questions
Does BlueStacks have built-in proxy settings?
Recent versions have no proxy option in BlueStacks' own settings. Use Proxifier on Windows or a proxy helper app inside the instance.
Can Proxifier give each BlueStacks instance a different IP?
Not reliably. All instances run as the same player process, so a Proxifier rule applies to all of them. Use a helper app per instance for separate IPs.
Can I use a SOCKS5 proxy with a password in BlueStacks?
Yes, through Proxifier or a helper app that supports authenticated SOCKS5. Android's own proxy fields take only a host and port.
Will my BlueStacks instance keep its IP when I renew?
Yes. Renewing a ProxyV4 proxy before it expires keeps the same address, and you can renew all proxies or a selection.
What if the proxy fails during testing?
A proxy that fails for a technical reason, such as not connecting or showing the wrong location, is covered by the refund policy and credited to your account balance.
Private IPv4 per BlueStacks instance
HTTP(S) and SOCKS5 with username and password, unmetered traffic and the same IP on renewal. Order one IP and test it in one instance before you scale.
One IP per profile