Enter your State Plane easting and northing on the left and click Convert to see the latitude and longitude here.
Converting a list of State Plane coordinates? Process them all at once.
Bulk coordinate converterThe practical problem
State Plane is the dominant coordinate system in US surveying, civil engineering, and county GIS. If you work in those fields, you see SPCS coordinates daily. Everyone else - clients, contractors, web developers, end users, anyone with a phone - expects latitude and longitude.
A surveyor drops 540,123.45 ft east, 1,847,221.18 ft north on a deliverable. A GIS analyst opens a county parcel dataset and finds easting and northing columns. A civil engineer receives a CAD file with site coordinates in NY-LI or CA-3. Each of those teams needs to share that location with a project manager, a client, or a public map - and lat/long is the only format everyone agrees on.
That is the conversion this page handles. Same physical location, different notation, no datum surprises.
How to convert State Plane to lat/long with CoordinateMapper
CoordinateMapper supports every NAD83 State Plane zone, including Alaska's 10 zones (with Oblique Mercator for Zone 1) and Hawaii's 5 zones. The conversion takes seconds.
- Open the converter using the quick-convert box above or the main Convert page.
- Choose State Plane from the format dropdown.
- Select your state (for example: Indiana) and zone (for example: East). If you know the FIPS code, you can paste it instead and the state and zone will auto-fill.
- Choose your units: US Survey Feet (default for most US states), Metres, or International Feet.
- Enter your easting and northing. Commas and spaces in numbers are handled automatically, so "354,956.2317" parses the same as "354956.2317".
- Click Add SPCS point. The converter projects your coordinate from the chosen SPCS zone to WGS84 latitude and longitude and shows the result on the map.
- Copy the lat/long output or open it directly in Google Maps from the result panel.
What you need before you convert
Three pieces of information are needed for a clean State Plane to lat/long conversion:
- The easting and northing values themselves. Both are required, and easting always comes first.
- The zone. State Plane numbers alone are ambiguous - the same easting and northing can refer to completely different places in different zones. The zone is usually specified in the source file (as a FIPS code, an EPSG code, or a named zone), in the survey software settings, in the project specification, or in the document header. If none of those are available, the zone can be inferred from which US state the project is in - smaller states have one zone, larger states have two to six.
- The units. Most US states use US Survey Feet; the federal default is metres; a handful of states use international feet. Treating feet as metres produces a 3.28× scaling error - the point will land in roughly the right region but kilometres from where it should.
Common State Plane zones by state
This table covers the highest-population US states and the most frequently encountered zones, so you can quickly identify which one your data belongs to. For a full list of all 124 zones, choose the state and then the zone in the converter's State Plane dropdown.
| State | Zone | FIPS code | Typical region covered |
|---|---|---|---|
| California | Zone 1 | 0401 | Far north (Eureka, Redding) |
| California | Zone 2 | 0402 | North-central (Sacramento, Lake Tahoe) |
| California | Zone 3 | 0403 | San Francisco Bay Area |
| California | Zone 4 | 0404 | Central coast (Monterey, Fresno) |
| California | Zone 5 | 0405 | Los Angeles, San Bernardino |
| California | Zone 6 | 0406 | San Diego, Imperial Valley |
| Texas | North | 4201 | Amarillo, Lubbock |
| Texas | North Central | 4202 | Dallas-Fort Worth |
| Texas | Central | 4203 | Austin, Waco |
| Texas | South Central | 4204 | San Antonio, Houston |
| Texas | South | 4205 | Corpus Christi, Brownsville |
| New York | East | 3101 | Albany, Adirondacks |
| New York | Central | 3102 | Syracuse, Utica |
| New York | West | 3103 | Buffalo, Rochester |
| New York | Long Island | 3104 | NYC metro, Long Island |
| Florida | East | 0901 | Miami, Jacksonville |
| Florida | West | 0902 | Tampa, Fort Myers |
| Florida | North | 0903 | Panhandle (Tallahassee, Pensacola) |
| Illinois | East | 1201 | Chicago, central-east |
| Illinois | West | 1202 | Springfield, western Illinois |
| Pennsylvania | North | 3701 | Erie, Scranton |
| Pennsylvania | South | 3702 | Philadelphia, Pittsburgh |
| Ohio | North | 3401 | Cleveland, Toledo |
| Ohio | South | 3402 | Cincinnati, Columbus |
| Georgia | East | 1001 | Atlanta, Savannah |
| Georgia | West | 1002 | Columbus, Macon (west portions) |
| North Carolina | Statewide | 3200 | Entire state (single zone) |
| Michigan | North | 2111 | Upper Peninsula |
| Michigan | Central | 2112 | Central Lower Peninsula |
| Michigan | South | 2113 | Detroit, Grand Rapids |
| Indiana | East | 1301 | Indianapolis (eastern half) |
| Indiana | West | 1302 | Terre Haute, Evansville |
What to do if you do not know your zone
This is one of the most common problems with State Plane data. Try these in order:
- Check the source file metadata. CAD drawings (DWG, DGN), GIS shapefiles, GeoJSON, and DXF exports almost always include a coordinate reference system tag. Look for "EPSG:", "FIPS", "SPCS83", or a named zone like "NAD83 / California zone 3 (ftUS)" in the file properties or accompanying PRJ file.
- Check your survey software or CAD settings. Trimble Business Center, AutoCAD Civil 3D, Bentley, and Carlson all display the active coordinate system somewhere in project settings or the title block.
- Ask the surveyor or engineer who provided the data. They will know - the zone is part of the deliverable specification.
- Use the coordinate magnitude as a guide. Most SPCS eastings fall between 100,000 and 3,000,000 (feet) or 100,000 and 1,000,000 (metres). Northings vary more widely. The combination of magnitude, units, and the rough US state where the project sits is usually enough to narrow it down to one or two candidate zones.
- Try the converter's auto-pick. If you know roughly where the project is, CoordinateMapper can infer the zone from a sample point's county - SPCS zones are defined to county boundaries. Open the State Plane format, pick the closest state, and try each candidate zone until the result lands in the expected location.
The datum question: NAD83 vs WGS84
State Plane sits on NAD83. Latitude and longitude in most modern systems (GPS, Google Maps, smartphones, web maps) is on WGS84. The two datums are similar but not identical.
For most practical purposes they can be treated as equivalent - they agree to within about a metre across most of the contiguous United States, which is accurate enough for navigation, web mapping, sharing locations, and almost every non-survey use case.
For survey-grade work (sub-decimetre accuracy), a proper datum transformation between the specific NAD83 realisation in your source data (NAD83(1986), NAD83(NSRS2007), NAD83(2011)) and the appropriate WGS84 realisation (G2139, ITRF, or local equivalents) may be required. That level of precision is beyond what consumer mapping tools and most GIS applications need.
Common mistakes
- Using the wrong zone. The same easting and northing in two different SPCS zones can plot in completely different parts of the country. If your result lands in the wrong state, the wrong zone is almost always the cause.
- Confusing easting and northing order. Easting always comes first. Reversing the order produces a result that may be off the map or in a different state entirely. SPCS easting is typically smaller than northing in most zones, so if your "easting" value is larger than your "northing" value, double-check the order.
- Not accounting for units. US Survey Feet, international feet, and metres differ. The unit must match what the source data actually uses. A survey report's title block or the CAD project settings will state the unit explicitly.
- Treating SPCS27 data as SPCS83. Older surveys used the NAD27 version of State Plane, which has different zones and different parameters. SPCS27 and SPCS83 coordinates for the same point differ by tens of metres. CoordinateMapper uses SPCS83. If your data is on SPCS27, convert through a tool that supports both - or contact the original surveyor.
- Pasting lat/long into the easting/northing fields. Lat/long values are small (degrees) and SPCS values are large (feet or metres). If your easting field contains "39.123", that is a latitude, not an SPCS easting. The converter will refuse to plot a coordinate that lands far outside the chosen zone.
Frequently asked questions
- Q: How do I know which State Plane zone I am in?
A: Check the source file metadata (EPSG, FIPS, or named zone), your survey software project settings, or the project specification. If those are unavailable, the zone is determined by which county the point falls in - SPCS zones are defined to county boundaries. CoordinateMapper can also auto-pick the zone from a known lat/long approximation. - Q: What is the difference between US Survey Feet and metres in SPCS?
A: One US Survey Foot is exactly 1200/3937 metres (approximately 0.30480060960 m). Most US states use US Survey Feet for SPCS by legislation; the federal default is metres. The unit is significant - treating feet as metres scales every coordinate by 3.28×. - Q: Can I convert State Plane to Google Maps directly?
A: Yes. Convert the State Plane coordinate to WGS84 lat/long using CoordinateMapper, then paste the lat/long into the Google Maps search bar (or into a Google Maps URL like https://maps.google.com/?q=LAT,LNG). The point will plot exactly. - Q: What datum does State Plane use?
A: Modern State Plane (SPCS83) uses NAD83. Older State Plane data may still be on NAD27 (SPCS27). For most non-survey purposes, NAD83 is treated as equivalent to WGS84 within about a metre. See What is State Plane Coordinate System?. - Q: Why does my converted coordinate look wrong?
A: The three most common causes are (a) wrong zone selected, (b) easting and northing swapped, and (c) wrong units. Double-check each of those. If the result is still off, the source data may be on SPCS27 (NAD27) instead of SPCS83 (NAD83), which CoordinateMapper does not convert directly. - Q: Can I batch convert hundreds of State Plane points?
A: Not currently. State Plane conversion in CoordinateMapper is point-by-point because each coordinate requires its zone and units to be specified. For other formats (lat/long, UTM, MGRS, UK Grid), bulk paste and file upload work normally.
Takeaway
Converting State Plane to lat/long takes three pieces of information: the easting and northing, the zone (FIPS code or named), and the units. With all three confirmed, the conversion is a clean projection from your chosen SPCS83 zone to WGS84 latitude and longitude. CoordinateMapper handles the projection mathematics and the NAD83 → WGS84 datum step in one move - paste your coordinates, pick your zone, and copy the lat/long output.
Converting for CAD or survey work?
If these coordinates are going into a drawing, CoordinateMapper Pro exports your converted points as DXF, ready to reference into AutoCAD or Civil 3D without any manual re-plotting.
See what Pro includes