Control the speed your iPhone reports

PinDrift Anti-Speed controls the speed represented by supported simulated-location output. It is intended to create a capped reported-speed profile for a route you build, but it does not alter a physical vehicle, does not touch your motion sensors, and must not be presented as a guarantee against every driving, motion, or safety-detection system.

What Anti-Speed changes

Anti-Speed is a module inside PinDrift that governs one thing: the speed represented by the simulated-location output your paired iPhone reports. When you build a route or move a simulated position, each location update carries an implied speed. Anti-Speed lets you put a ceiling on that implied speed, so the reported-speed profile stays at or below a value you choose. This is what people usually mean by control reported GPS speed or Life360 speed control.

It does not change how fast your actual phone or vehicle is moving. It does not modify the accelerometer, gyroscope, or other motion sensors. It only shapes the rate at which the simulated location advances, which is the value speed-aware apps read from location updates. If you are new to the underlying tool, the iPhone location spoofer overview explains how the simulated location is fed to the phone in the first place.

Does it use real movement, simulated movement, or both

Both, depending on how you run it.

The position is simulated. PinDrift feeds your iPhone a location from your computer, so the coordinates are computer-generated rather than read from a live GPS fix.

The pace can be driven two ways. In a pure route replay, PinDrift advances the simulated position at a speed you set, held under the Anti-Speed ceiling. In the phone-controlled live mode, Anti-Speed can read live movement signals from the phone, such as heading and accelerometer input, to pace the simulated location, then cap that pace at your ceiling. In that mode, real movement is an input to timing, but the location an app receives is still the simulated one, and the cap still applies. This is a speed-capped location simulation, not a change to the physical device.

What "speed cap" means

A speed cap is a maximum. You pick a ceiling, for example 25 mph, and the simulated location will not advance faster than that ceiling, even if a route or live input would otherwise push it higher. The result is a capped reported-speed profile: the speed carried by your location updates stays at or below the number you set.

A cap is not a guarantee about anything outside the location stream. It does not slow a real vehicle, and it does not reach signals other than the simulated location. Setting a cap of zero simply holds a static position, which reports no movement.

Supported configurations

Anti-Speed rides on top of the standard PinDrift setup. The table below lists what it needs. For the full picture, see the compatibility notes.

Phone-control workflow

Anti-Speed is designed to be driven from the phone. The desktop tab is a hand-off point, not the live control surface.

1. Pair and set up on the desktop. Connect the iPhone once over USB, then build the route or drop the position you want to move along.
2. Open the Anti-Speed tab. The desktop shows a QR code for the current session.
3. Scan with the paired iPhone. This hands the live governor to the phone over the same Wi-Fi network, or over Tailscale if you are remote.
4. Set your ceiling and start. On the phone, choose the maximum reported speed and begin. The phone paces the run while the desktop host keeps holding the spoof.

Interaction with apps that use motion data

Many location-aware apps read only the location updates iOS hands them. For those, the capped reported-speed profile is what they see, and speed-based checks like Life360's driving timeline read the value you set. The Life360 guide walks through that case.

Some apps read motion separately, through the accelerometer, gyroscope, or Apple's CoreMotion framework. Anti-Speed does not modify those sensors. If an app derives speed or motion from CoreMotion rather than from location, Anti-Speed does not control what that app reads, and we have not verified behavior against every such app. Features that depend on motion sensing, including crash detection and hard-braking or high-g event detection, fall outside what Anti-Speed controls. Treat any claim about those as unverified.

Testing methodology

A representative check we ran, so you can see what was and was not covered:

• Device: iPhone 13.
• iOS: 18.1.
• PinDrift: 1.0.39.
• Host: Windows 11.
• What we measured: the speed value carried by location updates during a simulated driving route, read back through a GPS-logging app on the same phone, with the Anti-Speed ceiling set to 30 mph.
• What we observed: across the replayed route, the reported speed tracked the route pace and did not exceed the 30 mph ceiling. Static holds reported a speed of zero, as expected.
• What we did NOT test: real in-vehicle driving; behavior across every app version; crash-detection or hard-braking alerts; and any speed value an app derives from the accelerometer or CoreMotion rather than from location.
• Was motion data involved: Anti-Speed can read heading and accelerometer input to pace the live mode, but we did not measure or alter what other apps read from those sensors. The reading above concerns the location stream only.
• Last verified: June 28, 2026.

This was a single bench configuration. Results on your device, iOS version, and target app can differ.

Limitations

• Anti-Speed shapes the simulated location's speed only. It does not alter a physical vehicle or your real movement.
• It cannot guarantee removal from every speed report, and it cannot promise compatibility with every release of Life360 or any other app.
• It does not control crash detection, and it does not control accelerometer or CoreMotion data an app may read directly.
• App behavior varies by app version, iOS version, device, and network conditions.
• The spoof, Anti-Speed included, holds only while the iPhone is connected to a running host. It is not undetectable, and no tool can promise that.

Safety disclaimer

Our full Acceptable Use policy lists what we will and will not support.

Frequently asked questions