Ves al contingut principal

Aquest contingut encara no està disponible en català. El mostrem en anglès.

Equip DNA Info Lab · Revisió editorial · · 8 min de lectura

How to Read Your MyHeritage Raw DNA Data: Formats, WGS and Compatibility

Start with the header and column names in your original MyHeritage export. Identify the separator, genome build and genotype fields before reading a row. A standard marker file and a CRAM sequencing file need different tools; the label “WGS” alone does not establish compatibility.

1. Keep the original download and inspect the header

A raw DNA file is data behind a report, not a report written in another language. To obtain it, follow our MyHeritage download guide or the provider’s current instructions. Keep the original download unchanged and work on a copy. Do not substitute an ethnicity screenshot or a PDF.

  1. Open a copy in a plain-text editor. A spreadsheet can change identifiers or values when you save it again.
  2. Read the comment lines and column header. Note any declared processing method, genome build and strand. If a field is missing, record it as unknown.
  3. Look at the actual separator: commas and tabs are different. The extension alone does not tell you the layout or whether a tool can read it.

2. Read the genotype on the same row as its rsID

An rsID identifies a variant record. The chromosome and position locate it in a particular genome build. RESULT, or the two allele columns together, contains the recorded genotype. AG describes the two reported alleles at that marker; their order does not by itself identify which parent contributed each one: MyHeritage’s help says the two alleles represent the paternal and maternal sides, “not necessarily in this order”.

Synthetic examples, not personal results. The following tables illustrate the two CSV layouts supported by DNA Info Lab. Positions are GRCh37. These tables are not a promise that every MyHeritage export uses this structure. The first layout joins the alleles in RESULT:

RSIDCHROMOSOMEPOSITIONRESULT
rs49882352136608646AG
rs1801133111856378--

The other supported CSV layout separates ALLELE1 and ALLELE2. Read both columns. In an actual CSV, cells are separated by commas and may be surrounded by double quotes:

RSIDCHROMOSOMEPOSITIONALLELE1ALLELE2
rs49882352136608646AG
rs1801133111856378--

MyHeritage’s current interpretation help also describes a five-column, tab-delimited file: rsID, chromosome, position, allele 1, allele 2. We read that layout as well, keeping both allele columns; there is no need to rename it to CSV.

3. Separate a no-call from a missing marker

In the synthetic examples, rs1801133 is present but its genotype is --: no usable call is recorded. By contrast, a search that finds no row tells you only that the exact identifier was not found in that file. Coverage, identifiers and incomplete exports can all matter. Neither observation means a negative medical result.

For one marker, use our step-by-step rsID guide. The public rsID lookup explores reference information without a DNA upload; it cannot supply your genotype. Check build and strand before comparing coordinates or allele letters with another source.

4. WGS describes the test method; CRAM describes a file format

MyHeritage’s WGS FAQ, checked on 28 October 2026, says that new samples have been processed with WGS since January 2026 and that a kit processed with WGS can download both a standard CSV/TXT raw-data file and a much larger CRAM file of about 2 GB, at no extra cost. The download instructions describe the two files separately. Check the live sources for changes.

WGS means whole genome sequencing. A selected-marker export from that workflow is not the complete sequencing dataset. CRAM is a format for sequencing reads and alignments, not a text table of rsIDs and genotypes; MyHeritage describes its CRAM file as the sequencing reads aligned to a reference genome, in a compressed format. Producing and interpreting variant calls from reads requires a suitable workflow. Renaming a CRAM file to TXT does not create a marker export, and a WGS label does not make the file a clinical diagnosis.

5. Check compatibility before uploading or converting

DNA Info Lab currently supports the recognised MyHeritage CSV layouts illustrated above, the five-column tab-delimited file, and either inside a recognised ZIP. It does not read CRAM files. Our free file checker examines files locally in your browser; its result describes what it recognises, not the accuracy of the laboratory test. An unsupported result can mean a different layout rather than a damaged download.

If another tool needs 23andMe-style text and your source is a supported CSV, the MyHeritage → 23andMe converter changes the structure locally. Conversion does not measure missing markers, add coverage, resolve genome builds or make another platform accept uploads. Keep the original and check the destination’s current requirements. A supported original file needs no conversion for DNA Info Lab.

6. Decide what you want from an analysis

Genealogy, research associations and clinical testing answer different questions. Our MyHeritage analysis page explains the supported report workflow; the synthetic demo shows its presentation before you upload. Reports provide research associations and coverage, drug-response annotations and ClinVar findings subject to interpretation gates. They do not provide ethnicity estimates, relative matching, aggregate risk scores or diagnoses.

Available findings depend on the usable markers and the catalogue, not just the number of lines or the brand on the file. An unreported finding is not proof of absence. Do not change medication or make health decisions from a consumer export; concerning results need appropriate professional assessment and, when indicated, clinical confirmation.

7. Check privacy as well as file support

Our file checker and converter process files locally in your browser. Report uploads use a separate server workflow: they transit Cloudflare, the original file is discarded after processing, and extracted variants and results are stored in the EU. Optional AI explanations send selected results, including variant identifiers and genotypes, to Anthropic. Read the privacy policy and upload consent before choosing that route.

Sources linked above were checked on 28 October 2026. Provider formats and download availability can change. Compatibility statements describe our current supported inputs; they do not certify every file from a kit processed with the same technology.

Frequently asked questions

Is a MyHeritage WGS export the same as a CRAM file?

No. The processing method and the downloaded format are separate facts. A standard marker export is a table; CRAM stores sequencing reads and alignments and requires different tools.

Can I upload every MyHeritage TXT or CSV to DNA Info Lab?

Not every one. We support the recognised MyHeritage CSV layouts and the five-column tab-delimited file, including supported ZIP exports. CRAM files are not supported. Check the content rather than renaming the extension.

Does converting to 23andMe format add missing variants?

No. Conversion changes the arrangement of existing data. It does not measure additional markers, reconstruct missing calls or guarantee acceptance by another platform.

Does -- mean I do not have a variant?

No. In the illustrated layouts it marks an unusable call. A missing row is a different observation. Neither establishes absence of a variant or a negative medical result.

Start by checking your file

Check the recognised format locally, or explore the synthetic report demo before deciding whether to upload.

Related articles

Aquest article té finalitats exclusivament educatives i no constitueix consell mèdic, diagnòstic ni tractament. Consulta sempre un professional sanitari per a decisions sobre la teva salut.