> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/software/cloud-software/software-cloud-software-reference_material-list/000003651.md).

# How to import files into a BaseSpace Project using the web Interface

The following file types can be uploaded to projects in BaseSpace Sequence Hub.

* FASTQ files (\*.fastq.gz),
* Analysis files (Variant Call Format (VCF) and Genomic Variant Call Format (gVCF)),
* Manifests (\*.txt),
* Sample Sheets (.csv),
* etc.

Note: User must have write access (ownership) of the BaseSpace project.

**To upload data via the web interface:**

1. Open the BaseSpace project.
2. From the project, select File (the paper icon), then Upload, and then select Files.
3. Select type of files to upload.

Note: Uploading multiple FASTQ, VCF, or manifest files in a single session requires files of the same type.

1. If uploading a FASTQ file, do the following.
   1. Select Select Biosample, then select or create a Biosample for the FASTQ file(s).
   2. Enter a library name.
   3. Select a library prep kit.
   4. \[Optional] Enter a position name.
   5. Select Finish Upload.
2. If uploading a VCF file, do the following.
   1. Select Select Biosample, then select or create a Biosample for the VCF(s).
   2. Select Finish Upload.
3. If uploading a manifest file, do the following.
   1. Select Select Biosample, then select or create a Biosample that the manifest will be associated with.
   2. Select Finish Upload.
4. If uploading other file types, do the following. (This option is only available in New mode.)
   1. \[Optional] Select Select Biosample, then select or create a Biosample that the files will be associated with.
   2. Select Finish Upload.

See the [Import Files Into a Project help page](https://help.basespace.illumina.com/manage-data/import-data#import-files-into-a-project) for additional information.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3651), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003651%20-%20Software%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/software/cloud-software/software-cloud-software-reference_material-list/000003651.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
