QGroundControl is the free, open-source ground control station for PX4 and ArduPilot vehicles. UgCS is a paid desktop planning and control software from SPH Engineering that supports PX4, Ardu, DJI, alongside MAVLink hardware and adds survey-specific mission tools. UgCS also has a free, limited version called UgCS Open. If you already fly ArduPilot or PX4 and QGroundControl handles your missions, the question is what does UgCS do that QGC does not, and does it matter for the work you actually sell?
This UgCS vs QGroundControl comparison goes feature by feature after using both products extensively and referring to information in their current documentation. Here, we cover vehicle support, terrain following and elevation data, LiDAR and photogrammetry mission planning, corridor and vertical scans, fleet handling, and support model, then give guidance by use case for applicable industries like oil and gas, mining, LiDAR corridors, and large-area photogrammetry. Both products change, so anything version-specific is marked as checked at the time of writing.
UgCS vs QGroundControl: Quick answer
QGroundControl (QGC) is a free, open-source ground control station for any MAVLink vehicle, with built-in survey, corridor and structure scan patterns. UgCS (Universal Ground Control Software) is paid desktop drone flight planning software supporting DJI plus MAVLink platforms, with custom DEM import and dedicated LiDAR tools. QGC is often enough for single MAVLink airframe and basic grids. But for mixed fleets or survey-grade LiDAR work, UgCS adds specific capability.
At-a-glance comparison
What QGroundControl is built for
QGroundControl is the reference ground control station for the MAVLink ecosystem. It handles full vehicle setup and configuration for PX4 and ArduPilot, firmware flashing, parameter editing, PID tuning, radio and sensor calibration, NTRIP/RTK, ADS-B and Remote ID settings, plus flight monitoring with video and instrument overlays. It works with every vehicle type those flight stacks support, including multirotor, fixed-wing, VTOL, rover and submarine.
For mission planning, it ships Survey, Corridor Scan and Structure Scan out of the box. With the Survey pattern, you can select a known camera, define a custom camera by sensor size, image resolution and focal length, or enter trigger distance manually. You set overlap separately along and across grid lines, specify either altitude or a target ground resolution, control transect angle, turnaround distance and entry point, refly the whole grid at a 90 degree offset, and hover-and-capture on multirotors. Corridor Scan does the same along a poly-line with configurable width and line spacing. Structure Scan flies layered orbits around a structure with configurable scan distance and entrance, exit and bottom altitudes.
This software also handles the field realities. Resume Mission rebuilds the plan from the last waypoint flown after an RTL or landing for a battery change. Terrain heights can be pre-downloaded for offline use. Multiple vehicles can connect to a single instance and be switched between in Fly View.
QGroundControl is genuinely enough when you fly one or a few ArduPilot or PX4 airframes, your grids and corridors are standard, your terrain is close to flat or your safety margin absorbs the variation, you are not running third-party LiDAR that needs calibration legs planned into the route, and your budget is a real constraint. It is free, it is open source, and it is the software the flight stacks themselves are developed against. A large amount of paid commercial survey work is flown this way.
Takeaway: if your missions are single-platform MAVLink grids over moderate terrain, QGC covers them without compromise.
What UgCS adds over free QGroundControl for surveying
Three capabilities carry most of the difference: import of your own DEM or DSM as GeoTIFF, so terrain following runs off survey-grade elevation data rather than a terrain service; a LiDAR mission toolset that plans IMU calibration patterns and loop turns into the route (Expert and Enterprise); and DJI support alongside ArduPilot and PX4 in one interface.
Underneath those sit the additions that matter once you are billing for the output. Smart AGL with adjustable terrain-following resolution and trajectory smoothing, vertical scan and circlegrammetry mission types, KML and CSV boundary import, per-waypoint control of gimbal pitch, speed and camera trigger, and vendor support with training instead of community forums.
- Custom DEM and DSM import: GeoTIFF elevation models you supply, rather than a server-queried terrain height.
- DJI support inside the same interface, alongside ArduPilot and PX4.
- A LiDAR-specific mission toolset: Including automated IMU calibration patterns (figure-eight, U-shape/J-hook, back-and-forth) and loop turns planned into the route. Available on Expert and Enterprise.
- Smart AGL with adjustable terrain-following resolution and slope, and trajectory smoothing, so the aircraft holds AGL over broken ground instead of stepping between waypoints.
- True Terrain Following through the SkyHub onboard computer and altimeter, for sensors that need to fly very close to the ground, such as GPR, echo sounders, metal detectors, and magnetometers.
- Vertical scan and circlegrammetry mission types for structures and towers.
- KML/CSV centerline and boundary import, which matters when clients hand you coordinates rather than a map to trace.
- Per-waypoint control of gimbal pitch, speed profile, camera trigger, turn behavior and lost-link action.
- Full 3D desktop planning environment with elevation profiles, on a full screen rather than a tablet.
- Vendor support and training, plus SDK access and multi-node deployment on Enterprise.
Takeaway: the paid delta is concentrated in elevation data control, LiDAR-specific planning, and multi-vendor hardware support. If none of those three touch your work, the delta is small.
Mixed fleets: can one tool plan for DJI and MAVLink hardware?
QGroundControl is MAVLink-only. Their website describes it as flight control and mission planning for any MAVLink-enabled drone, and DJI aircraft do not speak MAVLink natively. Community MAVLink-to-DJI-SDK bridges exist (RosettaDrone being the best known), but the original project is no longer actively maintained and their documentation warns about imperfect protocol translation. That is not a foundation for commercial survey work.
UgCS plans for DJI, ArduPilot, PX4, Freefly, Autel, Inspired Flight and Blue UAS airframes with the same workflow, and for DJI hardware syncs the finished mission to a controller running DJI Pilot 2 for execution. See the full UgCS vs DJI Pilot 2 comparison for that side of the workflow.
With these said, we should mention that QGC handles multiple simultaneous vehicles in a single instance, which UgCS puts in a separate product, UgCS Commander, with its own licence. If your requirement is several MAVLink aircraft flying at once and nothing else, QGC covers it at no cost.
Takeaway: mixed-vendor fleets are the clearest case for UgCS. Multiple MAVLink aircraft at once is the clearest case for QGC.
UgCS vs QGroundControl for survey-grade mission planning: terrain following, LiDAR, photogrammetry, corridor and vertical scans
Terrain following and elevation data
QGroundControl’s Survey documentation warns that when planning with camera specifications, the ground under the survey area is assumed to be flat at the launch altitude. If it is not, your effective overlap drifts and, over rising ground, you can plan a route into obstacles. Their recommended fix is its terrain-follow option, with tolerance and max climb and descent rate settings, and terrain heights come from AirMap servers. There is no documented official path to load your own GeoTIFF DEM into the planner. Terrain-follow behavior also differs between flight stacks, so check the release notes for your version and autopilot.
UgCS takes elevation data as an input you control. Import your own DEM or DSM as GeoTIFF, set the resolution and slope at which the route follows terrain, and use Smart AGL, which references both what is below and what is ahead of the aircraft, with trajectory smoothing. For a surveyor, the difference is whether the altitude your data spec depends on comes from your survey-grade elevation model or from a third-party terrain service.
LiDAR
QGroundControl's documented patterns produce geometry and camera triggering. There is no LiDAR mission type and no IMU calibration pattern generator. You can build calibration legs manually as waypoints, and experienced operators do.
UgCS plans them automatically. With UgCS LiDAR mission planning, you get figure-eight, U-shape/J-hook and back-and-forth calibration patterns inserted into the route, loop turns at line ends, and consistent AGL across the block, for DJI L-series and third-party sensors including YellowScan, Rock Robotic, Velodyne and RIEGL.
Photogrammetry
QGroundControl's Survey pattern gives you camera definition, separate along-line and across-line overlap, and altitude or target ground resolution. For a flat-to-moderate block with an RGB camera, that is a complete photogrammetry planner. UgCS adds photogrammetry and area scan tools with the same parameters plus terrain-corrected GSD from your own DEM, circlegrammetry, and per-waypoint camera and gimbal control.
Corridor and vertical
QGroundControl and UgCS both have a corridor pattern. QGC's Corridor Scan follows a poly-line with configurable width, spacing and turnaround. UgCS's Corridor Tool imports the centerline from KML or CSV, applies terrain following along it, and places battery swap points on long runs. Both software also have a vertical option: QGC's Structure Scan does layered orbits, while UgCS's vertical scan is aimed at facades and structures with sensor-specific control.
Takeaway: for photogrammetry the gap is narrow. For LiDAR and for anything where your own elevation model drives altitude, the gap is wide.
Open source and customizable vs commercial and supportedQGroundControl gives you the source, dual-licensed Apache 2.0 and GPLv3, so you can use it under either. It has a documented plugin architecture and a custom-build path covering branding, toolbar, Fly View and MAVLink customization. If you are an integrator shipping an aircraft with a GCS, or a research group that needs a mission type nobody sells, forking QGC is the way to go. You get no vendor obligation and no support SLA, and you own the maintenance and the merge conflicts with upstream.
UgCS gives you a supported product. Perpetual licences include first-year support and updates, Enterprise includes SDK access and multi-node deployment for a central server that field pilots connect to, and training runs through SPH Academy and regular webinars. However, you do not get the source, and you cannot add a mission type yourself.
The honest split here between QGroundControl and UgCS is that if engineering time is cheaper than licence cost and you need behavior that does not exist yet, customize QGroundControl. But if field time is your expensive resource and you need someone accountable when a survey fails at 3pm on a client site, buy the supported tool.
QGroundControl vs UgCS by use case
Oil and gas pipeline and facility inspection
Both tools have a corridor pattern. QGroundControl works if the corridor is flat and you are flying a MAVLink airframe. UgCS's advantage is in oil and gas is centerline import from client CSV or KML, terrain-following corridors from your own DEM, and battery swap points planned rather than improvised.
Mining: stockpile volumetrics and pit surveys
In mining applications, steep pit walls and benches are exactly where the flat-ground assumption in QGroundControl's survey planner costs you overlap consistency. Uploading a fresh site DEM daily and holding AGL against it is the UgCS case. QGroundControl will fly the grid, but the altitude reference is not yours.
LiDAR corridor and vegetation mapping
The clearest gap between UgCS and QGroundControl is in LiDAR corridor and vegetation mapping. Calibration legs, loop turns and consistent AGL over changing ground are planned automatically in UgCS Expert. On the flip side, in QGroundControl, you have to build them as manual waypoints on every mission.
Large-area photogrammetry
QGroundControl handles a single large polygon well. Where it gets manual is splitting a block across multiple flights and days and keeping overlap consistent across the seams. UgCS handles multi-segment routes and resume points inside one plan.
Which is the most suitable for your work?
When QGroundControl is enough
- You fly ArduPilot or PX4 exclusively, with no DJI or NDAA-compliant hardware planned
- Your missions are standard grids, corridors or structure orbits
- Your terrain is flat enough that a fixed safety margin is acceptable
- You are not running third-party LiDAR
- You need several MAVLink aircraft flying simultaneously at zero cost
- You want source access to modify or embed the GCS
- Budget is a hard constraint
When to choose UgCS
- Your fleet mixes DJI with ArduPilot, PX4 or NDAA-compliant airframes
- Altitude accuracy depends on your own DEM or DSM, not a terrain service
- You fly LiDAR, especially with third-party sensors needing calibration patterns
- You fly geophysical payloads close to the ground
- You plan large or long missions that cross battery and day boundaries
- You need vendor support, training and an accountable escalation path
FAQs
Does QGroundControl support DJI drones?
No, QGroundControl does not support DJI drones natively. It works with MAVLink-enabled vehicles, in practice PX4 and ArduPilot, and DJI aircraft do not use MAVLink. Community MAVLink-to-DJI bridges exist but are experimental and largely unmaintained.
What does UgCS add over QGroundControl for mapping?
For professional drone mapping, UgCS wins with custom DEM and DSM import as GeoTIFF, a dedicated LiDAR toolset with automated IMU calibration patterns, Smart AGL terrain following with adjustable resolution, DJI plus multi-vendor hardware support, vertical scan and circlegrammetry mission types, KML/CSV route import, and vendor support.
Is QGroundControl good enough for LiDAR surveys?
QGroundControl can fly LiDAR surveys, but it has no LiDAR-specific mission type and no automated IMU calibration pattern, so calibration legs and loop turns have to be built manually as waypoints on every mission. For occasional LiDAR work that is workable. However, for LiDAR as a core service line, it means repeated manual setups and can be a source of error.
Can QGroundControl import a custom DEM for terrain following?
Not according to its current documentation. QGroundControl's survey and corridor terrain following queries terrain heights from AirMap servers. There is no documented option to load your own GeoTIFF elevation model into the planner.
Can one program plan missions for a mixed DJI and ArduPilot fleet?
UgCS can, with the same interface and workflow across DJI, ArduPilot, PX4 and Blue UAS airframes. QGroundControl cannot do this, because it is limited to MAVLink vehicles.
Why pay for UgCS instead of customizing open-source QGroundControl?
Because the cost moves rather than disappears. Forking QGroundControl makes sense when you have engineering capacity and need behavior nobody sells. Buying UgCS is reasonable when field time is your expensive resource and you need vendor support, training and an SDK rather than a maintenance burden.
Conclusion
QGroundControl and UgCS are built for different scopes. QGroundControl is a complete, free, open-source ground control station for MAVLink vehicles, with survey, corridor and structure patterns that handle a great deal of real commercial work. UgCS is paid software built around the parts of professional surveying that QGC does not target, such as your own elevation data, LiDAR-specific planning, multi-vendor fleets, and supported deployment.
If the custom DEM import, LiDAR toolset, and mixed-fleet support do not touch your work, stay on QGroundControl. But if they do, test it against your own site. UgCS Open is free with no credit card and runs the same planning engine, so you can plan a real mission over your own DEM before deciding to commit to a paid UgCS license.