Private project handoff preflight

QGIS Project Broken-Layer & Source-Path Auditor

Open a QGS or QGZ project, map every supported layer to its stored data source, and optionally compare relative file paths with a selected project-folder inventory. Nothing is uploaded and no remote service or database is contacted.

Project plus optional folder evidence

Choose a QGIS project

No project selected.

Project input is limited to 32 MiB; embedded QGS XML is limited to 8 MiB.

No companion inventory selected; relative-file existence will remain unverified.

The browser shares filenames, relative paths, and sizes only. File content is not read. Folder selection preserves subdirectory evidence where supported.

Choose a QGS/QGZ project, optionally add companion files, or load the sample.

Private by design: project XML, local paths, endpoints, layer names, credentials, and companion filenames stay in this browser tab. Recognized secret values are redacted from displayed and downloaded reports.

What QGS and QGZ contain

A QGS project is XML describing the project, layer tree, renderers, layouts, relationships, and links to underlying data sources. QGZ is a ZIP archive whose QGS entry is accompanied by an optional QGD auxiliary-data database. This auditor validates the bounded archive framing and QGS entry, then inventories supported maplayer definitions.

What “missing” means in a browser

A web page cannot inspect arbitrary paths on your computer. A relative file is called missing only when you explicitly select a project folder and no matching relative path appears in that inventory. A basename-only match is reported as a candidate, not proof. Without folder evidence the status remains “not checked.” Remote services and databases are classified but never contacted.

Portability and secret checks

Absolute Windows, UNC, Unix, and home-relative paths are machine-specific. Parent-directory references can break when a project folder moves. Inline passwords, tokens, API keys, HTTP endpoints, disabled TLS modes, and QGIS authcfg dependencies are called out separately. Displayed and exported sources redact recognized secret values, but the original project remains unchanged.

Validation boundary

This is a bounded XML, archive, reference, and handoff diagnostic—not QGIS itself. It does not load providers, open GeoPackages or rasters, evaluate expressions, verify CRS definitions, authenticate, contact services, resolve environment variables, inspect QGD, validate styles or layouts, understand every plugin provider, rewrite paths, or guarantee that QGIS can render a layer. Open a copy in the target QGIS version for final verification.

Frequently asked questions

Why is a selected file only a basename candidate?

A normal multi-file picker may hide its original directory. Matching roads.gpkg cannot prove that data/roads.gpkg exists at the expected relative location, so the auditor keeps the result qualified.

Does a database source containing a username always expose a password?

No. The tool flags identity or secret material conservatively and distinguishes QGIS authentication references. Inspect the redacted source and original project in a trusted editor.

Can this repair broken paths?

No. Automatically substituting a same-named dataset can silently connect a layer to the wrong data. This tool provides evidence for deliberate repair in QGIS.

Primary references

The QGIS file-format documentation defines QGS as project XML and QGZ as a ZIP containing QGS plus optional QGD auxiliary data. The QGIS project-file guide documents unavailable data sources and path repair, while the PyQGIS project guide describes path rewriting through QgsPathResolver.

Audit a Shapefile bundle · Audit a raster world file · Browse GIS tools