A BigWig file stores quantitative, continuous-value data associated with genomic coordinates, such as RNA-seq coverage depth, ChIP-seq signal enrichment, or conservation scores. It is generated from a human-readable wiggle (WIG) or bedGraph file using the wigToBigWig utility, creating a compressed binary index that allows software to instantly query a specific region without reading the entire file.
Glossary
BigWig

What is BigWig?
BigWig is an indexed binary file format for the rapid, random-access visualization and storage of dense, continuous genomic data tracks in genome browsers.
The format's primary advantage is its support for random access via an internal R-tree index, enabling genome browsers like the UCSC Genome Browser and IGV to fetch and render a data track for any requested zoom level in milliseconds. This makes BigWig the standard for hosting large epigenomic signal tracks on remote servers, as only the data for the viewed region is transferred.
Key Features of BigWig
BigWig is an indexed binary file format optimized for storing dense, continuous-value genomic data tracks. It enables rapid, random-access retrieval of data slices for visualization in genome browsers without loading entire files into memory.
Indexed Random Access
BigWig files contain a built-in R-tree index that maps genomic coordinates to file offsets. This allows genome browsers to request data for a specific region (e.g., chr1:100,000-200,000) and retrieve only the relevant bytes, achieving sub-second query times even for terabase-scale datasets. The index is stored in a separate chromosome tree and data index structure, enabling efficient spatial queries without sequential scanning.
Compressed Storage Efficiency
BigWig employs run-length encoding and gzip block compression to dramatically reduce file size while preserving numerical precision. Dense tracks like RNA-seq coverage or ChIP-seq signal are stored as compressed blocks of raw values. This compression is lossless for fixed-step data and configurable for variable-step tracks, balancing storage footprint against access speed.
Fixed-Step vs Variable-Step Resolution
BigWig supports two internal data representations:
- FixedStep: Uniformly spaced values (e.g., every 10bp), ideal for tiled array data or binned coverage.
- VariableStep: Irregularly spaced intervals with associated scores, suited for peak calls or sparse signal.
- BedGraph-to-BigWig conversion: The
bedGraphToBigWigutility converts human-readable BED-like text into indexed binary format, requiring a chromosome sizes file for coordinate validation.
Summary Levels for Multi-Resolution Views
BigWig precomputes summary levels at multiple zoom resolutions, storing mean and maximum values for aggregated bins. When a user zooms out to view an entire chromosome, the browser fetches precomputed summaries rather than raw data points, enabling instant rendering of broad signal landscapes. This hierarchical aggregation is critical for interactive exploration of epigenomic tracks spanning gigabases.
UCSC Genome Browser Integration
BigWig is the standard format for UCSC Genome Browser custom tracks and track hubs. Files can be hosted remotely via HTTP or FTP, with the browser fetching only the index and requested data slices. This enables institutions to share massive epigenomic datasets without requiring users to download entire files. The format is also supported by IGV, WashU Epigenome Browser, and JBrowse.
Programmatic Access via libBigWig
The libBigWig C library provides a fast, dependency-free API for reading and writing BigWig files programmatically. Bindings exist for Python (pyBigWig), R, and Perl, enabling bioinformaticians to extract signal values at specific genomic coordinates directly within analysis pipelines. This bypasses the need for intermediate text conversions and supports high-throughput feature extraction for machine learning training sets.
BigWig vs. Other Genomic Data Formats
Comparison of BigWig with other common formats used for storing and visualizing continuous genomic signal data.
| Feature | BigWig | bedGraph | Wiggle (WIG) | BAM Coverage |
|---|---|---|---|---|
Indexed random access | ||||
Binary compressed storage | ||||
Supports variable step | ||||
Genome browser native | ||||
File size (100M reads) | ~50 MB | ~200 MB | ~180 MB | ~1.5 GB |
Query speed (region) | < 0.1 sec | 2-5 sec | 3-8 sec | < 0.5 sec |
Stores raw read alignments |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to common questions about the BigWig indexed binary format for dense, continuous genomic data tracks.
A BigWig file is an indexed, binary file format designed for the rapid visualization and storage of dense, continuous genomic data tracks in genome browsers. It works by storing data in a compressed, block-based structure with a companion index file that allows software to quickly retrieve only the data overlapping a specific genomic region without reading the entire file. The format is generated from a wiggle (WIG) or bedGraph text file using the wigToBigWig utility. Internally, it organizes data into fixed-size bins, pre-calculating summary statistics like mean and maximum for each zoom level. This hierarchical indexing enables seamless, real-time rendering of massive datasets—such as RNA-seq coverage depth or ChIP-seq signal enrichment—across any scale, from a single gene locus to a whole chromosome view.
Related Terms
Explore the file formats, tools, and computational concepts essential for storing, indexing, and visualizing the continuous signal tracks that BigWig files represent.
bedGraph Format
A simple, human-readable text format for storing continuous genomic data tracks. Unlike BigWig, bedGraph is uncompressed and unindexed, making it suitable for data exchange but inefficient for large-scale visualization.
- Structure: Four-column tab-separated format (chrom, start, end, value)
- Use Case: Intermediate format for converting wiggle data to BigWig
- Limitation: Slow random access; must be converted to BigWig for genome browser performance

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us