Digitizing without snapping produces a particular kind of almost-right data: the road that ends a hair before the junction, the parcel boundary that overlaps its neighbor by a sliver too thin to see at working zoom, the polygon that looks closed and is not. These defects are invisible at the scale you drew them and expensive at every scale afterward, in broken networks, failed overlays, and areas that sum to slightly more than the earth they cover. Snapping exists to prevent them at the moment of creation, by making your cursor magnetic: near an existing vertex or segment, the point you place snaps exactly onto it, so shared geometry is shared precisely, not approximately. QGIS implements snapping richly and controls it from one toolbar. This guide enables it, sets its behavior deliberately, and introduces the companion options that turn a magnet into a system for clean topology.
Home / GIS and Open Map Data for Beginners
QGIS Snapping: Enable It, Set the Tolerance, and Make Vertices Meet

Photo: Tima Miroshnichenko / Pexels
Vertices That Meet: The Snapping Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
Enable Snapping: The Toolbar and the S Key
Find the Snapping Toolbar, usually docked with the digitizing tools; if it is missing, enable it from the View menu's toolbars. Its first button, Enable Snapping, is the master switch, and the keyboard shortcut S toggles it while you work, which is how experienced digitizers actually run it: snapping on for boundary work, flicked off for free sketching, on again for the close. When snapping is live and your cursor comes within tolerance of a snappable feature, the cursor shows the snap indicator, a small magenta marker that jumps to the vertex or segment being offered. That indicator is your ground truth: if it does not appear, you are not snapping, whatever you believe about the settings, and the point you place will land where the cursor floats rather than where the geometry is. Build the reflex of watching for the indicator on every placement that is supposed to touch existing work. Our polygon drawing guide assumes this reflex throughout its closing-boundary routine; this guide is the settings workshop underneath it.
Snap Modes and Tolerance: The Two Decisions That Matter
With snapping enabled, two settings shape its behavior. The snap mode chooses what the magnet attracts to: vertex only, for work that must land exactly on existing corners; segment only, for planting points along existing lines, a new junction midway along a road; or vertex and segment, the general-purpose choice for most boundary digitizing. The tolerance sets how close the cursor must come before the magnet takes hold, and it is measured in one of two currencies. Pixels mean screen distance, forgiving and zoom-dependent: at 12 pixels the snap feels the same at every scale, which suits sketching and tracing over imagery. Map units mean ground distance, meters or degrees of the project CRS, which suits precision work: a tolerance of half a meter means the same thing zoomed in or out, and it is the honest setting when the data must meet a specification. Set tolerance too wide and the cursor grabs geometry you did not mean, across the street, onto the wrong parcel corner. Too narrow and you spend the session chasing the indicator. The craft is to start at the default, notice which failure you are having, and adjust in the direction of the evidence.

Layer Scopes: Current, All, and the Advanced Configuration
Snapping needs to know which layers are magnetic. The toolbar's scope choice offers three levels. Current layer restricts snapping to the layer you are editing, right for self-contained work like closing a polygon on its own first vertex. All layers makes every visible vector layer a snap target, right for drawing a new road network against existing parcels and boundaries. The third level, the advanced configuration, opens a per-layer table where you set, for each layer, whether it snaps at all, to vertices or segments, and with what tolerance. This is where serious projects live: the reference cadastre magnetic at a tight tolerance, the rough sketch layer non-magnetic so it never hijacks your cursor, the imagery-adjacent layers set to vertices only. Reach for the advanced configuration the first time you catch your cursor snapping to something irrelevant; that annoyance is the signal that one global setting has stopped fitting the project. The same dialog family holds two further options that deserve their own sections, because they change what snapping means: snapping on intersections, and the tracing and topological editing companions.
Snapping on Intersections, Tracing, and Topological Editing
Snapping on intersections extends the magnet to places where two segments cross without a vertex: with it enabled, you can snap a new point exactly onto a crossing, the spot where a new path meets a road at a point neither line bothered to mark. Enable it when networks and crossings are your subject. Tracing is snapping's partner for following existing geometry: with tracing enabled, your digitizing cursor, having snapped to a start point, will follow the existing line's vertices as you move toward the next snapped point, so a new boundary that shares a long edge with an old one copies that edge faithfully instead of approximating it click by click. Use it whenever a new feature shares more than a couple of vertices with an existing one. Topological editing, a separate toggle on the same toolbar, makes edits respect shared geometry after the fact: move a vertex that two polygons share, and both polygons move, so the clean edges snapping created stay clean under revision. Its companion setting, Avoid Overlap, found in the project's snapping options, refuses to let a new polygon overlap specified existing ones while you draw. Together with the vertex tool, which reshapes existing geometry vertex by vertex, these options form the full kit: snap to create cleanly, trace to share faithfully, edit topologically to stay clean, and repair with fix geometry the legacy data that was drawn before anyone cared.
A Short Working Routine
Settings become skill through a routine, so here is the one this guide recommends for a boundary digitizing session. Before the first click: enable snapping, set vertex and segment mode, choose map units if the project has a precision requirement, open the advanced configuration and silence the layers that should never attract your cursor, and enable topological editing and tracing if the work shares edges. During the session: watch for the snap indicator on every placement meant to touch, zoom in for the closes rather than trusting tolerance to bridge a wide view, and flick snapping off with S for the genuinely free points so the magnet never invents a relationship you did not intend. After the session: run a validity check on the new layer, because snapping prevents most defects and the check catches the rest while the session's intent is still in your head. Our beginner tutorial places this routine inside a first full project, and it is worth saying plainly to beginners: an hour spent learning this toolbar saves a week of repairing almost-right data, and almost-right is the most expensive kind of wrong in GIS.
Three Sessions Where Snapping Proves Itself
Abstract settings become obvious in concrete work, so consider the three sessions where digitizers convert. The road junction: a new side road must meet the main road at exactly the point where traffic will turn, not a meter before it. Segment snapping plants the junction on the main road's line, snapping on intersections lets the new line's endpoint find the crossing even before a node exists there, and the network analysis you run next month works because this month's magnet was on. The parcel split: dividing one parcel into two along a new fence line, the dividing line must start and end exactly on the parcel's boundary, or the children will not sum to the parent. Vertex and segment snapping with Avoid Overlap produces two clean heirs; freehand clicking produces a sliver, a gap, and a letter from the land registry. The shared river boundary: two districts meet along a river centerline, and the second district's edge must copy the first's, bend for bend, or the map invents a third, ungoverned territory between them. Tracing does in one gesture what a hundred honest clicks cannot. Notice what the three sessions share: the cost of the defect is never paid by the person drawing, at the moment of drawing. It is paid later, by analysis, by colleagues, by the public record. Snapping is how the person drawing pays a small attention cost now to retire a large repair cost forever, which is why it is a professional ethic wearing a toolbar's clothes.
When Snapping Fights Back: Dense Layers and False Friends
Honesty requires a section on the magnet's bad days. In very dense layers, a city center's worth of parcels or a utility network's junctions, the snap indicator can become a crowd: several candidates inside the search radius, the marker flickering between them as the mouse breathes, and the click landing on the runner-up. The remedies are the section on tolerances applied with feeling: shrink the radius, narrow the layer scope to the one layer this session serves, and zoom in until the geometry spreads out enough for the magnet to make up its mind. The second failure is the false friend: snapping succeeds perfectly onto the wrong feature, the old boundary instead of the new one, the service line instead of the main, and because a successful snap feels like correctness, the error survives review. Guard it the way you guard every silent success: keep reference layers you are not editing visually distinct, lock the layers whose geometry must not attract, and spot-check the session's first few snaps at full zoom before trusting the rhythm. The third is performance: snapping searches spatial indexes, and an enormous unindexed layer can make the cursor stutter across the canvas. Build the index, or scope the snapping, and the stutter retires. None of these are arguments against the magnet. They are the advanced course in the same lesson the beginner settings taught: snapping is a negotiation between your intention and the map's contents, and like every negotiation, it goes better when both sides are clearly identified.
Related Guides
Readers working through this topic usually need its closest companions too. These GIS and open data guides cover the neighboring ground:
- QGIS Vertex Tool: Move, Add, and Delete Vertices Without Redrawing: The reshaping companion: once snapping has created geometry cleanly, this tool revises it vertex by vertex.
- How to Draw a Polygon in QGIS: Digitizing a Boundary That Closes Cleanly: The creation workflow that leans on snapping hardest, closing boundaries exactly on their first vertex.
- Fix Geometry in QGIS: Find Invalid Polygons and Repair Them to Zero Errors: The repair shop for data drawn without snapping, and the validity check this guide ends with.
- QGIS Tutorial for Beginners: Your First Map, Start to Finish: This routine inside a complete first project, for readers building the habit from zero.
Frequently Asked Questions
How do I turn on snapping in QGIS?
Use the Snapping Toolbar: its first button enables snapping, and the S key toggles it while you digitize. If the toolbar is missing, enable it from the View menu's toolbars. When snapping is active and you near a target, the cursor shows a magenta snap indicator.
What is the difference between snapping to vertices and segments?
Vertex snapping lands your point exactly on existing corners and nodes. Segment snapping lands it anywhere along an existing line, for example to start a junction midway along a road. Vertex and segment mode offers both, and suits most boundary work.
Should tolerance be in pixels or map units?
Pixels are zoom-independent on screen and forgiving, good for sketching and tracing imagery. Map units are ground truth, the same at every zoom, and are the honest choice for precision work with a specification to meet.
Why is my cursor snapping to the wrong layer?
Your scope is probably All layers. Open the advanced configuration and set per-layer snapping: silence layers that should never attract the cursor, and tighten tolerances on the reference layers that should.
What is topological editing and should I enable it?
Topological editing makes shared vertices move together: edit a corner shared by two polygons and both update, so shared edges stay shared. Enable it whenever your layers share boundaries, alongside snapping, tracing, and Avoid Overlap.
Photo credits: Tima Miroshnichenko (Pexels); Yaroslav Shuraev (Pexels). Photos are served from this site; follow the credit to the library page for the original.