Skip to main content
To run an analysis, you first need to get your data into Galagos. Files are uploaded into a project’s isolated sandbox — each project has its own storage space, and files you upload are only accessible within that project.

How to upload files

1

Open your project

From the Galagos dashboard, click the project you want to work in. If you haven’t created a project yet, click New project and give it a name.
2

Navigate to the Files tab

Inside your project, click the Files tab in the left sidebar. This shows all files currently stored in the project sandbox.
3

Upload your files

Drag and drop your files onto the upload area, or click Upload files to open a file picker. You can upload multiple files at once.
4

Confirm the upload

Galagos displays a progress indicator for each file. Once all files show a checkmark, they are ready to use in an analysis.
You can also reference uploaded files by name when typing a prompt in the chat interface. For example: “Perform differential expression analysis on counts.csv.”

Supported file formats

Galagos natively handles the following formats: For a detailed breakdown of each format and its intended use cases, see Supported file formats.

Storage limits by plan

Each project counts toward your plan’s total storage quota. The limits are: For more information on storage and how it is calculated, see Credits and storage.

Data privacy and GDPR requirements

All biological or health data that can identify an individual — including raw sequencing reads, variant calls, and clinical metadata — must be pseudonymized before upload. This is required under GDPR and is your responsibility as the data controller.
Pseudonymization means replacing any direct identifiers (such as patient names, national ID numbers, or sample barcodes linked to identifiable individuals) with a code or token before the file leaves your institution. Galagos stores and processes the pseudonymized data, not the original identifiers.
Under GDPR, genetic data and data concerning health are special categories of personal data. This includes raw sequencing reads (FASTQ, BAM), variant files (VCF) derived from human samples, and any metadata table containing patient or donor identifiers.
Replace identifying fields in metadata CSVs with opaque tokens (for example, replace PatientID: Jane Doe with sample_id: S001). For sequencing files, ensure read headers do not contain patient identifiers. Keep the mapping between tokens and real identities in a secure location at your institution.
See the Data privacy and security page for details on data residency and subprocessor locations.

Reusing files across projects

If a file is something more than one project will need — a reference genome, a panel, a curated artifact — upload it to the workspace library instead of into a single project. Any project in the same workspace can then pull a copy in with one click (or by asking the agent), and you can push project results back to the library the same way. See Workspace library for the full workflow.

Next steps

Run an analysis

Describe your research question in plain English and let Galagos plan and execute the workflow.

Supported file formats

See the full format reference, including notes on compression and tool compatibility.

Workspace library

Upload once, reuse across every project. Works from the UI and from chat.