{
  "id": "variant-call-format",
  "title": "Variant Call Format",
  "lang": "en",
  "source_lang": "en",
  "summary": "Variant Call Format is a standardized text format for recording genomic sequence variants, their positions relative to a reference genome, and associated sample genotypes and annotations.",
  "category": "science",
  "subcategory": "biology",
  "type": "concept",
  "aliases": [
    "VCF"
  ],
  "generated_at": "2026-11-04",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/variant-call-format/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/variant-call-format/",
      "json": "https://aiwiki.page/zh/variant-call-format.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "Variant Call Format (VCF) is a tab-delimited text format used to describe variation in DNA sequences relative to a reference genome. A VCF file records the locations and identities of sequence differences and can also contain genotypes for one or more samples, quality estimates, filtering results, and biological annotations. It is widely used to exchange results from DNA sequencing analyses, particularly single-nucleotide variants, short insertions and deletions, and larger structural variants.\n\nVCF represents interpreted variant calls rather than the underlying sequencing reads. Its reference sequence, metadata, and field definitions are essential to interpreting its contents correctly."
    },
    {
      "heading": "Development and scope",
      "text": "VCF originated in the 1000 Genomes Project as a common representation for variation discovered across many human genomes. A description of the format and its associated VCFtools software was published in 2011. The format subsequently became widely used beyond human genomics, including research on other animals, plants, and microorganisms.\n\nThe specification is maintained through the HTS specifications project, alongside related high-throughput sequencing formats. Successive versions have clarified field definitions and extended support for complex variation. A file declares its specification version in its first line; support for particular features depends on both that version and the software reading the file.\n\nAlthough originally associated with variant sites, VCF can also represent reference observations and intervals of reference confidence through conventions such as genomic VCF."
    },
    {
      "heading": "File organization",
      "text": "A VCF file has a header followed by data records. Each record normally describes a variant site or a related genomic event.\n\nMetadata and column header\n\nMetadata lines begin with ##. The first line declares the format version, for example:\n\n##fileformat=VCFv4.3\n\nOther metadata can identify the reference assembly, sequence contigs, analysis software, filtering criteria, and annotation definitions. Structured declarations define fields used in the INFO and FORMAT columns, including their identifiers, types, numbers of values, and descriptions.\n\nA final header line begins with #CHROM. It names eight fixed columns, followed, when sample data are present, by FORMAT and one column for each sample.\n\nFixed columns\n\nColumn | Meaning\nCHROM | Reference sequence identifier, such as a chromosome or contig name.\nPOS | One-based position of the first reference base represented by the record.\nID | One or more identifiers for the variant, or . if unavailable.\nREF | Reference allele sequence.\nALT | Comma-separated alternate alleles, or . when no alternate allele is specified.\nQUAL | Phred-scaled quality associated with the assertion of variation represented by the record.\nFILTER | Filter results: PASS when all applied filters passed, named failed filters otherwise, or . when filters have not been applied.\nINFO | Semicolon-separated site-level annotations.\n\nCHROM may refer to a chromosome, an unplaced contig, or another sequence in the reference assembly. An allele is interpreted relative to that particular reference, not independently of it.\n\nThe optional FORMAT column lists colon-separated sample fields, such as GT:DP:GQ. Each subsequent sample column supplies values in that order."
    },
    {
      "heading": "Alleles, coordinates, and genotypes",
      "text": "Reference-relative representation\n\nFor a single-nucleotide variant, REF and ALT can each contain one base. A record with POS=100, REF=A, and ALT=G describes a G alternate allele at a position where the reference has A.\n\nShort insertions and deletions generally include a shared anchoring base so that neither allele sequence is empty. For example:\n\n- POS=100, REF=A, ALT=AT represents insertion of T after the reference base at position 100.\n- POS=100, REF=AT, ALT=A represents deletion of the T at position 101.\n\nThus, a deletion record's position may identify its anchor rather than the first deleted base. Special anchoring rules apply to events at the beginning of a reference sequence.\n\nVCF coordinates are one-based. Confusing them with zero-based coordinate systems used by some other genomic formats can shift an interpretation by one base.\n\nGenotype encoding\n\nThe GT field represents alleles by numerical indexes:\n\n- 0 denotes the reference allele.\n- 1 denotes the first allele listed in ALT.\n- 2 denotes the second alternate allele, and so forth.\n- . denotes a missing allele.\n\nFor a diploid sample, 0/1 indicates one reference allele and one copy of the first alternate allele; 1/1 indicates two copies of that alternate allele. With ALT=C,G, 1/2 represents one C allele and one G allele.\n\nA slash indicates that the genotype is unphased. A vertical bar, as in 0|1, indicates phase information: allele order is meaningful within the applicable phase context. Phase-set annotations can identify which records have a known phase relationship. A phased separator alone does not establish chromosome-wide haplotypes.\n\nGenotypes can contain other numbers of allele entries to accommodate haploid organisms, sex chromosomes, and polyploidy."
    },
    {
      "heading": "Example",
      "text": "The following example contains one biallelic site and one sample. Fields within the header row and data row are separated by tabs.\n\n##fileformat=VCFv4.3\n##contig=<ID=chr1,length=1000000>\n##FORMAT=<ID=GT,Number=1,Type=String,Description=\"Genotype\">\n##FORMAT=<ID=DP,Number=1,Type=Integer,Description=\"Read depth\">\n#CHROM\tPOS\tID\tREF\tALT\tQUAL\tFILTER\tINFO\tFORMAT\tSAMPLE_A\nchr1\t100\t.\tA\tG\t50\tPASS\t.\tGT:DP\t0/1:18\n\nThe record describes an A-to-G variant at position 100 on chr1. SAMPLE_A has an unphased heterozygous genotype, and its reported read depth is 18. The site has quality 50 and passed the filters that were applied. No variant identifier or site-level annotations are supplied.\n\nThis record does not, by itself, establish a biological effect, inheritance pattern, or association with a phenotype."
    },
    {
      "heading": "Annotations and quality measures",
      "text": "VCF distinguishes site-level annotations in INFO from sample-level annotations identified by FORMAT.\n\nCommon fields include:\n\n- AC: alternate-allele counts among the genotypes considered.\n- AN: total number of alleles counted in called genotypes.\n- AF: alternate-allele frequency.\n- DP: read depth, with scope and counting details dependent on the field definition and producing software.\n- AD: sample-level depths for the reference and alternate alleles.\n- GQ: sample-level genotype quality.\n- PL: Phred-scaled genotype likelihoods.\n\nQuality values commonly use the Phred transformation:\n\n\\[Q=-10\\log_{10}p,\\]\n\nwhere \\(p\\) is the relevant error probability. A value of 30 corresponds to an error probability of \\(10^{-3}\\) under that interpretation. Site quality, genotype quality, and genotype likelihoods describe different quantities and are not interchangeable. Their empirical calibration also depends on the calling model and data.\n\nHeader declarations specify annotation cardinality. For example, Number=A means one value per alternate allele, Number=R one per reference and alternate allele, and Number=G one per possible genotype under the applicable ploidy. These distinctions matter when splitting or merging records."
    },
    {
      "heading": "Structural variants and symbolic alleles",
      "text": "Larger changes, collectively called structural variation, may be represented by explicit sequences or symbolic alleles such as <DEL>, <DUP>, and <INV>. Additional fields can describe variant type, length, endpoints, and uncertainty in breakpoint positions.\n\nVCF also defines breakend notation for rearrangements. Brackets and reference coordinates describe how an end of one sequence connects to another. Depending on the event, multiple linked records may be needed.\n\nTwo special alternate-allele forms have distinct meanings:\n\n- * denotes an allele absent at the current position because of a deletion represented by another record.\n- <NON_REF>, used in genomic VCF workflows, represents possible non-reference alleles not explicitly listed.\n\nNeither should be interpreted as an ordinary DNA sequence."
    },
    {
      "heading": "Compression, indexing, and related formats",
      "text": "VCF is human-readable but can become large in studies containing many samples. It is commonly compressed with BGZF, a block-based compression format that supports efficient access to portions of a compressed file. Coordinate-sorted compressed VCF files can be indexed using tools such as Tabix, allowing retrieval of records overlapping a genomic region without reading the entire file.\n\nBinary Call Format (BCF) is a binary representation of the VCF data model. It reduces text-parsing overhead and is widely used for computational processing.\n\nGenomic VCF (gVCF) is a VCF-based representation that includes information about non-variant positions or blocks of positions, as well as candidate variants. It is commonly used as an intermediate in joint genotyping. The absence of a site from an ordinary variant-only VCF, by contrast, does not establish that the sample confidently matches the reference there.\n\nSoftware including VCFtools and BCFtools supports operations such as filtering, querying, merging, annotation, and conversion."
    },
    {
      "heading": "Applications and limitations",
      "text": "VCF provides a common exchange format for population genetics, genome-wide association studies, variant annotation, and comparison of sequencing analyses. Its support for multiple samples permits site-level summaries alongside individual genotypes.\n\nInteroperability nevertheless depends on more than syntactic validity:\n\n- Reference compatibility: Coordinates and alleles depend on a specific assembly. Converting between assemblies requires coordinate mapping and validation of allele sequences.\n- Equivalent representations: The same insertion, deletion, or complex event can have different valid representations, especially in repetitive sequence. Trimming redundant bases and left-aligning indels can improve comparisons, but do not resolve every complex equivalence.\n- Multiallelic transformations: Splitting a record into separate biallelic records requires appropriate updates to genotypes, allele-indexed annotations, and genotype-indexed values.\n- Missingness: A missing genotype is not a homozygous-reference genotype. An omitted site may reflect filtering, insufficient evidence, or the output conventions of the pipeline.\n- Annotation consistency: Custom fields, differing depth calculations, and caller-specific filters can make superficially similar files difficult to compare.\n- Representation limits: Complex rearrangements and variation relative to a pangenome may be cumbersome to express through records anchored to one linear reference.\n\nVCF standardizes how results are represented, not how they are inferred. A valid file can still contain incorrect calls, poorly calibrated quality scores, or incomplete annotations."
    }
  ],
  "links": [
    "dna",
    "reference-genome",
    "genotype",
    "dna-sequencing",
    "chromosome",
    "allele",
    "phenotype",
    "probability",
    "population-genetics",
    "genome-wide-association-study",
    "pangenome"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}