Why You Should Actually Read Salt Lake Tribune Obituaries in Full
Most people skip past them. They scan for a date of death and maybe one name, then move on. I have spent years pulling these out of archives and cross-referencing them with census records, land patents, and probate files. The obituaries themselves are where the actual story lives, buried under five or six paragraphs of survived-by lists. The Salt Lake Tribune has been publishing obituaries since 1871. That gives you a continuous paper trail of Utah residents that most genealogists never touch. The digital archive goes back to 1997, but the microfilm at the FamilySearch Library in Salt Lake City covers everything before that. Here is how I actually use these obituaries when I am trying to piece together family histories that official records don't tell you.
Uncovering The Hidden Stories Of Salt Lake Tribune Obituaries A Journey Through Time And Tributes
I start by pulling the exact URL or microfilm reel number for the date range I am working. The Tribune's online archive requires a subscription, but if you have a library card from Salt Lake County or Weber County, you can often get free access through the public library portal. Without that, you are looking at FamilySearch microfilm or visiting the Deseret News Archive, which sometimes indexes Tribune obits retrospectively. The first thing you need to know is that Tribune obituaries changed format over time. Before about 2003, most were written by the family and submitted as plain text. After that, the paper started using more standardized templates, often pulled from funeral home press releases. The pre-2003 ones tend to contain actual biographical detail. The later ones read like marketing copy for a funeral service. Knowing this saves you hours of reading filler. When I find a useful obituary, I extract four things immediately: the full list of survivors, the employer or occupation line, the place of birth or origin, and any military service notation. Those four fields give you enough to anchor a person in at least two other record sets. The survivors list alone can connect you to siblings, spouses, and children who appear in no other indexed source.
The Practical Method I Use
My process is straightforward and takes about twelve minutes per obituary once I am set up. First, I open the obituary in a browser tab and paste the text into a plain text file named by date and full name. I do this because screenshots and PDF captures are impossible to search later. A simple .txt file with the name in the filename lets me grep the whole archive in seconds. Second, I pull the surviving family members and check each one against the Utah Digital Newspapers project and Ancestry's Utah collection. Siblings and children often have their own obituaries that reference the original one. That cross-reference chain is how I built a three-generation timeline for a family in Box Elder County without touching a single cemetery record.
Get the Full Details
Third, I look for place names that are not Utah. The Tribune covers a fairly tight geographic area, so when someone died in Phoenix or Denver or California, that usually means they had migrated at some point. That migration pattern shows up again in census records, and it is a reliable way to break through brick walls that the Utah records alone cannot solve.
What Most People Miss
Obituaries in the Tribune sometimes contain errors. Funeral homes submit them, and funeral directors are busy people. I have seen at least a dozen cases where the birth year was off by three to five years, or where a surviving spouse's name was listed wrong because two families with the same surname shared a funeral home. Always verify against the actual vital records before you lock anything into your family tree. The other thing people miss is the deathplace line. If the obit says the person died in a hospital in Salt Lake City, check which hospital. Intermountain Hospital closed in the 1990s. LDS Hospital is now University Hospital. The distinction matters when you are trying to narrow down an exact location for a death certificate request, and the death certificate itself is where the final confirmation lives. I encountered a specific edge case a few years ago that illustrates this well. I was researching a woman who died in 1954. The Tribune obit listed her as survived by a sister named Martha, but Martha did not appear in any census record under that name. I spent two weeks looking for her before I realized the obituary had misprinted "Martha" instead of "Martz," which was actually her nickname. The census record used "Martz E." The sister's full name was in a probate file, but only after I figured out the spelling error. Tribune OCR does not catch handwritten or poorly typeset nicknames, so always check the original image, not just the digitized text version.
Advanced Tips for Digging Deeper
If you want to go further, start pulling the associated death certificates from the Utah Division of Vital Records. An obituary gives you the date of death and the funeral home. The death certificate gives you the exact street address, the informant's name, and the mother's maiden name. Those three fields combined with the survivors list from the obit usually unlock the next generation within an hour. The probate records are another underused source. The Tribune sometimes publishes brief notices about estate settlements alongside the obituary, especially for people who owned property in Salt Lake County. Those notices are free to search through the county clerk's online docket system and they list heirs by relationship, which is more precise than the survivor lists in obituaries. For military veterans, check the Salt Lake Tribune's Veterans Day coverage. They occasionally ran longer profiles on deceased service members that contained details not found in the standard obit. These profiles are harder to locate because they are filed under news rather than obituaries, so searching by service branch and rank plus the word "Tribune" in the newspaper database is the most reliable path.
What This Approach Cannot Do
Let me be clear about the limitations. The Tribune only covers residents of the Salt Lake City metropolitan area and surrounding valleys. If your ancestor lived in Moab, St. George, or rural Piute County, their obituary might have run in a different paper or not at all. I have hit dead ends multiple times where a person died in Utah but the family chose a paper in Idaho or Nevada for the notice. The digital archive only goes back to 1997. Anything before that requires microfilm access, and not all branches of the Utah Public Library system have complete Tribune runs. The FamilySearch library in Salt Lake City does, but you have to go in person or request a remote lookup, which costs time and sometimes money depending on the access arrangement. Another hard limitation: the Tribune stopped printing full obituaries in many cases around 2015 and switched to shorter funeral home summaries. The detailed biographical pieces did not disappear entirely, but they became less common. If you are researching recent deaths, you may find only a paragraph or two of actual content, which severely limits what you can extract.
For those cases, the alternative is to look at the funeral home websites directly. Many funeral directors still publish longer memorial pages that the newspaper excerpts or cuts down. Cross-referencing the funeral home page with the Tribune summary usually recovers the missing detail, but you need both sources to get the full picture.
Building a Working Collection
I organize my obituary findings into a simple spreadsheet with columns for date, full name, birth year, death year, survivors list (brief), employer, birthplace, and archive location. The archive location column notes whether the obit is online, on microfilm at FamilySearch, or at a specific library branch. This makes it fast to find a record again when I need to double-check something. I also keep a separate folder for images of the original obituary page. The OCR from any digitized newspaper archive can be wrong, especially with older typography or faded ink. A screenshot or PDF of the actual page is worth more than a clean text extraction when you are dealing with ambiguous names or dates. If you are starting this work for the first time, begin with one surname and one generation. Pick a great-grandparent or great-great-grandparent and pull every Tribune obit you can find for that family line over a ten-year span. You will quickly see patterns in how the obituaries are written, which helps you read between the lines faster. The method becomes intuitive after about twenty obituaries, and the time per record drops from fifteen minutes to under five.
Where to Find the Resources
The Salt Lake Tribune archive is accessible through several paths. The newspaper's own site requires a paid subscription, but many Utah public libraries offer free access with a valid card. The Deseret News Archive at newsevents.utah.edu sometimes mirrors Tribune obituaries for dates they covered in their own cross-references. FamilySearch has the microfilm collection for the pre-1997 runs, and the Utah Digital Newspapers project at utahdiginewspapers.org has a smaller but growing set of Tribune issues. For the salt lake tribune obituaries specifically, the best starting point is the FamilySearch catalog. Search for "Salt Lake Tribune (Salt Lake City, Utah)" and you will get the microfilm numbers for each year. The call numbers are listed with the date ranges, so you can pull exactly what you need without browsing through irrelevant reels. The probate and death certificate records are available through the Utah State Archives and the individual county clerks. Salt Lake County has an online docket search that is free and covers the last thirty years. Older records require a request form, but the turnaround is usually two to three weeks by mail.
Working through these records takes patience, but the payoff is real. I have found ancestral connections that no census or vital record alone could reveal, all because I took the time to read the obituaries thoroughly and cross-check them against the supporting documents. The stories are in the text if you know where to look.
