> 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/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000007440.md).

# Run folder sizes and disk space on the NextSeq 500/550

All run folder sizes listed below are only to be used for approximation. Folder sizes will vary depending on the raw cluster density and the number of clusters passing filter for a run.

* The examples below are based on dual-indexing runs with optimal clustering and clusters passing filter greater than 80%.
* The following also include FASTQ files generated on the instrument by the Local Run Manager FASTQ workflow (NextSeq Control Software v4.0 and higher).

  ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-7fe7e6583236d3d29da1964a55dcd24ea4683514%2Fimage1.jpg?alt=media\&token=37c56765-7912-4ec2-a1a7-6094aec835b4)

**Notes:**

* The NextSeq 500/550 hard drive is 1770 GB total.
* 498 GB are partitioned to C:\ for the Operating System Files and Illumina software Installation.
* The remaining 1272 GB are allocated to D:, where run data is stored.

For further information on other Illumina instruments, search for Knowledge Base article [Approximate sizes of sequencing run output folders](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001508.md).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7440), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007440%20-%20Instrumentation%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/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000007440.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.
