Gedmatch Basic Access

Important

The display formats of the tools can differ between access levels, as well as which version of the Gedmatch site is used. As such the user needs to be careful that not only are they on the correct version of the Gedmatch website to run the tool. but that they are selecting the correct import template for the tool they ran as well as for their access level.

Pay Attention

If your import fails, please check the following:

If you answered “No.” to any of the above or are unsure, adjust your actions as needed and try again.

This page covers the Basic Access Imports and the Gedmatch tools needed for them.

If you have Tier 1 access, please see Gedmatch Tier 1 for your instructions.

Data able to be collected from Gedmatch depends on the level of access, and your method of access.

Pay attention to import instructions as these may have have recently changed.

The available in-built templates are:

One to Many DNA Comparison Result

If your display does not look like this: Stop, return to the previous page and select the correct tool.

2. Enter the Kit Number and press the Display Results button. You may or may not need to answer a reCaptcha.

3. When the results appear, highlight the page (Ctrl a or Cmd a), and copy the data (Ctrl c or Cmd c).

4. In GDAT, select from the Import Menu, "Gedmatch: 1. Free Tools One to Many"

5. Place your cursor in the pop up window, and click “Paste”. The contents of the clipboard will be added to this window. Now click “Import”.

NOTE: This import has created the relative records for each of your matches. You have not yet loaded any Chromosomal information. This will be done via a series of One to One imports.

Autosomal 1-to-1 Comparison

The GDAT import template works for data obtained from both the “One to One Autosomal DNA Comparison” and the “One to One X-DNA Comparison”. 

Only images for the Autosomal tool are shown here, but the process is the same for both.

Note: While you do not have to essentially be on the correct profile when importing a One to One, it is highly recommended that you are on the correct profile, as being on the incorrect profile can result in effectively two matches being added, one for the true profile, and one for the active profile.

1. Log in via the "New" option, and under the "Free Tools" heading, select "One-to-One Autosomal DNA Comparison".

2. Enter the GDAT Profiles kit number in Kit Number 1

3. Enter the kit to compare in Kit Number 2

4. Select Position Only. Other options can be left at default settings. If a different Build is desired, select it, but ensure that only one Build level is selected.

5. Press Submit button. You may or may not need to answer a reCaptcha.

6. When the results appear, highlight the page (Ctrl a or Cmd a), and copy the data (Ctrl c or Cmd c).

7. In GDAT, select from the Import Menu, " Gedmatch: 2: Free Tools One-to-One Autosomal DNA Comparison"

8. Place your cursor in the pop up window, and click “Paste”. The contents of the clipboard will be added to this window. Now click “Import”.

10. Repeat for every match you wish to have chromosomal data for in GDAT.

People who match both kits (ICW)

Note: This tool can only be used on the Google Chrome browser and if you have the Pedigree Thief browser extension installed.

1. Log in via the "New" option, under the "Free Tools" heading, select "People who match both, or 1 of 2 kits".

2. Enter first kit number and enter second kit number. Other fields can be adjusted or left at the recommended default.

3. Press Display Results button. You may or may not need to answer a reCaptcha.

4. Press Save ICW button and save the file to a location easily remembered. It will be named similar to
"GedMatch ICW {name1} and {name2}.csv"

5. Import this file through the GDAT Import Menu, "Gedmatch: 3: Free Tools People Who Match Both Kits"

6. Repeat as desired for other matches.

Troubleshooting Tip: If you cannot see the “Save ICW” button, you may have another browser extension active that is interfering with the Pedigree Thief extension. The Genetic Family extension is known to cause this issue.