Over the years, QField has gained a number of ways through which authors can share their mapping projects. This post looks at the multiple ways this can be achieved and what scenarios fit each method best.
QField developer here trying the community platform integration into blog posts. Looking forward to interesting discussions.
QField’s sharing capabilities are pretty solid once you understand the different use cases for each method. I’d add a few practical considerations to what’s typically discussed.
The cloud-based sharing through QField Cloud works well for team coordination in the field, but I’ve found the real bottleneck is initial project setup. Make sure your QGIS project is properly configured before pushing to the cloud—layer naming, symbology, and form logic all need to be finalized beforehand. Changing these later creates sync headaches across devices.
For one-off sharing with non-technical stakeholders, exporting as a packaged QField project (.qfz file) is underrated. It’s self-contained, doesn’t require cloud credentials, and works offline. The file size is usually manageable unless you’re dealing with massive raster datasets.
One thing I’d recommend: test your shared projects on the actual devices your team will use, not just desktop previews. Screen sizes, GPS accuracy, and network connectivity vary significantly in the field. I’ve seen projects that looked perfect in QField on a laptop perform poorly on Android tablets with weaker GPUs.
If you’re sharing read-only maps for public consumption, embedding a web map viewer through QGIS Server integration is more scalable than distributing individual QField files. It keeps your data source centralized and version-controlled.
What’s your primary use case for sharing. That tends to determine which method makes most sense.