Home / GIS and Open Map Data for Beginners

QGIS Reproject Layer: Change a Layer's CRS Without Breaking Its Geometry

A person examining an antique world map printed on large paper

Photo: Gül Işık / Pexels

Every GIS dataset speaks a coordinate dialect. One layer stores its points as degrees of latitude and longitude, another as meters east and north in a national grid, a third in a web projection invented for tiles. QGIS is fluent enough to display them all together, which creates a dangerous illusion: because the layers line up on screen, it is easy to believe they line up in fact, and to skip the step where their coordinates are actually converted into one system. That step is reprojection, and this guide treats it with the respect it deserves. Reprojection is not a cosmetic conversion. Done right, it is invisible: the layer looks identical and only its numbers change. Done wrong, with the wrong tool or the wrong target, it moves your data across town or across the ocean while looking perfectly calm about it. The whole skill is knowing which of QGIS's three similarly named operations you are actually performing.

Interactive tool

Same Place, New Numbers: The Reproject Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 8 complete

0% done

Project CRS and Layer CRS Are Different Questions

The confusion starts with two settings that share an acronym. The project CRS, shown in the corner of the QGIS window, governs the map display and the units of your measuring tools. Each layer also has its own CRS, a property of the data itself, recorded in the layer's properties and in its files. QGIS bridges the two with on-the-fly reprojection: whatever a layer's own CRS, it is converted for display into the project CRS, instantly and silently. This is a wonderful display feature and a terrible teacher, because it means layers in three different systems can stack perfectly on your screen while remaining mutually incompatible for analysis, export, and delivery. Geoprocessing tools, other software, and anyone you send the file to will meet the layer's stored coordinates, not your screen's diplomacy. So the working rule: the project CRS is about how you look; the layer CRS is about what the data is. Reprojection changes the second one. If you are unsure what system a layer is actually in, that identification problem comes first, and our guide to finding the coordinate system of a layer works through it.

The Honest Tool: Reproject Layer

When the goal is a converted layer inside QGIS, the direct instrument is the Reproject Layer algorithm in the Processing Toolbox, among the native vector algorithms. Open it, choose the input layer, and choose the target CRS, the system the new coordinates should be written in. Run it and QGIS produces a new layer: same features, same attributes, same shapes on the ground, with every coordinate recalculated into the target system. The original layer is untouched, which is the correct posture for an operation this consequential: conversion should always write new data, never overwrite in place. The target choice is the real decision. Match the system your project has standardized on, the system the receiving software expects, or the system suited to the analysis ahead: a projected system in meters for measuring areas and distances, a geographic system in degrees for exchange and archiving. What the target should never be is a guess picked because the name sounded familiar; CRS names are dense with zones, datums, and units, and the wrong zone of the right projection is still the wrong answer, off by whole degrees of longitude.

The File Route: Export With a New CRS

Often the reprojection is really about a deliverable: a file someone else, or some other program, will open. Then the cleanest route is the export itself. Right-click the layer, choose Export and Save Features As, and the save dialog contains a CRS field. Set the format and filename as usual, set that CRS field to the target system, and the file QGIS writes contains coordinates already converted, while your working layer in the project keeps its original system. This route is the right one more often than beginners expect, because it matches the actual intent: the project's data stays canonical, and each export is a translation made for its audience. It is also the route to remember when a web service, a GPS workflow, or a colleague's older software expects degrees, or when a client demands the national grid. One warning travels with it: the CRS field in the save dialog is easy to leave at the layer's current setting, producing a perfect copy when you wanted a conversion, so read it before you click save, every time. Workflows that bring data the other way, like adding GPS coordinates to QGIS, face the mirror-image choice at import.

Detailed view of an antique world map showcasing historical cartography
Detailed view of an antique world map showcasing historical cartography

Choosing the Target: The Usual Answers

Target selection deserves one more pass, because it is the decision in the whole operation and the defaults will not make it for you. Three answers cover most real work. If the layer is joining an existing project, the target is the project's established CRS, full stop: consistency inside a body of work outranks any theoretical preference, because mixed systems are where silent errors breed. If the layer is a deliverable, the target is whatever the recipient's system expects, which is a question to ask rather than assume: a web team usually wants Web Mercator or plain degrees, a government office often wants the national grid, a GPS workflow wants degrees. If the layer is headed for measurement, the target is a projected system whose units are meters and whose distortion is small where you work: a UTM zone chosen by your longitude for most of the world, a national or state grid where one exists and the work is local. What unites the three answers is that the target comes from the data's destination, never from habit. The CRS you used on the last project is a precedent, not an argument, and a layer reprojected to a system nothing downstream speaks is work that has to be done again, this time by someone less pleased about it.

The Trap: Assign Projection Is Not Reprojection

QGIS offers another operation with a dangerously similar name, and the difference between them is the difference between translating a book and relabeling its cover. Assign Projection, in the vector geoprocessing tools, does not recalculate a single coordinate. It declares what system the existing numbers should be interpreted as. Used correctly, it is a repair tool: a layer whose CRS definition was lost or never written, but whose numbers you know belong to a specific system, gets its label restored, and the data snaps to its true place. Used as a substitute for reprojection, it is a teleportation device: take numbers written in degrees and declare them to be meters, or numbers from one grid zone declared as another, and the features relocate accordingly, sometimes subtly, sometimes to another continent. The diagnostic question is always about the numbers. If the numbers are right but the label is missing or wrong, assign. If the label is right but you need different numbers, reproject. When a layer sits in the wrong place after an operation, nine times in ten someone assigned when they should have reprojected, or the reverse. Knowing which mistake you are looking at turns a mystery into a thirty-second fix.

Datum Transformations: The Prompt That Matters

Reprojection has one more layer of depth, and QGIS surfaces it as an occasional dialog: the datum transformation choice. A CRS rests on a datum, a model of the Earth's shape and its anchoring, and converting between datums is not pure arithmetic: there can be several published transformation paths between the same pair of datums, with different accuracies, and QGIS will sometimes ask you to pick one rather than guessing. Treat the prompt as information, not interruption. It is telling you that this conversion crosses datums, and that the path matters at the level of precision survey-adjacent work cares about. For most mapping purposes the default QGIS offers is the right selection, and the correct behavior is to accept it knowingly rather than to hunt for a setting that silences the question. The deeper lesson is that reprojection is not always lossless at the centimeter level: coordinates converted between datums can shift by amounts that are invisible on a city map and significant on a construction plan. Know which regime your project lives in, and if it is the precise one, document the transformation you used alongside the data, the way you would document any other measurement decision.

Verify the Result Before You Build on It

Reprojection errors are silent, so verification is not optional. Three checks, in ascending order of strength. First, the overlay check: display the reprojected layer over a trusted basemap or a layer whose system you know, and look at whether features sit where they belong, roads on roads, boundaries on boundaries. Second, the extent check: read the layer's extent in its properties and confirm the numbers are plausible for the new system, degrees within their legal ranges for a geographic CRS, meters in the expected millions or hundred-thousands for a grid; an extent that makes no sense in the target system's units means the conversion was actually a relabeling. Third, the measurement check: measure something known, a distance between two landmarks, the width of a parcel, and confirm it comes out right in the new units; this is the check that catches zone errors and degree-meter mix-ups that pass visual inspection at small scales. Only after the third check should the reprojected layer feed real analysis, an area calculation, a join, a delivered map. The layer will look the same as it always did. That is the point of the operation, and exactly why the numbers, not the picture, are what you verify.

Related Guides

This guide does not stand alone. The GIS and open map data guides below take up the questions it leads into:

Frequently Asked Questions

Does reprojecting change my original layer?

No. Both real routes write new data: Reproject Layer creates a new layer in the project, and exporting with a different CRS writes a new file. Your original layer keeps its original coordinates. Keep it that way: if a conversion turns out wrong, the untouched source is what lets you redo it correctly.

Why do my layers line up in QGIS but not in other software?

Because QGIS reprojects on the fly for display. Your screen shows every layer converted into the project CRS in real time, whatever their stored systems. Other software, and geoprocessing tools, meet the stored coordinates directly. Reprojecting the layers into one shared CRS is what makes the alignment real instead of theatrical.

What CRS should I reproject my layer to?

The one your purpose dictates. Match the project standard when joining an existing workflow, match the recipient's expectation when delivering a file, use a projected system in meters when you will measure distances and areas, and a geographic system in degrees for broad exchange and archiving. The wrong answer is whichever one was already in the box, chosen by default.

Why did my layer vanish or land in the ocean after I changed its CRS?

Almost certainly the assign-versus-reproject mix-up: the numbers were relabeled instead of recalculated, so they are now being interpreted in a system they were never written in. Undo it by restoring the correct CRS label with Assign Projection, then reproject properly to get genuinely converted numbers.

Is on-the-fly reprojection enough for analysis?

For looking, yes. For measuring and geoprocessing, it is risky: tools may compute in a layer's stored units, so distances and areas can come out in degrees or in a mismatched grid. Reproject the layers into a shared, fit-for-purpose CRS before analysis, and your measurements inherit the right units by construction.

Photo credits: Gül Işık (Pexels); Gabriel González Encarnación (Pexels). Photos are served from this site; follow the credit to the library page for the original.