• Home
• Resource
• Micro-C Sequencing Depth and Resolution Guide for High-Resolution Chromatin Mapping

Key takeaways

• Micro-C sequencing depth sets the ceiling on what you can interpret, but the "usable" part is the number of informative, unique contacts after filtering and deduplication.
• Micro-C resolution typically depends on contact density, library complexity, and your biological question, not on a universal read-count target.
• Higher depth is not always better: if sample quality or library complexity is limiting, deeper sequencing can turn into more duplicates instead of more information.
• For promoter-scale biology, consider whether targeted strategies (e.g., capture-based approaches) are a better match than pushing genome-wide Micro-C to the deepest possible depth.

Introduction

If you're planning Micro-C Sequencing, you're usually trying to answer three practical questions:

1. How much Micro-C sequencing depth is required?
2. What resolution can you realistically achieve?
3. Is higher depth always better?

Here's the direct answer: Micro-C sequencing depth helps when it increases the number of informative contacts supporting the bin size and features you need to interpret (domains, loops, or fine regulatory interactions). But the depth you need typically depends on sample complexity, genome size, and the specific structures you are trying to resolve.

Just as important, higher depth is not always better. Once duplication rises, or library complexity is exhausted, extra sequencing mainly buys redundant reads.

Based on our experience supporting chromatin interaction studies, researchers often need to balance sequencing depth, expected resolution, biological questions, and project resources before initiating Micro-C experiments.

In this guide, we'll frame "depth vs resolution" the way you have to handle it in real project design: as a set of trade-offs, QC gates, and decision points that help you get interpretable maps rather than expensive noise.

Why Sequencing Depth Matters in Micro-C Studies

Micro-C is often chosen when the biological question lives at fine scales: short-range loops, promoter-proximal contacts, or nucleosome-level organization. But even with Micro-C's small fragment sizes, the map you can interpret is limited by the number of informative contacts you recover.

In practice, Micro-C resolution typically depends on:

• Number of informative contacts (usable unique contacts after filtering)
• Sequencing coverage (how much contact-supporting data you obtain)
• Sample and library complexity (how many distinct molecules exist to be sequenced)
• Genome size (a larger genome spreads contacts over more possible bins)

A useful mental model is to separate:

• Raw reads (what the sequencer outputs), from
• Usable contacts (what supports your contact matrix after mapping, filtering, and deduplication).

Depth only improves resolution if it raises the second number.

This guide is written for researchers planning Micro-C as part of a broader program of chromatin interaction analysis—where the output has to be interpretable, reproducible, and aligned with a specific biological question.

The Relationship Between Micro-C Sequencing Depth and Resolution

The cleanest way to think about Micro-C sequencing depth is as a lever that increases contact density, which can enable smaller bins and more confident feature calling.

• Low depth tends to produce sparse matrices. You may still see large-scale structure, but fine-scale loops become unreliable.
• Moderate depth increases informative contacts and stabilizes domain-level interpretation.
• High depth can support finer binning and more confident detection of loop-scale features, assuming the library remains complex.

Relationship between Micro-C sequencing depth and chromatin interaction resolution.

Why "resolution" is not a single number

A common misunderstanding is to treat Micro-C resolution as a fixed property of the method.

In reality, resolution is usually defined operationally as the smallest bin size that is sufficiently supported by contact counts across the genome. One operational definition used in the literature links resolution to whether most bins meet a minimum contact threshold (for example, the smallest bin size such that a high fraction of bins have at least a certain number of contacts) (see discussion summarized in Overcoming artificial structures in resolution-enhanced Hi-C data (2024)).

For planning, you don't need to adopt a single metric. You need to decide what "resolution" means for your biology:

• Compartment and TAD-scale conclusions tolerate coarser bins.
• Loop interpretation needs finer bins and stronger local signal.
• Promoter-scale and enhancer-scale questions can require both fine binning and robust feature calling.

What the literature supports (and what it doesn't)

Peer-reviewed Micro-C work establishes that Micro-C can reach nucleosome-level folding maps because MNase digestion produces nucleosome-scale fragments, enabling access to fine structure that restriction enzyme Hi-C cannot (see Hsieh et al., Cell (2015)).

However, published "depth required for X resolution" numbers are system- and analysis-dependent. For example, a comparative evaluation in prostate cancer cells reported that extremely deep Micro-C data were needed to support loop detection at 1 kb binning in that specific setting (see Lee et al., Epigenetics & Chromatin (2022/2023)).

The planning implication is not that every project must match that depth. It's that fine bins are expensive in contact space, and you should decide whether you need them.

Factors That Influence Micro-C Data Quality Beyond Sequencing Depth

If a Micro-C project underperforms, it is often because the experiment was treated like a simple "buy more depth" problem.

Depth matters, but it is rarely the only bottleneck.

1) Sample quality

Micro-C is sensitive to the condition of the chromatin going into the workflow.

Key considerations include:

• Chromatin integrity (intact nuclei and consistent handling)
• Sample preparation (conditions that preserve crosslinked contacts and avoid degradation)

When sample integrity is compromised, you can end up with a library that produces reads but does not preserve interpretable structure at the scales you care about.

2) Library complexity

Library complexity is the practical ceiling on how much benefit you can get from additional sequencing.

A high-level way to think about it:

• If the library contains many distinct ligation products, deeper sequencing can reveal more unique contacts.
• If the library is low complexity, deeper sequencing increasingly produces duplicates.

This is why, in planning, depth should be paired with a strategy for monitoring complexity and duplication, not treated as an afterthought.

3) Biological replication

If your objective includes comparing conditions (treatment vs control, perturbation vs wild type), replication is a first-class design variable.

Sequencing a single sample to extreme depth can produce a visually dense map, but it does not substitute for biological replication when the question is about reproducible differences.

Designing a Micro-C Experiment Based on Research Objectives

This section translates "depth and resolution" into study design decisions.

Scenario 1: Genome architecture studies

If the project focus is genome architecture—for example compartments and TADs—you are usually optimizing for:

• Robust domain-level interpretation
• Consistent global structure
• Reproducibility across replicates and conditions

In this scenario, pushing for the smallest possible bin is often unnecessary. A depth plan should be chosen to support stable domain calling and reliable comparisons.

Scenario 2: Fine-scale chromatin looping

If the focus is fine-scale chromatin looping, the biology often requires:

• Strong local enrichment at loop anchors
• Fine binning near candidate loci
• Loop-calling methods that perform well at your data sparsity level

This is where Micro-C sequencing depth becomes a more dominant driver, but it still competes with library complexity and QC.

If your hypothesis is specifically about a Promoter-enhancer interaction, it's worth considering whether a targeted approach is more efficient than exhausting the genome-wide contact space. In many programs, promoter-focused strategies such as promoter capture Hi-C are used to concentrate contact support on promoter-centered questions (see Promoter Capture Hi-C Service).

Scenario 3: Mechanistic studies

Mechanistic studies often focus on:

• Specific chromatin structures
• Known loci or a constrained genomic region
• Integration with orthogonal assays (e.g., ChIP-seq, ATAC-seq, RNA-seq)

Here, the depth decision is usually tied to what you must show convincingly at the locus level, and what analysis outputs will be considered "evidence" for your mechanism.

Micro-C Data Analysis and Quality Assessment

Practical Planning Framework: From Biological Goal to Depth and Resolution

Use this quick framework to translate your question into an actionable depth plan.

Step 1: Define the feature you must interpret

• Compartments / TADs (genome architecture): prioritize robust global structure and replicate consistency.
• Loops / stripes (fine-scale features): prioritize local contact density and stable loop calling.
• Promoter-anchored questions at known loci: consider whether targeted strategies (e.g., capture-based approaches) will be more efficient than pushing genome-wide depth.

Step 2: Decide what "resolution" means for your analysis

In practice, resolution is the smallest bin size that has enough contact support to produce stable patterns and reproducible feature calls.

Step 3: Use QC to decide whether deeper sequencing will help

Deeper sequencing is most helpful when it increases unique contacts (valid interaction pairs) without a steep rise in duplication.

Step 4: A practical checklist (copy/paste)

• What feature(s) do we need to call (TADs, loops, promoter-enhancer contacts)?
• What bin size(s) will we evaluate in the first pass?
• What are the QC gates for: valid pairs, duplication/complexity trend, and matrix sparsity?
• Do we need more depth, a better library, more replicates, or a targeted design?

Micro-C sequencing depth is only useful if the analysis workflow can turn raw reads into reviewable structural outputs.

A typical analysis workflow includes:

1. Raw sequencing QC
2. Read mapping
3. Contact matrix generation
4. Resolution assessment
5. Loop/TAD analysis

A credible analysis plan also defines QC gates early, so you can tell whether deeper sequencing is likely to help.

Instead of relying on a single "read-count target," evaluate whether your data are becoming more informative as depth increases. Practical QC signals to include in your report are:

• Valid interaction pairs (unique contacts) after filtering/deduplication (the key denominator for resolution)
• Duplication rate / library complexity trend vs. depth (look for saturation: more reads → mostly duplicates)
• Cis/trans balance and distance-dependent decay (sanity checks for expected interaction patterns)
• Mapping and filtering breakdown (e.g., mapped reads, valid pairs, removed artifacts)
• Resolution support summary: for each candidate bin size, whether contact density is sufficient for your planned analysis (domains vs. loops)

If your QC indicates early saturation (rapidly rising duplicates with minimal gain in unique contacts), improving the library or changing strategy is usually more effective than sequencing deeper.

When evaluating a service provider or an internal pipeline, ask whether the QC report includes (at minimum) categories like:

• Sequencing quality (read quality and adapter/ligation artifact checks)
• Mapping statistics (alignment behavior and filtering)
• Valid interaction pairs (usable contacts after filtering and deduplication)
• Resolution assessment (what bin sizes are supported by contact density for the intended analysis)

Micro-C Deliverables From a Research Service Provider

For a Micro-C project to be reusable and publishable, deliverables should support both transparency and downstream analysis.

Typical deliverables include:

• Raw sequencing files
• Processed contact matrices
• Interaction maps
• Genome architecture analysis results
• QC report

If your goal is fast iteration (pilot → refine → full run), deliverables should also make it easy to compare libraries and conditions without re-running the entire pipeline from scratch.

Frequently Asked Questions

How much sequencing depth is needed for Micro-C?

It depends on genome size, your research objective, and the resolution you need to interpret with confidence. A practical way to plan is to define the feature you need to call (domains vs loops vs fine regulatory interactions), then work backward to the bin size and contact density needed to support that call.

Does higher Micro-C sequencing depth always improve resolution?

Not always. If sample quality is limiting or the library has low complexity, additional sequencing can return more duplicates rather than more informative contacts. Biological design also matters: a single ultra-deep sample does not replace well-matched biological replicates when you need reproducible comparisons.

What resolution can Micro-C achieve?

Micro-C can access very fine-scale chromatin folding because it fragments chromatin to nucleosome-scale units (see Hsieh et al., Cell (2015)). In practice, the resolution you can interpret typically depends on sequencing depth, library complexity, genome size, and the analysis strategy.

For mammalian systems, Micro-C maps have been used to reveal fine-scale features such as dots/loops and stripes in high-resolution contact maps (see Krietenstein et al., Molecular Cell (2020)).

Is Micro-C suitable for promoter-enhancer interaction studies?

Yes, Micro-C can be used for high-resolution chromatin interaction studies, including promoter-proximal regulatory questions. That said, if your primary question is specifically about promoter-centered contacts, a targeted workflow may be more efficient than pushing genome-wide Micro-C depth. You can also consider promoter-focused strategies such as promoter capture Hi-C (see Promoter Capture Hi-C Service).

Conclusion

Micro-C sequencing depth is best treated as a planning variable: it influences how many informative contacts you recover and therefore what bin sizes and structural features you can interpret.

Researchers should define biological objectives first and then determine appropriate Micro-C sequencing depth and analytical strategy.

If you are planning genome-wide Micro-C, a good first step is to confirm how the project will be evaluated: which features must be detected, which bin sizes must be supported, and which QC gates will be used to decide whether deeper sequencing is likely to help.

If you'd like feedback on your study design, prepare the following and discuss with CD Genomics scientists:

• organism/genome size and sample type
• primary features to interpret (TADs vs. loops vs. promoter-anchored questions)
• planned replication strategy
• any constraints on input amount and sequencing budget

Research Use Only (RUO). This content is for research planning and does not constitute medical advice.

Last updated: 2026-07-22

---