EAD Metadata Standard Explained: What Archivists Need to Know

EAD — Encoded Archival Description — is the international standard for structuring archival finding aids in a machine-readable XML format. Maintained jointly by the Library of Congress and the Society of American Archivists through its Technical Subcommittee for Encoded Archival Standards, EAD is the common language archives use to encode and share archival descriptions across systems and institutions.

What the EAD standard does

EAD uses XML to encode archival descriptions in a consistent, hierarchical structure. Rather than a finding aid locked in a PDF or Word document, EAD wraps your content in standardised XML tags — at collection level, series level, and item level — that software can process, search, and exchange. This structure reflects how archival collections are actually organised: a fonds contains series; series contain files. EAD encodes that hierarchy directly into the document, making archival descriptions portable and reusable. Key EAD elements include the <eadheader>, which carries administrative metadata, and nested tags that encode scope and content, dates, and repository details. Using XML as the encoding mechanism means an EAD document is both human-readable and machine-readable — interoperability between repositories is built in.

An important distinction: EAD encodes archival description — it does not generate it. The intellectual work of description comes first. An archivist must establish arrangement, determine provenance, define scope and content, and make descriptive judgements about a collection before any of that work can be expressed in EAD. Encoding is the final step, not the starting point. Without the underlying descriptive decisions — how to represent hierarchy, what level of detail to provide, how to handle uncertainty — an EAD document is an empty structure.

To illustrate how archival description maps into EAD3, consider a small local authority archive:

• Collection level (<archdesc>) — “Westbury Parish Council Records, 1890–1962” — scope and content note, provenance, access conditions, and administrative history sit here.
• Series level (<c01>) — “Meeting Minutes, 1890–1955” — describes the series as a whole, its date range, and its relationship to the creating body.
• Item level (<c02>) — “Minutes of Parish Meeting, 14 March 1923” — the individual record, with its own date, extent, and any specific access notes.

Each level inherits context from the level above. The EAD3 schema enforces this nesting, so the encoded finding aid preserves the same hierarchical relationships the archivist established during description.

EAD 2002 vs EAD3

EAD 2002 relied on a DTD (Document Type Definition) for validation and remained the dominant standard for over a decade. EAD3, released in 2015 by SAA and the Library of Congress, replaced the DTD with an XML schema, improving structural validation and aligning more closely with modern metadata standards including ISAD(G), DACS, and MARC. The EAD3 schema is maintained on GitHub by the technical subcommittee, and version EAD3 1.1 is the current release.

EAD3 handles multilingual and non-Western content better, separates content from presentation more cleanly, and is where new development is focused. For any new project, implement EAD3. Existing EAD 2002 archives can continue operating, but migration to EAD3 is advisable before integrating with modern aggregators. Open-source platforms such as AtoM and ArchivesSpace both support EAD3 import and export.

When your archive needs EAD

Not every archive must produce EAD immediately, but these situations make it essential for an archivist:

• Funder requirements — many digitisation grants expect EAD-compliant finding aid outputs.
• National aggregators — Archives Hub ingests EAD to make archival collection records searchable across institutions.
• Inter-institutional sharing — contributing to a shared catalogue or transferring records to a national repository requires EAD as the standard for encoding archival finding aids.

For context on broader cataloguing practice, see our guide to archival cataloguing standards and the complete guide to archival cataloguing. If your EAD output is linked to a funded digitisation project, our guide to NLHF metadata standards including ISAD, EAD3, and Dublin Core explains what funders expect.

---

The Archiver exports directly in EAD3 format, producing compliant finding aids without requiring an archivist to write a single XML tag manually. It is the practical way to implement the EAD standard from day one. See the features overview or our dedicated page for archivists. Request early access to try it on your own collection.