How to Archive One Diary Entry with Text, Photos, and Audio Together
To keep one diary entry’s writing, photos, and audio together outside an app, give the entry a stable ID, keep its original media files in one entry folder, and make a readable index that names every file and explains its connection to the entry. A small manifest adds a checkable record of which attachment belongs where. The example below shows a format-neutral way to do this; it does not depend on a universal archive standard or a particular app.
What makes a mixed-media entry hold together?
A folder can keep files near each other, but proximity alone does not explain what they are or whether a photo belongs to the entry or is an unrelated copy. The relationship should be recorded in readable text. At minimum, preserve:
A stable entry ID that does not change when you rename or move files.
The entry’s date and time, including its time zone or UTC offset.
The written entry, in a form you can open without the original diary app.
Each original photo and audio file, with its exact filename and a short description.
A manifest listing the entry ID and the attachments assigned to it.
The National Archives’ personal digital memories brochure recommends selecting important personal files, exporting selected photos and audio, giving files descriptive names, arranging them in a folder structure, and writing a brief description of that structure. For audio, it also advises recording export metadata such as the export date. These are practical organizing suggestions, not a prescribed diary format ([National Archives, *Preserving Your Digital Memories*](https://www.archives.gov/files/preservation/formats/pdf/preserving-your-digital-memories.pdf)).
Example: one entry, three kinds of material
The following fictional entry describes a rainy walk beside a harbor. Its identifier, file names, time and captions are illustrative; they are not records of an actual event.
Archive root: `DiaryArchive/entries/2026/E-7F3A91/`.
Readable entry: `index.md`; attachment inventory: `manifest.csv`.
Original attachments: `media/IMG_4812.JPG`, `media/IMG_4813.JPG`, and `media/harbor-note.m4a`.
Here, `E-7F3A91` is the entry’s stable ID. The year in the path helps browsing, but the ID is the key that connects the record and attachments. The camera’s original names remain intact. The directory and index say what the files mean without requiring you to infer it from a filename such as `rainyday-final2.jpg`.
A readable `index.md` might look like this:
The entry index records ID `E-7F3A91`, date and time `2026-09-14 18:42`, and `America/New_York` with its UTC offset.
The index contains the original diary text and references to both JPEG photos and the original audio export.
The optional partial transcript marks the word “ferry” as uncertain and points back to the audio file.
The text is deliberately readable without special software. Markdown is one possible choice, not a requirement: plain text or another documented, accessible format can work. If you select a different format, keep the filenames and links to attachments explicit and make sure the index itself can be opened outside the diary app.
Why keep original media separate from captions and previews?
A caption or transcript helps you recognize and search an attachment; it does not replace the attachment. Keep the original photo and audio export as files in the archive, and treat thumbnails, compressed previews, edited copies, and generated transcripts as separate derivatives. If a derivative is useful, name it as such and note which original it came from. Never silently point an index entry at a preview when the original is missing.
File types also carry different kinds of information. The National Archives describes audio in terms that include sampling frequency, bit depth, and whether the recording is mono or stereo; its page discusses WAV and MP3 in the context of NARA products. Those format details explain why the audio export needs its own file description; the page does not establish a universal best format for personal diaries ([National Archives, *Digital File Types*](https://www.archives.gov/preservation/products/definitions/filetypes)). Preserve the files you exported, record their roles, and avoid assuming that a smaller preview contains everything in the original.
Add a manifest that connects each file to its entry
A manifest is a compact inventory, separate from the prose index. CSV is one readable option; a spreadsheet or another plain, documented format can serve the same purpose. Keep one row per attachment, repeat the entry ID on each row, and use paths relative to the entry folder so the references remain understandable when the whole folder is moved.
A readable `manifest.csv` can use columns `entry_id`, `entry_datetime`, `local_time_zone`, `relative_path`, `media_type`, `role`, and `caption_or_note`.
One row connects `E-7F3A91` to `media/IMG_4812.JPG` as an original image, and a second row connects the same entry ID to `media/harbor-note.m4a` as original audio. Both rows repeat the dated entry context.
If a transcript is added, give it a separate derivative row linked to the original audio. An uncertain word remains marked as uncertain in the note.
Each row should point to one file that currently exists, and each file should have one clear role. A manifest can also record an optional caption or transcript note, but mark uncertain wording as uncertain. Avoid using a thumbnail path as if it were the original photo. If you later add a crop or compressed version, list it on a separate row, identify it as a derivative, and state which original it relates to. The entry ID stays fixed even if an attachment is renamed; update both the index and manifest together.
How to export and build the record
**Choose the entry and its attachments.** In the diary app, identify the text, photos, and voice notes that belong to this one entry. Export or save the selected media as files. The National Archives brochure recommends exporting selected audio and photo files and using descriptive names; keep the app’s original filenames when they already help identify the file.
**Create the entry ID and folder.** Use a unique, stable ID and make one folder for the entry. Do not make the filename itself the only link between a file and the entry.
**Copy the original media exports.** Put the exported photo and audio files into `media/`. Keep previews and edited derivatives distinct. If the app offers several versions, label which version you saved rather than implying an export is an untouched capture.
**Write the readable index.** Include the full date and time, local time zone, the entry text, and one attachment reference and description per file. If the export process changes file metadata, preserve relevant dates in the index rather than relying solely on the file’s modified time.
**Make the manifest agree with the folder.** List each attachment using its exact relative path, the stable entry ID, media type, and role. Check names character for character; a path that differs by extension or capitalization can point to the wrong file or no file at all.
**Keep a brief archive note if needed.** If the folder structure is not obvious, write a short note at the archive root explaining it. The National Archives brochure recommends a brief structure summary and periodic checks that saved files remain readable; its advice supports a useful maintenance habit, not a promise of permanent access ([brochure](https://www.archives.gov/files/preservation/formats/pdf/preserving-your-digital-memories.pdf)).
Test one entry after export
Test the exported folder as a self-contained record, not through the original diary app:
Copy the entry folder to a different location, such as a separate drive or a temporary test folder. Work from that copy so you can see whether the export itself is complete.
Open `index.md` and confirm that the entry text, date, time zone, captions, and any transcript uncertainty are visible and understandable.
Follow every path in the index and manifest. Open each image and play each audio file with software that supports its format. Confirm that the file is the expected item, rather than assuming a successful filename match means the contents are right.
Compare the manifest against the folder: every listed attachment should exist, and every attachment you intend to keep should have a manifest row and an explanation in the index.
If you made a transcript, listen to the referenced audio and correct clear transcription mistakes. Keep genuinely uncertain words marked as uncertain instead of turning a guess into a fact.
This is a practical spot check, not proof that a file will remain readable indefinitely. Repeating the check occasionally can reveal missing paths or files that no longer open while the original context is still familiar.
What to do if a file is missing or renamed
If a manifest path does not resolve, mark the attachment as missing or unresolved in the index and manifest. Preserve the expected filename and add what you know, such as “not present in this export” or “original sought; preview found.” Do not replace the missing file’s path with a visually similar thumbnail or an audio excerpt without labeling it as a preview or derivative. A transparent gap is more useful than a false match.
When you intentionally rename or move a file, update every reference in the index and manifest in the same maintenance pass. Keep the entry ID unchanged, and, if the former name helps explain an older reference, record it in a note such as “renamed from `IMG_4812.JPG`.” Then repeat the copy-and-open check. If you cannot tell whether a file belongs to this diary entry, leave the relationship unresolved until you can verify it; do not assign it based on proximity or a suggestive filename alone.
A simple rule for keeping the entry coherent
Treat the entry ID as the anchor, the readable index as the explanation, the manifest as the attachment map, and the original exported media as the things being described. Keep their references together, preserve the date and local time context, and test the entry from its exported folder. That structure makes a mixed-media diary entry easier to understand when the original app is no longer part of the workflow, while leaving file-format choices open to the needs of the person keeping it.