Home / GIS and Open Map Data for Beginners

QGIS Open GDB: Read a File Geodatabase With the OpenFileGDB Driver

Rows of black server racks with fiber cables in a modern data center

Photo: Brett Sayles / Pexels

Sooner or later someone sends you a folder whose name ends in .gdb, full of cryptic files, and inside it lives the dataset you actually need: an Esri file geodatabase. If your shop runs QGIS, the good news is structural: QGIS reads file geodatabases through GDAL, and GDAL ships a driver for them in every standard install, no Esri license, no extra download. The honest news is that reading and fully editing are different achievements, and the space between them is where this article lives. It opens a geodatabase the reliable way, explains the two drivers you will meet in the documentation, states what the open driver can and cannot do as the driver documentation itself puts it, and teaches the escape hatch that turns a read-only encounter into a working dataset.

Interactive tool

Open It Without Esri: The Geodatabase Checklist

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

0 of 7 complete

0% done

What a File Geodatabase Actually Is

A file geodatabase is a folder, not a file: a directory named something like survey.gdb containing dozens of system files that together store feature classes (the vector layers), tables, raster datasets, and the relationships and domains Esri tools define among them. Treat the folder as a single object. Never rename, delete, or "tidy" the files inside it; the database's integrity lives in their exact arrangement, and a geodatabase with one system file missing is a corrupted database, not a slightly smaller one. Copy the whole folder when you move it, and if you receive one as a zip, the zip is the database wearing a coat: extract it fully before opening. Recognizing the shape matters because every route below begins with pointing QGIS at the folder itself.

Open It: The Directory Route in the Data Source Manager

The reliable route runs through the Data Source Manager:

  1. Open the Data Source Manager (the toolbar icon, or Layer, Add Layer, Add Vector Layer).
  2. Set the source type to Directory.
  3. Set the source type dropdown beside it to OpenFileGDB.
  4. Browse to the .gdb folder and select it.
  5. QGIS lists the feature classes inside; select the ones you need and add them.

Specifying OpenFileGDB explicitly is the step that saves the afternoon. Left to automatic detection, QGIS may try the other driver (next section) or hesitate over the folder; naming the driver tells GDAL exactly how to read what you are pointing at. The layers arrive with their attributes, ready to style, filter, and analyze. One variant worth knowing: QGIS can also read a geodatabase directly from its zip archive in many setups, which is handy for a quick look, but extract first for any real session, because performance and some operations prefer the honest folder.

The Two Drivers: OpenFileGDB Against FileGDB

GDAL carries two drivers for this format, and documentation that does not say which one it means is documentation that will confuse you:

OpenFileGDBFileGDB
Ships with standard QGISYes, built inNo, requires Esri's File Geodatabase SDK
BasisReverse-engineered open implementationEsri's official library
Reads vector feature classesYesYes
Writes and createsYes, with limits (below)Yes, fuller Esri fidelity
Reads raster contentsSince GDAL 3.7Yes

OpenFileGDB is the driver this article, and nearly every QGIS user, actually uses: present by default, maintained by the GDAL project, sufficient for reading and for a documented range of writing. The FileGDB driver exists for shops that need Esri's own library's behavior and have installed the SDK it wraps; if you have not deliberately done that installation, you do not have this driver, and instructions assuming it will fail in ways that look like your fault. Check which drivers your install carries in the QGIS system information or GDAL driver list before troubleshooting an open that refuses to work; nine times in ten the mystery is a missing optional driver, and the cure is to use the built-in one by name, as the steps above do.

A detailed close-up of a server rack used for data storage
A detailed close-up of a server rack used for data storage

What OpenFileGDB Can Write, Stated Carefully

Secondary sources argue about this section, so here is the driver documentation's position, which is the one to build on. OpenFileGDB gained write support, including creating new file geodatabases and writing vector layers into them, with GDAL 3.6, which is the GDAL generation bundled from QGIS 3.28 onward. Reading raster datasets stored in a geodatabase arrived later, with GDAL 3.7. Within that support, limits remain around the richer Esri machinery: editing existing Esri geodatabases in place, with their domains, relationships, and Esri-specific behaviors fully honored, is the area where the open driver is most limited and where claims in tutorials run ahead of the documentation. The safe professional posture follows directly: read freely; create new geodatabases when a deliverable demands the format; and for serious editing of data that arrived as a geodatabase, export to an open format first (next section) rather than editing in place and discovering a limit mid-project. Version floors matter, so check your QGIS and GDAL versions before expecting 3.6 or 3.7 behavior from an older install.

The Escape Hatch: Export to GeoPackage and Edit Freely

The workflow that never fails: open the geodatabase with OpenFileGDB, right-click each layer you need, Export, Save Features As, and write it to a GeoPackage. GeoPackage is the open standard QGIS treats as its native working format: full editing, no driver limits, one file, no folder of mysteries. Do your analysis and editing there, where every QGIS tool behaves exactly as documented. If the deliverable must return as a geodatabase, write the finished layers back into a new geodatabase at the end, using the write support above, and verify the result by reopening it. This pattern, read in the sender's format, work in yours, deliver in theirs, is how interoperable shops survive mixed-format worlds, and it converts the geodatabase from an obstacle into a shipping container. Our shapefile against geodatabase comparison covers the format politics behind this; the Excel export guide covers the other direction data usually leaves QGIS.

Troubleshooting the Opens That Fail

Three failures account for nearly every bad first encounter. The folder will not open at all: you pointed QGIS at a file inside the .gdb folder, or at the zip, instead of selecting the folder itself through the Directory route; redo it by the steps, naming OpenFileGDB. The layer list is empty: the geodatabase holds only rasters or tables your current view is not listing, or your GDAL predates raster reading (3.7) for a raster-only database; check the contents with the sender and your version numbers before assuming corruption. It opens but editing refuses or misbehaves: you have met the in-place editing limits of the open driver; stop negotiating and take the escape hatch, export to GeoPackage, edit there. Each failure has a named cure, and none of them is "reinstall QGIS," which is where unguided troubleshooting usually goes to waste its evening.

The Command Line: ogrinfo and ogr2ogr

Everything QGIS does with the geodatabase, GDAL also does from the command line, and for batch work the shell is faster than the mouse. ogrinfo inspects a geodatabase without opening any application: list its layers, read a layer's schema and feature count, confirm in seconds whether the folder you were sent contains what the sender claims. ogr2ogr is the conversion workhorse: point it at the .gdb folder with the OpenFileGDB driver and it writes GeoPackage, shapefile, or any other GDAL format, whole layers or filtered subsets, which makes it the natural engine for the escape-hatch workflow run over forty layers at once, and the natural partner to the processing toolbox's batch habits inside QGIS. Learn these two names even if you never type them: when a geodatabase misbehaves in a GUI, the command line's plain error messages are often the first honest diagnosis available, because GDAL reports what the driver actually refused, in words, without a dialog's diplomacy.

Tables, Domains, and the Rest of the Contents

A geodatabase usually holds more than its map layers, and a complete reader should know what else is in the folder and what survives the trip. Standalone tables (the non-spatial spreadsheets of the database: inspection records, species lists, join fodder) come along through the same driver and can be added and joined like any table in QGIS. Relationship classes and Esri domains, the database's own rules about how records connect and which values a field may hold, are the layer where the open driver's fidelity thins: the data reads, but the rules do not enforce themselves in QGIS, which will happily let you type a value the domain would have forbidden. This is not a reason to avoid the data; it is a reason to ask the sender for the domain lists when a project depends on them, and to rebuild critical value constraints as QGIS form widgets or value maps in your working GeoPackage, so the discipline the geodatabase enforced by structure is re-enforced by your forms. Data travels; governance must be re-established at each border, and knowing that is most of what interoperability expertise consists of.

Knowing Your Version: The Two-Minute Check

Because the write and raster thresholds are version floors, GDAL 3.6 for writing and 3.7 for raster reading, the practical skill is reading your own installation's numbers. QGIS reports its GDAL version in the About dialog and in the system information, and that one number predicts most of the behavior this article describes: below 3.6, plan on read-only work and the escape hatch; at 3.6, new-geodatabase writing joins the toolkit; at 3.7, raster contents become visible too. Check it before a project that depends on a threshold, and write the number into the project's notes, because "it worked on my machine" is usually a version sentence in disguise, and the next machine's answer is already printed in its About box. Installations drift apart across a team more quietly than data does, and half of all interoperability mysteries are two honest installs of different ages giving different answers to the same folder.

Related Guides

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

Frequently Asked Questions

Can QGIS open a file geodatabase without Esri software?

Yes. QGIS reads file geodatabases through GDAL's OpenFileGDB driver, which is built into standard installs. Open the Data Source Manager, set the source type to Directory and the driver to OpenFileGDB, and select the .gdb folder.

What is the difference between the OpenFileGDB and FileGDB drivers?

OpenFileGDB is GDAL's open, reverse-engineered driver and ships with QGIS. The FileGDB driver wraps Esri's own SDK library and is present only if that SDK was deliberately installed. Most QGIS users have and need only OpenFileGDB.

Can QGIS write to a file geodatabase?

With limits. OpenFileGDB supports creating new geodatabases and writing vector layers since GDAL 3.6, bundled from QGIS 3.28, and reading geodatabase rasters since GDAL 3.7. In-place editing of existing Esri geodatabases with their full Esri machinery remains limited, so for serious editing, export to GeoPackage first.

Why does my .gdb folder show dozens of strange files?

Because a file geodatabase is a folder-based database, and those files are its storage. Treat the whole folder as one object: copy it whole, never rename or delete its contents, and point QGIS at the folder itself.

QGIS lists no layers when I open a geodatabase. What is wrong?

The database may hold only rasters or standalone tables, or your GDAL version may predate geodatabase raster reading (3.7). Check the database contents with the sender and check your QGIS and GDAL versions; an empty list is usually a contents or version story, not corruption.

Photo credits: Brett Sayles (Pexels); panumas nikhomkhai (Pexels). Photos are served from this site; follow the credit to the library page for the original.