> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/components/library-file-management/adding-a-variant-effect-predictor-vep-database.md).

# Adding a Variant Effect Predictor (VEP) Database

Click the **+ Add VEP database** button under the *VEP database* section on the [library file management page](/partek/partek-flow/user-manual/settings/components/library-file-management/library-file-management-page.md).

If you are using an species supported by Partek (i.e., human, mouse, rat), a VEP database from [ENSEMBL](http://www.ensembl.org/info/data/ftp/index.html) will be available for automatic download. Select the **Download database** radio button and click **Create** (Figure 1).

![Figure 1. For certain model organisms, automatic downloads of VEP databases are available](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-6e9f023c34a5cd1183ae0c9b607af12756226ad0%2Fadd-vep-auto.png?alt=media)

If you are working with a custom assembly, choose the **Import database** radio button and click **Create** (Figure 2). A VEP database can be added from the *Partek Flow Server* or a *URL* download link. The behavior of each option is similar to when importing a reference sequence (see [Adding a Reference Sequence](https://github.com/illumina-swi/partek-docs/blob/main/docs/partek-flow/user-manual/settings/components/library-file-management/adding-reference-sequence.md)). ENSEMBL maintains an extensive list of VEP databases for various species. We recommend going to [ENSEMBL's ftp download site](http://www.ensembl.org/info/data/ftp/index.html) and finding the VEP database download link for your species of interest.

![Figure 2. VEP databases can be added for other species](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-0b068b4db229fbb7941439f9a94e737f4a7f3e95%2Fadd-vep-custom.png?alt=media)

One VEP database is allowed per genome assembly. Once a VEP is successfully imported, the **+ Add VEP database** button will not be shown (Figure 3).

![Figure 3. Successful addition of a VEP database library file](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-a7983f02cee0ba56dd4704385181a30785e08bdf%2Fvep-added.png?alt=media)

## Additional Assistance

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/components/library-file-management/adding-a-variant-effect-predictor-vep-database.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.