Folklore

Getting a GEDCOM onto an iPhone, and what private actually means for a family tree

You have a .ged file and an iPhone. Two things usually go wrong. The file will not import, and you cannot tell what any app actually does with your relatives' details once it has them.

This page covers both. The format half explains what GEDCOM is and why files travel badly between programs. The privacy half explains the four different things people mean by private, and what Apple says iCloud does and does not protect.

A GEDCOM export imports imperfectly because 5.5.1 files are not valid 7.0 files, and encodings and custom tags differ. On privacy, syncing through your own iCloud means the developer holds no copy, but that is not end-to-end encryption unless Advanced Data Protection is on.

What a GEDCOM file is

GEDCOM is the file format genealogy programs use to hand data to each other. It is published by FamilySearch, a service of The Church of Jesus Christ of Latter-day Saints.

Version 7.0 is the released current specification. Versions 5.5 and 5.5.1 are described on the specification index as currently in use in the marketplace, which is a frank way of saying the old format never went away. The 7.0 specification dates 5.5.1 to a draft from November 1999 and states that 5.5.1 files are, in general, not valid 7.0 files.

A .ged file is plain text. Each line is a level number, an optional cross-reference, a tag, and an optional value. You can open one in a text editor and read it.

Why exports import imperfectly

Character encoding is the biggest culprit. GEDCOM 7.0 only uses UTF-8. The specification notes that previous versions allowed multiple encodings, defaulting to ANSEL, an old library character set. An ANSEL file read as UTF-8 gives you mangled accented letters in names.

Custom tags are the second. Extensions may introduce new structures, and the spec warns that data in extension tags will not be interpreted by other systems correctly. Anything one vendor invented can be dropped on import.

Photos are not inside the file. A multimedia record refers to external digital files, so moving the .ged without its image folder loses the pictures. The spec defines GEDZIP for bundling media, which is why some exports arrive zipped. Finally, the spec says of its own sourcing model that it is known to be insufficient for some use cases, so citations often arrive as plain text.

The file you can see but cannot select

A common experience: the .ged sits in iCloud Drive, you tap Import, and the file is greyed out.

The mechanism is Apple's type system. Apps declare the file types they handle using Uniform Type Identifiers, either as exported types when the app is the canonical source of the format, or imported types when the format is defined elsewhere. Apple also warns that a document type must conform to public.data or the system cannot tell that a stored item has that type.

There is no system-provided identifier for GEDCOM, so each app declares its own. A picker only offers files matching the types the app asked for. I have not inspected any specific app's configuration and cannot say which apps declare what.

Workarounds that usually work

Use the share sheet instead of the picker. Find the file in Files or Mail, tap Share, and look for the app. Share routing and picker filtering are separate paths.

Make sure the file is actually downloaded. A file in iCloud Drive that has not come down to the device can behave oddly in a picker. Open it once in Files, or copy it to On My iPhone.

Zip it, or rename it to .txt if the app accepts text. Where your desktop program offers GEDZIP, re-export that way so photos travel with the data. Large files are a separate problem: in a public GEDitCom discussion thread a user reported being quite unable to get their GEDCOM in while the bundled sample loaded fine, and the developer's advice was to test with the free version before paying.

Four different things people mean by private

On device only. The data never leaves the phone, and is lost with the phone unless backed up.

Synced through your own iCloud. The data sits in your Apple account and the app vendor has no copy.

Stored on a company's server, where the vendor holds the data and can read it subject to its policy. Or published to a searchable public tree, where other users can find, copy and build on it.

These are genuinely different arrangements, and marketing language tends to flatten all four into one word.

What iCloud does and does not protect

Apple publishes the detail in its iCloud data security overview. Under standard data protection everything is encrypted in transit and on Apple's servers, and Apple holds the keys for most categories. Fifteen categories are end to end encrypted by default, including Health, Messages in iCloud, and Passwords and Keychain. iCloud Drive, Photos, Notes and iCloud Backup are not among them by default.

Advanced Data Protection raises that to twenty-five categories and adds iCloud Drive, Photos, Notes and Backup. Apple states that with it enabled, third-party app data in iCloud Backup and in CloudKit encrypted fields and assets is end to end encrypted. Apple's page does not say that applies without it. Mail, Contacts and Calendars are never end to end encrypted, and metadata such as timestamps stays under standard protection either way.

Folklore's App Store listing says the tree is stored on your device and synced through your own private iCloud, that sharing is private iCloud sharing with no accounts and no public links, and that the developer cannot see it. Those are the listing's claims, not something verified here. What the mechanism supports is that the data sits in your Apple account rather than a vendor's. Syncing through iCloud is not the same as end to end encryption unless Apple says that category is.

Why family trees are a special case, and being fair to the big services

The data is mostly about other people. Your living cousins did not consent and will probably never know. The fields are also the classic identity verification set: mother's maiden name, date of birth, place of birth.

Uploads are close to permanent. Ancestry's guidance notes that files saved from your tree into other trees while it was public stay visible there after you make it private. On FamilySearch, a person's record becomes public once a death date is added.

The large platforms are not careless about this. Ancestry hides living people even in public trees and offers searchable-private and unsearchable-private settings. FamilySearch keeps living people visible only to the person who entered them. The tradeoff is real on both sides: a public shared tree gets you record hints and other researchers' work, a private local tree gets you neither. Pick knowing which deal you signed.

Questions

Which GEDCOM version should I export?

If the receiving app states a version, match it. Otherwise 5.5.1 is the safest for compatibility, since gedcom.io still describes 5.5 and 5.5.1 as currently in use in the marketplace, while 7.0 is the released current specification and handles accented characters more reliably because it requires UTF-8.

Why is my .ged file greyed out in the file picker?

Most likely the app has not declared GEDCOM as a file type it handles. iOS pickers only offer files whose Uniform Type Identifier matches what the app asked for, and there is no system-provided identifier for GEDCOM. Try the share sheet instead, make sure the file has downloaded from iCloud, or zip it.

Why did the names come through with strange characters?

Almost certainly a character encoding mismatch. GEDCOM 7.0 requires UTF-8, but the specification notes that earlier versions allowed several encodings and defaulted to ANSEL. An ANSEL file read as UTF-8 mangles accented letters. Re-exporting as UTF-8 from the original program usually fixes it.

Where did my photos go?

They were never inside the .ged. The specification says a multimedia record refers to external digital files, so the file holds references, not images. Export as GEDZIP if your program offers it, or move the media folder alongside the .ged.

Is iCloud sync the same as end to end encryption?

No. Apple encrypts all iCloud data in transit and at rest, but only fifteen categories are end to end encrypted by default. With Advanced Data Protection on, that rises to twenty-five, and Apple states that third-party app data in CloudKit encrypted fields and assets is end to end encrypted in that case. Apple's page does not say the same applies without it.

If I put my tree on a public site, can I take it back?

Not reliably. Ancestry's own guidance says files saved from your tree into other trees while it was public remain visible in those trees after you make it private. On FamilySearch, a person's record becomes public once a death date is added. Decide before you upload, not after.

Sources read at origin: gedcom.io, gedcom.io/specs, the FamilySearch GEDCOM 7.0 specification at gedcom.io/specifications/FamilySearchGEDCOMv7.html, Apple's iCloud data security overview at support.apple.com/en-us/102651, Apple's Defining file and data types for your app, the Folklore App Store listing (id6803038052), the MobileFamilyTree 11 listing (id6480510866), and a public geditcom-ii-discussions thread. Not verified: support.ancestry.com and articles.familysearch.org returned 403 to direct fetch, so the Ancestry and FamilySearch statements are reported from indexed summaries of those pages rather than read first hand. The greyed-out file complaint was not found in App Store reviews; the mechanism is sourced from Apple's type documentation, and the cited user thread reports import failure rather than greying. Folklore's source code was not read, so every claim about the app is attributed to its App Store listing. No maximum GEDCOM file size is stated here because no listing read gave one.

Try Folklore

Get Folklore on the App Store

More about Folklore ยท Contact us