Read a VCF as a set of variant records

A VCF is valuable because it is compact relative to raw sequencing files and describes called variants in a standardized form. The header may identify the reference build, sample fields, filters, and provenance. That context matters: the same coordinate can mean different things across builds, and a variant record is not automatically a health conclusion.

Preserve the header before doing anything else

Keep the VCF or compressed VCF.GZ unchanged after download. Do not rename it as a spreadsheet or manually remove its header. Store it in encrypted storage you control, alongside the provider's original report and a note of the test date.

When sharing the file with a tool, check whether it accepts your build and whether it explains what it stores. Prefer services that return source-level provenance and distinguish an observation from an interpretation or recommendation.

The columns you will see

A basic VCF row includes chromosome, position, identifier, reference allele, alternate allele, quality, filters, and an INFO field. Sample columns can add genotype and read-level fields. The header defines these tags, names the file format version, and may identify the reference assembly and calling software.

FILTER and quality fields deserve attention. A record present in the file can still have a failed filter or uncertain genotype. Downstream tools should state how they use those fields. A clean interface should preserve the original record and show any filtering or annotation as a separate step.

Safe ways to inspect the file

Use tools such as bcftools, tabix, or a trusted genomic viewer for large files. A plain text editor can inspect a small header. Spreadsheet software may alter identifiers, dates, or scientific notation and can truncate large datasets, so it is a poor place for the master copy.

When a service requests a build, read the VCF header and the provider documentation. Guessing between GRCh37 and GRCh38 can produce incorrect coordinates. If the build remains unclear, ask the provider before analysis.

  • Work from a copy
  • Keep the header attached
  • Record the reference assembly
  • Check FILTER and genotype quality fields
  • Document every conversion or normalization step

VCF handoff checklist

  • Original filename and checksum recorded
  • Reference assembly confirmed
  • Provider, test date, and sample identifier retained
  • Supported file size and compression checked before upload
  • Storage, retention, export, and deletion terms reviewed

Use VCF data with visible provenance

WellNizz accepts WGS VCF/VCF.GZ in its genetics flow and keeps outputs linked to their source. A product can combine the resulting genetic context with biomarkers and wearables while retaining modality and source boundaries in the dashboard contract.

Protect a file that can identify you

A VCF can contain highly sensitive information about you and relatives. Only upload it to services whose privacy, retention, export, and deletion terms you understand.

Editorial sources

Read the primary guidance

These sources support the technical and health boundaries in this article. Provider prices, availability, and product terms should always be checked at the provider before purchase.

Questions, answered

FAQ

Is a VCF file the same as a genome?

A VCF contains called variants relative to a reference. FASTQ, BAM, or CRAM files hold other layers of sequencing data, and the provider report contains the original interpretation.

Can I open a VCF in Excel?

You can inspect parts of one as text. Spreadsheet software can corrupt or truncate genomic files, so preserve the original and use a tool built for VCF.