Data lands in ArcGIS from a dozen sources, and the first professional question about any layer is not what it shows but where it thinks it is: which coordinate system its numbers are written in. ArcGIS stores that answer in two places, the layer and the map frame, and confusing them causes the classic beginner disaster of data drawn in the wrong ocean. This guide gives the exact locations in ArcGIS Pro and ArcMap, explains the default that Pro applies to new maps, and teaches you to identify an undocumented system from its extent numbers. The platform free version of the same skill, reading systems in any GIS, is how to find coordinate system; the QGIS counterpart workflow lives in how to find coordinates in qgis.
Home / Coordinates and Location Formats
How to Find the Coordinate System in ArcGIS: Pro and ArcMap, Layer and Map

Photo: Daniil Komov / Pexels
Hunt the Spatial Reference: Pro and ArcMap
Check off each step as you finish it. Your progress stays on this page.
0 of 6 complete
0% done
ArcGIS Pro: The Layer's Own System
In the Contents pane, right click the layer and open Properties. Go to the Source tab and find the Spatial Reference section: it names the coordinate system in full, for example "NAD 1983 UTM Zone 17N" or "GCS WGS 1984", with the WKID code beneath it. This is the system the layer's stored numbers are written in, the ground truth about the data itself. Expand the section and Pro also reports the layer's extent in that system's units, which becomes your identification tool in the section below. Read this tab for every layer you did not create, before you analyze anything: two layers can draw aligned in Pro while being stored in different systems, because Pro reprojects on the fly, and some tools honor the stored systems in ways the display forgives and the output does not.
ArcGIS Pro: The Map Frame's System
The map has its own coordinate system, independent of every layer. Right click the map name in Contents (or open Map Properties) and go to the Coordinate Systems tab: the current system of the map frame is listed at the top, with the available transformations below it. This frame system governs the display, the coordinate readout at the bottom of the map view, and the units of any measuring you do. A new map in Pro defaults to WGS 1984 Web Mercator Auxiliary Sphere, which surprises people twice: first because their data is not in Web Mercator (that is fine, Pro reprojects for display), and second because Web Mercator distorts area and distance, so measuring hectares or kilometers on a Web Mercator frame quietly inflates them, badly at high latitudes. For analysis, set the frame to a system suited to your region and task, or run tools that compute geodesically, and never quote a Web Mercator ruler measurement as ground truth. The readout at the map's bottom edge can also be switched between units and formats from its own dropdown, which changes the display only, never the data.
ArcMap: The Same Two Places, Older Furniture
ArcMap keeps the identical model behind older menus. For a layer: right click it in the table of contents, Properties, Source tab, where the coordinate system is named in the extent and data source summary. For the data frame: right click Layers at the top of the table of contents, Properties, Coordinate System tab, which shows the frame's current system and lets you change it. The ArcMap specific trap is the unknown system warning: when a layer with no defined system is added to a frame that has one, ArcMap draws it by assuming the layer's numbers are already in the frame's system, which can put a degrees based layer at the center of the earth or a meters based layer off the map entirely, with only a dismissible warning as notice. That warning is the subject of the next section, because it is where undocumented data announces itself.

Unknown System: Identify It From the Extent Numbers
When a layer's Source tab says the spatial reference is Unknown, do not guess and do not define randomly; read its extent and let the magnitudes testify. Extent values that look like small decimals, X between minus 180 and 180 and Y between minus 90 and 90 (for example minus 81.7, 25.9), are degrees: the system is a geographic one, most often WGS 1984 or NAD 1983, and choosing between those two is a small error (about a meter in North America) compared to every other mistake available. Values in the hundreds of thousands, like 512000, 3842000, are meters in a projected system, and the Y value's size hints at the zone and hemisphere: a northing near 3,842,000 fits UTM in the southern United States. Values in the millions with a false easting flavor, or feet sized numbers in US data (state plane coordinates in US survey feet run large), narrow it further with knowledge of where the data is from. Once identified, apply the answer with Define Projection (Pro: the geoprocessing tool of that name), which labels the data without changing a single number. Defining is labeling; Project is the different tool that recomputes numbers into a new system, and running Project on unidentified data bakes the mystery in permanently. The same identification method, written for any GIS rather than ArcGIS specifically, is in our how to find coordinate system guide.
Geographic vs Projected: Reading the Name
The name on the Source tab tells you the family at a glance. GCS (or a name like WGS 1984, NAD 1983 with no zone) means a geographic system: units are degrees, and the numbers are angles on a datum's ellipsoid. A name with UTM Zone, State Plane, Web Mercator, or a national grid means a projected system: units are meters or feet on a flattened grid, with a datum underneath (UTM Zone 17N sits on a datum the full name in the Spatial Reference section spells out). Two layers in the same projected zone but on different datums still misalign by up to a few hundred meters in old NAD 1927 data, which is why the datum half of the name matters and why Pro's Coordinate Systems tab lists transformations when the frame must bridge datums. When someone says "the layer is in UTM", the professional follow up is "on which datum", and the Source tab is where the answer lives. What a coordinate pair in each family looks like is compared in gps coordinates vs utm.
Transformations: When Frame and Layer Disagree on Datum
One Pro behavior deserves its own warning, because it presents as a data error and is actually a settings gap. When the map frame's system and a layer's system sit on different datums (an older NAD 1927 layer in a WGS 1984 frame is the classic), Pro must apply a geographic transformation to draw the layer in the right place. The Coordinate Systems tab lists the transformation in use; if none is selected or the wrong one is, the layer draws shifted, in North America by up to a few hundred meters for NAD 1927 data, with no error message, because as far as Pro is concerned an approximate placement is a placement. The symptom is a layer that is uniformly offset from everything else, aligned in shape and wrong in position, and the fix is choosing the correct transformation for the region (Pro suggests candidates) rather than moving the data. Rule of thumb: a layer that is the right shape in the wrong place by a consistent offset has a datum or definition problem; a layer in the wrong ocean has a units problem; a layer in the right place needs no rescue at all. Diagnose by the pattern before touching any tool.
Related Guides
This guide does not stand alone. The coordinates guides below take up the questions it leads into:
- How to Find the Coordinate System in Civil 3D: MAPCSASSIGN, the Status Bar, and Drawing Settings: A Civil 3D drawing carries its coordinate system inside the file, and there are four places that will tell you what it is: the MAPCSASSIGN dialog,...
- How to Find the Coordinate Direction Angles of a Moment: Cross Product First, Then the Angles: The direction angles of a moment hide a trap that the direction angles of an ordinary vector do not: nobody hands you the moment.
- How to Find the Length Between Coordinates: The Distance Formula, in 2D, 3D, and on the Earth: The length between two coordinates is the distance formula, which is Pythagoras wearing coordinates: square the gap in x, square the gap in y,...
- Geocoding in ArcGIS Pro: Build a Locator, Geocode a Table, and Rematch What Failed: what to do with addresses once the system is known
Frequently Asked Questions
Where does ArcGIS Pro show a layer's coordinate system?
Right click the layer in the Contents pane, open Properties, and read the Spatial Reference section on the Source tab. It names the full system and its WKID. That is the system the layer's stored coordinates are written in, regardless of how the map is displaying it.
Why is my ArcGIS Pro map in Web Mercator?
Because that is the default coordinate system for a new map frame in Pro. It is a display choice, not a statement about your data; Pro reprojects layers on the fly to draw them. Change it under Map Properties, Coordinate Systems, especially before measuring area or distance, which Web Mercator distorts.
What is the difference between the layer's system and the map's system?
The layer's system describes its stored numbers. The map frame's system describes the display, the coordinate readout, and on screen measurement. They can differ safely for viewing because Pro reprojects on the fly, but analysis and measurement should be planned around the stored systems and a suitable frame.
A layer says its spatial reference is Unknown. What do I do?
Read its extent on the Source tab and identify the family from the magnitudes: small decimals are degrees (a geographic system, usually WGS 1984 or NAD 1983); hundreds of thousands are meters in a projected system. Then label it with the Define Projection tool. Do not use the Project tool until the system is identified.
Define Projection or Project: which one fixes my layer?
Define Projection if the numbers are right but unlabeled: it stamps the system name onto the data without changing any coordinate. Project if the data is correctly labeled in one system and you need the numbers recomputed into another. Using Project on unidentified data converts a mystery into a permanent error.
Photo credits: Daniil Komov (Pexels); Daniil Komov (Pexels). Photos are served from this site; follow the credit to the library page for the original.