Home / GIS and Open Map Data for Beginners

QGIS Cloud: The Hosted Route from Desktop Project to Web Map

Rolling green fields under a wide cloudy sky in the countryside

Photo: Brett Sayles / Pexels

QGIS Server asks you to run a server. QGIS Cloud, run by Sourcepole, the company behind much of QGIS's server side, asks you to install a plugin. The proposition is the desktop-to-server identity of QGIS Server, the same project file rendered by the same engine, with the machinery moved into someone else's data center: you prepare the project on the desktop, upload it through the QGIS Cloud plugin, and receive a published web map plus live OGC services at a hosted address. For a small team, a consultancy delivering a map to a client, or a researcher who needs a service URL for a paper's data, that trade, a subscription in exchange for never meeting a FastCGI binary, is often the right one. This guide explains the flow precisely, describes the viewer your audience receives, states the free tier's restrictions as the service's own documentation states them, and closes with the honest comparison against running your own server, which the neighboring guide teaches.

Interactive tool

Publish Without a Server: The QGIS Cloud Checklist

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

0 of 7 complete

0% done

The Publishing Flow

The workflow begins where QGIS work always begins, in a desktop project, and the plugin's promise is that the project transfers one-to-one: the layers, their order, their styling, and the print layouts are uploaded to a hosted QGIS Server instance, which then serves them. Practically, the flow has four beats. You build and style the project on the desktop, with the same care the server guide demands, because the hosted engine inherits the project's virtues and defects alike. You sign in through the plugin and upload, which carries the project and its data to the hosting. The service provisions your publication: a web map in the hosted viewer, and WMS, WFS, and WCS service endpoints for the same project, so other GIS clients can consume your layers as services, not just view the one map. And you share the resulting addresses: the map's URL for people, the service URLs for software. Updating is the same flow repeated: revise on the desktop, upload again, and the publication moves. The one-to-one principle is the discipline to hold onto: there is no second, web-side styling pass to drift out of sync, because there is no web-side styling at all.

The Viewer: QGIS Web Client 2

Your audience does not receive raw services alone; the publication includes a web map in QGIS Web Client 2, the project's standard web viewer. It presents the uploaded project's layers in a browser with the furniture a map reader expects: layer control, search, measurement, and printing through the project's own layouts. Two implications matter for authors. First, the viewer's behavior is the project's behavior: layer names, grouping, and which layers start visible are authoring decisions you make on the desktop, and they arrive in the browser as you set them. Second, the viewer is a viewer: it presents and explores the project, and it is not an editor or a data-collection surface, so a workflow that needs the public to change the data needs a different tool than a publication viewer. Judge QGIS Cloud first as a publishing channel: its job is to put a finished project in front of an audience and behind service endpoints, and the viewer is the front of that channel.

Lines of HTML and CSS code on a dark computer screen
Lines of HTML and CSS code on a dark computer screen

The Free Tier, Stated Plainly

QGIS Cloud offers a free tier, and its restrictions are stated in the service's own documentation, which this guide reports rather than embellishes. Free publications are public: there is no private or access-controlled map on the free tier, so anything you publish there is published to the world. And the free tier excludes commercial and government use: it is offered for personal, educational, and community purposes, and organizations and businesses are directed to the paid plans. Those two clauses decide most evaluations by themselves. A community mapping project, a course, a personal atlas: the free tier fits, and public is arguably the point. A consultancy delivering to a client, a municipality publishing its zoning: the use is commercial or government by definition, and the paid tiers are the honest route, with privacy controls among what the payment buys. This guide prints no plan prices: prices change, the service's own site is the authority, and a guide that hard-codes a price table is wrong on a schedule. The restrictions, by contrast, are structural, and they are the part a reader needs before investing an afternoon in an upload.

Hosted or Your Own Server: The Decision

The neighboring guide teaches QGIS Server; this one exists so the two can be weighed. Choose the hosted route when the publication is the goal and the infrastructure is not: no server to provision, patch, or monitor; publication in an afternoon; service endpoints without a FastCGI configuration; and an operator whose business is running exactly this software. Choose your own server when the constraints point the other way: data that may not leave your premises, publications that must be private by architecture rather than by plan, integration into an existing hosting estate, or a volume of services where running the binary yourself is the cheaper line on the spreadsheet. The middle fact is that the project file is identical either way, because both routes serve the same format with the same engine: a project published on QGIS Cloud today can move to your own QGIS Server later without restyling, and that reversibility lowers the risk of starting hosted. What does not transfer is the audience's address: URLs belong to the host, so a publication with an audience should treat its address as an asset and plan accordingly.

Preparing a Project for the Cloud

The preparation discipline mirrors the server guide's, with the data question sharpened. The upload carries your project and its data to the host, so the project must be self-contained: layers drawn from files the upload can gather, rather than live connections to a database on your office network that the hosted server cannot reach. Check every layer's source before uploading, the way you would before emailing a project to a colleague, because the failure mode is identical: a map that renders for you and arrives empty elsewhere. Name layers for strangers, since the viewer's layer list is your project's layer names read by people who have never met you. And test the publication as a stranger: open the web map in a private browser window, fetch the WMS capabilities document, and confirm the services answer without your sign-in, or with it, exactly as your tier intends. A publication verified from outside is a publication; anything less is a hope with a URL.

What the Upload Carries, and What It Cannot

Precision about the upload prevents the two classic disappointments. The plugin carries the project and the data the project reads from files: your shapefiles, GeoPackages, rasters, and their styling, symbology, labels, and layouts, reassembled on the hosted server as the same project. What it cannot carry is your local infrastructure: a layer reading from a PostGIS database on your office network, a file on a colleague's machine, or a service behind your firewall is a connection the hosted server cannot open, and the one-to-one promise applies to the project, not to your network. The practical consequence is a pre-flight habit: before uploading, walk the project's layer sources the way the server guide teaches for self-hosting, and convert any layer that depends on your premises into a file-based copy that travels with the upload, accepting that the copy is a snapshot whose freshness you manage by re-uploading. Teams whose data lives in a database by design, and changes hourly, are the natural constituency of the self-hosted route; teams whose data is a curated set of files are the cloud's. Neither is a compromise: they are different data lives, and the upload's manifest, files yes, connections no, is the line between them.

When the Cloud Is the Wrong Tool

Honesty about fit closes the evaluation. The hosted route is the wrong tool when the data may not leave the building, by law, by client contract, or by the sensitivity of what is mapped; no plan tier changes where the bytes live. It is the wrong tool when the publication must be deeply integrated into an existing portal, identity system, or hosting estate, where a service you operate slots in and a hosted island does not. It is the wrong tool when the map is not the product: a data-collection workflow, a public editing campaign, or an application with its own logic needs platforms built for those jobs, with QGIS perhaps authoring the base data behind them. And it is the wrong tool, trivially but commonly, when a static export would do: a map that never changes and serves no live services is a file, and the qgis2web route linked below publishes it from any web host without an account at all. The cloud's home ground is the live, styled, service-backed publication maintained by people who would rather map than administer, and on that ground it is genuinely hard to beat.

The Costs That Stay Yours

Hosted does not mean weightless, and a clear-eyed guide should list the burdens that remain on the author's side of the contract. The project's quality is yours: the host renders what you upload, and a slow, cluttered, or carelessly styled project publishes exactly as it is. The audience relationship is yours: the map's readers find you, not the host, when a layer is wrong, and a publication without a contact and a maintenance habit decays in public. The data stewardship is yours: uploads are copies of your data living on someone else's machines under the service's terms, which you should read with the same care as the tier restrictions, particularly for data with licensing or sensitivity attached. And the exit is yours to plan: the project file travels freely, as this guide notes, but audiences bookmark addresses, and an address belongs to the host. None of these burdens argues against the hosted route; they argue for entering it as a publishing decision with an owner, rather than as a button that made a map appear.

Related Guides

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

Frequently Asked Questions

What is QGIS Cloud?

A hosted publishing service by Sourcepole. A desktop plugin uploads your QGIS project one-to-one to a hosted QGIS Server, producing a web map in QGIS Web Client 2 plus WMS, WFS, and WCS service endpoints, without a server of your own.

What are the free tier's restrictions?

As the service's documentation states them: free publications are public only, and the free tier excludes commercial and government use. Paid plans are the route for private maps and for organizations.

Do I need to restyle my project for the web?

No. The one-to-one principle is the product: layers, order, styling, and print layouts transfer from the desktop project to the hosted server, which renders with the same QGIS engine.

Can other GIS software use my QGIS Cloud publication?

Yes. Alongside the viewer, the publication exposes WMS, WFS, and WCS endpoints, so desktop GIS and other clients can consume your layers as standard OGC services.

Can I move from QGIS Cloud to my own server later?

The project can: both routes serve the same project format with the same engine, so no restyling is needed. The published web addresses belong to the host, so plan for the audience's URL to change.

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