This article helps you choose among Hi-C, Micro-C, Capture Hi-C and HiChIP for 3D genome studies. It explains how each chromatin interaction method works, what kind of 3D genome features it captures, and how to match methods to real project questions.
Use Hi-C for global 3D genome architecture, Micro-C for high-resolution loops, Capture Hi-C for focused loci such as promoters or GWAS blocks, and HiChIP for histone-mark–anchored contacts linked to specific proteins or chromatin states.
Quick decision list
Chromatin interaction sequencing is now a core part of epigenomic sequencing and bioinformatics analysis. Yet many teams still ask the same question at the start of a 3D genomics project:
"For this system, should we run Hi-C, Micro-C, Capture Hi-C, or even HiChIP?"
The answer matters for several reasons:
A mismatch between method and question can produce technically sound data that still fails to resolve key regulatory mechanisms. This guide looks at Hi-C vs Micro-C vs Capture Hi-C, with HiChIP as a complementary option, from a decision-making perspective rather than as a purely technical protocol manual.
Hi-C, Micro-C, Capture Hi-C, and HiChIP all measure chromatin contacts, but they do so in different ways and with different biological emphasis.
In practice:
The rest of this article explains why these rules of thumb work, and how to translate them into solid study designs and appropriate epigenomic sequencing services.
Hi-C is a chromosome conformation capture method that turns spatial DNA contacts into paired reads. A typical in situ Hi-C workflow includes:
After alignment and binning, the project team obtains genome-wide contact maps.
Overview of a Hi-C experiment and data analysis workflow, from cross-linking and restriction digestion to read mapping, contact matrix generation and downstream identification of compartments, TADs and loops. (Kolovos P. et al. (2014) Epigenetics & Chromatin)
These support analysis of:
From a practical standpoint, Hi-C is the most established option, with many published protocols and analysis workflows. When we support Hi-C sequencing projects, most optimisation time goes into fixation conditions and restriction digestion, because they strongly affect library complexity and contact patterns.
Micro-C was developed to extend 3D genome mapping down to the nucleosome scale. Instead of restriction enzymes, it uses micrococcal nuclease (MNase) to digest chromatin into mono- or oligo-nucleosomes. The later steps—ligation, library construction, sequencing—are conceptually similar to Hi-C.
As a result, Micro-C:
However, MNase digestion is sensitive to chromatin state. In our experience, successful Micro-C projects always begin with careful MNase titration on a small batch of the same sample type. Over-digestion can remove informative fragments; under-digestion lowers effective resolution. Micro-C also typically requires higher sequencing depth than a basic Hi-C experiment to achieve usable signal at very fine bins.
Conceptual comparison of Micro-C and Hi-C, highlighting nucleosome-level fragmentation, reduced restriction site gaps and the resulting higher resolution chromatin contact maps across genomic regions. (Hsieh T.-H.S. et al. (2015) Genome Biology)
Capture Hi-C sits between global and highly targeted approaches. It:
This makes Capture Hi-C ideal when:
Overview of a Capture Hi-C experiment and CHiCAGO analysis pipeline, illustrating probe-based enrichment of promoter-anchored contacts and statistical modelling of significant DNA looping interactions. (Cairns J. et al. (2016) Genome Biology)
The design of capture probes is critical. We usually combine previous ATAC-seq, ChIP-seq, or DNA methylation data with gene annotations when helping clients build capture panels, then validate enrichment profiles on pilot libraries before committing to full-scale Capture Hi-C sequencing.
HiChIP is an anchor-based chromatin interaction assay. It effectively asks:
"What 3D contacts involve genomic regions bound by this protein or carrying this histone mark?"
Overview of the HiChIPdb resource, summarizing large-scale HiChIP data collection, unified processing, loop calling and functional annotation of protein-centric chromatin interactions across diverse cell types. (Zeng W. et al. (2023) Nucleic Acids Research)
In HiChIP:
HiChIP is not a direct alternative to Hi-C or Micro-C, but a complement. It does not provide a uniform view of all contacts, but rather of contacts associated with particular regulatory features. For instance, H3K27ac HiChIP can highlight active enhancer–promoter loops more efficiently than a promoter-based Capture Hi-C design in some contexts.
The table below summarises Hi-C vs Micro-C vs Capture Hi-C vs Hi-Chip in key practical dimensions. These are typical patterns rather than strict rules; specific protocols may differ.
| Feature | Hi-C | Micro-C | Capture Hi-C | HiChIP |
|---|---|---|---|---|
| Main readout | Genome-wide contact matrix | Genome-wide contact matrix | Contacts involving captured regions | Contacts anchored at a protein/histone mark |
| Typical resolution focus | Compartments, TADs, large loops | Loops and nucleosome-scale local structure | Promoter–enhancer and locus-specific contacts | Active or mark-specific regulatory contacts |
| Fragmentation strategy | Restriction enzyme | Micrococcal nuclease | Follows Hi-C plus capture probes | Similar to Hi-C plus immunoprecipitation |
| Relative sequencing depth need | Moderate to high | High, especially for very fine binning | Moderate overall, very dense in targets | Moderate; focused on immunoprecipitated regions |
| Typical starting material | Millions of cells or equivalent tissue | Similar or slightly higher | Follows Hi-C; depends on capture design | Similar to ChIP-seq plus Hi-C requirements |
| Main strengths | Global view, mature analysis ecosystem | High resolution, better short-range coverage | Cost-efficient focus on defined loci | Protein/mark-centred regulatory networks |
| Main limitations | Restriction bias, limited very fine detail | Protocol sensitive, depth-hungry | Limited to probe regions | Restricted to antibody-defined anchors |
For epigenomic sequencing services, this comparison often drives the first discussion:
Later sections show how these differences translate into concrete 3D genome study designs.
If your central question is "Does this perturbation change genome architecture at a global scale?", a Hi-C–centred design usually makes the most sense.
Typical goals in this category include:
A practical Hi-C study plan often includes:
At this stage, links to a Hi-C technology introduction, Hi-C data analysis: from basics to advanced techniques, and a 3D genome bioinformatics analysis service page can guide readers towards concrete workflows, reports, and example deliverables.
When the aim is to study promoter–enhancer loops and local rewiring, the trade-off becomes Global vs Focused: Micro-C vs Capture Hi-C vs HiChIP.
A useful rule of thumb is:
A sophisticated project may combine these approaches over time—first Micro-C or Hi-C for discovery, then Capture Hi-C or HiChIP for focused validation of selected regulatory hubs.
For GWAS-driven projects, the candidate non-coding regions are usually known, but the target genes and contact partners are not. In this scenario, Capture Hi-C is often the most efficient first choice.
A typical workflow is:
HiChIP can then complement this by focusing on interactions that specifically involve active or repressed states, depending on the histone mark or factor chosen. Integration of Capture Hi-C and HiChIP with regulatory network analysis services helps prioritise variant–gene pairs with consistent evidence across layers.
Many 3D genomics studies now use primary tissues, small patient-derived cohorts, or complex mixtures of cell types. These introduce constraints that affect method selection.
Practical points to consider:
From real project experience, sample quality and fixation are the most common early failure points.
Key lessons include:
These steps may feel slow, but they can often prevent entire batches of Hi-C, Micro-C, or HiChIP libraries from failing QC.
Well-designed 3D genome bioinformatics pipelines include early QC metrics that capture library quality before deep interpretation. Common ones are:
Projects that pay attention to these metrics usually avoid investing heavily in downstream analyses on suboptimal data. When we run Hi-C and Micro-C data processing, the QC report is often the first document a PI or project manager reviews before deciding on additional sequencing or replicate runs.
The meaning of contacts differs slightly by method:
Combining these outputs with other epigenomic sequencing services—ATAC-seq, ChIP-seq, DNA methylation mapping, RNA-seq—allows you to build multi-layer regulatory models that explain both 3D structure and functional readouts.
Micro-C often detects more short-range loops because of its higher resolution and more uniform fragmentation. However, it is not automatically the best option in every project. It requires careful MNase optimisation and typically higher sequencing depth. If your main questions concern compartments, TADs, or broad rearrangements, a well-designed Hi-C experiment can deliver the necessary insight in a more cost-effective way.
Most studies use at least two biological replicates per condition, and sometimes three or more for noisy systems or primary tissues. Two replicates provide a basic check on reproducibility of contact maps and loop calls. For subtle effects or complex models, additional replicates improve statistical power and help separate real rewiring from technical variability.
For mammalian genomes, many Hi-C projects use hundreds of millions of read pairs per sample, chosen to support the desired resolution (for example 50–100 kb bins). Micro-C often needs deeper sequencing to maintain signal at finer bins that resolve nucleosome-scale loops. Instead of focusing on a fixed number, it is better to define target bin sizes and features, then estimate depth together with a Hi-C or Micro-C data analysis service provider.
Capture Hi-C makes the most sense when you already have a defined set of regions—such as GWAS blocks, promoter lists, or enhancer clusters—and you want dense contacts around them. In that situation, increasing depth on whole-genome Hi-C may still leave those regions under-sampled, while Capture Hi-C concentrates reads where they matter most. If your question is exploratory and you do not yet know which regions to focus on, starting with Hi-C or Micro-C is usually more flexible.
Capture Hi-C enriches contacts involving specific genomic coordinates, regardless of which proteins bind there. HiChIP enriches contacts anchored by a particular histone mark or protein. If your question is primarily structural—"which genes contact these non-coding loci?"—Capture Hi-C is often the more straightforward choice. If you want to know "which 3D contacts are associated with active enhancers or a given transcription factor?", a mark- or protein-based HiChIP design is more appropriate. In practice, some teams run both, using HiChIP to highlight functionally active interactions within the structural network revealed by Capture Hi-C or Hi-C.
Choosing between Hi-C, Micro-C, Capture Hi-C and HiChIP is less about which protocol is trendiest and more about aligning each technique with your biological questions, sample constraints, and analysis capacity.
A focused planning process usually includes:
If you are shaping a new 3D genome project and want to move from high-level ideas to a concrete plan, you can:
With a clear view of Hi-C vs Micro-C vs Capture Hi-C vs Hi-Chip, you can make method choices that fit both your scientific goals and practical limits—and turn 3D genome mapping into actionable insight rather than an expensive experiment in the dark.
References
Terms & Conditions Privacy Policy Copyright © CD Genomics. All rights reserved.