What is TreeScope?
TreeScope is a browser-based tool designed specifically for genealogists working with DNA match trees. It helps you import, visualize, and analyze the family trees attached to your DNA matches — and convert them into GEDCOM files for use in other genealogy software.
Unlike general-purpose genealogy software, TreeScope is focused on match tree analysis as a dedicated workflow — evaluating the pedigrees behind your DNA matches to identify Most Recent Common Ancestors (MRCAs) and understand how you connect to each match.
Version 4 introduces a more structured research workflow — allowing you to evaluate, track, and refine relationships over time instead of treating analysis as a one-time pass.
TreeScope works with the family trees that belong to your DNA matches, not just your own tree. Each imported tree is called a kit. You can import dozens of kits and analyze them together.
What TreeScope does
| Feature | Description |
|---|---|
| Import match trees | From GEDmatch, FTDNA, One2Tree, WikiTree, and standard GEDCOM files |
| Import DNA match data | Attach cM, segment, X-DNA, and haplogroup data from GEDmatch and FTDNA match lists, or enter it manually in a kit overview |
| Visualize pedigrees | Interactive fan chart with grandparent line coloring, X-DNA highlighting, and Origin Mode |
| Find and verify MRCAs | Compare two kits or run all kits against each other, then mark promising results as Verified or dismiss them for later review |
| Track research progress | Assign kit statuses such as Needs Review, In Progress, or Investigated and use phase assignments to focus on maternal or paternal lines |
| Use the MRCA Matrix | Review All vs All results in a visual grid and jump directly into a pair comparison from any matching cell |
| Search surnames & places | Across all loaded kits simultaneously |
| Export GEDCOMs and CSVs | Export individual kits, bulk downloads, and MRCA results with verification and research note fields |
| Save your work | Auto-saves to your browser between sessions, with a full JSON backup available for portable sessions |
You can use square brackets inside a kit name for your own reference notes while working in TreeScope. Those bracketed notes stay visible inside the app but are stripped automatically from GEDCOM exports.
All data is processed entirely in your browser. Nothing is ever transmitted to or stored on any server. Your data never leaves your device unless you explicitly export it.
Quick Start
Get up and running in a few minutes. This assumes you have a GEDmatch account with DNA matches that have linked GEDCOMs.
In GEDmatch, run One-To-Many (Full Version), select matches with GEDCOMs, then go to Visualization Options → GEDCOM tab → Find Matching GEDCOMs (anc) → POST TO ANC. Copy the full text output.
Click the 📋 Paste GEDCOM text tile, paste your copied data, and click ↓ Import. Your kits will appear in the left panel.
Select any kit from the left panel. The Overview tab shows statistics, top surnames, and a pedigree fan chart for that match's tree.
Go to the MRCA Finder tab and use All vs All mode to scan every kit pair for common ancestors automatically.
Your session auto-saves in the browser as you work. For a portable backup, click ⬇ Save JSON in the header to download a file you can reload next time.
Use Mark as Me on your own kit to unlock the Compare to Me shortcut on every other kit's Overview — this instantly runs a 1-to-1 MRCA comparison between you and any match.
Interface Overview
TreeScope is organized into a few main regions that stay visible throughout your session.
| Region | Description |
|---|---|
| Header | App name, project name field, theme toggle, User Guide link, JSON save/import controls, Feedback button, Clear Data button, and support link |
| Import Zone | Import tiles for GEDmatch paste, Kit Links, Tree CSV, WikiTree, GEDCOM file, GEDmatch Match Data, and FTDNA Match Data. In v4 the zone can also be collapsed to free up workspace. |
| Stats Bar | Live counts of loaded kits, individuals, events, selected kits, and auto-save status |
| Kit Panel | Searchable list of kits with sort controls, source filter, side filter, tree/no-tree filtering, research status dots, checkbox selection, and source badges |
| Tab Area | Overview, GEDCOM Preview, Bulk Export, MRCA Finder, and Surnames & Places |
| Footer | Version, copyright, privacy reminder, feedback link, and terms link |
Import Zone
The import zone at the top of the page gives you access to all data sources in one place. The Tree CSV tile handles both FTDNA and One2Tree exports — click the ℹ FTDNA & One2Tree link to see instructions for both formats without leaving the app.
In v4, the import zone can also be collapsed after you load your kits, which gives you more room to work in the main interface during analysis.
Source Badges
Each kit in the kit panel displays a source badge so you can see at a glance where it came from.
GEDmatch FTDNA One2Tree GEDCOM WikiTree
Auto-Save
TreeScope automatically saves your session to your browser's local storage (IndexedDB) as you work. When you return to TreeScope, your previous session is restored automatically — no manual save required to preserve your work between visits.
Version 4 introduces a more structured research workflow — allowing you to evaluate, track, and refine relationships over time instead of treating analysis as a one-time pass.
Auto-save is convenient but tied to a single browser on a single device. If you want to transfer your session to another device, share it, or keep a permanent archive, you still need to export a JSON backup.
The auto-save status is shown in the stats bar. The stats bar also shows a running count of kits, individuals, and how many have birth dates, birth places, death dates, and death places recorded. A green indicator means your current session is saved. If you clear browser data or use a different browser, the auto-saved session won't be available — always export a JSON backup for anything you want to keep long-term.
Importing from GEDmatch
GEDmatch is the primary data source for TreeScope. The paste import brings in the full individual-level data from match trees — names, dates, places, and family relationships.
Select matches with GEDCOMs, then click Visualization Options → GEDCOM tab.
Copy the full text output from the results table.
Paste the copied data and click ↓ Import.
Importing GEDmatch Kit Links
Kit links connect your imported tree data to specific GEDmatch kit numbers, enabling direct links to GEDmatch profiles from within TreeScope. Run this after the paste text import.
Go to Visualization Options → GEDCOM tab → Find Matching GEDCOMs → Search. Copy the full results table.
Paste or upload the report, and click ↓ Import Links.
Importing from FTDNA
Family Tree DNA match trees can be exported as CSV files via DNAGedcom and imported directly into TreeScope using the 📥 Import Tree CSV tile.
Click Gather → FamilyTreeDNA, toggle on Trees, and click Gather Data → Run Report.
Drag the generated CSV file onto the 📥 Import Tree CSV tile, or click the tile to browse.
Click the ℹ FTDNA & One2Tree link next to the tile for a step-by-step reminder without leaving TreeScope.
Importing from One2Tree
One2Tree is a Chrome extension that extracts family trees from Ancestry, MyHeritage, and FTDNA. TreeScope accepts its CSV export through the same 📥 Import Tree CSV tile used for FTDNA.
Load a tree on Ancestry, MyHeritage, or FTDNA.
Click Go! and wait for the list to build.
Click Save List as CSV and leave the default options as is.
Drag the generated CSV file onto the 📥 Import Tree CSV tile, or click to browse.
Importing from WikiTree
WikiTree's Compact Tree view can be copied and pasted directly into TreeScope — no export or account required for public profiles.
The Compact Tree shows up to 8 generations in a text-based diagram and is the quickest format to grab from any public WikiTree profile.
Find the profile for the person you want to import.
Choose Compact Tree from the menu at the top of the page.
Press Ctrl+A / Cmd+A, then copy the full page text.
Click 🌐 Paste WikiTree Tree, paste the text, and click ↓ Import.
Importing GEDCOM Files
Standard GEDCOM files (.ged) from any genealogy software can be imported by dropping the file onto the import tile. TreeScope identifies the tree subject automatically by counting ancestors rather than descendants.
As of v4.0.3 you can import multiple GEDCOM files at once — select or drop as many .ged files as you like and they'll all be merged in sequentially. A summary shows each filename and individual count when the import is done.
RootsMagic, Family Tree Maker, Ancestry, FamilySearch, and most other programs support GEDCOM export.
Drag any number of .ged files onto the 🌳 Import GEDCOM tile at once, or click to open a file browser and select multiple files using Shift+click or Cmd/Ctrl+click.
TreeScope supports GEDCOM 5.5.1 and common variants. Generation numbering is calculated from the tree subject outward, so fan charts display correctly even for complex tree structures.
Importing a JSON Backup
JSON backups preserve your entire TreeScope session — all kits, individuals, notes, GEDmatch kit links, project name, and your Me flag. Use these to continue research across sessions or to transfer your work to another device.
Click ⬆ Import JSON in the header and select your previously saved .json file.
Importing a JSON backup merges with any currently loaded data. To start fresh from a backup, click ✕ Clear Data first, then import.
Importing GEDmatch Match Data
Once you have tree kits loaded and GEDmatch kit links imported, you can enrich those kits with DNA match data from GEDmatch's One-to-Many results. This attaches cM values, segment counts, X-DNA data, and haplogroups directly to each kit.
TreeScope accepts both the classic One-to-Many (Full Version) format and the newer GEDmatch Pro One-to-Many Segment-Based format — it detects which format you've pasted automatically.
Version 4 introduces a more structured research workflow — allowing you to evaluate, track, and refine relationships over time instead of treating analysis as a one-time pass.
Kit Links must be imported first so TreeScope can match GEDmatch kit numbers to your loaded trees. Kits without a linked kit number will be skipped unless you choose to import all matches.
Classic: Run One-to-Many (Full Version) and copy the match rows. Pro: Run One-to-Many Segment-Based — you can select all including any header or navigation text and paste it all; TreeScope filters out the noise automatically.
Click the 🧾 Paste Match List tile under GEDmatch Match Data and paste the rows.
Import all matches creates placeholder kits for matches that don't have an associated tree yet — useful for tracking all your DNA connections. Import matches with trees only skips anything without a linked tree. Then click ↓ Import.
Fields imported
| Field | Description |
|---|---|
| Total cM | Total shared centimorgans with this match |
| Largest segment | Size of the largest shared DNA segment in cM |
| Total X-DNA | Total shared X-DNA in cM |
| Largest X segment | Largest shared X-DNA segment in cM |
| mt haplogroup | Mitochondrial haplogroup of the match |
| Y haplogroup | Y-chromosome haplogroup of the match (males only) |
Importing FTDNA Match Data
You can also attach DNA match data from FTDNA's Family Finder match table. TreeScope matches rows to already-imported kit subjects by name.
Switch to Table View to see the full match list.
Select and copy all the match rows.
Click the 🧾 Paste Match List tile under FTDNA Match Data and paste the rows.
Import all matches creates placeholder kits for matches that don't have a linked tree. Import matches with trees only skips anything without a matched kit. Then click ↓ Import.
Fields imported
| Field | Description |
|---|---|
| Shared DNA | Total shared centimorgans with this match |
| Longest block | Length of the longest shared segment in cM |
| X match | Whether X-DNA is shared with this match |
| mt haplogroup | Mitochondrial haplogroup of the match |
| Y haplogroup | Y-chromosome haplogroup of the match (males only) |
Match Placeholders
When you import GEDmatch or FTDNA match data using Import all matches mode, TreeScope creates placeholder kits for any match that doesn't have an associated tree yet. These placeholders appear in the kit list with the match's name, cM value, and relationship range — so you have a complete picture of your match list even before trees are attached.
What placeholders show
- Match name and source badge
- Total cM and relationship range estimate
- 🧬 DNA badge, since they have match data attached
- A note in the Overview indicating no tree has been imported yet
Merging a placeholder into a kit with a tree
Once you import a tree for a match who already has a placeholder, you can merge the placeholder into the new kit. This copies the DNA data from the placeholder to the tree kit and removes the placeholder.
Click it in the kit list to open its Overview.
A searchable picker appears showing kits that have trees. Search by name, source, or kit ID.
The DNA data transfers over immediately and the placeholder is deleted.
You can also use the Cross-Platform Linking workflow instead of merging — linking keeps both kits intact and combines their ancestor pools for MRCA analysis. Merging is the cleaner option when the placeholder has no unique data beyond the DNA values.
Kit Panel
The left panel lists all loaded kits. Each kit represents one tree — either a DNA match's tree or any tree you've imported for comparison. Kits are sorted alphabetically by subject name by default.
Kit Panel Features
| Feature | How to use |
|---|---|
| Search | Type a name, kit ID, GEDmatch kit number, surname, or place name to filter the list. Click ✕ to clear. When searching by surname or place, the panel switches to individual search mode and shows a label indicating this. |
| Select kit | Click a kit name to open it in the main tab area. |
| Checkbox selection | Check boxes to select multiple kits for bulk export or MRCA comparison. |
| Select all visible | Selects all kits currently shown, respecting any active search filter. |
| Sort A–Z / Highest cM | Switch between alphabetical sort and sorting by total shared cM. The cM sort is only meaningful after DNA match data has been imported. |
| All Sources filter | Cycle through sources (GEDmatch, FTDNA, One2Tree, WikiTree, GEDCOM) to show only kits from a specific platform. |
| Side filter | Filter the kit list to show only Maternal, Paternal, or Unknown kits. |
| Tree filter | When placeholder kits without trees are present, switch between all kits, kits with trees, and no-tree placeholders. |
| Research status dots | Assign and review kit progress at a glance. Status markers can be used to show which kits still need review, which are actively being worked, and which have already been investigated. |
| 🧬 icon | Appears on kits that have DNA match data attached — either imported from GEDmatch or FTDNA match lists, or entered manually in the kit Overview. |
| Relationship range | Kits with DNA data show an estimated relationship range below the cM value (e.g. ≈ 3C1R / 4C / more distant). This is a probability-based estimate, not a confirmed relationship. |
| Duplicate kit detection | If two imported kits appear to be the same person or close relatives, TreeScope shows a review banner so you can decide how to handle them. |
Overview Tab
The Overview tab is the main view for a selected kit. Click any kit in the left panel to open it.
Overview sections
| Section | Description |
|---|---|
| Kit header | Subject name, source badge, GEDmatch kit number (if linked) with copy button |
| Statistics | Total individuals, those with birth dates, birth places, and linked parents |
| Mark as Me | Flags this kit as your own. Enables the Compare to Me button on all other kits. |
| Compare to Me | Appears when a Me kit is set. Jumps to MRCA Finder and runs a 1-to-1 comparison instantly. |
| Link to kit | Manually link this kit to another kit that belongs to the same person — for example, connecting a GEDmatch match to a WikiTree tree you found for them. Linked kits share their ancestor data in MRCA analysis. See Cross-Platform Linking below. |
| Side | Assign this kit to Maternal, Paternal, or Unknown. Used for filtering and MRCA phase scope. |
| Top Surnames | The most common surnames in this kit shown as proportional bars. |
| Notes | Free-text research notes for this kit. Saved with JSON exports and auto-save. |
| DNA Info | If GEDmatch or FTDNA match data has been imported, cM, segment, X-DNA, and haplogroup values are shown here. For kits without imported DNA data, you can enter values manually — testing company, total cM, largest segment, X cM, mt haplogroup, and Y haplogroup. Manually entered data is saved with the session and triggers the 🧬 badge and cM sort. |
| Clean View toggle | Hides single-letter entries, short all-caps codes, and other data artifacts from the individual list. |
| Table / Pedigree toggle | Switch between a data table of all individuals and the interactive fan chart. |
Clicking any kit name link from MRCA results or the Surnames tab navigates directly to that kit's Overview and opens the fan chart automatically.
Cross-Platform Linking
If you find a tree for a match on a different platform — for example, you have a GEDmatch match and you locate their tree on WikiTree — you can link the two kits together so TreeScope treats them as the same person.
What linking does
| Behaviour | Detail |
|---|---|
| Shared ancestor pool | In MRCA analysis, both kits' trees are combined into one view, so ancestors from either tree can be matched against other kits. |
| Skipped in All vs All | The two linked kits are not compared against each other — comparing a tree to itself isn't useful. Each linked kit still runs against all other kits independently. |
| Reversible | An Unlink button appears next to the linked kit name. Unlinking restores both kits to independent status instantly. |
How to link
Import the GEDmatch, WikiTree, GEDCOM, or any other tree for the same person using the normal import tiles.
Click the kit in the left panel to open it.
A searchable picker appears showing all other loaded kits with their source badge and individual count. Search by name, source, or kit ID.
The kits are linked immediately. The Overview shows "Linked → [Name]" with an Unlink button.
TreeScope also detects likely same-person pairs automatically during All vs All analysis. When detected, a review banner appears so you can confirm or dismiss the suggestion.
Pedigree Fan Chart
The fan chart visualizes a kit's pedigree as a semicircle expanding upward from the subject at the bottom center. Each ring is one generation. Segments get progressively narrower toward the outside as the number of ancestors doubles each generation.
Fan chart controls
| Control | What it does |
|---|---|
| Scroll to zoom | Zoom in and out on any part of the chart. |
| Click and drag | Pan around when zoomed in. |
| Fit to window | Resets zoom and centers the chart. |
| X-DNA toggle | Highlights ancestors who could be on your X-DNA inheritance path. |
| Origin Mode 🌍 | Colors each segment by the ancestor's birthplace region or country. See Origin Mode below. |
| PNG export | Downloads the current fan chart as a PNG image file. |
Grandparent line coloring
In the default view, each grandparent line is colored distinctly so you can see at a glance which branch of the tree has the most documented ancestors. Empty segments (unknown ancestors) appear as a pale outline.
Origin Mode
Origin Mode colors each fan chart segment by the ancestor's birthplace rather than by grandparent line. Activate it with the 🌍 button in the fan chart toolbar.
How places are colored
US birthplaces are grouped into eight geographic regions, each with its own color:
| Region | States |
|---|---|
| New England | CT, MA, ME, NH, RI, VT |
| Mid-Atlantic | DC, DE, MD, NJ, NY, PA |
| Upper South | KY, NC, TN, VA, WV |
| Deep South | AL, FL, GA, MS, SC |
| South Central | AR, LA, OK, TX |
| Midwest | IL, IN, IA, KS, MI, MN, MO, NE, ND, OH, SD, WI |
| Mountain / West | AZ, CO, ID, MT, NM, NV, UT, WY |
| Pacific | AK, CA, HI, OR, WA |
Non-US birthplaces are colored by country. Ancestors with no birthplace recorded appear as a pale gray segment.
Origin Mode is particularly useful for spotting geographic clusters in a match's ancestry — a tree dominated by one region can help you quickly identify which of your own ancestral lines might be the connection point.
MRCA Finder
The MRCA (Most Recent Common Ancestor) Finder compares two family trees and identifies individuals who appear in both. Use this to find how you connect to a DNA match.
Modes
| Mode | When to use |
|---|---|
| All vs All | Scans every loaded kit pair automatically. Best for getting a broad picture across all your matches at once. |
| 1 to 1 | Compares two specific kits. Use when you want to examine a particular pair in detail or when All vs All produces too many results to review. |
| Matrix | Displays the All vs All results as a grid — rows and columns are kits, and each cell shows whether that pair has a Confirmed, Candidate, or no result. Click any cell to jump directly to that pair's results. Use this to spot patterns across your full match set at a glance. |
Result types
Each MRCA result is labeled to help you evaluate its reliability:
Confirmed — TreeScope traced a complete, unbroken parent-child chain from both subjects up to the shared ancestor. Every link in both paths is connected with no gaps.
Candidate — The ancestor appears in both trees but at least one path has a gap somewhere — usually because the tree doesn't go back far enough, or a parent link is missing partway up the chain. The match may still be correct, but it can't be fully verified from the tree data alone.
Verified and dismissed results
In v4, MRCA results are no longer just something you review once and lose. Promising results can be marked as Verified with a research note, while weak or incorrect results can be dismissed so they no longer appear in future runs. Both decisions persist in your JSON backup and across future sessions until you change them.
Version 4 introduces a more structured research workflow — allowing you to evaluate, track, and refine relationships over time instead of treating analysis as a one-time pass.
A practical workflow is to verify strong candidates as you confirm them, dismiss clear false positives, and leave the rest unmarked until additional evidence emerges. That turns MRCA Finder into a working research queue instead of just a one-time report.
Match threshold
The threshold slider controls how strictly ancestor records need to match to be considered the same person. A higher threshold requires more matching fields (name, dates, places) and produces fewer but more reliable results. A lower threshold casts a wider net and is useful when trees use inconsistent naming or have sparse dates.
Phase scope
The Phase scope dropdown lets you filter which kit pairs are compared based on their assigned maternal/paternal side. You can limit analysis to same-side pairs only, maternal-only, or paternal-only — useful once you've assigned sides to your kits and want to focus on one branch at a time. This is especially useful in v4 when you have a larger kit set and want to avoid cross-side comparisons that are unlikely to be helpful.
In All vs All mode, kits where both trees belong to the same person are silently skipped. In 1-to-1 mode, if you select two kits that appear to be the same person, TreeScope will warn you before running the comparison.
Matrix View
After running All vs All, switch to Matrix mode to see results as a grid. Each row and column represents a kit, and each cell shows the result for that pair — a green ✓ for Confirmed, a gold ~ for Candidate, or empty for no result. See Result types above for what Confirmed and Candidate mean. Hover over any cell to see a tooltip with the shared ancestor name and score. Click a cell to jump straight to a detailed 1-to-1 view of that pair.
The matrix can be filtered to show only Confirmed pairs, only Candidate pairs, or only pairs with no result — useful for quickly identifying matches that still need research. Kits with no qualifying results are excluded from the matrix so the grid stays easier to read.
A kit that shows up as Confirmed or Candidate across many rows is one worth investigating closely — it likely connects to a well-documented ancestral line that multiple matches share.
Surnames & Places
The Surnames & Places tab searches across all loaded kits simultaneously. Type a surname or place name to see every kit that contains a matching individual, along with the individual's details and their generation in that tree.
Tips for searching
- Search is case-insensitive and matches partial strings
- Combine a surname with a place name to find kits with both — useful for locating geographic clusters
- Use Clean View in individual kit overviews to reduce noise from data artifacts before searching
Exporting GEDCOM
Each kit can be exported as a standard GEDCOM file for importing into RootsMagic, Family Tree Maker, Ancestry, FamilySearch, or any compatible software.
In v4, any text you place in square brackets inside a kit name stays visible while you work in TreeScope, but those bracketed notes are removed automatically from GEDCOM exports to keep exported files cleaner.
Export options
| Button | Behaviour |
|---|---|
| ⬇ Export GEDCOM | Downloads the kit as a .ged file using the default filename. |
| ⬇ Export As… | Prompts for a custom filename before downloading. |
Default GEDCOM filenames follow the pattern kit_XXXXXXX_SubjectName.ged. Use Export As to override this with any name you choose.
Saving & Exporting JSON
JSON backups capture everything in your current session — all kits, all individuals, all notes, GEDmatch kit links, kit phase assignments, manual DNA data, cross-platform links, research statuses, verified and dismissed MRCA decisions, your project name, and your Me flag. Unlike GEDCOMs which export one kit at a time, a JSON backup captures the whole workspace.
Saving in the header
Click ⬇ Save JSON in the header. You'll be prompted for a filename each time — pre-filled with the last name you used, so saving an updated version is quick. To create a dated snapshot just edit the name before confirming.
Name your backup once at the start of a session, then re-save with the same name throughout. The browser auto-save handles in-session persistence, but the JSON file is your portable backup you can share or reload on any device.
Bulk Export
The Bulk Export tab lets you export multiple kits at once. Select kits using the checkboxes in the kit panel or the Select all visible option, then choose one of the three download options.
MRCA CSV exports in v4 also include additional workflow fields such as verification status and research notes, making it easier to move from TreeScope analysis into external tracking, documentation, or reporting workflows.
Download options
| Button | What it does |
|---|---|
| ↓ Download as ZIP | Bundles all selected kits into a single ZIP file. Each kit is a separate .ged file inside the archive, named kit_XXXXXXX_Name.ged. |
| ↓ Download Each Separately | Downloads every selected kit as its own individual .ged file one after another — useful if you want the files without packaging them in a ZIP. |
| ↓ Merge into One GEDCOM | Combines all selected kits into a single GEDCOM file. Each individual in the merged file is tagged with a NOTE identifying which source kit they came from. Use this when you want to load multiple match trees into a single genealogy program session. |
DNA suffix option
Before downloading, you can check Include DNA suffix on Gen 1 to append DNA data to the subject's name in the exported GEDCOM — total cM and largest segment are always included, and the GEDmatch kit number is appended for GEDmatch kits specifically. For kits from other testing companies, the internal TreeScope ID is used instead. You can also add a custom prefix text that appears before the kit number in the suffix.
Merge into One GEDCOM produces a single file containing floating trees for each of your selected matches — no connections between them, just each match's pedigree sitting independently in the same file. If you include a custom prefix on the DNA suffix, that prefix becomes a quick search term you can use in any genealogy program to jump straight to the home person of each match's tree.
Frequently Asked Questions
Why did my data disappear when I closed the browser?
TreeScope auto-saves your session to browser storage, so data should restore when you return. If it didn't, browser storage may have been cleared (private/incognito mode, browser settings, or clearing site data). For permanent storage, always export a JSON backup before ending a session.
Can I import data from Ancestry?
Not directly from match trees — Ancestry doesn't let you download other members' trees. However, you have two options: you can use the One2Tree Chrome extension to extract a match's tree from Ancestry and import the resulting CSV, or you can export your own Ancestry tree as a GEDCOM from your tree settings page and import it using the GEDCOM tile.
What WikiTree format does TreeScope support?
TreeScope supports the Compact Tree view, accessible from the dropdown menu on any WikiTree profile page. Select all the text on that page, copy it, and paste it into the WikiTree import tile.
Do I need DNA match data to use TreeScope?
No — DNA match data is optional enrichment. All tree import, fan chart, MRCA Finder, and export features work fully without it. Importing match data just adds cM values, segment sizes, and haplogroups to kits that already have trees, and unlocks the Sort by Highest cM option in the kit panel.
Can I enter DNA data manually without importing a match list?
Yes. Open any kit's Overview and find the DNA Info section. You can type in total cM, largest segment, X cM, mt haplogroup, Y haplogroup, and testing company. The data saves automatically as you type, triggers the 🧬 badge on the kit, and is included in the cM sort and relationship range estimator.
Can I connect a tree from one platform to a match from another?
Yes — use the 🔗 Link to kit button in the kit Overview. For example, if you find a GEDmatch match's tree on WikiTree, import both and link them. Linked kits share their ancestor data in MRCA analysis but are still compared independently against all other kits. See Cross-Platform Linking for full details.
Why does a kit show "1 individual"?
The match linked a GEDmatch kit but their tree contains only themselves — no ancestors were added. These kits have limited research value for MRCA analysis but are still tracked in your kit list. If you imported the match data using "Import all matches" mode, you may also see placeholder kits with 0 individuals — these are matches that don't have a tree at all yet. See the Match Placeholders section for how to work with them.
What does the match percentage mean in MRCA Finder?
The percentage is a confidence score based on how closely two ancestor records match across name, birth date, birth place, and death information. It is not a centimorgan value. Higher scores mean more data points align; lower scores may still be valid when trees are shallow or have limited dates.
What's the difference between Confirmed and Candidate?
A Confirmed result means TreeScope traced a complete, unbroken parent-child chain from both subjects up to the shared ancestor — every link in both paths is connected with no gaps. A Candidate means the ancestor appears in both trees but at least one path has a gap, usually because a tree doesn't go back far enough or a parent link is missing somewhere along the chain. The match may still be correct, but can't be fully verified from the tree data alone.
Can I use TreeScope on mobile?
Yes — TreeScope runs in any modern browser including mobile. The interface is optimized for desktop given the amount of data typically displayed, but all features are accessible on mobile.
Is my data shared with anyone?
No. All processing happens locally in your browser. Nothing is ever sent to any server. See the Privacy section below for full details.
Research Tips
Getting the most from import modes
- Use Import all matches when you want a full inventory of your DNA matches — even those without trees — so you can track the full picture in one place
- Use Import matches with trees only when you want to keep your kit list clean and focused on matches that have useful data for MRCA analysis
- After finding a tree for a placeholder match, use Merge into Kit with Tree to consolidate the DNA data without losing anything
Getting the most from MRCA Finder
- Start with All vs All to get a broad picture before diving into 1-to-1 comparisons
- Switch to Matrix view after running All vs All to spot patterns — a kit with hits across many other kits often points to a particularly well-documented ancestral line
- Lower the threshold to 40–50% when trees have inconsistent naming conventions or abbreviations
- Use the Compare to Me button after marking your own kit to quickly run every match against yourself
- Use Phase scope to limit comparisons to one side of your family once you've assigned maternal/paternal flags to your kits
Using Origin Mode
- A tree that shows a strong regional cluster — say, mostly Deep South with a few Midwest ancestors — can help you quickly narrow down which of your own lines might be the connection
- Use Origin Mode alongside MRCA Finder: after finding a candidate ancestor, check their Origin color in the fan chart to see if it fits your known geography
Working with the Fan Chart
- Grandparent line coloring makes it easy to see which branch of a tree has the most documented ancestors
- Use the X-DNA toggle to check whether a match could be on your X-DNA line before investing research time
- Export the PNG for use in research notes or sharing with other researchers
Session management
- Browser auto-save handles in-session preservation — you don't need to manually save every change
- Export a JSON backup at the start or end of a significant research session as a portable archive
- Use kit notes to record what you've found or what needs further research — these are preserved in both auto-save and JSON exports
- Edit the filename prompt when saving to create dated snapshots at key milestones (e.g.
treescope-backup-2026-04-07)
Privacy & Data
TreeScope is built on a strict local-first architecture. Here is exactly what happens with your data:
| Data type | Where it lives | When it disappears |
|---|---|---|
| Imported kits & individuals | Browser memory + auto-save (IndexedDB) | Auto-save persists until you clear browser data |
| Kit notes | Browser memory + auto-save (IndexedDB) | Same as above; also preserved in JSON exports |
| JSON backup files | Your device (downloads folder) | When you delete the file |
| GEDCOM export files | Your device (downloads folder) | When you delete the file |
No genealogical data, DNA match information, names, dates, places, or any personal information is ever sent to a server. TreeScope makes no network requests except loading the page itself, Google Fonts for typography, and optionally the feedback form submission (which only sends what you type into the feedback form — no genealogical data is included).
DNA match data is sensitive. TreeScope's local-first design means you can work with confidence that your research data and your matches' family information stays on your device.