Family memories · Practical parent tips

A baby journal backup checklist for photos and the stories beside them

A photograph of a tiny hand is lovely. The sentence explaining whose finger it held may be the part you most want to keep.

By The Cocoon Editorial Team · Updated 17 October 2026 · 10 min read

Little moments. A little more understanding.

The short answer

Export a small sample and open it outside the journal app. Check the photo or video, date, caption and any voice note. Keep an untouched backup in a place you control and review who can access it before sharing.

A practical next step

Make an archive you can understand later

A folder called “final-backup-new” is hard to trust six months later. This fictional archive shows how to keep an untouched export, a readable copy and a short explanation together. Download it to inspect ordinary files outside the app; it is not a new Cocoon restore format.

Read the diagram as text

Keep untouched exports, human-readable notes and a file inventory together. A checksum can show a byte change; it cannot prove a memory is complete.

The steps and worked examples are explained in full below.

The ZIP contains three invented example files, a README and a manifest. No family data or media is included.

journal-example-2026-10-17/
  README.txt
  manifest.csv
  originals/cocoon-backup-example.json
  readable/cocoon-readable-example.csv
  context/inspection-note.txt

What each example file can and cannot show
File	Purpose	Limit
originals/cocoon-backup-example.json	Untouched fictional structured export	One invented note; no photo or video; not a full account archive.
readable/cocoon-readable-example.csv	Human-readable copy of the fictional note	No time-zone column, attachments or faithful restore structure.
context/inspection-note.txt	What was inspected, by whom and what was not tested	An inspection note is evidence of the checks named, not proof of a successful restore.

Three files to check against the inventory

The complete example copy matches all three recorded checksums. In the other examples, leaving out the context note produces one missing file; editing the CSV produces one changed file.

What these checks do not establish: completeness, accuracy, safety, origin or successful restoration. If the inventory itself was changed, comparing against it cannot establish that the original was preserved.

Download the fictional archive ZIP Inspect the example inventory CSV

Inspect only. The ZIP is not a Cocoon import format. Keep a real export untouched and use an appropriate separate environment for any restore test.

Give the folder a job and a date

Use a stable name such as journal-example-2026-10-17. The date here is the export date, not a claim that every memory happened that day. Put the original export in an originals folder and keep it unchanged. Put a readable copy in readable, with an inspection note in context. These are organising suggestions you create yourself; Cocoon does not create this folder structure.

Write what the collection leaves out

The sample includes one invented written memory, a CSV version and an inspection note. It contains no photos, videos, real child information or full account data. In your own inventory, record omitted media and files you still need to find. An empty media list can mean none were included; it does not prove none existed in the original journal.

Understand the file inventory

The downloadable manifest lists the relative path, purpose, byte count and SHA-256 checksum for each of three files. A matching checksum tells you that file’s bytes match this inventory. It does not prove a date is correct, a backup contains every record, the author is trusted or an app can restore it. The inventory is generated for this teaching archive; Cocoon does not automatically supply it.

Inspect a copy without overwriting your journal

Unzip the teaching folder, read README.txt and open the CSV and context note in ordinary text or spreadsheet software. The JSON is a fictional Cocoon-format example; inspect it as text. Do not restore a demonstration into a family journal merely to see what it does. The ZIP itself is not importable as a Cocoon backup. A real restore check needs an appropriate separate environment and the original media you intend to verify.

Make a second copy, then check that copy

The Library of Congress recommends organising important photos, keeping descriptions or an inventory and storing copies in different places. Apply the same organisational idea to the files you choose to keep. A folder copied elsewhere still needs an opening check; two shortcuts to one cloud folder are not two independent copies. Keep real family archives private and avoid putting access secrets in the manifest.

Context and product references: Library of Congress: keeping personal digital photographs — Personal-archiving guidance; checked 17 October 2026. Supports descriptions, inventories and copies in separate places.

Try a worked example

One journal, three different exports

A CSV is a readable table, a PDF is a report, and a Cocoon JSON backup contains structured journal data with available media within export limits. These formats are not interchangeable.

CSV: a readable table

The fictional sample uses Cocoon’s Date, Time, Type and Detail columns. It contains one written memory. The time is a local label without an offset. It has no media and is not a generic restore template.

Date,Time,Type,Detail
2026-10-17,09:00,Note,Fictional memory: laughing at the yellow socks

Inspect the date, the words and which columns are absent. A spreadsheet opening successfully does not establish that another importer can recreate the record.

Download the fictional CSV

PDF: a report to read

Cocoon’s report PDF presents report information and logged events for reading or discussion. Check its date range, any missing records and the original entries behind a summary. It is not a package of original photo/video files or a restorable journal.

For an appointment, begin with the question you want to discuss and bring relevant records. See how checkup reports work.

JSON: structured journal backup

The fictional file has a format signature, version, export timestamp, child label, one note event and empty growth/media arrays. It is an inspection sample; it has no photos and is not your backup. Opening it as text does not restore it or test a media restore.

signature: "hearth.backup" (Cocoon’s historical format identifier)
version: 2
child: "Fictional example — not a real child"
events: 1 written memory
growth: []
media: []

A real backup can contain available photos and videos within the app’s size limits. Read omission warnings, keep affected originals separately and confirm the intended child before restoring.

Download the fictional JSON

Product formats checked against Cocoon’s source on 17 October 2026. The detailed scope, omissions and source links are below.

Decide what you expect a backup to preserve

List the parts of an entry that matter: the original photo, a video, a caption, the date of the memory, a voice recording or who wrote the note. A downloaded image without its caption may preserve only part of the story.

Choose a varied sample: one photograph with words, one video, a dated text entry and any other media type you use. Include an older entry as well as a recent one. This helps reveal whether the export covers the whole history or just what is currently on screen.

Do not assume that a visible thumbnail proves the original file is included. Open the media itself and check that it is usable.

Open the export outside the app

Item	A useful check
Photo	Opens at a usable size, not just as a thumbnail
Video or audio	Plays through with the expected sound
Date	Refers to the memory, not only the export day
Caption or note	Words are present and associated with the right media
Multiple children	You can tell whose entry it is
Archive	Extracts successfully and includes any described manifest or index

An app-specific backup may be designed for restoring into the same app. A readable export may be designed for browsing elsewhere. They serve different purposes; check which one you have and whether you need both.

If you test a restore, use the provider’s documented process and avoid overwriting the only copy of your current journal.

What Cocoon’s current export formats actually keep

These detailed format checks are Cocoon’s own product notes; the linked public guides explain the export workflows.

A CSV has Date, Time, Type and Detail columns. It is a readable account of selected records, using local date and time labels. It does not include a time-zone column, attached media or all the structured fields needed for a faithful restore. Do not feed it back through the generic importer and assume it recreates your journal. Product guide: CSV summaries.

A PDF report is for reading and discussion. It presents report information and logged events, rather than packaging original media or functioning as a journal backup. Product guide: PDF reports.

A Cocoon JSON backup contains a child’s logged events, growth records and available photo/video attachments within export limits. It is not a full account backup: milk inventory, sleep programs and preferences are outside its scope. The current media limits are 25 MiB per file and 150 MiB in total; unavailable or oversized media can be left out, and the export reports those omissions. Check the warning and keep affected originals separately. Product guide: backups and media limits.

The fictional JSON sample has one written memory and no media. It shows the structure without pretending to test a photo restore. Real backups contain family information. Keep them private and check the intended child before any restore.

Treat the exported copy as family information

A backup can include names, dates, locations in notes or media, and more than the particular photo you wanted to share. Review the contents before giving a copy to someone else. For a single memory, a selected file and caption may be more appropriate than the full archive.

Store the backup where you can find it and where access is intentional. An export in a shared downloads folder can be seen by people who do not have access to the journal app. Deleting a copy from one device does not remove copies you have already shared.

Write down the export date and source app next to the archive. Keep the original archive unchanged if you make a separate edited copy for family sharing.

Choose a backup routine you can maintain

A practical reminder is “export, open a sample, confirm where it is stored”. Repeat it when you make a significant change, such as moving apps or devices, and at an interval that fits how much new material you would mind losing.

Synchronising devices and keeping an independent export solve different problems. Check the app’s own documentation for what is backed up, what needs a connection and how account deletion affects access.

Cocoon’s private journal keeps written and recorded moments together. Read its privacy and export features and verify a small sample before relying on any new backup workflow.

Leave a short inspection note beside the archive

Record the export date, app, child or private identifier, file name, what you opened and any missing media. For example: “17 October: opened the JSON and found the expected written memory; no media in this demonstration file.” That is a check you performed, not a claim that everything is complete.

For your own archive, inspect a few old and new entries and the media you most care about. Keep the original unchanged and store edited or shareable copies separately. A proposed folder name such as journal-2026-10-17/originals is an organising suggestion; Cocoon does not automatically create that folder. The CSV row lab explains why a human-readable table and a restore file should remain distinct.

Sources and scope

Sources support the specific health, timekeeping or product context cited above; each has its own check date. The recording examples and templates are Cocoon’s own. External organisations are cited for context, not as endorsers. This article has not been independently clinically reviewed. Read our editorial standards and AI-assistance disclosure.

Cocoon: backups, exports and media limitsPublic product guide; detailed format checks by Cocoon · Checked 17 October 2026
Cocoon: CSV and PDF summariesPublic product guide; detailed format checks by Cocoon · Checked 17 October 2026
Cocoon: checkup reports and PDF summariesPublic product guide; detailed format checks by Cocoon · Checked 17 October 2026