Keep the original as the master
Start from a fresh UTF-8 GEDCOM export made by your genealogy application. Keep that original outside the editing workflow. A subset is a deliberate selection for a particular recipient, not a replacement for the complete archive, source documents or research notes. Check the exported version and encoding before importing.
This workbench reads the hierarchy and cross-reference structure locally. It does not connect to Ancestry, FamilySearch or another account, and external media paths are never opened. A readable path in the source is simply text evidence that another application may use; it does not mean that a photograph has been included in your download.
Choose a family-link scope
Select a focus individual and a distance from zero to six family links. Distance zero includes that person. Each additional step follows membership in a family record, which can reach parents, partners or children. This is not a count of biological generations, and it should not be described as a proven ancestry relationship.
Review the prepared person list and family records. A source can have multiple parent families, adopted relationships, cycles or one-sided references. The traversal is bounded and avoids repeating people. Unsupported or out-of-subset pointers are removed from the new GEDCOM and listed in the audit instead of being resolved by guesswork.
Test the handoff separately
Download the subset and its audit together. Import the GEDCOM into a new test tree in the receiving application and compare a few important family links, names and uncertain dates. A successful structural parse is not a guarantee that every custom convention has the same meaning in another genealogy program.
Keep a note of the focus ID, distance and privacy policy used for the export. If the recipient needs a wider branch, generate a new subset from the master rather than repeatedly expanding an already reduced file. The original records and external documents remain the source of record for later research.