Forward and Reverse Strand - Why the Same Variant Looks Different

Why one DNA file shows A/G and another shows T/C for the same position, what strand orientation means, and how to compare files without being fooled.

You look up the same variant in two raw DNA files and get different letters. One says AG, the other says TC. Neither file is wrong. This is one of the most confusing things about raw DNA data, and it comes down to strand orientation.

DNA has two strands

Your DNA is a double helix - two strands that mirror each other. The bases always pair the same way: A pairs with T, and C pairs with G. So if one strand reads A, the strand facing it reads T at that spot. They carry the same information from opposite directions.

Because a variant can be described from either strand, the same position has two valid ways to write it:

  • Forward (plus) strand: A/G
  • Reverse (minus) strand: T/C

Swap each letter for its pair and you move between them. A becomes T, G becomes C, and back again.

Why services disagree

Different testing chips and different eras of data settled on different conventions for which strand to report. Public databases have largely standardized on the forward strand of the current genome build, but plenty of older exports and tools still report the other orientation. The result is that two honest files can list complementary letters for the exact same variant.

This is not an error in your data. It is a labeling choice.

How to compare files correctly

If you are matching a variant across two files, or checking your genotype against a reference, keep this in mind:

  • If the letters look unrelated - AG versus TC - try flipping one to its complement before deciding they disagree
  • Treat a genotype as an unordered pair, since AG and GA mean the same thing for most purposes
  • Confirm both files use the same genome build, or positions will not line up in the first place

A tool that handles this well will normalize orientation for you, so a match is a match regardless of which strand each file happened to use.

The tricky case: ambiguous variants

Strand flipping works cleanly except for two combinations. A variant with alleles A/T or C/G is its own complement - flipping A/T still gives T/A. For these, strand alone cannot tell you the orientation. Careful tools rely on allele frequency or simply avoid leaning on ambiguous sites. It is a small share of variants, but a good reason not to assume a naive flip always resolves a mismatch.

Why this matters for your results

Strand confusion is a quiet source of wrong answers. If a tool checks your genotype against a reference without accounting for orientation, it can miss real matches or invent false ones - which throws off trait calls and comparisons. This is exactly the kind of detail worth getting right when you compare two DNA files or read a raw export line by line.

You can explore your own variants, with orientation handled for you, using on device DNA analysis that keeps your file in your browser.

This article is educational and is not medical advice.

Further reading