Home / GIS and Open Map Data for Beginners

QGIS Atlas: One Layout, Forty Maps, or However Many Features You Have

A detailed political map showing Europe and Asia

Photo: Magda Ehlers / Pexels

There is a specific moment Atlas exists for: someone needs the same map forty times. Every district in the county, every parcel in the development, every segment of the trail, same design, same legend, different place and different title each time. Done by hand, that is a week of zooming, exporting, and mislabeling. Atlas does it from one layout in one export, because the layout is a template and the features drive it. This guide builds an atlas end to end in QGIS's print layout. If you are still new to QGIS itself, our QGIS guide covers the basics first; this article assumes a project with data in it and a recurring map to produce.

Interactive tool

Build the Atlas: Layout to Export

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

0 of 6 complete

0% done

The Idea: A Coverage Layer Drives the Series

Atlas needs one concept before any clicks: the coverage layer. It is the layer whose features each get a page. Districts, parcels, grid tiles, sites, whatever your series counts. Every other layer in the project is scenery that appears on every page; the coverage layer is the cast that changes. Design decisions follow from that split. Style the coverage layer knowing it will sometimes be the subject (framed and centered) and sometimes hidden (a page about a district often hides the district boundaries of its neighbors or shows them faintly). If your series has no natural feature layer, make one: a grid of rectangles over your study area is a perfectly good coverage layer, and page per tile atlases are how map books are built.

Build the Layout Once

  1. Open Project, New Print Layout, name it, and add a map item covering the page the way you want every page to look. At this moment you are designing page one of forty; the other thirty nine will inherit everything.
  2. Add the fixed furniture: title block space, legend, scale bar, north arrow, logos, disclaimers. Leave room in the title for a name that changes length, because it will.
  3. Set the map item's scale behavior in your head before the next step: Atlas can zoom each page to its feature at a fixed scale, a best fit scale, or with a margin around the feature. Know which your series wants; a parcel atlas wants fixed scale for comparability, a district atlas usually wants best fit with a margin.

Turn Atlas On and Wire the Map to It

In the layout's Atlas Settings panel (the Atlas menu or the toolbar icon), check Generate an atlas and choose your coverage layer. Options here decide the series' manners: you can filter the coverage features (only districts in the north, only parcels above a size), sort them (by name, by an order field), and hide the coverage layer itself on the page if the boundaries would clutter their own portrait.

Then select the map item and, in its Item Properties, set it to Controlled by Atlas. This checkbox is the entire mechanism: it tells the map item to reframe itself on each coverage feature in turn, applying the scale mode you chose. Preview with the atlas preview button and the page navigation arrows: the layout steps through your features, reframing and retitling as it goes. Watching page three become page four correctly is the moment the week's work evaporates.

A close-up of a vintage style map of South America and Africa
A close-up of a vintage style map of South America and Africa

Dynamic Text: Titles That Write Themselves

A series whose every page says "District Map" is half finished. Atlas pages title themselves from the coverage feature's attributes through dynamic text: insert a text item with an expression such as [% @atlas_pagename %] or build the page name in the Atlas settings from a field or expression, for example the district's name field, and each page renders with its own title. The expression engine gives you the whole attribute row, so subtitles can carry the feature's statistics ("Population: [% "population" %]"), and a page counter ("Sheet [% @atlas_featureid %] of [% @atlas_totalfeatures %]") keeps a printed series collatable. Set the atlas page name thoughtfully: it becomes the sheet name, the PDF bookmark, and, in single file export mode, the filename, so a good page name is three kinds of organization bought with one expression.

Export: One PDF or a File per Feature

The Export Atlas button offers the fork that ends the build:

  • Export as a single multi page PDF (or one long image strip, rarely wanted): one file, pages in your sort order, bookmarks from your page names. This is the deliverable for reports, council packets, and anything a human will flip through.
  • Export as multiple files, images or PDFs named by the page name expression: one file per feature, for handing each district office its own map, feeding a website, or archiving sheets independently.

Either way the export renders every page without further clicks, which is the entire point: the marginal cost of map forty is zero, and the marginal cost of rerunning the whole series after a data update is one button. That rerunnability is Atlas's deepest value. A hand made series rots the day the data changes; an atlas is regenerated.

The Mistakes That Cost a Rerun

Three errors account for most spoiled atlases. Forgetting the margin: best fit framing with no margin crops labels and features at page edges, so set the margin around the feature generously, ten percent or more. A legend that lies: a fixed legend lists layers absent from half the pages; either accept it as a series legend or drive legend filtering by the map item so each page lists what it shows. Unsorted, unfiltered coverage: exporting every feature including the three test polygons and the null geometry, discovered at page 38 of 40. Preview the full series quickly before the real export; the arrows are cheap and the rerun is not. Build the habit and Atlas becomes what it is for the people who rely on it: the difference between maps as craft projects and maps as a product line. For the measurements that often accompany a series like this, our guide to calculating polygon area in QGIS pairs naturally, since per feature statistics are usually computed there and displayed here.

Expressions Everywhere: Rotation, Scale, and Data Defined Control

Once the basic series runs, the expression engine opens a second level of polish, because nearly every property in a layout can be driven by the current atlas feature. Rotation: a long thin feature, a river reach, a pipeline corridor, often fits its page better rotated, and the map item's rotation can be set per feature from an attribute or an expression, so each page turns to flatter its subject. Scale: data defined scale lets a series hold one scale for city districts and another for rural ones, driven by a field, instead of forcing one compromise on both. Visibility and styling: layers can appear only on pages where an attribute calls for them, the flood layer on the pages of flood prone districts, through layer visibility expressions tied to the atlas feature. None of this is required for a working atlas, and all of it is the difference between a series that looks generated and a series that looks designed. Add these touches after the plain version exports cleanly; an atlas, like a map, is finished in layers.

Paper Reality: Size, Margins, and the Print Check

Atlases usually end on paper or in a PDF that pretends to be paper, and the layout's physical decisions deserve the same deliberateness as its data ones. Choose the page size your audience's printer or report format actually uses, and keep live content inside margins a home printer can reach, because the most elegant sheet in the series is worthless if the office printer crops its scale bar. Set the scale bar and north arrow to follow the atlas map item so they stay truthful as pages reframe and rescale; a scale bar frozen from page one is a lie by page nine. Then do the unfashionable thing: print or render three real pages, the first, a middle one with the longest title, and the page whose feature is the oddest shape, and read them at arm's length. Long titles overflow, margins crop, and legends lie at exactly the pages you did not check, and finding that in a three page proof costs minutes while finding it in a printed run of forty costs the run.

When an Atlas Is the Wrong Tool

Honesty about the tool's edges finishes the lesson. If your audience needs to explore, zooming, filtering, asking their own questions, a printed series is the wrong medium and a web map serves them better; the atlas's strength is a fixed, authoritative, identical view for every reader. If the features number in the thousands and each needs a page, question the page per feature assumption itself: an index map with a table sometimes serves better than a four hundred page PDF nobody opens. And if the underlying data changes weekly, a generated series is a snapshot with an expiry date, and the honest move is printing that date on the cover sheet and regenerating on a rhythm rather than letting an old atlas circulate as current truth. Choose the atlas when the job is many places, one design, on paper or PDF, for readers who need the same page to argue from. That job is common, honorable, and exactly what the feature was built to finish.

The Atlas Habit

Teams that publish map series well share one habit: the layout is treated as a product, versioned and improved like code, not rebuilt from memory each time. Save the layout with the project, export a style file for the coverage layer, and keep a short note of the decisions, the scale logic, the sort field, the filename pattern, beside it. The next series then starts from a working system instead of a blank page, and its first export is already better than the last series' final one. An atlas is a promise that forty places will be shown one fair way. The habit of keeping the machinery is how that promise gets kept on deadline, series after series.

Related Guides

Readers working through this topic usually need its closest companions too. These GIS and open map data guides cover the neighboring ground:

Frequently Asked Questions

What is a QGIS Atlas?

Atlas is a print layout feature that generates a series of maps from one layout. You choose a coverage layer whose features each get a page, set the map item to Controlled by Atlas, and QGIS reframes the map for every feature in turn, with titles and text drawn from each feature's attributes. Export produces the whole series at once.

What is a coverage layer?

The layer whose features drive the series: districts, parcels, sites, or a grid of tiles you create for the purpose. Each feature becomes one page. Other layers appear as scenery on every page, and the coverage layer itself can be shown, styled faintly, or hidden per your settings.

How do I make each atlas page show its feature's name?

Use dynamic text. Set the atlas page name from a field or expression in the Atlas Settings, and place text items containing expressions such as @atlas_pagename or direct field references in the layout. Each page then renders with its own title, and the page name also becomes the PDF bookmark and the filename in multiple file export.

Should I export one PDF or many files?

Export a single multi page PDF when the series is one document: a report, a map book, a packet. Export multiple files when each page has a different destination: one office, one web page, one record per feature. The atlas generates either from the same setup, so the choice costs nothing to revisit.

Why do my atlas pages crop features at the edges?

The map framing needs a margin. In the map item's atlas settings, increase the margin around the feature (ten percent is a good starting point) so each page frames its feature with breathing room for labels and linework. Also check whether a fixed scale is fighting irregularly shaped features; best fit with a margin is the forgiving mode for mixed shapes.

Photo credits: Magda Ehlers (Pexels); Davide Locatelli (Pexels). Photos are served from this site; follow the credit to the library page for the original.