Install bcftools with Homebrew, apt, dnf, MacPorts, Nix, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• bcftools
• color-chrs.pl
• gff2gff
• gff2gff.py
• guess-ploidy.py
• plot-roh.py
• plot-vcfstats
• roh-viz
• run-roh.pl
• vcfutils.pl
• vrfs-variances

Project history

BCFtools grew out of the SAMtools ecosystem for high-throughput sequencing data. The upstream README says it implements utilities for variant calling, in conjunction with SAMtools, and for manipulating VCF and BCF files, with the intention of replacing Perl-based tools from vcftools.

The Samtools project now presents three related repositories: Samtools for SAM/BAM/CRAM, BCFtools for BCF2/VCF/gVCF and variant calling/filtering/summarising SNPs and short indels, and HTSlib as the underlying C library.

Adoption history

The 2021 GigaScience paper by the SAMtools/BCFtools authors describes SAMtools and BCFtools as widely used programs for processing and analysing high-throughput sequencing data, first appearing online 12 years earlier and used in many other projects and genomic pipelines.

The same paper reports that both SAMtools and BCFtools had been installed more than one million times via Bioconda, making bcftools a rare CLI package whose package-manager footprint maps directly to scientific infrastructure.

How it is used

bcftools is used for file-format conversion and manipulation, sorting, querying, statistics, variant calling, filtering, and effect analysis. In pipelines it commonly appears after alignment and BAM/CRAM processing, where it calls or filters variants into VCF/BCF outputs.

The executable is usually scripted rather than used as a single monolithic command: subcommands such as view, query, filter, stats, mpileup, call, norm, annotate, merge, and concat make it a toolkit for repeatable genomics workflows.

Why package nerds care

bcftools is package-nerd significant because it is a dependency-shaped scientific standard: small enough to install as a CLI, but central enough that entire variant-calling workflows assume it is available and versioned consistently.

It is also a good example of package-manager science: Homebrew, Debian, Fedora, MacPorts, Nix, Ubuntu, and Bioconda-style environments turn a research-code lineage into a reproducible command people can pin in workflows, containers, and clusters.

The BCF/VCF domain makes versioning matter. File formats, reference assumptions, compression/indexing via HTSlib, and pipeline reproducibility all mean bcftools is not just a convenience binary; it is part of the scientific record for many analyses.

Timeline

• 2009: SAMtools/BCFtools lineage begins, per the 2021 'Twelve years' project history.
• 2013: Official GitHub bcftools repository created.
• 2021: GigaScience publishes 'Twelve years of SAMtools and BCFtools'.
• 2020s: bcftools continues as part of the Samtools/HTSlib ecosystem and remains broadly packaged.

Related projects

• SAMtools handles SAM/BAM/CRAM operations in the same project family.
• HTSlib is the C library used internally for high-throughput sequencing formats.
• vcftools is the older Perl-based toolkit that bcftools was intended to replace for many VCF/BCF operations.
• Bioconda, workflow engines, and containerized genomics environments are major adoption channels.

Sources

• https://doi.org/10.1093/gigascience/giab008
• https://github.com/samtools/bcftools
• https://samtools.github.io/bcftools/bcftools.html
• https://www.htslib.org/
• source_facts.package-manager