DNA_CHECKS
Menu

Beta report workflow

Upload DNA

Check your raw DNA file locally, review the report scope, complete the £3 Stripe checkout, then securely submit the file for DNA_CHECKS processing.

The current beta accepts AncestryDNA raw DNA .txt files and MyHeritage raw DNA .csv files. Provider detection is automatic from the file contents. Your file is checked locally before payment. After Stripe returns you to this page, you will reselect the same file for secure upload.

Current inputsAncestryDNA · MyHeritage
Beta report£3 one-off
PaymentStripe
Raw DNADeleted after processing

Step 01

Choose your raw DNA file

Select the file you downloaded from your DNA provider. DNA_CHECKS first inspects basic file characteristics locally in your browser.

AncestryDNARaw DNA .txt
MyHeritageRaw DNA .csv
Pre-paymentLocal browser check only

Step 02

Local file check

DNA_CHECKS checks whether the selected file looks compatible before asking you to continue.

Waiting for a file

Choose a file above to begin local validation.

—
Supported file type

AncestryDNA TXT or MyHeritage CSV.

—
Reasonable file size

Rejects empty or unexpectedly large files.

—
Genotype structure

Text files are checked for genotype-table fields and rsID-style markers.

Using a MyHeritage download?

MyHeritage downloads its raw DNA data as a ZIP file. Extract the ZIP first, then upload the CSV inside. DNA_CHECKS does not currently accept ZIP uploads.

Step 03

Report details

Review what the beta report includes and provide the email address used for essential report communication.

IncludedOrigins & History
IncludedGenetic Curiosities
IncludedImportant Clinical Findings
IncludedMedication & Pharmacogenomics

Used for report delivery and essential job communication. No marketing subscription is created.

Step 05

£3 Stripe checkout

Payment is the gate that authorises the secure DNA upload job. Checkout is handled securely by Stripe.

Beta report£3one-off

Stripe Checkout

Ready for checkout

Your DNA file has not been uploaded. Stripe will process the checkout first.

Why reselect the file after payment?

Browsers intentionally do not preserve access to a local file through an external payment redirect. After Stripe returns, DNA_CHECKS asks you to select the same file again before it is uploaded.

Step 06

Secure upload & processing

After payment confirmation, reselect the same DNA file and DNA_CHECKS will submit it for temporary processing.

○
Payment confirmedStripe confirms your checkout.
○
File receivedEncrypted upload reaches temporary R2 storage.
○
DNA file recognisedThe job is queued for DNA_CHECKS processing.
○
DNA analysis & report generation
The local DNA_CHECKS worker runs the scientific pipeline and builds the HTML report.
○
Report generatedThe finished HTML report is returned for temporary delivery.
○
Raw DNA deletedThe temporary raw upload has been deleted.

Before uploading

Want to inspect the report first?

The public example uses the same report structure without containing personal genetic data.

Preview ReportRead the FAQ →