Mock location has been a two-tap developer setting on Android since 2014, and that has not changed heading into September 2026. There is no new native spoofing capability to report here, just the same Developer Options toggle Google shipped more than a decade ago. It still works, and demand for it keeps climbing: the global GPS spoofing app market hit $2.33 billion in January 2025 and is on track to reach $2.59 billion in 2026 at an 11.38% CAGR, per IReS/Global Info Research. Android’s own slice of that spend came to roughly $86.61 million in 2025, according to a June 2026 PW Consulting estimate — a reminder that most of the category’s dollar growth still traces back to the platform with the two-tap toggle. It also gets caught within seconds by most apps worth spoofing. For background, see our recent coverage.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Android vs. iOS at a glance
Both platforms open through an official developer interface rather than a jailbreak or a root exploit, but the two paths behave differently enough to be worth comparing before working through the steps below.
| Aspect | Android | iOS |
|---|---|---|
| Native path | Developer Options, then a mock-location app (Steps 1-3) | Developer Mode, then Xcode’s Simulate Location (Steps 7-8) |
| What you need first | An installed app that declares android.permission.ACCESS_MOCK_LOCATION | A Mac running Xcode and a custom .gpx waypoint file |
| Manual cleanup required | Wi-Fi/Bluetooth scanning, timezone and locale, set by hand (Steps 4-5) | None client-side — the simulated fix only affects the connected app |
| How long it holds | Until the mock app is switched or force-stopped | Ends the moment the USB cable is disconnected |
| What still gives it away | The mock-provider flag on the location object | Significant Locations history and Find My, which keep syncing the real position (iOS 27’s Find My can pause sharing with one contact for up to 12 hours, but that does not touch the coordinate itself) |
| Cost | Free | Free, but requires access to a Mac |
The four signals that decide whether a spoof holds
Almost no serious app trusts GPS coordinates on their own. Android’s fused location provider blends satellite fixes with Wi-Fi scan results, Bluetooth beacons and cell tower identifiers, and any app receiving a location object can inspect whether that object arrived from a mock provider. Three more checks run server-side, in parallel: the IP address the request came from, the timezone the device reports, and the language headers the client sends.
A spoof fails when those four disagree with each other. Coordinates in Toronto, a device timezone of Europe/Madrid and an IP allocated to a Spanish residential ISP is not a location. It is a flag.
Google’s turndown of the SafetyNet Attestation API in January 2025 pushed developers onto the Play Integrity API, which reports whether a device passes hardware-backed integrity checks. A phone with Developer Options unlocked and a mock provider running fails a meaningful share of those checks on its own, before anyone looks at the coordinates.
Everything below assumes the goal is a consistent set of signals rather than one convincing fake coordinate.
Android still hands you the keys
Step 1. Install the mock provider first
Android will not populate the mock location dropdown until at least one installed app declares android.permission.ACCESS_MOCK_LOCATION in its manifest. Install the app before hunting for the setting, otherwise the menu appears empty and the usual conclusion is that the feature was removed.
Step 2. Unlock Developer Options
Settings, About phone, then tap Build number seven times. On Samsung and Xiaomi builds the entry sits under Software information.
Step 3. Select the mock location app
Developer options, then Select mock location app. One app at a time. Switching requires closing the previous one, and some apps hold the provider until force-stopped. For a cleaner reset, open Select mock location app again and choose Nothing — Google’s own documentation confirms that stops the override immediately, which beats hunting down a stubborn app to force-stop.
Step 4. Cut the scanning signals
This is the step most guides skip. Under Location, Location services, turn off Wi-Fi scanning, Bluetooth scanning and Google Location Accuracy. Left on, the fused provider keeps harvesting real Wi-Fi BSSIDs from the surrounding area, and those map to a physical address with roughly 20 metre accuracy in dense cities.
Step 5. Match timezone and locale by hand
Disable automatic date and time, then set the timezone for the target region. Change the system language region as well if the app serves market-specific content. Two minutes of work that removes the cheapest detection method in existence.
Where most of this falls apart
Step 6. Deal with the IP address
The device layer is the easy half. Every request still leaves the handset from an IP address, and commercial geolocation databases resolve that address to a city or a region with enough confidence that streaming platforms, betting operators and banks all rely on it. MaxMind GeoIP2 remains the most widely deployed of these. No amount of GPS mocking touches that layer.
Masking it means routing traffic through an endpoint in the target region, and the tooling for that is a crowded, uneven category — one WiseGuy Reports valued at $1.4028 billion globally in 2025 and projects will grow to $4 billion by 2035 at an 11.0% CAGR, in a report published June 2026. The 2016 CSIRO, UC Berkeley and UNSW analysis of 283 Android apps requesting VPN permissions found 38% flagged for malware by VirusTotal and 84% leaking IPv6 traffic outside the tunnel, which is a useful reminder that the category punishes casual selection. Gizmodo published a breakdown of what separates the usable options from the rest if the shortlist matters more than the mechanism.
Two failure modes survive even a correct setup: DNS queries resolving through a local resolver, and WebRTC exposing the real address from inside a browser session. Both are worth testing rather than assuming.
iOS does not offer the same door
Step 7. Turn on Developer Mode
Required on any iPhone running iOS 16 or later, and Apple still gates it the same way heading into 2026: Settings, Privacy & Security, Developer Mode, then restart once the toggle is switched on. That same setting covers more than Xcode — the computer-based location changers described in Step 9 need Developer Mode enabled before they can touch the device’s reported position, too. The toggle only appears after a development tool has attempted to connect at least once.
Step 8. Feed Xcode a GPX file
Connect the iPhone to a Mac running Xcode, create an empty project, then use Debug, Simulate Location. A custom .gpx file with a single waypoint holds a static position. Multiple waypoints produce movement, which matters because a coordinate that never drifts by a metre is itself suspicious.
Step 9. Accept the limits
The simulated fix ends when the cable comes out. iOS also keeps Significant Locations history and syncs location to Find My independently of what Xcode reports, so the spoof covers the app in front of you and nothing else. That gap narrowed slightly in September 2026: iOS 27 added a native hide-location control inside Find My that lets a user stop sharing their real position with one specific contact without notifying that person, reverting automatically after 12 hours by default or after a custom duration, according to MacRumors and Business Insider reporting on September 14, 2026, with The Apple Post confirming the custom-time option on September 16. It is a sharing toggle, not a coordinate spoof — the device’s actual GPS fix and its Significant Locations history are untouched, and any app reading location directly still sees the real position. For the narrow case of hiding a live location from a friend or family member inside Find My itself, iOS 27 now does that natively instead of requiring a workaround.
Desktop utilities that promise the same result without Xcode exist, and as of September 2026 the guides for this keep pointing at computer-based tools ahead of phone-only methods. 3uTools and Fonelora Location Changer are two names that come up alongside iToolab, and most of them do exactly what Xcode does through the same Developer Mode interface, with a subscription attached. iToolab’s own October 2026 product listing goes further, specifically advertising compatibility with iOS 27 and Android 17, which signals these desktop tools are being updated in step with each new OS release rather than lagging behind them. These typically pair with the iPhone over USB or Wi-Fi and apply the new coordinate from the desktop app once it is connected — less fiddly than hand-editing a .gpx file, but still gated behind the same Step 7 toggle. Their 2026 marketing has not moved from one line: iToolab and a wave of YouTube guides still sell the pitch as jailbreak-free for iPhone and root-free for Android. That claim is accurate as far as it goes, since neither platform has ever required jailbreaking or rooting for this specific technique. Xcode’s simulated location and Android’s Developer Options are both sanctioned, documented features, not exploits. The ones that ask to install a configuration profile or a helper daemon are asking for persistent system access to solve a problem that a free Apple toolchain already solves. That trade is rarely worth making.
Browsers are a separate fight
Step 10. Override geolocation at the browser layer
Chrome DevTools, Sensors panel, Location override handles the HTML5 Geolocation API. That API is one input among several. Sites routinely read Intl.DateTimeFormat().resolvedOptions().timeZone, compare it against the claimed position, and quietly discard the session when the two conflict.
Firefox exposes the equivalent control through geo.provider.network.url in about:config, which redirects the lookup to a JSON endpoint returning fixed coordinates. Useful for testing, awkward for daily use, and it does nothing for the timezone check. The DevTools override also resets on every browser restart, which catches people out more often than it should.
One detail worth carrying over from the mobile section: browser extensions marketed as location changers frequently request permission to read and modify data on every site visited. That is a wide grant for a narrow function.
Check the work before relying on it
Step 11. Verify each layer separately
A real check treats the IP-derived city, the DNS resolver’s apparent country, WebRTC exposure, browser timezone and reported locale as five distinct results, not one. A setup that passes four out of five is a setup that fails, because detection looks for contradiction rather than for any single wrong value.
| Signal | What it reveals | Quick way to check it |
|---|---|---|
| IP-derived city | The city or region a commercial geolocation database assigns to the connection | Any IP lookup tool, or the location a streaming or banking site displays back |
| DNS resolver country | Which country’s network actually resolved the request | A DNS leak test |
| WebRTC exposure | The real IP address leaking from inside a browser session even when the displayed IP is masked | A WebRTC leak test run in the browser being used |
| Browser timezone | The Intl.DateTimeFormat() timezone the browser reports, checked against the claimed position | The browser’s own developer console |
| Reported locale | The language and region headers the client sends with each request | The network inspector in the browser’s developer tools |
The three-step tools now crowding this search
Search for ways to spoof a location today and the walkthrough above is not what most results show. The dominant format as of September 2026 is a three-step pitch: choose a mode, connect the phone, change the GPS position. Mock-location apps as a category had racked up roughly 14.8 million global downloads by May 2026, according to gOGig, and individual titles do serious numbers on their own — The High Tech Society’s August 2026 count found just 9 dedicated GPS-spoofing apps spread across Android and iOS, yet one of them, Lexa’s Fake GPS, had already amassed roughly 56 million downloads by that same tally, far outpacing the Android app Fake GPS Location – LocaEdit, which crossed 1 million installs on March 1, 2025, per AndroidRank. The update cadence is just as telling: APKMirror shipped Fake GPS Location Professional version 1.93 in May 2026, still listing support back to Android 5.0, which shows developers keep polishing these apps for hardware most manufacturers stopped selling years ago. iToolab’s own 2026 materials describe the process in exactly those terms, and a wave of 2026 YouTube walkthroughs for both Android and iPhone repeat the same shape. Tap a location on a map, hit start, done.
That framing is not wrong, but it skips a detail worth spelling out. On Android, GUI tools in this category still need a way to feed a fake coordinate to the operating system, and the interface available to a third-party app without root is the same mock-location provider this guide uses in Steps 1 through 3. The installer usually sets the app as the system’s mock location app automatically, but the underlying hook has not changed, and neither has the underlying tell: a location object flagged as arriving from a mock provider. Rooted devices sidestep that entire mechanism: the LSPosed module XposedFakeLocation reached version 0.1.4 in August 2026, and because it requires a rooted Android 11 or later handset to hook location calls directly, it never has to declare ACCESS_MOCK_LOCATION or trip the mock-provider flag the rest of this section relies on — a narrower audience, since rooting itself is the harder barrier, but a cleaner bypass for anyone who clears it. Lexa’s Fake GPS, one of the handful The High Tech Society tracked in its August 2026 rundown, still lists support back to Android 5.0, which is part of why a decade-old hook keeps racking up downloads across such an old spread of hardware. An app checking for that flag does not care whether a human tapped through Developer Options or a GUI tool did it on their behalf.
On iPhone, the pattern is similar. No jailbreak is the headline claim on nearly every 2026 product page and guide in this category, and it holds up. These utilities connect through the same developer-mode interface Xcode uses to simulate a location, which is why nearly all of them still require a cable and a running desktop app instead of working as a standalone phone tool. That is the same tether described above in Step 9, marketed under different words.
None of this makes the three-step tools a bad choice, and the market numbers back that up: DataInsights Market sized the Fake GPS Location apps segment at $500 million in 2025, while its broader Location Changing App category — the subscription tools bundling Developer Options, mock-provider selection and app-switching — was projected to reach $1.5 billion that same year, a total well above PW Consulting’s narrower June 2026 estimate of $86.61 million in 2025 Android-specific spoofing-app revenue, which suggests most of the wider figure comes from iOS-side subscriptions and cross-platform bundles rather than Android alone. A subscription that handles all of that in one interface removes real friction, particularly for anyone who wants one setup to work across an Android phone and an iPhone without learning two separate menus. What it does not do is remove the detection surface described earlier. The fused location provider still flags the source, the IP address still resolves to a real city through a database like MaxMind, and timezone and locale still need to match by hand in most of these tools, exactly as they do in Developer Options. A three-step interface changes how many taps the job takes. It does not change how many independent signals an app on the other end is checking.
For a one-off check, such as seeing how a storefront or a streaming catalog looks from another country, the free native tools this guide walks through are still the faster path, since neither Developer Options nor Xcode’s location simulator costs anything beyond setup time. The three-step tools earn their subscription when the job repeats often enough that reopening Developer Options or Xcode each time becomes the real cost.
What this looks like in two years
The direction of travel is attestation, not coordinates. Play Integrity already reports device state alongside the location payload, and the practical consequence is that the presence of Developer Options becomes evidence regardless of what the GPS says. Banking apps have enforced that logic for years. Ride-hailing and delivery platforms adopted it after driver-side fraud became a measurable cost line.
There is a second pressure worth watching, and it cuts against hardware spoofing too. DataIntelo sized the dedicated GPS spoofer hardware market at $140 million in 2025, with GPS spoofer devices holding a 48.3% share and consumer electronics accounting for just 10.2% of that spend, in a report published May 2026 — a niche next to the app ecosystem described above. Dual-frequency GNSS receivers, standard on flagship handsets since roughly 2020, pick up the L5 civilian band alongside L1, and the raw measurement data those chipsets expose to Android gives developers a way to compare reported position against observable satellite geometry. Few apps do that today. The API has been sitting there since Android 7.
Which leaves an odd conclusion for anyone reading a step-by-step guide: the device-level techniques are the part with a visible expiry date, and the network layer is the part that keeps working precisely because it never touches the device at all.
Frequently Asked Questions
Is it legal to spoof your phone’s GPS location?
In most jurisdictions, changing the location your own device reports is not illegal by itself. Android’s Developer Options and Apple’s Xcode location simulator are both official, documented features rather than exploits. What creates legal or contractual exposure is what the spoofed location gets used for. Violating a service’s terms of use, committing fraud, or evading a court-ordered restriction turns a technical setting into a real problem. Check the terms of service for any app before spoofing location inside it, since a ban for a policy violation is far more likely than any legal action.
Will apps be able to tell I’m using a fake location?
Increasingly, yes. As the detection section above covers, apps built to care about location cross-check the GPS coordinate against the device’s mock-provider flag, the IP-derived location, the timezone, and the language setting, and Google’s Play Integrity API adds a device-level integrity check on top of all four. A spoof that gets only the coordinate right and ignores the other three signals is the most common way these attempts get caught.
Do I need to jailbreak my iPhone or root my Android phone?
No. Every method in this guide, and nearly every third-party tool marketed for this purpose in 2026, works through each platform’s own developer interface: Android’s Developer Options with a mock-location app, or the same Xcode simulate-location feature the third-party desktop tools connect through. iToolab’s 2026 materials and a wave of YouTube guides for both platforms advertise this explicitly as jailbreak-free and root-free, and the claim holds because neither the built-in method nor the tools that wrap it require modifying the operating system itself — as of iToolab’s October 2026 listing, that root-free, jailbreak-free pitch is now explicitly extended to cover iOS 27 and Android 17. The one notable exception is the rooted-only LSPosed module XposedFakeLocation, which reached version 0.1.4 in August 2026 and, by design, requires rooting an Android 11 or later device rather than working around it.
What is the difference between a VPN and GPS location spoofing?
A VPN changes the IP address a server sees, which affects IP-based geolocation and content-licensing checks but only indirectly touches signals like device timezone. GPS spoofing changes the coordinate an app receives from the device’s own location APIs. Apps that check IP location alone can be satisfied by a VPN. Apps that request GPS permission need the device-level mock location as well, since a VPN does nothing to the coordinates Android or iOS actually reports.
Does location spoofing still work on apps like Pokemon GO, dating apps, or streaming services?
It depends entirely on how aggressively that specific app checks for mock locations, and that changes often enough that no guide can promise a lasting answer. Gaming and dating apps have historically been among the most aggressive at detecting and banning spoofed accounts, since accurate location is core to how both categories function. Streaming and e-commerce platforms tend to lean more heavily on IP-based geolocation, which is why the network layer covered earlier in this guide matters as much as the device-level steps for that particular use case.
Does the iOS 27 Find My hide-location feature count as spoofing?
No. The Find My update that MacRumors and Business Insider covered in mid-September 2026 lets a user hide their real-time location from one shared contact for 12 hours by default, or for a custom duration, without notifying that person. It only changes who can see the location already stored in Find My — it does not alter the coordinate the device reports to other apps, and it leaves Significant Locations history untouched. Anyone who needs the device itself to report a different position to a specific app still needs Xcode’s Simulate Location (Step 8) or, on Android, a mock-location app (Steps 1-3).





