> 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/basespace-sequence-hub/software-basespace-sequence-hub-faq-list/000003636.md).

# Why are underscores in sample names changed to dashes in the FASTQ file names?

Any underscores in Sample ID and Sample Names are converted to dashes to preserve sample naming conventions required for downstream analysis. Illumina FASTQs use the following format: `SampleName_SampleNumber_Lane_Read_FlowCellIndex.fastq.gz`

Local Run Manager, MiSeq Reporter, bcl2fastq, and BCL Convert when used through BaseSpace Sequence Hub (BSSH) will automatically make this change. However, locally-run BCL Convert, locally-run bcl2fastq, and onboard analysis on the NovaSeq X and NextSeq 1000/2000 will keep underscores exactly as provided in the input.

* Because the underscore-to-dash conversion can cause two distinct sample names to resolve to the same FASTQ filename, do not rely on underscores/dashes as the sole distinguishing characters between sample names. In instances when the underscore-to-dash conversion leads to samples with non-unique names, this can lead to analysis prematurely terminating or overwriting of data, depending on the software.

Additionally, note that FASTQs containing underscores in the SampleName field **cannot be uploaded to BSSH**; any underscores in sample names must be replaced with dashes or removed prior to upload. This requirement is described in the article [Requirements for uploading FASTQ Files to BaseSpace via web interface.](https://knowledge.illumina.com/software/basespace-sequence-hub/software-basespace-sequence-hub-troubleshooting-list/000001313.md)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3636), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003636%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/basespace-sequence-hub/software-basespace-sequence-hub-faq-list/000003636.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.
