Comprehensive Guide To LDS Temple Abbreviations And Codes For 2026 Genealogy Records
While the term abbreviations may occasionally surface in medical contexts or academic references to Temple University, in the specialized field of genealogical research and family history, temple abbreviations refer almost exclusively to the shorthand codes used by The Church of Jesus Christ of Latter-day Saints (LDS) to identify specific temple locations and religious ordinances within historical and digital records.
Understanding these codes is essential for any researcher, archivist, or family historian operating in 2026. As the number of dedicated temples worldwide continues to expand—surpassing the 350-temple milestone this year—the complexity of these identifiers has evolved. Modern digital systems like FamilySearch have largely transitioned to full-text names, but millions of microfilmed records, legacy GEDCOM files, and mid-20th-century extraction records rely on a dense system of three-to-five-letter abbreviations. Mastery of this nomenclature ensures data integrity and prevents the misattribution of vital ordinance work.
The Evolution of Temple Coding Systems in 2026
The methodology for abbreviating temple names has undergone three distinct phases. Originally, in the 19th and early 20th centuries, abbreviations were informal and often varied by the clerk's personal preference (e.g., "SL" or "S.L." for Salt Lake). By the mid-20th century, as the Church began utilizing early computational systems for the International Genealogical Index (IGI), a standardized set of four-letter codes was established.
In 2026, we find ourselves in the "Universal ID Phase." Modern APIs (Application Programming Interfaces) now prioritize Unique Resource Identifiers (URIs), but the historical abbreviations remain the primary "keys" found in printed pedagogical materials and legacy database exports. For researchers working with physical family Bibles or older printed pedigree charts, these abbreviations are the only link to the geographic origin of the record.
Current Standards for Record Management
Contemporary genealogical standards in 2026 dictate that while abbreviations may be used for internal data storage, public-facing reports should expand these to full names to maintain clarity. However, when performing "Data Cleaning" on legacy files, knowing that "LOGA" refers to the Logan Utah Temple and not a location in Logan, West Virginia, is critical for geographic accuracy.
Master Reference Table: Historic and Modern Temple Abbreviations
The following table provides the most frequently encountered temple abbreviations found in genealogical databases and historical extraction records. This list focuses on high-traffic historical sites and common 2026 record identifiers.
| Abbreviation | Temple Name | Location | Primary Usage Era |
|---|---|---|---|
| ALBE | Cardston Alberta Temple | Alberta, Canada | 1923–Present |
| ARRI | Rexburg Idaho Temple | Idaho, USA | 2008–Present |
| AZ | Mesa Arizona Temple | Arizona, USA | 1927–Present |
| BAVA | Freiberg Germany Temple | Saxony, Germany | 1985–Present |
| BERN | Bern Switzerland Temple | Münchenbuchsee, Switzerland | 1955–Present |
| BOIS | Boise Idaho Temple | Idaho, USA | 1984–Present |
| CHIC | Chicago Illinois Temple | Illinois, USA | 1985–Present |
| DENVER | Denver Colorado Temple | Colorado, USA | 1986–Present |
| HAWA | Laie Hawaii Temple | Hawaii, USA | 1919–Present |
| IFID | Idaho Falls Idaho Temple | Idaho, USA | 1945–Present |
| JOST | Johannesburg South Africa | Gauteng, South Africa | 1985–Present |
| LOND | London England Temple | Surrey, England | 1958–Present |
| LOGA | Logan Utah Temple | Utah, USA | 1884–Present |
| LOSA | Los Angeles California Temple | California, USA | 1956–Present |
| MANTI | Manti Utah Temple | Utah, USA | 1888–Present |
| NAUV | Nauvoo Illinois Temple | Illinois, USA | 1846 / 2002 |
| NZEA | Hamilton New Zealand Temple | Hamilton, New Zealand | 1958–Present |
| OAKL | Oakland California Temple | California, USA | 1964–Present |
| OGDO | Ogden Utah Temple | Utah, USA | 1972–Present |
| PROV | Provo Utah Temple | Utah, USA | 1972–Present |
| SLAKE | Salt Lake Temple | Utah, USA | 1893–Present |
| STGE | St. George Utah Temple | Utah, USA | 1877–Present |
| SWISS | Bern Switzerland Temple | Bern, Switzerland | Historical Variant |
| WASH | Washington D.C. Temple | Maryland, USA | 1974–Present |
Medical Abbreviations 2024 / Updated 2025 Guide & Test Bank / Score 100 ...
Technical Specification: Ordinance Type Abbreviations
Beyond the location of the temple, researchers must also decode the ordinance codes that frequently accompany temple abbreviations. These specify the nature of the religious rite performed. In 2026, standardized genealogical software uses the following single-letter or short-string codes:
Common Ordinance Identifiers
B or BAP: Baptism This indicates the date and location of a proxy baptism. In historical records, this is often the first date listed alongside a temple abbreviation.
C or CONF: Confirmation Usually performed immediately following baptism, this code is essential for verifying a completed record in 2026 standards.
I or INIT: Initiatory This refers to the preliminary ceremonies preceding the endowment. In records from the late 20th century, these were often grouped under the endowment date but are now tracked individually.
E or END: Endowment The most common code found in temple records. When a record says "E 12 MAY 1950 LOGA," it confirms the endowment was completed in the Logan Utah Temple on that date.
SP: Sealing to Parents This code indicates the sealing of a child to their parents, creating a multi-generational link in the genealogical tree.
SS: Sealing to Spouse This denotes a marriage sealing. It is often accompanied by the name of the spouse and a specific temple code, which may differ from the individual's endowment temple.
Comparison: Digital Full-Text vs. Legacy Shorthand
As we navigate 2026, a tension exists between the efficiency of shorthand and the necessity of data clarity. Professional genealogists often debate the merits of each.
Legacy Shorthand (e.g., SLAKE, MANTI)
- Pros: Significant space-saving in printed charts; faster data entry for high-volume extraction work; historical consistency with 20th-century microfiche.
- Cons: High barrier to entry for novice researchers; ambiguity between newer temples with similar names (e.g., Saratoga Springs vs. Salt Lake); lack of machine-readability for non-specialized AI tools.
Digital Full-Text (e.g., Salt Lake Temple)
- Pros: Zero ambiguity; 100% SEO and search-friendly; accessible to international researchers who may not know English-based shorthand.
- Cons: Excessive character counts in narrow-column genealogical reports; requires robust database structures to handle long-form strings.
Strategic Guide to Identifying Obscure Abbreviations
If you encounter an abbreviation not found in standard 2026 databases, follow this systematic identification process:
- Analyze the Date of the Record: Context is paramount. If the record is dated 1890 and uses the abbreviation "LOG," it almost certainly refers to Logan, as only a handful of temples were operational then (St. George, Logan, Manti).
- Cross-Reference with Geographic Residency: Examine where the individual lived at the time of the record. Before the era of jet travel, individuals typically traveled to the temple nearest their residence. A person living in Arizona in 1930 using an abbreviation "AZ" is logically tied to the Mesa Arizona Temple.
- Check for Clerk-Specific Variants: In 19th-century "Endowment House" records, you may see "EH." This was not a temple but a temporary structure in Salt Lake City used before the Salt Lake Temple was completed.
- Verify via the 2026 Global Temple Portal: Use the official Church chronological list to see which temples were dedicated just prior to the record's date. If a record from 2025 uses "DESE," you can identify it as the Deseret Peak Utah Temple.
Expert Insight: The Impact of the 2026 Temple Expansion
With the unprecedented acceleration of temple construction over the last five years, the "old guard" of four-letter codes has become insufficient. We are seeing a shift toward 5-character alphanumeric codes in backend systems to account for the sheer volume of new locations in Africa, Asia, and Latin America.
For instance, whereas "LOND" was sufficient for decades, the addition of multiple temples in the United Kingdom requires more specific identifiers. As a Senior Strategist in this niche, I recommend that researchers always include the Temple ID Number (a unique numerical string assigned by FamilySearch) in their private notes to "future-proof" their research against further changes in nomenclature.
Frequently Asked Questions
What does the abbreviation "SL" mean in older family records?
"SL" almost universally stands for the Salt Lake Temple in Salt Lake City, Utah. It is perhaps the most common abbreviation in LDS genealogy due to the temple's long history and high volume of records since 1893. In some very rare early records, it might refer to the "Salt Lake City 19th Ward," but the context of an ordinance date nearly always confirms the temple.
Are temple abbreviations the same as airport codes?
No, although they occasionally overlap (e.g., "LAX" for Los Angeles and "LOSA" for the Los Angeles Temple). Temple abbreviations are a proprietary system used for ecclesiastical record-keeping and do not follow IATA (International Air Transport Association) standards.
How do I handle abbreviations for temples that have been renamed?
In 2026, the standard practice is to use the current name of the temple while noting the historical name in the metadata. For example, the "Swiss Temple" is now officially the "Bern Switzerland Temple." Legacy abbreviations like "SWISS" should be updated to "BERN" or the full name in modern databases.
Why do some records show "E.H." instead of a temple abbreviation?
"E.H." stands for the Endowment House, which operated in Salt Lake City from 1855 to 1889. It was used to perform ordinances before the Salt Lake Temple was finished. It is treated with the same authoritative weight as a temple in genealogical research.
Where can I find a complete list of 2026 dedicated temples?
The most accurate, real-time list is maintained on the official Newsroom of The Church of Jesus Christ of Latter-day Saints and within the FamilySearch "Helper" dashboard. These platforms provide the most current status—whether a temple is "Announced," "Under Construction," or "Dedicated."
Advanced Research and Data Integrity
When managing high-volume genealogical databases in 2026, the accuracy of temple abbreviations is not merely a matter of tradition but of technical necessity. As AI-driven research tools become more prevalent, providing these tools with standardized, unambiguous location data prevents the "hallucination" of family links and ensures that the digital legacy of the 19th and 20th centuries is preserved accurately for future generations.
If you are a professional researcher or a family historian, auditing your legacy files for non-standard abbreviations is a recommended task for 2026. Replacing ambiguous three-letter codes with standardized identifiers ensures that your work remains compatible with the global genealogical infrastructure.
