The Android proxy settings you can actually reach do not belong to your phone. They belong to one saved Wi-Fi network, they sit four taps deep inside that network's page, and they do nothing at all once you leave that network or switch to mobile data. A device-wide proxy does exist, but it is not something you can set from Settings, and Section 7 covers that case.
That is the first thing almost every guide gets wrong by omission, and it is why people set a proxy, walk out of the building, and assume it broke. The second thing they get wrong is bigger: they treat the proxy as something that controls your apps. Android's own code treats it as a suggestion apps are free to read or ignore.
This guide covers where the setting actually lives on Android 17, what it reaches and what it quietly skips, why there is no SOCKS option, what to do when a work profile has locked the field, and the one method that really does push every app through a proxy without rooting anything.
Quick Answer: Android Proxy Settings
What the Proxy Setting on Android Actually Is
It is a place to name a middleman. Instead of your phone fetching a web page directly, it asks the server you named to fetch it, and the site sees that server's address instead of yours. Google's own help page describes it in one line: "A proxy is like a gate or tunnel between devices."
On a personal phone the correct value is None, and it almost certainly already is. A proxy is something a workplace, a school or a provider hands you, not something you switch on to be safer. The mechanism itself is not specific to Android, and if you want it from the ground up, our full explanation of how a proxy server works and where it sits in a network covers it.
What is specific to Android is the scope. The field belongs to a saved network, not to the device, which is a narrower thing than the word "settings" suggests. If you arrived here because some screen on some device asked you to configure a proxy, the general version of that question is answered in what that Configure Proxy setting is asking for. Knowing where it lives on Android is the next step.
Where Android Proxy Settings Live, and What the Three Options Do
Google publishes the path, and it is worth quoting because it is shorter than every guide built on top of it. From Google's own Pixel help page: open Settings, tap Network & internet then Internet, tap a network, tap Edit then Advanced options, and under "Proxy" tap the down arrow and pick the configuration type.
Two details in that sequence trip people up. You tap the network you are already joined to, not a plus button, and the proxy fields hide behind Advanced options, which is collapsed by default. Samsung's One UI groups the same fields under Connections and Wi-Fi instead of Network & internet. Samsung publishes no documentation for this screen, so treat that as a pointer rather than a citation; the fields themselves are identical once you reach the network's Advanced section.
| Option | What it does | When you want it |
|---|---|---|
| None | No proxy on this network | Every personal phone, unless told otherwise |
| Manual | You type a Proxy hostname, a Proxy port, and optionally a bypass list | Somebody gave you those exact values |
| Proxy Auto-Config | Downloads a PAC script from a URL and follows its rules | A workplace gave you a PAC file address |
Those three labels come from Android's Settings source rather than from Google's help page, which only tells you to "pick the configuration type" without naming the options. Worth knowing about the third one: there is no auto-discovery mechanism behind it in Android's Settings source, so selecting Proxy Auto-Config and leaving the URL box empty appears to switch nothing on. With no URL to paste, None is the setting you want.
One oddity before we move on. The page above is Google's Pixel help. Its general Android help page for advanced network settings promises "proxy settings" in the description Google shows in search results, then covers metered Wi-Fi, MAC addresses, certificates and Private DNS without using the word proxy once. If you do not own a Pixel, Google's page for your phone advertises this answer and does not give it.
Why Some Apps Follow the Proxy and Others Ignore It
Android answers this on the screen itself, and no guide on the subject quotes it. The warning string in Android's Settings source reads: "The HTTP proxy is used by the browser but may not be used by the other apps." That is not a caveat somebody added to a blog post. It is the operating system managing your expectations at the moment you type the address in.
The reason is in the class behind the screen. ProxyInfo, whose comment in the Android source says: "Proxy configurations are already integrated within the java.net and Apache HTTP stack. So URLConnection and Apache's HttpClient will use them automatically. Other HTTP stacks will need to obtain the proxy info by watching for the PROXY_CHANGE_ACTION broadcast and calling methods such as ConnectivityManager.getDefaultProxy."
Read that twice, because it is the whole answer. An app built on Android's standard HTTP plumbing picks up your proxy for free, with nobody writing code for it. An app that ships its own networking stack has a documented way to opt in, and plenty simply never do. It is less a decision than a consequence of what the app was built on.
This also makes it an application-layer arrangement rather than a network-level one, which is different again from a desktop browser that can override the machine, as covered in our guide to where Chrome's proxy settings really come from. On Android there is one published value, and software reads it or does not.
What It Does Not Cover: Mobile Data, DNS and SOCKS
Several gaps account for most of the "my proxy is not working" traffic on this topic, and none of them is a fault in your configuration. Android's own framing gives the game away: the managed, device-wide proxy is documented as the network-independent one, which tells you what the ordinary kind is.
| What people expect | What Android actually does |
|---|---|
| The proxy follows the phone | It is stored with one saved Wi-Fi network. Another network is untouched |
| It covers mobile data too | No. Leaving Wi-Fi leaves this proxy behind. Cellular has its own proxy fields, inside the APN, and carriers normally lock them |
| DNS goes through it | Not your phone's. Private DNS is its own setting. For a request that does use the proxy, the proxy resolves the name |
| You can enter a SOCKS5 proxy | No. The field is HTTP only, and the reason is structural |
| You can add a username and password | No. There are no credential fields on that screen |
The SOCKS answer is worth more than a flat no, because the limit runs deeper than the screen. ProxyInfo, the object behind the field, declares a host, a port, an exclusion list and a PAC file URL, and nothing that records a scheme. And it is not a phone-only object: in Google's Android Management API, the policy field that sets a device-wide proxy is typed as that same ProxyInfo. One structure, with no protocol in it, from the Wi-Fi screen to the management console.
So this is not a missing checkbox that a future Android might add to the screen. With no scheme recorded anywhere, proxy support on Android is modeled end to end as an HTTP proxy, and SOCKS would need a different object rather than a longer dropdown. iPhone lands in the same place by a similar route, which we covered in what the Configure Proxy screen does on iPhone and iPad.
Private DNS deserves its own paragraph because it causes a specific confusion, and because almost every guide on this topic gets the direction backwards. Private DNS is a separate setting on the same screen, and the Proxy field does not touch it. What people then expect is that setting a proxy will change what their phone resolves. It does not, and the reason is the opposite of "DNS goes around the proxy".
For a request that does go through an HTTP proxy, RFC 9112 has the client send the entire target URI to the proxy, which is then "requested to either service that request from a valid cache, if possible, or make the same request on the client's behalf". The proxy looks up the name and contacts the site. Your phone never resolves it. So your own DNS settings sit there unchanged, a DNS leak test reports the same resolver it always did, and none of that means the proxy failed.
If Someone Gave You a Proxy to Enter
Use this when an employer, a school or a provider handed you a host and a port. To set up a proxy on Android there is nothing to install, no proxy handler to add, and no account to make. The whole setup is the five steps below and it takes about a minute. If a proxy is already set and you want it gone, skip to the next section.
1 Open the right network
2 Expand Advanced options and choose Manual
3 Enter the hostname and the port separately
4 Fill "Bypass proxy for" only if you were told to
5 Save, then confirm from outside
Two mistakes copied straight from other guides
Setting one is straightforward. Removing one you did not set is where people lose an evening.
How to Turn Off a Proxy on Android
Same path, one change: Settings, Network & internet, Internet, tap the network, Edit, Advanced options, set Proxy to None, then Save. That is how you disable a proxy on Android, and for most people it ends there.
What catches people is repetition. Because the value belongs to a saved network, clearing it at home does nothing to the network at work, the one at a relative's house, or a café you joined once and forgot. A proxy that keeps coming back is usually a different saved network, not a setting that refuses to stick.
If you want a network gone entirely rather than corrected, forgetting it removes the stored proxy with everything else, at the cost of retyping the password next time. And if the underlying goal is a different address rather than no proxy, that is a separate job covered in our walkthrough of changing the IP address on an Android phone.
If the Proxy row will not change at all, the reason is not on this screen.
When You Cannot Change It: Work Profiles and Managed Devices
A field you cannot edit means an administrator owns it. On Android that happens through device management, and the mechanism has a name worth knowing because the name is the whole lesson.
Android exposes setRecommendedGlobalProxy, and Google's Android Management API reference carries the matching policy field, recommendedGlobalProxy. Android's documentation for the method calls it a "network-independent global HTTP proxy" and states that it "requires the caller to be the device owner". That is the whole reason you cannot reach it: it is not a hidden screen, it is an API only a management app can call.
Android says it outright, twice
| Kind of proxy | How far it reaches | Who can put it there |
|---|---|---|
| The Proxy field in Advanced options | One saved Wi-Fi network, and only apps that read it | Anyone who can open Settings on the phone, including you |
| Recommended global HTTP proxy | Network-independent, so Wi-Fi and mobile data, but still only apps that read it | A device owner app on a managed device. Not an ordinary app |
| A VPN-based routing app | Every app, on any connection, whether or not they read proxy settings | Any app you install and then grant VPN permission to |
That third row is the only one that does not depend on an app's goodwill, which is why it is the last section on this page.
On a company or school device you are not going to override it, and you should not try. The profile is the reason the device is managed. There is one quirk administrators run into that is worth knowing if you are on the other side of this. Android's own note on the method: "The device owner won't be able to set a global HTTP proxy if there are unaffiliated secondary users or profiles on the device." That is why a policy sometimes appears to apply to nothing at all.
Android 17 added a change that touches this corner directly. Google's behavior notes state: "Beginning with Android 17, cross-profile loopback traffic is no longer permitted by default. Loopback traffic within the same profile is not affected. This change applies to all apps running on Android 17 or higher, regardless of what API level the app targets."
Read that last clause twice. It lands on apps that already exist, without waiting for anyone to rebuild them. My own read is that the setups at risk are the ones with a local listener on one side being reached from the other, which would include some proxy and filtering tools. Google names none, and traffic staying inside one profile is untouched.
There is also a quieter case: a personal phone where an app you installed is doing the routing. That is not this screen either, and it leads to the last question on this page.
How to Actually Route Every App Through a Proxy
Two beliefs follow this question around: that forcing a stubborn app through a proxy needs root, and that an app which ignores the proxy simply cannot be made to use one. Neither is true, and the real answer is neither exotic nor difficult.
An app can ask you for permission to run a VPN service, and once you grant it that app opens a tunnel interface and can carry every app's traffic to an upstream proxy. No root involved. Android's developer documentation is explicit about the scope, in one sentence: "If you don't create allowed or disallowed lists, the system sends all network traffic through the VPN."
Android then lets you lock it down. Android Enterprise Help documents always-on VPN in a line worth having: "Android can start a VPN service when the device boots, and keep it running while the device or work profile is on." It is available in Android 7.0 or higher, and it pairs with a switch called Block connections without VPN. That same Google page still prints an older menu path with an "Advanced" step in it; on current Android the switch sits beside your VPN entry directly under Network & internet.
One warning Google attaches and most guides drop: "When non-VPN traffic is blocked, apps that aren't in an allowed list or in a disallowed list lose their network connection." They do not quietly fall back to an ordinary connection. They go offline.
Be clear about the trade you are making. That app now carries all of your traffic and can see where it goes, so it deserves the same scrutiny as any VPN, including checking that it is actually doing what it claims. Our guide to checking whether your IP is leaking past a VPN covers the tests, and our browser leak test shows what a page can still read from your browser regardless.
The Short Version
Android proxy settings live inside one saved Wi-Fi network, behind a collapsed Advanced options section. On a personal phone the right value is None, and an empty field means no proxy is enabled on that network.
The field is narrower than it sounds. It does not travel to other networks, it has nothing to do with mobile data, it leaves your phone's own DNS settings alone, and it has no room for SOCKS or for credentials because the object behind it holds only a host, a port, an exclusion list and a PAC URL.
Most apps follow it because Android's standard HTTP plumbing reads it for them, not because their developers chose to. Google's own documentation for the managed version says the proxy "is only a recommendation", which is the fairest description of the whole feature. If you need every app covered, that is a VPN-based tool plus always-on VPN, not this screen.
Whatever you change here, verify it from the outside rather than trusting the field. Our IP trust score checker tells you how the address you are actually leaving from is classified, which answers the real question faster than any settings page can.