Choosing a PacBio sequencing service really depends on what you’re trying to find out with your study. Are you trying to piece together a complicated genome, spot structural variants, or analyze full-length transcripts? The goal you have in mind influences everything—like what kind of reads you need, how much coverage, and what kind of analysis you'll do. Sure, HiFi reads can give you really accurate long-read data, but there’s no one-size-fits-all platform or service for every project. Little details matter a lot—like if your DNA sample is a bit degraded, it might limit how long your reads can be even before sequencing starts.
It’s a good idea to ask how the provider evaluates your samples, how they report quality, and what happens if something goes wrong or a library fails. Make sure to get clear info on what kind of input they require, what kind of yield you can expect, how long the turnaround usually takes, and what exactly is included in the price. A trustworthy service should walk you through their workflow and share some experience they have with similar types of samples. Also, check whether their bioinformatics support only covers basic quality checks or if it includes assembly, variant calling, and interpretation too—those are different levels of support. And don’t forget to clarify the data formats they deliver and if raw reads are part of the package. Comparing these details is way more important than just looking at the price tag.
A good provider is happy to answer practical questions and will be upfront about any limitations. Be wary of guarantees that ignore your sample quality or how complex your project is. It’s easy to get caught up in the accuracy of the reads and overlook things like storage needs, analysis time, or whether their staff has enough expertise. I’ve seen teams do much better in their planning when they have these conversations early—though I’ll admit it’s not a foolproof way to avoid surprises. There’s no perfect checklist here. Ultimately, the best choice is a service that aligns with your methods, communicates clearly, and delivers what you need—while being honest about any uncertainties along the way.
A sequencing plan should begin with the biological question, not a preferred read length. If the study needs to resolve complex regions, phase variants, or assemble genomes with repeated sequences, HiFi reads around 10–25 kb may provide useful context. A 10 kb read can suit many routine assembly tasks, while longer reads may span larger repeats or structural changes. Longer is not automatically better. DNA integrity, library preparation, and the sample itself can limit the read lengths actually recovered.
Before choosing a service, compare the expected read length with the size of the regions you need to interpret. For example, a repeat spanning 14 kb may be difficult to resolve if most reads are shorter than that region. Ask for the expected read-length distribution, not just a single target number, and confirm how much usable sequence is anticipated. Coverage matters too: a longer read set with too few reads may leave gaps. A small pilot can reveal whether DNA extracted from your tissue or sample type holds up during processing. I have seen planning focus too heavily on an ideal number; real samples can be less tidy. It is worth revisiting the plan after checking DNA quality and the analysis requirements.
When comparing a PacBio sequencing service, look beyond a headline accuracy figure. HiFi reads can exceed 99.9% accuracy, but that result depends on sample quality, library preparation, sequencing conditions, and analysis methods. Ask the provider how accuracy is measured and whether the reported value reflects read-level accuracy or a broader consensus result. The distinction matters when interpreting difficult regions or calling small variants.
Ask for quality-control details from a representative project. These might include read-length distributions, yield, coverage uniformity, and the proportion of reads that pass quality filters. For example, a high average accuracy may not compensate for uneven coverage across a GC-rich region. Requesting a sample report can show how these metrics are presented.
Small details count. Confirm whether the service flags low-input or degraded DNA before sequencing, and how it communicates limitations. I would not treat one threshold as a guarantee: even a careful workflow can produce uneven results, and that is worth discussing upfront.
A clear provider should explain the assumptions behind its figures and help match the required accuracy and coverage to the study’s specific questions.
Choosing a long-read sequencing service begins with sample scale, not instrument prestige. In project planning, I estimate genome size, ploidy, target coverage, and sample number. A high-output sequencing cell can produce up to 90 Gb of data, but that figure is a ceiling, not a promise. Actual yield depends on DNA quality, library preparation, loading, and run performance. Keep it practical.
For a 3 Gb diploid genome, 30x coverage requires roughly 90 Gb of usable data. One cell may suit one deeply covered sample, or several samples at lower coverage. A microbial genome needs far less output, so sharing a cell can reduce waste and cost. However, barcoding requires careful balancing. Uneven pooling may overrepresent one sample and weaken another. Small details matter.
Ask the provider for recent yield distributions, not only the best-case specification. Request read-quality thresholds, failed-library handling, raw-data delivery, and coverage uniformity. An experienced service team should model expected yield before accepting samples. I would also reserve capacity for repeats; perfect DNA rarely arrives. That assumption is uncomfortable, but realistic. If your project needs phased haplotypes, structural variants, or complete assembly, coverage depth alone is not enough. Read length, accuracy, and DNA integrity matter equally.
When choosing a PacBio sequencing service, define coverage before comparing prices. For de novo HiFi genome assemblies, many projects target 20× coverage or more. Coverage means total usable bases divided by the estimated genome size. A 3-gigabase genome therefore needs at least 60 gigabases of reliable sequence at 20×.
Twentyfold coverage is a useful baseline, not a universal guarantee. Heterozygous genomes, repeat-rich regions, polyploid samples, and uneven DNA quality can require deeper sequencing. In practice, a target of 25× to 30× may provide helpful breathing room. More data is not always better. Excessive coverage can increase cost without fixing poor DNA or biased libraries.
Ask the provider how coverage is calculated. Does it use raw output or quality-filtered reads? Request expected read accuracy, read-length distribution, usable yield, and possible duplication levels. Confirm the genome-size estimate, too. A small error there changes the real coverage substantially. Sample preparation matters. High-molecular-weight DNA, careful extraction, and limited fragmentation help preserve long, accurate reads. Poor input can quietly reduce assembly continuity.
A practical request might specify 30× planned output, with a minimum acceptable yield and clear quality thresholds. That wording is stronger than asking for “deep sequencing.” It also leaves room for honest review when the first estimate proves optimistic. I would revisit coverage after a pilot run, especially for an unfamiliar species. Twentyfold may work beautifully—or expose gaps that only additional, well-distributed reads can address.
How to Choose a PacBio Sequencing Service
Verify High-Molecular-Weight DNA and SMRTbell Library Preparation
A reliable sequencing service should examine your DNA before library construction. High-molecular-weight DNA preserves long fragments and improves read-length potential. Ask for concentration data from a fluorometric method, not absorbance alone. Purity ratios can reveal contamination, but they do not prove DNA integrity. Request an integrity assessment using pulsed-field gel electrophoresis or another validated fragment-analysis method. The electrophoresis image should show most DNA in a high-size range, with limited smearing. Handle samples gently. Repeated pipetting, vortexing, and unnecessary transfers can damage long molecules.
SMRTbell preparation requires controlled repair, end processing, adapter ligation, and cleanup. Ask how the laboratory confirms each stage. A prepared library should have measurable concentration, suitable fragment-size distribution, and minimal adapter-related artifacts. The service should also explain its size-selection method and recommended input amount. In my experience, missing pre-library records makes troubleshooting slower. I have also seen good DNA perform poorly after rushed handling. That is an imperfect reminder: extraction quality alone cannot guarantee library success.
Tips: Send enough DNA for testing and preparation repeats. Use low-binding tubes and wide-bore tips when appropriate. Confirm storage temperature and shipping conditions before dispatch. Ask for raw quality-control plots, not only a pass or fail statement. Keep sample labels consistent across extraction, library preparation, and sequencing. Clear documentation matters.
| Evaluation Dimension | What to Require | Recommended Acceptance Criteria | How to Verify Before Sequencing |
|---|---|---|---|
| Project Scope | A service plan matched to the intended application | Application-defined Whole-genome, targeted, transcriptome, amplicon, metagenome, or structural-variant projects should be planned separately because DNA input, library size, coverage, and analysis requirements differ. | Request a written workflow covering sample intake, extraction, library preparation, sequencing, quality control, data delivery, and analysis. |
| High-Molecular-Weight DNA | Intact DNA with limited fragmentation and degradation | DNA should show a high-molecular-weight profile, with the majority of material above approximately 20 kb for many long-read workflows. Larger DNA fragments may be preferred when very long reads are required. | Ask for an electropherogram or pulsed-field assessment, not only a standard fluorometric concentration result. Confirm whether degraded or sheared samples are re-extracted. |
| DNA Quantity | Sufficient DNA for the selected library protocol and repeat testing | The required amount depends on the library method and project design. A practical submission plan should include enough material for library preparation, quality-control measurements, and potential troubleshooting. | Obtain the exact minimum concentration, total mass, volume, and buffer requirements from the service laboratory before shipment. |
| DNA Purity | Low levels of contaminants that can inhibit enzymatic reactions | Typical screening targets are an A260/A280 ratio near 1.8 and an A260/A230 ratio generally near 2.0–2.2. Ratios are indicators rather than complete proof of suitability. | Request concentration by a fluorometric method, absorbance ratios, and information on residual salts, phenol, ethanol, detergents, EDTA, polysaccharides, and other extraction reagents. |
| DNA Extraction Method | An extraction process designed to preserve long DNA molecules | Gentle handling, limited vortexing, appropriate lysis, and low-shear purification are preferred. Extraction should be adapted to the sample type, including blood, tissue, plants, microorganisms, or environmental material. | Ask whether extraction is included, whether the laboratory has experience with the sample type, and whether an aliquot will be retained for repeat preparation. |
| Sample Identification | Traceable labeling and chain-of-custody controls | Each sample should have a unique identifier, species or material description, extraction date, concentration, volume, and relevant biological metadata. | Confirm barcode or naming rules, acceptance documentation, storage conditions, shipping temperature, and procedures for resolving mismatched or insufficient samples. |
| SMRTbell Library Preparation | A documented workflow for converting HMW DNA into sequencing-ready libraries | The process should address DNA damage repair, end repair, adapter ligation, cleanup, size selection when applicable, and removal of short or unligated products. | Request the library-preparation method version, input requirements, expected library size range, cleanup approach, and criteria for repeating a failed preparation. |
| Library Size Selection | A size-selection strategy appropriate for the desired read length | Size selection can enrich longer DNA molecules but may reduce yield. It should be chosen according to genome complexity, target read length, and the sequencing platform configuration. | Ask whether the library is size-selected, which approximate size range is targeted, and how the laboratory balances read length against library recovery. |
| Library QC | Quality checks performed after SMRTbell preparation | QC should include library concentration, fragment-size distribution, and evidence that the library is suitable for sequencing. A library yield alone is not sufficient. | Request representative post-library-preparation QC results, including concentration method, electropherogram or sizing data, and the laboratory's pass/fail criteria. |
| Sequencing Configuration | A run design consistent with the required accuracy, read length, and throughput | Confirm instrument configuration, movie time or run duration, loading strategy, number of cells or consumables, and whether sequencing is performed in a multiplexed or dedicated format. | Request an estimated yield range, expected read-quality metrics, and an explanation of how the design supports the requested coverage or target depth. |
| Coverage Planning | Coverage calculated from genome size, ploidy, sample complexity, and project goals | Coverage should be specified as a target rather than inferred only from the number of reads. De novo assembly, variant detection, haplotyping, and transcript analysis may require different depths. | Ask for the coverage formula, expected data yield, allowance for filtering, and the policy if the delivered data do not meet the agreed target. |
| Data Quality Metrics | A standardized post-run QC report | The report should include total bases, read count, read-length distribution, read-quality distribution, N50 or equivalent length statistics where relevant, and usable data after filtering. | Confirm which metrics are delivered, how they are calculated, and whether raw, subread, circular-consensus, or other processed data are included. |
| Analysis and Deliverables | Clearly defined files and analysis responsibilities | Possible deliverables include raw sequencing files, quality reports, demultiplexed data, assembled genomes, variant calls, transcript isoforms, or other application-specific results. | Request a file-format list, delivery method, retention period, analysis pipeline versions, reference databases, and whether intermediate files are available. |
| Turnaround and Communication | A timeline that separates sample QC, library preparation, sequencing, and analysis | The schedule should identify dependencies, possible rework, batching, instrument availability, data transfer, and review of failed QC checkpoints. | Ask for milestone dates, status-update frequency, escalation contacts, and the process for approving additional work or replacement sequencing. |
| Risk Management | A documented response to failed sample or library QC | The service should define whether it will re-clean, re-extract, remake the library, resequence, or return the sample, together with any additional charges and material requirements. | Review the acceptance policy and confirm who bears responsibility when failure is caused by sample quality, preparation, instrument performance, contamination, or insufficient yield. |
Choosing a long-read sequencing service requires more than comparing prices. Request provider-level QC, not averaged marketing figures. Q30 means a base-call error rate of 0.1%, or 99.9% accuracy. Q40 improves that to 0.01%. The NIST Genome in a Bottle benchmarking work uses these quality thresholds when evaluating variant-calling performance. Ask for the percentage of HiFi reads above Q30, read-length N50, yield, and pass-rate distribution from your own project type.
Look for evidence from each run. A useful report should show read-length histograms, per-sample yield, loading performance, and failed-library rates. HiFi datasets often target approximately 15–25 kb reads, but extraction quality can reduce this sharply. The Human Pangenome Reference Consortium’s 2023 Nature report demonstrated the value of highly accurate long-read assemblies across 47 diverse haplotypes. That finding supports checking coverage uniformity, not only total gigabases. Ask whether difficult regions, GC extremes, or repeat-rich loci are reported separately.
Data delivery can quietly create delays. Confirm delivery formats, metadata, checksums, transfer security, and retention periods before purchase. Request raw subreads, circular-consensus reads, and analysis-ready files when appropriate. I would not accept “Q30 guaranteed” without the denominator, because a small high-quality subset can distort the impression. Ask for historical QC examples. Small details matter. One weak point remains: provider reports may omit failed libraries, so compare promised yield with delivered yield and record every exception. Sources: NIST Genome in a Bottle benchmarking resources, 2023; Human Pangenome Reference Consortium, Nature, 2023.
Yes, they can exceed 99.9% under suitable conditions. Results depend on DNA quality, library preparation, sequencing, and analysis.
No. Ask whether the figure describes individual reads or a consensus result. These measurements answer different questions.
Request read-length distributions, total yield, coverage uniformity, and the percentage of reads passing quality filters. A sample report helps.
High accuracy may hide uneven coverage in difficult regions, including GC-rich sequences. Small gaps can still affect variant analysis.
Use fluorometric concentration testing and validated fragment analysis. Purity ratios alone cannot confirm DNA integrity.
Most DNA should appear in a high-size range, with limited smearing on an electrophoresis image. Smearing may suggest degradation.
Ask about DNA repair, end processing, adapter ligation, cleanup, concentration, fragment size, and possible adapter-related artifacts.
Repeated pipetting, vortexing, and unnecessary transfers can break long DNA molecules. Use gentle handling and low-binding tubes.
Confirm storage temperature, shipping conditions, sample volume, and possible preparation repeats. Labels must remain consistent.
No. Even careful workflows can produce uneven results. I would treat the threshold as guidance, not certainty.
Choosing a Pacbio Sequencing service begins with clearly defining your study goals and the expected HiFi read length, which is often between 10 and 25 kb. Consider the accuracy required for your project, as high-quality HiFi reads can exceed 99.9% accuracy and support reliable variant detection, genome assembly, and complex genomic analysis.
Next, match sequencing capacity to your sample scale and establish an appropriate coverage target. De novo HiFi assemblies commonly require 20× coverage or more, depending on genome size and complexity. Confirm that your provider can handle high-molecular-weight DNA and offers dependable SMRTbell library preparation. Finally, compare quality-control procedures, reporting standards, and data-delivery options. Important metrics include read quality, yield, read-length distribution, and Q30 HiFi read performance, all of which help ensure that the final data are suitable for your intended analysis.