Practical guide
Export a Day One Journal with Media: Check the JSON ZIP Before Moving
Choose the right journal and JSON/media export, then inspect what was actually saved. Compare entry scope, download warnings and attachments before importing or discarding the originals; “Export Complete” can still accompany missing media.
Write down what the archive needs to include
English Day One documentation checked 11 November 2026. Match the platform and controls to your app. Examples and check records are original fictional material; no private journal, app export, import or recovery was operated for this guide.
For re-importing a Day One archive, the official guide recommends its JSON export format. The ZIP contains a JSON file for the selected entries and can optionally include media in photos, videos, audios and pdfs folders. Media is a selection to check, not a consequence of seeing .zip in a filename.
Sources: [1].
Record the journal, intended entries and any date/tag selection before exporting. If you need the whole journal, check that a range, tag filter or selected-entry list has not narrowed it. Preserve the original journal and separate media while testing. Available media in Day One may already differ from a pre-import original photograph; an export does not undo earlier photo optimization.
Use the route and selection for the actual platform
| Platform | Starting route | Selection/media check |
|---|---|---|
| iOS/iPadOS | Settings → Import/Export | Choose journal, date range/tags and JSON; include the media needed |
| macOS | File → Export; or journal/entry context menu | For selected entries use List view; inspect selections and media options |
| Android | Settings → Export; or Settings → Journals and selected journal(s) | Turn off Optimize Local Media Storage as the guide directs; wait for media and keep completion warnings |
| Web/Windows | Journal → Edit Journal → Journal Settings → Export Journal | Whole journal or documented single-entry JSON; inspect Include media and download prompts |
On a narrow screen, scroll inside the table. Keyboard users can focus the region and use the arrow keys.
The Mac guide places multi-select and right-click export in List view; it does not provide the same date-range picker as iOS. Web/Windows supports whole-journal and single-entry JSON rather than an arbitrary date-range export. Use the current controls for your platform, rather than applying another platform’s selection steps.
Android’s single-entry sharing route supports text, not single-entry JSON or PDF export. For JSON, use its documented journal export route and verify the selected scope.
Save the output and keep download warnings
- Let the required media finish downloading. On Android, the current export guide asks you to turn Optimize Local Media Storage off and wait for sync/media downloading.
- Choose JSON and the required media option in the actual export controls. Keep the intended selection written down.
- Save the completed file to a location you can inspect. Android’s completion notification offers Save to device or Share; the guide says dismissing it without acting requires another export.
- Read the completion information for missing-media warnings. Record the saved filename and size. An empty ZIP is not usable archive evidence.
- Inspect a separate copy of the saved ZIP; retain the original archive and journal unchanged while comparing.
The current guide describes Android notifications reporting exported entries, included media and failed media downloads. Failed downloads can leave files missing from the export even though they remain in the source journal. Check connection, media-storage setting and completed downloading before retrying; keep the earlier result available for comparison.
Reconcile two entries and three expected attachments
Our original fictional log has two entries and three expected media files: A has a photo and an audio file; B has a PDF. The fictional copy contains the photo and PDF but lacks the audio. This is an inspection example, not a Day One export, vendor JSON schema or actual archive test.
| Entry | Original text ending | Expected media | Seen in fictional copy |
|---|---|---|---|
| A | Ask one question next time. | photos/bench.jpg; audios/voice-note.m4a | photos/bench.jpg |
| B | Write the decision before replying. | pdfs/list.pdf | pdfs/list.pdf |
On a narrow screen, scroll inside the table. Keyboard users can focus the region and use the arrow keys.
Download the fictional transfer log. The reconciliation is 3 expected − 2 observed = 1 missing. A count of two entries would not reveal the missing audio. Inspect the full text, including each ending, and the selected attachments; a total alone does not identify which file is absent.
Case 1
A fictional transfer has two expected entries and three expected attachments. Its saved copy has both text entries, one photo and one PDF. Is it ready to replace the originals?
Show answer and explanation for case 1
No. The audio attachment in entry A is still unaccounted for.
The two text records match the entry count, but the media count is only two of three. Find the download warning or missing-file cause and compare a later export with the original log. Do not fill the gap with a placeholder audio file and call it preserved.
Use the Day One JSON import and inspect the result
Day One’s importer is designed for Day One JSON exports. Its guide allows JSON imports on iOS, macOS, Android, Web and Windows; iOS and Android require the file in local storage, and macOS recommends Downloads. Web/Windows uses Settings → Import and a ZIP containing the exported Day One JSON data. The guide does not promise support for arbitrary third-party JSON files.
Sources: [2].
After an actual import, compare representative entries against the source: intended dates, complete text endings and each expected media attachment. Keep the originals until differences are understood. The documents do not establish a universal deduplication rule for repeated imports, so inspect what an earlier attempt created before rerunning the same archive.
Download the blank transfer check. It records the chosen scope, saved file, missing items and actual post-import comparison. No app import has been performed for this guide.
Stop on an empty file or unexplained missing media
The current export guide lists a known Web/Windows issue that can produce a 0-byte ZIP. It suggests trying another browser for the web app or exporting from the iOS/macOS app instead. Those are documented workarounds, not guarantees that your next file will be complete. Inspect the new result and preserve the earlier evidence.
Sources: [1].
Case 2
A fictional Web export downloads as 0 bytes. A second attempt produces a larger ZIP. Can the reader now assume all photos and entries were moved?
Show answer and explanation for case 2
No. The second file passes the empty-file check, but scope and contents still need inspection.
Compare the selected journal, entries, media options, warnings and expected files. A non-empty ZIP can still omit a requested attachment or contain only a narrower selection. Resume migration only after the actual archive and imported result account for what you intended to preserve.
Sources and further reading
- Day One Help: Exporting entriesEnglish official documentation checked 11 November 2026. Export formats, platform and entry-selection routes, media inclusion, download warnings, empty Web/Windows ZIP issue and iOS PDF table/formatting limitations.
- Day One Help: Importing Data from JSON filesEnglish official documentation checked 11 November 2026. Day One JSON archive scope and documented platform/local-storage import requirements; no third-party schema or repeated-import behavior inferred.
- Day One Help: Optimize Device StorageEnglish official documentation checked 11 November 2026. Local/cloud media distinction and platform-specific Download All Media/storage options; no deletion, cloud availability or backup guarantee.