Free tool · no account · no upload
Convert your raw DNA file, without uploading it
Drop a raw DNA export from 23andMe, AncestryDNA, MyHeritage or FamilyTreeDNA and download it in any of the other formats. The conversion runs entirely in your browser: it rewrites the file's layout — delimiter, header, chromosome naming, no-call symbol — and never touches your genotypes, positions or genome build. No byte of your DNA ever leaves this device.
Drop your raw DNA file here
or choose it from your device
Accepts the original .txt or .csv exports from 23andMe, AncestryDNA and FamilyTreeDNA, and MyHeritage's export, as CSV or as the five-column tab-separated text file its help describes. Extract a .zip or .gz first.
Private by construction: the file is read and rewritten locally with your browser's File API. There is no upload button, and no part of the file — contents, name or results — is sent anywhere; you can disconnect from the internet before choosing the file. The only thing the page may send is a usage event saying a conversion finished, which names the tool and nothing about the file.
What a format conversion is — and what it is not
- It rewrites the file's representation: delimiter, column header, chromosome naming and the no-call symbol. Your rsIDs, positions and genotype letters pass through unchanged.
- It does not change the genome build, and it never infers one. If the source header declares a build, the converted file repeats it, unverified.
- It does not perform liftover, strand flips or imputation, and it cannot turn one chip's marker list into another's: positions the source chip never tested are not in the file, and no format change can add them.
- It never forges a provider's header. The output opens with an honest comment naming the real source — a converted file is a converted file, not a counterfeit export.
- Every change of representation is counted and shown in the conversion report, including the rows that could not be carried over.
Format compatibility is not platform acceptance
Whether a company accepts an uploaded file is that company's decision, made by their upload pipeline — not something any converter can promise. The honest status, per target format:
- 23andMe
- 23andMe's help centre explains how to download your raw data, but documents no way to upload a file from another company. A file in 23andMe format is useful for third-party tools that read that layout — not for creating a 23andMe profile.
- Source: the company's help centre, checked 28 October 2026
- AncestryDNA
- Ancestry's help centre states that DNA data from other websites cannot be uploaded to Ancestry. The AncestryDNA format matters when a third-party tool expects that exact five-column layout.
- Source: the company's help centre, checked 28 October 2026
- MyHeritage
- MyHeritage's help centre states that DNA uploads are no longer supported, so data from other testing services cannot be uploaded. A file in MyHeritage format is still useful for third-party tools that read that layout.
- Source: the company's help centre, checked 28 October 2026
- FamilyTreeDNA
- FamilyTreeDNA accepts raw data transfers from AncestryDNA, 23andMe and MyHeritage only for the test versions and date ranges it lists, and states that it cannot accept files altered or reformatted from the version the testing company provided. For a FamilyTreeDNA transfer, upload the original file, not a converted one. Their rules can change.
- Source: the company's help centre, checked 28 October 2026
Popular conversions
Each guide explains exactly what changes between the two formats — and what does not.
The four formats, side by side
| 23andMe | AncestryDNA | MyHeritage | FamilyTreeDNA | |
|---|---|---|---|---|
| File extension | .txt | .txt | .csv | .csv |
| Column separator | tab | tab | comma | comma |
| Chromosome naming | 1–22, X, Y, MT | 1–22, 23 (X), 24 (Y), 25 (XY), 26 (MT) | 1–22, X, Y, XY, MT | 1–22, X |
| No-call symbol | -- | 0 0 | -- | -- |
Converter questions
Does my DNA leave my device?
No. The file is read, converted and rewritten in your browser with the File API. Nothing from the file is uploaded — the privacy promise is architectural, not a policy. When a conversion finishes, the page records a usage event that names the tool and carries nothing about the file.
Does the conversion change my genotypes or genome build?
No. Only the representation changes: delimiter, header, chromosome naming and the no-call symbol. Genotype letters, rsIDs and positions are byte-identical, and the genome build is neither changed nor guessed.
Will the platform I convert for actually accept the file?
Check each company's own rules. FamilyTreeDNA accepts transfers from AncestryDNA, 23andMe and MyHeritage for the versions it lists, but not files altered or reformatted from the provider's version — so a converted file is not the one to send it. Ancestry and MyHeritage state that they do not accept DNA data from other services, and 23andMe documents no upload route. Converted files are mainly useful for third-party analysis tools that expect a specific layout.
What happens to no-calls?
They are preserved, in the target format's own notation: -- in 23andMe, MyHeritage and FamilyTreeDNA files, a pair of zeros in AncestryDNA files. A converter that drops them silently shrinks your file.
Why is the converted file slightly different in size?
Different formats spend different bytes on the same data: quotes, tabs versus commas, chromosome names versus numbers, and our provenance comment at the top. The data rows carry the same content.
Can it convert my file to a newer chip or add missing SNPs?
No, and be wary of tools that claim to: adding positions your chip never tested is imputation — statistical guessing — not conversion. This tool only rewrites the representation of what your file already contains.
Want to know what is actually in that file?
Explore your variants with our paid report: GWAS research associations, drug-response annotations and ClinVar findings subject to interpretation limits. Use your original file.
Continue to DNA analysis →