Home / GIS and Open Map Data for Beginners

QGIS Browser Panel: The Front Door to Your Data

A person writing computer code at a desk with a laptop and an external monitor

Photo: Mikhail Nilov / Pexels

Every QGIS guide on this site silently assumes you can get data into the program, and the surface that assumption rests on is the Browser panel. It sits docked at the side of the window, easy to ignore precisely because it is always there, and most users reduce it to a file tree they occasionally drag a shapefile from. That undersells it considerably. The Browser is a unified index of everything QGIS can reach: your filesystem, your GeoPackages and their contents, database connections, web services from WMS to STAC, your saved favorites and spatial bookmarks, and the home folder of the current project. It previews, it filters, it inspects properties without loading, and it loads by drag-and-drop. Learned as a system rather than furniture, it becomes the fastest route between sitting down and working, and the place where a well-organized data life visibly pays off. This guide walks the panel branch by branch, then covers its twin inside the Data Source Manager and the second Browser panel almost nobody opens.

Interactive tool

Walk Through the Front Door: The Browser Checklist

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

0 of 7 complete

0% done

Opening the Panel and Its Twin

The Browser panel opens with Ctrl+2, and if it is not visible, that shortcut or the View menu's Panels entry restores it. Its more powerful twin hides in the Data Source Manager, opened with Ctrl+L, the dialog most users meet through the Open Data Source button: the manager's left-hand column is a Browser tree mirroring the panel's, so anything you can find in the panel you can find inside the manager, with the manager adding per-format loading options the panel's drag-and-drop skips. The working rule is simple: reach for the panel when you know what you want and want it on the canvas now; reach for the manager when the loading itself needs choices, a subset, a specific encoding, a query against a database. Both read the same tree, the same favorites, and the same connections, so organizing one organizes the other. A third fact completes the picture: QGIS allows a second Browser panel, so a project with data in two distant places, a local drive and a network share, can keep both open in separate docks instead of scrolling one tree up and down all day.

The Tree, Branch by Branch

The tree's order is a small curriculum in how QGIS thinks about data. Favorites sits at the top: folders you have promoted because you return to them constantly, added by right-clicking any directory, and the single highest-value customization in the panel. Below it, Spatial Bookmarks stores saved map extents, yours and the project's, so returning to a study area is a double-click rather than a pan-and-zoom expedition. Project Home points at the folder holding the current project file, the answer to the perennial where-did-that-export-go question. Then come the data branches proper: your drives and home directory as a plain filesystem tree; GeoPackage, PostgreSQL, and the other database connections, each expanding to schemas, tables, and layers inside the database rather than stopping at its door; and the service branches, WMS and WMTS, XYZ Tiles, WFS, STAC, and their kin, each holding connections you have configured once and reuse forever. Expanding a GeoPackage in the tree and seeing its layers listed, ready to drag, is the moment the panel stops looking like a file manager: it reads inside containers and databases, not just between files.

A programmer working on code across a laptop and desktop screens
A programmer working on code across a laptop and desktop screens

Loading, Previewing, and Inspecting Without Loading

Three gestures cover daily work. Drag and drop is the headline: drag a layer from the tree onto the canvas, or onto the Layers panel, and it loads with its stored styling and defaults; you can also drag between containers, dropping a layer into a GeoPackage to copy it there, which turns the Browser into a quiet data-management tool. Preview answers the what-is-this question before commitment: select an item and the panel's preview shows the layer's geometry on a small map, or its attribute table, so an unfamiliar folder of exports can be triaged without loading a dozen layers into the project. Properties goes deeper still: the item's properties widget reports the layer's fields, extent, feature count, and coordinate reference system, the facts you need to judge whether a dataset belongs in your analysis at all. The discipline these three build is inspect before you load: a project that only admits data which passed a preview and a properties check stays comprehensible, and the Browser is where that discipline lives.

Filtering and Finding

A tree is only as good as your ability to shrink it. The panel's filter narrows the visible tree by text, so a connection holding four hundred tables becomes the three whose names match your term, and the filter respects the tree's structure rather than flattening it into a list of paths. Filtering pairs with favorites as the two ends of one strategy: favorites shrink the tree permanently, to the places you live; the filter shrinks it momentarily, to the thing you need now. Search discipline extends to connections themselves: a service or database you connect to once and name clearly repays the naming every session afterward, while a tree full of forgotten connections named by their defaults is a tax the panel will happily let you keep paying. Tidy the tree the way you tidy a workbench, because that is what it is.

Connections: Databases and Services Live Here

The Browser is also where QGIS's reach beyond files is organized. A PostgreSQL connection defined once appears in the tree with its schemas and tables, draggable like files but carrying live database behavior behind them. WMS and WMTS connections expand to the layers a service advertises, each loadable as a layer in its own right. XYZ tile connections put basemaps a drag away. STAC connections bring catalog search into the same tree, so finding a scene by catalog and loading a file from disk become neighboring acts. The architectural point is worth stating plainly: in QGIS, a table in a database, a layer in a GeoPackage, a WMS layer from a national mapping agency, and a file in a folder are all citizens of one tree, loaded by one gesture. The Browser panel is where that unity is visible, and why learning it pays across every other workflow this site teaches.

The Habits That Make It a Front Door

Close with practice. Promote ruthlessly: every project folder and data root you touch weekly belongs in Favorites. Name connections like you will read them in a year, because you will. Preview before loading as a reflex, and check the CRS in properties before a layer joins a project it might silently distort. Use Project Home instead of hunting the filesystem for the folder you are already standing in. Open the second Browser when a job straddles two data worlds. And when a beginner asks where QGIS keeps everything, resist pointing at the Open dialog: point at the Browser, teach Ctrl+2 and Ctrl+L, and the rest of the program gets easier from that day on. The front door is only a front door if you walk through it daily; the panel rewards exactly that.

A Session, Walked Through

The panel's value compounds across an ordinary session, and it is worth tracing one. You open yesterday's project; the Project Home branch is already pointing at its folder, so the spreadsheet the field team emailed overnight, saved beside the project, is visible in the tree without a filesystem expedition. You drag it in, preview first: the Browser's attribute preview shows the columns are what the team promised. A new basemap is needed, so the XYZ branch gives you the tile connection you configured last spring, dragged in as a layer in one gesture. Midday, a colleague asks what else the survey GeoPackage holds; expanding it in the tree answers without opening anything, and its boundary layer drags straight into your project, styled as stored. A national agency's WMS connection, defined once months ago, supplies the orthophoto layer through the same tree. Late in the day you save a spatial bookmark for the extent you kept returning to, and promote the project's data root into Favorites, because tomorrow's session starts here too. Nothing in that day was a feature demonstration; it was one panel, used as the front door it is, replacing a dozen dialog boxes with a tree and a drag. That is the habit the panel is designed to build, and sessions like it are why experienced QGIS users arrange their whole data life to be reachable from it.

The Panel at Speed: Gestures and Context Menus

Fluency in the Browser is mostly right-clicks and drops, and the full gesture vocabulary is short. Double-clicking a layer in the tree loads it, for the moments when dragging is awkward. Dragging onto the Layers panel rather than the canvas places the layer at a chosen position in the stack, which matters when draw order is the difference between a map and a soup. The context menu on any item is the panel's control room: from it you add favorites, open the item's properties, export or duplicate layers where the format allows, manage the connections themselves, and reach the layer's home folder in your file manager when the question stops being a QGIS question. Database and GeoPackage items expose their own verbs there, including creating new layers inside a container without leaving the tree. None of this is hidden functionality; it is the panel's ordinary surface, and the users who seem to operate QGIS at twice the normal speed are usually just the users whose right hand knows this menu. Learn it the way you learned the canvas: one gesture per real task, inside real work, until the tree stops being a place you visit and becomes the way in.

The Panel as a Diagnostic

One last role deserves naming: the Browser is where data problems confess early. A layer that expands oddly in the tree, a GeoPackage whose contents are not what its filename promises, a service connection that lists layers the provider swore it did not have: the tree shows the truth of your data estate before any analysis depends on it, and a five-minute browse at a project's start is the cheapest audit in GIS.

Related Guides

If this page answered part of the question, these GIS guides cover the rest of the same ground:

Frequently Asked Questions

How do I open the Browser panel in QGIS?

Press Ctrl+2, or enable it from the View menu under Panels. Its twin lives inside the Data Source Manager (Ctrl+L), whose left column mirrors the same tree with per-format loading options added.

What is the difference between the Browser panel and the Data Source Manager?

The Browser loads fast, by drag-and-drop, with stored defaults. The Data Source Manager offers the same tree plus loading choices: subsets, encodings, and database queries. Use the panel when you know what you want; use the manager when the loading itself needs decisions.

Can the Browser look inside GeoPackages and databases?

Yes. GeoPackages expand to their layers, and database connections such as PostgreSQL expand to schemas and tables, all draggable onto the canvas. Service connections for WMS, XYZ, WFS, and STAC live in the same tree.

Can I preview a layer before loading it?

Yes. Selecting an item shows a preview of its geometry or its attribute table, and the properties widget reports fields, extent, feature count, and coordinate reference system, so you can judge a dataset before it enters the project.

Can I have two Browser panels open?

Yes. QGIS allows a second Browser panel, useful when a job straddles two data locations, such as a local drive and a network share, that you want visible side by side.

Photo credits: Mikhail Nilov (Pexels); Christina Morillo (Pexels). Photos are served from this site; follow the credit to the library page for the original.