Upload a TSV to parse and review variant rows in the table below (data comes from your file).
Back to ToolsNo file chosen
| Variant ID | Location | Type | Gene | Clinical Significance | Population MAF | Protein Impact | Publications |
|---|
This tool reads a TSV you upload and renders variant rows in a table. It does not query ClinVar, gnomAD, or other services—every value must already be in your file. Maximum upload size is 15 MB.
.tsv or .txt. Confirm the filename appears; then enable Analyze Variants.
Scope: Not a VCF importer—convert to this TSV layout first. No live re-annotation. For research and teaching, not clinical reporting.
Use a tab-separated file with a header row and one variant per row. Expected column order: variant ID, location, type, gene, molecular consequences, clinical significance, 1000 Genomes MAF, ESP MAF, ExAC MAF, publications (comma-separated within the cell if needed). The first column must contain a variant identifier (for example an rs ID). This tool does not call external annotation APIs; it displays the values you supply.
It shows the text from your clinical significance column after parsing the TSV. Prepare that column with your own classifications or notes from sources you trust; the app does not query ClinVar or other databases automatically.
The table shows a single MAF value taken from your file: it prefers the 1000 Genomes MAF column, then ExAC, then ESP, when those cells are filled. It reflects whatever you encoded in the TSV, not a live lookup from gnomAD or other servers.
The Protein Impact column displays the molecular consequences field from your row (for example consequence terms or notes you exported from another pipeline). The tool does not run SIFT, PolyPhen, or CADD on the server.
The server walks your rows in chunks of that size and waits briefly between chunks. For very large files this spreads work over time; for smaller files the choice has little effect. There is no separate “live” analysis step per batch beyond reading your data.