You open a photo album and find a handwritten note, but the phone that held the last conversations with a loved one is already locked, the app no longer updates, and the backup you thought was safe has been overwritten. In the weeks after a death, the urgency to keep those messages can clash with the reality that digital services change, devices are replaced, and data can disappear without warning. A systematic approach to locating, exporting, and storing the texts can prevent that loss and keep the words accessible for future generations.
Digital memories are more fragile than they appear
Most messaging services store data on remote servers that are subject to policy changes, subscription lapses, or complete shutdowns. Even when a service remains active, the device that holds the local copy can be wiped during a factory reset, or the operating system may no longer support the app. Links that once pointed to media files can break as servers retire old content. Because the format of the stored messages is often proprietary, a simple screenshot does not guarantee long‑term readability. Recognizing these vulnerabilities early helps you prioritize the preservation steps before the opportunity disappears.
A practical way to gauge risk is to check the service’s public roadmap or recent news for any announced discontinuations. If the platform is still operational, consider the age of the device used to receive the messages; older phones may no longer receive security updates, increasing the chance of data loss through hardware failure.
Conduct a quick audit of what exists
Start by listing every channel through which the deceased exchanged text: built‑in SMS, iMessage, WhatsApp, Facebook Messenger, Signal, and any email‑to‑SMS gateways. Note the device(s) that hold local copies, the cloud backups linked to each account, and any third‑party archiving services that may have been used. A simple spreadsheet with columns for platform, device, backup method, and last access date provides a clear overview and prevents duplicate work later.
Checklist:
1. Identify all messaging apps used.
2. Record the primary device(s) for each app.
3. Locate associated cloud backups (iCloud, Google Drive, etc.).
4. Note any export tools the app offers.
5. Mark the last time each backup was verified.
Download and export data from each platform
Most services provide a data‑download feature in their settings or privacy sections. For iMessage, enable iCloud backup and then use a Mac to export the conversation archive. WhatsApp offers a “Export Chat” option that creates a .zip file containing a .txt transcript and any attached media. Facebook Messenger can be accessed through the Facebook “Download Your Information” tool, where you select the “Messages” category. Signal requires a manual copy of the encrypted database from the device, which can then be exported via the desktop client. Follow each platform’s instructions carefully and keep the exported files in a temporary folder until they are converted and filed.
Tip: When exporting, choose the highest‑resolution media options available to preserve image and video quality.
Convert proprietary formats to lasting ones
Exported files often arrive as .zip, .json, or app‑specific database files. Convert text to plain UTF‑8 .txt or .pdf, which are widely supported and can be opened without the original app. Media files should be saved as .jpeg for photos, .png for graphics, and .mp4 for videos, using the original resolution. For database files, use open‑source tools that can read the format and output a .csv or .txt transcript. Keeping a copy of the original export is still useful for verification, but the converted files become the primary archive for long‑term access.
A simple conversion workflow:
1. Unzip the archive.
2. Open the .json or database with a viewer.
3. Export the text to .txt.
4. Rename media files with descriptive timestamps.
5. Store the originals in a separate “raw” subfolder.
Name and file the data consistently
A clear naming convention prevents confusion when the archive grows. Use a structure that includes the deceased’s name, the platform, and the date range of the conversation, for example: “Doe_John_WhatsApp_2020-03-15_to_2022-07-01.txt”. Organize the files in a folder hierarchy that mirrors the broader family archive: top‑level “Memories”, then “Messages”, then subfolders for each platform. Include a short README file that explains the folder layout and any conversion steps taken. Consistency makes it easier for other family members to locate specific exchanges later.
Example folder tree:
Memories/
Messages/
SMS/
Doe_John_SMS_2018-05-10.txt
WhatsApp/
Doe_John_WhatsApp_2020-03-15_to_2022-07-01.txt
Handle accounts after death
Most platforms have a process for deceased users, often called “legacy contacts” or “account memorialization”. For iMessage, you can request the removal of the Apple ID and retrieve the iCloud backup with a court order or a death certificate. WhatsApp requires the phone number to be deactivated; the backup can be extracted before the SIM is cancelled. Facebook allows you to designate a legacy contact who can download the data. Signal does not retain messages on its servers, so the only copy is the one stored on the device. Review each service’s policy, gather the required documentation, and submit the request promptly to avoid automatic data deletion.
If the platform does not offer a formal process, consider contacting their support team directly and providing proof of death to gain temporary access for export.
Back up and maintain the archive
Store the final files in at least two separate locations: one physical medium such as an external hard drive or USB flash drive, and one cloud storage service that you trust for long‑term retention. Rotate the physical media every few years to avoid degradation, and verify the cloud backup annually by downloading a random file. Schedule a yearly review of the archive; during that time, repeat the export process for any new messages that may have been added before the account was fully closed. This habit prevents a decade‑long scramble when the next generation needs the material.
Annual maintenance checklist:
1. Verify integrity of physical backup.
2. Confirm cloud backup access.
3. Export any newly added messages.
4. Update naming conventions if needed.
5. Document changes in the README.
Worth remembering: Treat digital conversations as any other family document: locate them early, export in open formats, name them clearly, and keep at least two backups—one physical and one cloud—while reviewing the collection each year.
Common questions
What format or settings should I use?
Export text as plain UTF‑8 .txt or as .pdf, and save photos as .jpeg, graphics as .png, and videos as .mp4; choose the highest resolution offered to preserve original quality.
How should I label the files or items?
Use a consistent pattern that includes the deceased’s name, platform, and date range, such as “Doe_John_WhatsApp_2020-03-15_to_2022-07-01.txt”, and place them in a folder hierarchy that mirrors the overall family archive.
How many backup copies should I keep?
Keep at least two copies: one on a physical medium like an external drive and one in a reputable cloud storage service, and verify both at least once a year.