Geofence Map Tool
Draw a circle, polygon, or rectangle zone, then export GeoJSON, WKT, KML, or coordinates for Radar, Samsara, PostGIS, or any geofencing platform.
Draw a Geofence in Under 60 Seconds
Geofence planning doesn't need to happen inside your app's SDK. Draw the boundary here first (where it sits, what shape it takes, what it should cover), then export the geometry to your production geofencing platform. This separates the planning step from the implementation step, which is usually how product and engineering teams collaborate.
- 1Go to the location. Search an address, postal code, or landmark, or tap “Use my location.” The map recenters so you can draw exactly where the zone belongs.
- 2Pick a shape. Circle for a symmetric zone (a store, a stadium), Polygon to trace an arbitrary boundary corner by corner, or Rectangle for a quick box. Circle sizes to know: 500 m for a single store, 2 km for a neighborhood, 10 km for a metro trigger.
- 3Draw and refine. Tap to place the circle center or polygon vertices, then drag the edge, the center pin, or any vertex to fine-tune. The area, perimeter, and center coordinates update in real time on the map.
- 4Export. Download GeoJSON for mapping platforms and SDKs, WKT for PostGIS and spatial SQL, KML for Google Earth or QGIS, copy the raw coordinates to your clipboard, or grab a PNG for docs. Every format works for both circles and polygons.
All exports use the standard WGS84 coordinate datum, which is what every major geofencing platform expects. No coordinate conversion needed.

What Is a Geofence?
A geofence is a virtual boundary around a real-world location. When a mobile device (or any GPS-equipped asset) enters, exits, or dwells inside the boundary, software triggers an event: a push notification, a database update, a workflow step, an analytics log.
Circle geofences are the most common type. They're defined by a center point (latitude and longitude) and a radius measured in meters or kilometers. Polygon geofences, which trace an arbitrary shape, are supported by most major platforms but require more work to author.
Geofences are enforced in two ways. On-device geofences live inside a mobile SDK and trigger events locally when the device crosses the boundary. Server-side geofences query the user's reported location against a stored boundary on your backend. The first is more efficient for battery; the second is more flexible for complex logic.
Geofencing is widely used in retail proximity marketing, fleet management, workforce clock-in automation, asset tracking, and compliance zones.
How Geofencing Works Under the Hood
Three things happen when a geofence triggers an event: the device determines its location, the system compares that location to the boundary, and software executes a response.
Location sources. Outdoors, phones lean on GPS, which GPS.gov says is typically accurate to within 4.9 m (16 ft) on a smartphone under open sky, and less accurate near buildings, bridges, and trees. Phones also locate themselves from Wi-Fi and cell networks. Android's geofencing guide says accuracy is usually 20–50 m when Wi-Fi is available, can be as small as 5 m where indoor location is available, and can grow to several hundred meters or several kilometers without Wi-Fi, for example on a drive through rural areas.
Trigger types. Platforms distinguish three event types:
- Entry: fires when the device crosses the boundary into the geofence.
- Exit: fires when it crosses the boundary going out.
- Dwell: fires when the device has stayed inside the boundary for a configured length of time.
Dwell cuts false alarms. Android's guide says that if you get many alerts from people driving briefly past a geofence, the best way to reduce them is a dwell trigger instead of an entry trigger, so the alert fires only after the device stops inside the zone for a set time.
Battery and delay. Android's geofence service does not query location continuously, so expect a delay: alerts usually arrive within 2 minutes, take about 2–3 minutes on average when background location limits apply, and can take up to 6 minutes after the device has been still for a long time. The guide adds that a longer notification responsiveness and a radius of at least 100 m both cut power use. The built-in APIs on Android and iOS monitor circles only, so an app that needs a polygon has to test the shape in its own code or on its server.
Platform limits. Apple's Core Location lets one app monitor no more than 20 conditions at once, and each geofence is one condition. Android allows 100 active geofences per app, per device user. Apps with more locations keep only the nearest ones on the device: Braze, for example, stores at most 20 per app and, when a user qualifies for more, downloads the ones closest to the user at the start of the session.
Geofence Types: Circle vs Polygon
Most geofences are circles. They're simple to author (one point, one distance), efficient to evaluate (is this GPS coordinate inside this radius?), and supported natively by every major SDK. They work well when the triggering zone is symmetric: a store location, a stadium, a workplace.
Polygon geofences trace an arbitrary shape. They're the right choice when the boundary follows a real-world feature: a city-center district, a shopping mall's actual footprint, a warehouse perimeter, a park. Polygons take more work to author (you draw each vertex) and cost more CPU to evaluate, but they eliminate the dead zones and false positives that circles produce in irregular spaces.
This tool draws all three: switch the shape selector to Circle for symmetric zones, Polygon to trace an arbitrary boundary vertex by vertex, or Rectangle for a quick axis-aligned box. Drag any vertex to reshape a polygon after you draw it, and export the result as GeoJSON, WKT, KML, or coordinates, all of which carry polygon geometry natively.
Practical rule: start with a circle. A well-placed circle serves most geofencing use cases. Reach for a polygon when the circle produces obvious false triggers at the boundary or misses obvious real-world zones, then draw it right here rather than jumping to a heavier GIS editor.
Geofencing Platforms Comparison
If you've planned your geofence here, your next step is implementing it in a production platform. Below is how the major geofencing platforms compare on the dimensions that matter for most teams.
| Platform | Type | Geofence Limit | Polygon Support |
|---|---|---|---|
| Radar | Location platform (SaaS + SDKs) | Unlimited | Yes (also isochrone) |
| Android geofencing API | Mobile SDK (Android) | 100 per app, per device user | No (circles only) |
| Apple Core Location | Mobile SDK (iOS) | 20 conditions per app | No (circles only) |
| Braze | Customer engagement | 20 per app on the device | No (circles only) |
| OneSignal | Push notifications | None built in; uses Radar | Through Radar |
Sources, checked November 2026: Radar, Android, Apple, Braze, and OneSignal documentation. Limits change, so check the current docs before you commit.
Export Formats Explained
Draw the zone once, export it in whatever format your stack speaks. Every format below works for both circle and polygon zones and uses the WGS84 datum. Because neither WKT nor KML has a native circle primitive, circles are written as a fine polygon approximation in those two; GeoJSON keeps a circle as a center point plus a radius property.
GeoJSON (the universal standard)
The format nearly every modern mapping platform and SDK ingests directly: Mapbox, Leaflet, AWS Location Service, Radar, Turf.js, and geojson.io. Coordinates are stored as [longitude, latitude] pairs. If you only learn one format, learn this one; it is the closest thing geofencing has to a lingua franca.
WKT (databases & spatial SQL)
Well-Known Text is what spatial databases understand. Paste the POLYGON((…)) string straight into a PostGIS geography column, a MySQL spatial field, or a BigQuery ST_GEOGFROMTEXT call. This is the format to use when your geofence check runs as a ST_Contains query in your backend.
KML (Google Earth, QGIS, ArcGIS)
Keyhole Markup Language opens directly in Google Earth and every major desktop GIS. Use it to review a zone visually, drop it into a mapping deck, or hand it to a GIS team that works in QGIS or ArcGIS.
Copy coordinates (raw lat/lng)
Puts the plain latitude/longitude list on your clipboard. For a circle you get the center plus the radius in meters; for a polygon, one lat, lng pair per line. Paste it into a spreadsheet, a config file, or straight into an SDK's geofence constructor.
PNG (docs & mocks)
A snapshot of the map with your zone drawn on it, for design mocks, tickets, and documentation. Not machine-readable, so use one of the formats above when you need the actual geometry.
Common Geofence Sizes and Use Cases
| Radius | Area Covered | Typical Use | Business Scenarios |
|---|---|---|---|
| 100 m | 0.03 km² | Single storefront or venue | In-store proximity offers, loyalty check-ins, foot-traffic counting |
| 500 m | 0.79 km² | City block or shopping center | Mall-level retargeting, event venue entry triggers |
| 1 km | 3.14 km² | Small neighborhood | Competitor conquesting (e.g. targeting shoppers near a rival store), hyper-local delivery zones |
| 2 km | 12.6 km² | Urban district | Walkable commute zone campaigns, university campus coverage |
| 5 km | 78.5 km² | Small city or metro core | Ride-share driver deployment zones, local news alerts |
| 10 km | 314 km² | Urban metro area | Fleet dispatch zones, regional retail attribution |
| 25 km | 1,963 km² | Metropolitan region | Sales territory boundaries, weather alerts |
| 50 km | 7,854 km² | Multi-county region | Regional distribution, franchise territory enforcement |
Accuracy, Privacy, and Platform Limitations
Before a geofence goes live, plan for these limits:
Accuracy isn't uniform. A phone's position can be off by anything from a few meters to several kilometers. Braze's documentation puts it at 5–50 m with precise location on, from GPS, Wi-Fi, and cell positioning, and Android's guide warns that without Wi-Fi, as on rural roads, the error can reach several hundred meters or several kilometers. Plan the boundary for the worst case your users will meet, or you'll get false triggers at the edges.
Small geofences are noisy. Android recommends a minimum radius of 100–150 m, and Braze asks for the same 100–150 m minimum on its geofences. A smaller zone fits inside the phone's own position error, so it misses people who are inside and catches people who aren't. For compliance, payments, or clock-in, back the geofence with a second signal.
Privacy law applies. The EU's GDPR names location data as one of the identifiers that make information personal data (Article 4). California treats a consumer's precise geolocation, meaning data that places a person within a circle of 1,850 feet (about 564 m) radius, as sensitive personal information, and consumers can tell a business to limit how it uses it (Civil Code §1798.140 and §1798.121). On Android, geofencing needs the fine location permission, plus background location for apps that target Android 10 or later. The SDKs handle the mechanics; the privacy policy and the consent screens are your job.
Platform limits bite at scale. With 20 monitored conditions per app on iOS and 100 geofences per app on Android, a chain with hundreds of stores can't register them all at once. Plan to load the zones nearest each user and refresh them as the user moves.
Frequently Asked Questions
How do I create a geofence on the map?
How do I export a geofence as GeoJSON, WKT, or coordinates?
What's the difference between a geofence and a radius map?
Can I draw polygon geofences here, or only circles?
Which export format should I use for my platform?
How accurate is the planning here vs. what my platform will enforce?
Does this tool send my geofence data anywhere?
/embed endpoint.)