# Exporting data

> Clean CSV or Excel of anything in the project — big jobs run in the background.

Source: https://geodb.io/guide/topic/export_data/ · Category: Sharing your data
Sometimes you genuinely need files — for a consultant's model, a
regulator, an archive. The **project export** page produces them cleanly,
from the same database everything else reads.

## Exporting

Tick the data types you want — or everything — pick CSV or Excel, and
export. Assay values can ride along with samples, flattened one column
per element using your project's merge settings, so the spreadsheet a
consultant receives matches what your strip logs show.

## Big projects

Large exports (a hundred thousand samples with assays) build in the
background: the page shows the job's progress and gives you the download
when it's ready — no held-open browser tab, no gateway timeouts. Recent
export jobs stay listed on the page so you can re-download.

## Coordinates

Exports honour your project's output coordinate setting — the same one
the ODBC connection uses — so exported eastings and northings land in the
grid your recipient expects.

## Before you export, a thought

If the recipient needs it *current* rather than *once*, consider the
alternatives on this shelf: a **dataroom** (curated link, always
up-to-date), **ODBC** (live desktop connection), or an **API grant**
(their software pulls it). Files go stale; those don't.