Cited by 135DNA and Biological ComputingAdvanced Data Storage TechnologiesAdvanced biosensing and bioanalysis techniques

The DOI matches its Crossref record; 21 of the 21 references it cites were found in a registry or an index; 1 of the 13 sources its claims cite were checked for support.

Probing the physical limits of reliable DNA data retrieval.

Open access
Organick, Lee, Chen, Yuan-Jyue, Dumas Ang, Siena, Lopez, Randolph, Liu, Xiaomeng, Strauss, Karin, Ceze, Luis·2020·Nature Communications

Abstract

Synthetic DNA is gaining momentum as a potential storage medium for archival data storage. In this process, digital information is translated into sequences of nucleotides and the resulting synthetic DNA strands are then stored for later retrieval. Here, we demonstrate reliable file recovery with PCR-based random access when as few as ten copies per sequence are stored, on average. This results in density of about 17 exabytes/gram, nearly two orders of magnitude greater than prior work has shown. We successfully retrieve the same data in a complex pool of over 10 10 unique sequences per microliter with no evidence that we have begun to approach complexity limits. Finally, we also investigate the effects of file size and sequencing coverage on successful file retrieval and look for systematic DNA strand drop out. These findings substantiate the robustness and high data density of the process examined here.

Overview

AI snapshot

Written from the paper’s full text.

TL;DR

PCR-based random access recovered three DNA-encoded files reliably when each sequence was present at an average of only 10 copies, yielding a density of about 17 EB g−1. The same data were retrieved from pools with over 10^10 unique sequences per microliter, with no evidence that the complexity limit had been reached.

Key findings

  • Successful file recovery with no bit errors required an average of 10 copies per sequence (SD 3), regardless of file size or pool complexity; the files encoded 0.1 KB (2,042 sequences), 1.7 KB (26,404 sequences), and 18 KB (271,447 sequences).
  • The demonstrated density was 17 EB g−1, nearly two orders of magnitude greater than prior work; with 15% logical redundancy the maximum estimated density was 38 EB g−1, and with 50% logical redundancy it was 124 EB g−1, ignoring other errors.
  • No distinguishable difference in sequence loss was found between water-diluted and 150 Nmer-diluted complex pools; for the large file, only three samples differed, with a mean difference of 0.98% missing sequences (SD 1.82%).
  • Increasing sequencing coverage from 20× to 200× reduced missing sequences by only 1.8% on average (SD 1.1%); samples successfully recovered at the lowest copy number had mean sequencing coverage of 35× (SD 11×).

Methods

  • Three files were randomly accessed from a DNA pool encoding nine files (1.6 M total oligonucleotides), then serially diluted either in water or in 1 ng μL−1 150 Nmers to raise complexity from 1.6 × 10^6 to over 10^10 unique sequences per microliter.
  • Copy numbers were measured by triplicate qPCR; for small and medium files, diluted-sample copy numbers were calculated using the large file’s dilution factors because of amplification-efficiency differences.
  • Sequencing data were randomly sub-sampled with replacement to 20× coverage 100 times per file per sample to estimate missing sequences; sequence loss was modeled with power regressions (R² 0.90–0.98).

Limitations

  • The paper states that appropriate logical and physical redundancy depends on the specific DNA data storage workflow, since synthesis, sequencing, and wet-protocol errors can affect sequence recovery.
  • The paper states that only one of the two dilution series was sequenced, and that small and medium file copy numbers for diluted samples were inferred from the large file’s dilution factors rather than measured directly by qPCR.
  • The paper states that maximum density estimates of 38 and 124 EB g−1 ignore all other errors such as insertions, deletions, and substitutions; it also notes that increasing sequencing coverage is useful only as a last resort because of cost.
  • No dedicated limitations section is present; the above are limitations stated in the text, not an external critique.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1038/s41467-020-14319-8

Cites

21 of 21 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Fig. 1 Experiment overview. a A high-level representation of the DNA data storage pipeline. b (Left) The bar chart depicts contents of the initial, undiluted pool. (Right) The illustration shows the serial nature of subsequent dilutions. Mean copy number refers to the mean number of copies of each file's unique sequences as determined by qPCR (Supplementary Note 1). One serial dilution used water as the diluent in each step; the other used a solution of 150 Nmers to dilute the pool to much greater complexity. c Details of how the samples were diluted. Note that the dilution steps were identical regardless of diluent. The smallest percent of pool accessed is calculated by dividing the size of the smallest file by the number of unique sequences in the 1 μL of solution used for PCR random access. This percentage refers to the 150 Nmer diluent pool since the small file in the water diluent pool is a constant 0.13%.
Fig. 1 Experiment overview. a A high-level representation of the DNA data storage pipeline. b (Left) The bar chart depicts contents of the initial, undiluted pool. (Right) The illustration shows the serial nature of subsequent dilutions. Mean copy number refers to the mean number of copies of each file's unique sequences as determined by qPCR (Supplementary Note 1). One serial dilution used water as the diluent in each step; the other used a solution of 150 Nmers to dilute the pool to much greater complexity. c Details of how the samples were diluted. Note that the dilution steps were identical regardless of diluent. The smallest percent of pool accessed is calculated by dividing the size of the smallest file by the number of unique sequences in the 1 μL of solution used for PCR random access. This percentage refers to the 150 Nmer diluent pool since the small file in the water diluent pool is a constant 0.13%.CC BY · PubMed Central
Fig. 2 Examining sequence loss behavior. a Each plot illustrates a file's loss of sequences recovered at 20× coverage, directly comparing the samples diluted in water to those diluted in 150 Nmers (150nt sequences comprised of random nucleotides). The threshold of the maximum number of sequences that can be lost while still permitting file recovery is plotted for reference, as determined by previous work10. Error bars represent 95% confidence intervals; x-axis errors are taken from triplicate qPCR data (see Methods), and y-axis errors are the result of 100 simulations of the original sequencing data sub-sampled to 20× sequencing coverage (see Methods). b Each plot illustrates behavioral similarities for each file in each diluent condition, with a power regression overlayed (see Supplementary Note 4). The data used here are also sub-sampled to a sequencing coverage of 20×.
Fig. 2 Examining sequence loss behavior. a Each plot illustrates a file's loss of sequences recovered at 20× coverage, directly comparing the samples diluted in water to those diluted in 150 Nmers (150nt sequences comprised of random nucleotides). The threshold of the maximum number of sequences that can be lost while still permitting file recovery is plotted for reference, as determined by previous work10. Error bars represent 95% confidence intervals; x-axis errors are taken from triplicate qPCR data (see Methods), and y-axis errors are the result of 100 simulations of the original sequencing data sub-sampled to 20× sequencing coverage (see Methods). b Each plot illustrates behavioral similarities for each file in each diluent condition, with a power regression overlayed (see Supplementary Note 4). The data used here are also sub-sampled to a sequencing coverage of 20×.CC BY · PubMed Central
Fig. 3 Examining file recovery, sequencing coverage, and sequence loss behavior. a The limit of successful, no bit error decoding is shown with the gray bar in each graph. Data points below the gray bar are samples where the file was successfully decoded and recovered with no bit errors. Done post-sequencing, decoding involves clustering sequences, finding consensus, then correcting errors10. A more detailed view of this data including exact copy number and sequencing coverage is in Supplementary Note 7. b For the small file, when each sample diluted in water was sequenced at greater depth, minimal improvement on the proportion of missing sequences occurred. The 100× coverage data were found by sub-sampling the data used to create the 200× coverage data. c Missing sequences are compared between the initial pool prior to any dilutions where the mean copy number was 194 (in red) and the last dilution where the mean copy number was <1 (in blue). Note the different total number of sequences in the small (2042), medium (26,404), and large (271,447) files. The fact that some sequences are missing only from the initial pool but “reappear” in the final dilution suggests that the lost sequences are a result of stochastic variation that occurs during sub-sampling for file recovery, rather than irretrievably lost due to some property of the sequence. This pattern of sequences reappearing in subsequent dilutions is shown for every dilution step in Supplementary Note 6. Note that for a, b, x-axis and y-axis error bars represent 95% confidence intervals; x-axis errors are taken from triplicate qPCR data (see Methods), and y-axis errors are the result of 100 simulations of the original sequencing data sub-sampled to 20× sequencing coverage (see Methods).
Fig. 3 Examining file recovery, sequencing coverage, and sequence loss behavior. a The limit of successful, no bit error decoding is shown with the gray bar in each graph. Data points below the gray bar are samples where the file was successfully decoded and recovered with no bit errors. Done post-sequencing, decoding involves clustering sequences, finding consensus, then correcting errors10. A more detailed view of this data including exact copy number and sequencing coverage is in Supplementary Note 7. b For the small file, when each sample diluted in water was sequenced at greater depth, minimal improvement on the proportion of missing sequences occurred. The 100× coverage data were found by sub-sampling the data used to create the 200× coverage data. c Missing sequences are compared between the initial pool prior to any dilutions where the mean copy number was 194 (in red) and the last dilution where the mean copy number was <1 (in blue). Note the different total number of sequences in the small (2042), medium (26,404), and large (271,447) files. The fact that some sequences are missing only from the initial pool but “reappear” in the final dilution suggests that the lost sequences are a result of stochastic variation that occurs during sub-sampling for file recovery, rather than irretrievably lost due to some property of the sequence. This pattern of sequences reappearing in subsequent dilutions is shown for every dilution step in Supplementary Note 6. Note that for a, b, x-axis and y-axis error bars represent 95% confidence intervals; x-axis errors are taken from triplicate qPCR data (see Methods), and y-axis errors are the result of 100 simulations of the original sequencing data sub-sampled to 20× sequencing coverage (see Methods).CC BY · PubMed Central

Verification

Claims the paper makes

18 Own interpretation · 12 Not checked yet · 12 Own result · 3 No basis given · 1 Partly supported · accuracy not yet measured

Verify all 12 references — free account

Show all 24 claims

  • It may state two separate claims as one. 14
  • Probably not a substantial claim. 11
22 of 22

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 21 references

Cited by

Sorted by citations

Items 101–134 of 134

Metadata

Authors
Organick, L., Chen, Y.-J., Dumas Ang, S., Lopez, R., Liu, X., Strauss, K., & Ceze, L.
Affiliations
  • University of Washington (US)
  • Microsoft (United States) (US)
Corresponding author
  • Organick, Lee
  • Strauss, Karin
Venue
Nature Communications
Published
2020-01-30
Volume
11
Issue
1
Pages
616-616
ISSN
2041-1723 (ISSN-L)
OpenAlex
W3003918453
Cited by
135
References
21
Citations by year
2026: 25 · 2025: 20 · 2024: 24 · 2023: 13 · 2022: 16 · 2021: 26 · 2020: 11
FWCI
5.35
Type
journal article
Language
en
Open access
Locations
  • Nature Communications (publishedVersion, cc-by)
  • PubMed Central (publishedVersion, cc-by)
  • PubMed (publishedVersion)
  • RePEc: Research Papers in Economics (submittedVersion)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion)
Funders
  • Microsoft
  • United States Department of Defense | Defense Advanced Research Projects Agency
Topics
  • Physical Sciences › Mathematics › Theoretical Computer Science › DNA and Biological Computing
  • Physical Sciences › Computer Science › Computer Networks and Communications › Advanced Data Storage Technologies
  • Life Sciences › Biochemistry, Genetics and Molecular Biology › Molecular Biology › Advanced biosensing and bioanalysis techniques
Keywords
DNA data storage, synthetic DNA, data archiving, file recovery, data density, sequencing depth, nucleotide sequence
MeSH terms
Base Sequence, DNA, Genetic Engineering, Information Science, Information Storage and Retrieval, Gene Dosage, Databases, Nucleic Acid, High-Throughput Nucleotide Sequencing

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

A language model drew the claims from the paper on 2026-10-09, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-10-09 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Cited sources are checked with a language model’s help (gpt-6-sol).

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review