How do reverse-frame positions map to my input?

Reverse-strand ORF start/end are given as coordinates along the reverse complement (read 5′ → 3′ on the minus strand), not the forward input — translate accordingly when mapping back.

How is this different from the ORF finder?

The ORF finder searches only the three forward frames. This tool adds the three reverse-strand frames, so it catches genes encoded on the opposite strand.

Six-frame ORF finder

Find open reading frames in all six reading frames — three forward and three on the reverse-complement strand — and translate each to protein.

How it works

Formula

Search the three forward frames of the sequence and the three frames of its reverse complement (reverse strand), reusing the same ATG → stop scan and standard codon table as the single-strand ORF finder. Forward frames are +1/+2/+3; reverse frames are −1/−2/−3.

Worked example

CTATTTCAT has no forward ORF, but its reverse complement is ATGAAATAG, which contains one ORF translating to MK — reported as frame −1 on the reverse strand.

When to use it

When you do not know which strand or frame codes for your protein — for example, characterising an unannotated insert or contig, where the gene could be on either strand.

Sensible defaults

The default sequence has a 33 nt forward ORF (MAKFGPTDEF). Reverse-frame ORF positions are reported as coordinates on the reverse-complement strand (5′ → 3′).

FAQ

How do reverse-frame positions map to my input?: Reverse-strand ORF start/end are given as coordinates along the reverse complement (read 5′ → 3′ on the minus strand), not the forward input — translate accordingly when mapping back.
How is this different from the ORF finder?: The ORF finder searches only the three forward frames. This tool adds the three reverse-strand frames, so it catches genes encoded on the opposite strand.