Raw DNA upload troubleshooting
Fix the most common raw DNA upload problems.
If a 23andMe raw data upload fails in GenoSight, GEDmatch, or another raw-data tool, the problem is usually file format or compatibility, not your account. Use this checklist to find the right 23andMe, AncestryDNA, or MyHeritage genotype export before running a report.
Quick pre-upload checklist
Five checks before you run analysis.
- The file is not a PDF, screenshot, or web page
- You know whether the destination wants the ZIP or the TXT inside
- The file has not been opened and resaved in Excel or Sheets
- The first rows contain rsIDs or provider comments
- The file is from 23andMe, AncestryDNA, or MyHeritage
- You understand the report is educational, not clinical confirmation
Common upload errors and fixes
These are format, provider, chip-version, and coverage issues. They do not say anything medical about your DNA.
You selected a PDF report
Provider reports are usually polished PDFs with charts and explanations. They are not raw genotype data.
Fix: Download the raw data export from your provider account instead. It is usually a large text, CSV, or TSV file with rsID rows.
A tool wants TXT, not the 23andMe ZIP
23andMe and other providers often download raw data as a compressed archive. Some tools want the archive; others reject it and expect the raw .txt file inside.
Fix: Check the destination tool instructions. For GenoSight, extract the archive first, then upload the genotype text file inside the folder.
You saved a dashboard web page
A saved account page can look like a file download, but it contains HTML rather than genotype calls.
Fix: Go back to the provider download flow and choose the raw DNA data export option.
GEDmatch, Promethease, or GenVue rejects the file
A valid consumer raw-data file can still fail if the tool expects an older chip version, a specific provider layout, a different ZIP/TXT choice, or a file that was opened and resaved.
Fix: Start from the fresh provider download, avoid Excel/Sheets resaves, and confirm whether that tool accepts your provider, chip version, and exact file wrapper.
The file has too few genotype rows
A clipped sample, partial report, or copy-pasted table may contain some rsIDs but not enough coverage for useful reports.
Fix: Use the original full raw data export. Consumer files often contain hundreds of thousands of variant rows.
The file is not a supported raw DNA format
GenoSight is built for consumer genotype files, not whole-genome FASTQ, BAM, CRAM, or clinical VCF workflows.
Fix: Use a compatible 23andMe, AncestryDNA, or MyHeritage raw genotype export for the current product.
The file works but a report has gaps
Even compatible files can miss specific markers because each provider chip tests a different set of positions.
Fix: Read the report caveats and coverage notes. A missing marker is not the same thing as a negative clinical result.
A clean recovery path
The goal is not to retry the same failed file. Fix the file source first, then move forward only when the local preflight looks compatible.
Identify the failed file type
Check whether the rejected file is a PDF, saved web page, ZIP archive, partial sample, or unsupported genome format.
Download the raw genotype export
Return to 23andMe, AncestryDNA, or MyHeritage and download the raw DNA data file rather than a report or account archive.
Match ZIP vs TXT expectations
If the provider download is compressed, check whether the destination tool wants the ZIP itself or the raw text, CSV, or TSV file inside the archive.
Run the local file check
Use the browser-only checker to confirm that the corrected file has genotype-style rsID rows before spending credits.
Why the right file matters
GenoSight reads variant rows from a consumer raw DNA file, then generates educational reports with caveats. A PDF, screenshot, or provider dashboard cannot provide that genotype table.
See how raw DNA analysis worksUpload only after consent
The local checker can run before sign-in. The real upload happens only after account creation and GenoSight's consent flow.
Coverage gaps are normal
Different chips include different markers. A missing marker should be treated as unknown, not as a diagnosis or result.
After the file is fixed
Once the file looks compatible, choose the smallest next step that matches your confidence level.
Start free
Use 250 no-card credits after the file looks compatible and the consent boundary is clear.
Start freeChoose monthly
Use the paid path when you already know you want multiple reports, regenerations, PDFs, and chat.
Choose monthlyPick first report
If you are unsure which report should use your credits first, map your question before uploading.
Open pickerRaw DNA upload questions
Why does GenoSight reject my raw DNA file?
The most common reason is selecting the wrong file type: a PDF report, saved web page, ZIP archive, empty file, or partial sample instead of the original raw genotype text file.
Why will my 23andMe raw data not upload to GEDmatch or another tool?
It is often a format or compatibility issue: the tool may want the .txt file inside the 23andMe ZIP, may reject a file that was opened and resaved, or may not support that provider/chip version.
Should I upload the ZIP file from my provider?
For GenoSight, extract the ZIP first, then upload the raw DNA text, CSV, or TSV file inside the archive. Other tools vary, so check whether they ask for the ZIP or the extracted text file.
Can GenoSight analyze a VCF, BAM, or whole-genome file?
Not in the current product. GenoSight is focused on consumer raw genotype exports from 23andMe, AncestryDNA, and MyHeritage.
Can a compatible upload still miss a gene?
Yes. Consumer genotyping chips vary by provider and version. If a marker is not present in your raw file, GenoSight should treat that as a coverage gap rather than a medical result.
Free checker, then free credits