> 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/microarray/designstudio-microarray/microarray-designstudio-microarray-reference_material-list/000007910.md).

# DesignStudio Microarray Assay Designer Input Target File Templates

DesignStudio Microarray Assay Designer is a web-based software tool that enables customers to design custom and semi-custom Infinium BeadChips.

Design requests must be submitted using files which follow specific formatting requirements. Template files demonstrating the required formats are available to download from [DesignStudio Microarray Assay Designer](https://designstudio-array.illumina.com/) (MyIllumina login required). Direct links to each template, along with a brief description of each, are provided below.

**Files**

[Region List (Human only)](https://designstudio-array.illumina.com/uploadTemplates/WGGT/Region.csv)

Specify a chromosome, start coordinate, and end coordinate for each target.

[Identity File (Human only)](https://designstudio-array.illumina.com/uploadTemplates/WGGT/Identity.csv)

Specify an rsID from dbSNP for each target.

[Gene List (Human only)](https://designstudio-array.illumina.com/uploadTemplates/WGGT/Gene.csv)

Specify a gene name (RefSeq accession IDs or HUGO identifiers) as well as bases upstream/downstream for each target.

[Existing Design](https://designstudio-array.illumina.com/uploadTemplates/WGGTXT/ExistingDesign.csv)

Specify an ILMN ID from previously designed iSelect, XT iSelect, or Commercial+ assays for each target.

[Sequence List](https://designstudio-array.illumina.com/uploadTemplates/WGGTXT/Sequence.csv)

Specify a sequence in context of a SNP or Indel for each target.

[Score File](https://designstudio-array.illumina.com/uploadTemplates/WGGT/Score.csv)

Specify an assay from any DesignStudio Microarray Assay Designer (or ADT) generated Score File for each target.

**Reference:**

[DesignStudio Microarray Assay Designer Documentation](https://support.illumina.com/array/array_software/designstudio-microarray/documentation.html)

\
\
\ <br>

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