<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sveta Kors</title>
    <description>The latest articles on DEV Community by Sveta Kors (@sveta_kors_c98787db329806).</description>
    <link>https://dev.to/sveta_kors_c98787db329806</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3925431%2Fb26c93b7-702e-480b-93e8-dd28bdfd9bb5.jpg</url>
      <title>DEV Community: Sveta Kors</title>
      <link>https://dev.to/sveta_kors_c98787db329806</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sveta_kors_c98787db329806"/>
    <language>en</language>
    <item>
      <title>Parsing Raw DNA Files: Why 23andMe and MyHeritage Are Incompatible</title>
      <dc:creator>Sveta Kors</dc:creator>
      <pubDate>Mon, 11 May 2026 16:58:24 +0000</pubDate>
      <link>https://dev.to/sveta_kors_c98787db329806/parsing-raw-dna-files-why-23andme-and-myheritage-are-incompatible-13p3</link>
      <guid>https://dev.to/sveta_kors_c98787db329806/parsing-raw-dna-files-why-23andme-and-myheritage-are-incompatible-13p3</guid>
      <description>&lt;p&gt;While working with consumer DNA data, I noticed that many people assume raw DNA files from different providers are compatible with each other. In practice, this is rarely true.&lt;/p&gt;

&lt;p&gt;Services like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;23andMe&lt;/li&gt;
&lt;li&gt;AncestryDNA&lt;/li&gt;
&lt;li&gt;MyHeritage&lt;/li&gt;
&lt;li&gt;FamilyTreeDNA&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;all export genetic data differently.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;h2&gt;
  
  
  23andMe
&lt;/h2&gt;

&lt;p&gt;Uses a TSV-like structure with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;rsid&lt;/li&gt;
&lt;li&gt;chromosome&lt;/li&gt;
&lt;li&gt;position&lt;/li&gt;
&lt;li&gt;genotype&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;rs3094315   1   752566  AA
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  AncestryDNA
&lt;/h2&gt;

&lt;p&gt;Uses CSV formatting and separate allele handling.&lt;/p&gt;

&lt;h2&gt;
  
  
  MyHeritage
&lt;/h2&gt;

&lt;p&gt;Uses another CSV variant with different parsing expectations.&lt;/p&gt;

&lt;p&gt;Even though the biological data is similar, direct upload between services often fails because:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;column order differs&lt;/li&gt;
&lt;li&gt;delimiters differ&lt;/li&gt;
&lt;li&gt;genotype representation varies&lt;/li&gt;
&lt;li&gt;SNP coverage is inconsistent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I created a small open-source repository documenting these differences and conversion logic between providers.&lt;/p&gt;

&lt;p&gt;GitHub:&lt;br&gt;
&lt;a href="https://github.com/milaza/dna-raw-data-converter-23andme-myheritage-ancestry/" rel="noopener noreferrer"&gt;https://github.com/milaza/dna-raw-data-converter-23andme-myheritage-ancestry/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The repository includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;format explanations&lt;/li&gt;
&lt;li&gt;conversion examples&lt;/li&gt;
&lt;li&gt;sample files&lt;/li&gt;
&lt;li&gt;compatibility notes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is also an online converter for users who do not want to manually process raw DNA data:&lt;br&gt;
&lt;a href="https://tendna.com/en/dna-converter" rel="noopener noreferrer"&gt;https://tendna.com/en/dna-converter&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It was interesting to discover how fragmented consumer genetic data formats still are, despite the growing popularity of DNA testing.&lt;/p&gt;

</description>
      <category>dna</category>
      <category>23andme</category>
      <category>myheritage</category>
      <category>science</category>
    </item>
  </channel>
</rss>
