Every QGIS user wants the same thing at some point: Google's satellite imagery or street map as the background under their own layers. It can be done, it takes a minute, and tutorials all over the internet will show you how. Almost none of them tell you the whole story, which has a technical half (two reliable methods, one projection quirk) and a legal half (what those tiles are actually licensed for). This guide covers both halves, because a basemap you cannot legally publish is a trap dressed as a shortcut. For the desktop foundations, our OpenStreetMap in QGIS guide covers the same connection machinery with fully open data.
Home / GIS and Open Map Data for Beginners
Google Maps in QGIS: The Two Working Routes, and the Licensing Catch You Must Know

Photo: Element5 Digital / Pexels
Basemaps in QGIS: Routes and Licenses
Check off each step as you finish it. Your progress stays on this page.
0 of 6 complete
0% done
Route 1: An XYZ Tiles Connection (No Plugin)
QGIS speaks the XYZ tile protocol natively, which is the same tiling scheme Google Maps uses:
- In the Browser panel, right-click XYZ Tiles and choose New Connection.
- Name it (for example, "Google Satellite") and paste a tile URL template. The widely published templates are:
- Satellite: https://mt1.google.com/vt/lyrs=s&x={x}&y={y}&z={z}
- Streets: https://mt1.google.com/vt/lyrs=m&x={x}&y={y}&z={z}
- Hybrid (imagery plus labels): lyrs=y; terrain: lyrs=t
- Set the maximum zoom to 19 or 20 and click OK.
- Double-click the new connection to add it as a layer, then drag it to the bottom of your layer stack.
The layer behaves like any web basemap: it streams tiles as you pan and zoom, in the Web Mercator projection (EPSG:3857) that all tile services share. QGIS reprojects your other layers on the fly to match, or reprojects the view if your project CRS differs. For on-screen reference behind vector data, this is the entire job.
Route 2: The QuickMapServices Plugin
If you would rather not handle URLs, install the QuickMapServices plugin from the QGIS plugin manager. It ships a catalog of basemaps and, through its contributed services pack (enable it in the plugin's settings under "Get contributed pack"), it includes Google's street, satellite, hybrid, and terrain layers alongside dozens of others: OpenStreetMap variants, Esri imagery, Bing, and national mapping agency services where available. The plugin route is easier to maintain (the service definitions update centrally) and better for discovery, since it puts the licensed alternatives one click from the Google layers, which matters for the second half of this article.

The EPSG:3857 Behavior You Will Notice
Tile layers live in Web Mercator, and three consequences follow. First, if your project CRS is EPSG:3857, everything aligns natively and rendering is fastest. Second, if your project is in a local projection, QGIS reprojects the tiles on the fly, which works but can look soft at some zooms because the tiles are resampled. Third, and most important, never measure on the Mercator plane: distances and areas computed planimetrically in EPSG:3857 inflate with latitude, severely toward the poles. Set QGIS's measurement to the ellipsoid, or do measurement work in a proper projected CRS with your data, using the Google layer purely as a picture underneath. The basemap is scenery; your data and its CRS are the instrument.
The Licensing Catch, Stated Plainly
Here is the part the quick tutorials omit. Google Maps content is licensed for use through Google's own products and official APIs, under the Google Maps Platform terms. Those terms do not permit scraping or bulk downloading tiles, using the tile endpoints as a general basemap service in third-party software, tracing features from the imagery to create data, or publishing maps built on the tiles outside Google's ecosystem. The XYZ endpoint in Route 1 is a mechanism Google operates for its own clients, not a public tile service with a license for your QGIS project.
What does that mean in practice, stated without drama? Viewing Google imagery in QGIS for your own orientation sits in the same gray zone millions of users occupy, and this guide describes the technique because it is standard practice and widely documented. But the moment the work becomes professional output, the ground firms up: do not digitize from Google tiles, do not derive datasets from them, and do not publish or print maps that use them as the basemap. A published map is a product, and its basemap needs a license that covers publication. The next section exists so that this restriction costs you nothing.
The Licensed Alternatives (Which Are Also Excellent)
- OpenStreetMap standard layer. Fully open data, available in QGIS via QuickMapServices or XYZ, free to use and publish with attribution to OpenStreetMap contributors. For street-level basemaps it is often more current than Google in well-mapped regions.
- Esri World Imagery. Esri publishes its satellite layer for use in GIS workflows, including in QGIS through the standard tile service, with attribution; its terms are written for exactly the professional basemap use Google's are not. For most published satellite basemaps, this is the practical answer.
- Sentinel-2 and Landsat. Genuinely free satellite imagery from the Copernicus and USGS programs, at 10 to 30 meter resolution: too coarse for property work, perfect for regional and environmental mapping, and yours to publish without restriction. Our open data coverage treats these as the backbone of honest remote sensing.
- National and local open imagery. Many governments publish aerial photography as open data or open tile services (the same agencies whose layers appear in QuickMapServices' contributed pack). Where it exists, it is usually sharper and more current than global services, and licensed for use.
The professional pattern is therefore: Google layer for a quick private look if you must, Esri or open imagery for anything that leaves your desk. The switch costs one click in the same plugin, and the resulting map can be published, printed, and defended.
A Clean Working Setup
For a project that will produce output, build the basemap stack deliberately: Esri World Imagery or OpenStreetMap as the citable base (attribution added to the layout, as their terms require), your own data above it, project CRS chosen for your region and your measurements, and the Google layer, if present at all, kept out of the print layout. In QGIS print layouts, exclude any layer you cannot license from the exported map, and put the attribution text for the layers you do use in the layout where a reader can find it. This is not bureaucracy; it is the difference between a map you can put in a report, a paper, or a planning submission and a screenshot you have to apologize for.
Troubleshooting: Blank Tiles, Wrong Zooms, Vanishing Layers
- The layer loads but shows nothing. Tile layers are streams, not files: no internet, no tiles, and the layer fails silently rather than with an error. Check the connection first, then zoom; at very large scales you may simply be beyond the service's maximum zoom, where the layer has nothing to show.
- The basemap is offset from your data. A small, consistent offset usually means your data's CRS is declared wrong (defined rather than reprojected, the classic GIS own goal), not that the tiles moved. The tiles are the reference here; suspect the data layer's CRS declaration and verify against a known coordinate.
- Tiles look blurry at some zooms. On-the-fly reprojection into a non-Mercator project CRS resamples the tiles. If crispness matters for a layout, set the project CRS to EPSG:3857 for the basemap-driven view, or accept the softness as the price of your working projection.
- The layer vanished from a reopened project. XYZ connections live in your QGIS profile's browser connections, not inside the project file. On a different machine or a fresh profile, recreate the connection (or use QuickMapServices, whose definitions travel with the plugin) and the layer revives.
Saving the Setup So the Team Shares It
Basemap connections are per-user configuration, which makes them a small team-management problem. The durable solutions: standardize on QuickMapServices across the team so everyone resolves the same service definitions; keep a written note in the project documentation of which basemap (and which license) each deliverable uses; and store project templates with the approved layers preloaded, so a new project starts with the licensed stack rather than with whoever's favorite tiles. None of this is glamorous, and all of it is the difference between an organization whose maps can be published on sight and one where every output triggers a licensing archaeology session. The technique in this article takes a minute to perform. The judgment around it is the actual professional skill, and it scales from a solo consultant to a national mapping program.
Attribution in Layouts: The Two-Minute Compliance Step
Whichever licensed basemap you publish on, its terms ask for one visible thing: credit. In a QGIS print layout, add a small text item in a corner naming the basemap and its source (for example, "Imagery: Esri World Imagery; Map data: OpenStreetMap contributors"), sized to be legible at final print size, not at your editing zoom. Digital exports need the same credit in the image or its caption, because a PNG travels without its project file and its layer metadata. This step is where amateur maps quietly fail professional review: not in the analysis, but in the missing credit line that the basemap's license required. Build the credit into your layout templates, next to the scale bar and north arrow, so it is present by default rather than remembered per project. Templates are how good intentions become habits, and habits are how licenses stay honored across a whole body of work instead of on the days somebody remembered.
Related Guides
If this page answered part of the question, these GIS and open map data guides cover the rest of the same ground:
- Offline Maps in QGIS: Generate Your Own MBTiles Tile Pack: Most offline map guides tell you which app to download areas in.
- QGIS Atlas: One Layout, Forty Maps, or However Many Features You Have: Atlas is the QGIS print layout feature that turns one designed map into a series: point the layout at a coverage layer, set the map item to...
- QGIS: How to Georeference an Image, From Scan to GeoTIFF: Georeferencing teaches a dumb picture, a scanned map, an old aerial photo, a floor plan, where it lives on Earth, so QGIS can drape it over real data.
Frequently Asked Questions
How do I add Google Maps to QGIS without a plugin?
Create an XYZ Tiles connection in the Browser panel with Google's tile URL template (the lyrs parameter selects streets, satellite, hybrid, or terrain), then add it as a layer. It streams as a Web Mercator basemap under your data.
What is QuickMapServices?
A QGIS plugin that provides a ready-made catalog of basemaps, including Google, OpenStreetMap, Esri, and Bing layers, with more available through its contributed services pack. It saves managing tile URLs by hand.
Can I publish a map that uses Google tiles as the basemap?
Under Google's terms, no. The tiles are licensed for use through Google's own products and APIs, not for derived data or published maps in third-party software. Use Esri World Imagery or OpenStreetMap, whose terms cover publication with attribution, for anything that leaves your desk.
Why does the Google layer look distorted or measure wrong?
It is in Web Mercator (EPSG:3857), which distorts distances increasingly with latitude. Treat the layer as a picture: set measurements to the ellipsoid or work in a suitable local CRS for your data.
Is the Google satellite layer in QGIS the same imagery as Google Earth?
It draws on Google's imagery program, but it is delivered as flat tiles without Earth's 3D, historical slider, or terrain tools. For historical imagery and 3D viewing, use Google Earth itself; our QGIS vs Google Earth comparison explains the division of labor.
Photo credits: Element5 Digital (Pexels); fauxels (Pexels). Photos are served from this site; follow the credit to the library page for the original.