Exporting to the Cloud

3 min read

The Exports window sends your insights to the Cloud; the Cloud window’s Exports tab is where they land. Everything you configure here happens per insight.

Two ways to export #

  • After visualizing (the main path) — once you’ve rendered a Visual, export what’s on the Globe. The key rule: every active layer is exported exactly as it appears. If you applied a threshold, a Mask or any analytical-tool step, the export carries that — what you see is what you get.
  • Without visualizing — from the Scenes panel actions you can export straight from a search: the selected insights (or stacks) for the chosen scenes, or the raw bands (the native spectral data, the input for stochastic models). Handy when you already know what you want and don’t need to look at it first.

Either way you land in the same Exports window described below.

The export queue #

Each insight in the queue shows its date, Area, instrument and size, plus three per-insight controls:

  • Resolution — the pixel size of the export, in meters. You can only export at the insight’s native resolution or coarser — never finer than the data really is.
  • ModeGrey (the raw index values, one band, the choice for further analysis) or Comp (the RGB composite as displayed). Some insights only make sense one way — true-color composites, for instance — and show a fixed mode.
  • Export region — the whole Area or just one of its Zones: a Zone export clips to that geometry, producing a smaller file billed by the Zone’s area.
📷 Screenshot pending — Exports window with three insights queued, one Zone selected as export region.

Blocked rows #

A row can be locked (BLOCKED) for two reasons, always with the explanation in its tooltip:

  • EULA restrictions — raw composites of purchased scenes can’t be exported below 4× the instrument’s native resolution. Raise the row’s resolution to unlock it.
  • Trial licences can’t export insights from private instruments.

One blocked row disables the whole export — fix or remove it first.

Options and launch #

  • Email me when ready — for large batches, get a notification (subject: “Your Remote exports have completed”) instead of watching the ring.
  • Include metadata — adds a .txt sidecar per export with the legend and visualization range, color palette, band details and calculation methods, plus acquisition metadata.
  • Export to Cloud launches everything.

What happens next #

Exports run entirely in the background, on our servers. Once the window closes you can keep working, close the tab, log out, or shut down your computer — the export won’t stop and doesn’t need your session to stay open. Depending on the insight, resolution and area, it can take from a few seconds to minutes or even hours; turn on Email me when ready and you’ll be told the moment it finishes.

While you’re around, the navbar’s progress ring tracks each task and the cloud icon’s badge counts completions. Files land in Cloud → Exports under the Area’s folder and the export date, named so you can read them at a glance: insight, instrument, type, mode and date (Zone exports carry the Zone’s tag in the name).

Two details worth knowing:

  • Masked insights export exactly as displayed — pixels you masked on the Globe stay masked in the GeoTIFF.
  • Raw data exports (all native bands, no insights — see Creating a Visual) arrive here too, typed raw, at the instrument’s native resolution.

If an export is refused before it starts — area too large for the resolution, or over your download cap — nothing is charged: see Storage Limits & Export Caps.

Updated on July 20, 2026