Past journalers5 min read

How to export your Day One journal (step by step)

Day One exports in three formats and only two of them are useful outside Day One. Here is which to pick, how to get it, and what survives the move.

Day One is a good app. People who leave it rarely leave because it is bad — they leave because they want their writing somewhere it gets read back, or because the plan they are on stopped being worth it, or because they simply want their decade of entries in a format that is not locked to one company.

Whatever the reason, the first question is the same: how do you actually get everything out?

The short version

Day One exports in three formats: PDF, JSON, and Plain Text / Markdown. If you are moving to another app, you almost certainly want Plain Text / Markdown. If you want something a human can read and keep, you want PDF. JSON is only useful for going back into Day One.

The export lives in Day One's settings under the journal you want to export. On iOS, iPadOS, macOS and Android you can export in all three formats. On the web app and the Windows app, JSON is the only bulk option — which is worth knowing before you sit down at the wrong device.

Which format to choose

Plain Text / Markdown — the one to pick

This is the right answer for almost everyone leaving Day One.

You get a zip file containing a single text file with all of your selected entries in it, one after another, each with its date. On iOS and macOS the Markdown syntax is preserved, so bold stays **bold**, headings stay # headings, and quotes stay > quotes.

That single-file structure sounds crude and is actually the most portable thing Day One produces. A plain text file with dated entries can be read by anything — another journal app, a text editor, a script you write yourself, or a tool that splits it back into separate entries. Nothing about it expires or depends on a vendor.

PDF — for reading, not for moving

PDF exports include your formatted text and your photos inline, which makes them genuinely nice to keep or print. A PDF of your 2019 is a real object in a way a text file is not.

What a PDF is bad at is being data. Dates are visual rather than structured, entries run together, and anything that imports it has to read the layout to work out where one entry ends and the next begins. Some apps do this well. Treat it as a second copy rather than your migration path.

JSON — only for going back to Day One

Day One's JSON export is the complete, lossless version: entries, metadata, media references, the lot. It is also a Day One-specific format, which means it can be read by Day One and by the small number of tools written specifically to parse it.

The official documentation is clear that JSON is best for re-importing archived data to Day One. If you are migrating away, this is the format that looks the most thorough and helps you the least. Export it anyway as an archive — just do not expect another app to open it.

For the full official walkthrough, Day One publishes its own export guide, which is worth reading before you start.

Doing it

  1. Open Day One and go to Settings, then the journal you want to export. Day One exports one journal at a time, so if you have split your writing across several, you will do this more than once.
  2. Choose Export and pick your format. Take Plain Text / Markdown first.
  3. Optionally include media. Photos make the export much larger and are not useful if your destination is text-only.
  4. Wait. A long archive takes a while, and the app will tell you when the file is ready.
  5. Save the zip somewhere you will find it again, and unzip it. Many import tools will not read a zip directly.

Do this for every journal, and do it before you cancel any subscription. Export is not usually gated behind a plan, but being locked out mid-migration is a bad afternoon.

What survives, and what does not

Be realistic about this before you move, because disappointment here is almost always a surprise rather than a loss.

  • Your text survives. Every time. It is the part that matters and it is the part that is portable.
  • Dates survive in all three formats, though in PDF they survive as something a human reads rather than something a program parses.
  • Markdown formatting survives in the Plain Text / Markdown export on Apple platforms.
  • Photos and audio do not travel well unless you are moving to another media-first app. In a text export they become filenames at best.
  • Tags, locations, and weather usually do not survive a move to a different app's data model, because the destination has nowhere to put them.

If the metadata matters to you more than the writing does, that is a genuine argument for staying where you are.

Then what?

Here is the part nobody tells you: exporting is the easy half. Most people who successfully export their journal end up with a zip file in their downloads folder that they never open again. The archive moves from one place it is not read to another place it is not read.

The useful question is not "how do I get my entries out" but "what will actually read them once they are out". A decade of writing is only an asset if something goes back through it.

That is the specific thing Ember is built to do. You can bring an old journal in from a Day One plain text or PDF export — Ember splits the file back into separate entries on the dates it finds, and then reads across the whole archive to surface the themes that keep returning, the ones you never named while you were writing them. If you want to see what that looks like before moving anything, the patterns page walks through it.

And if you are still deciding whether to move at all, we wrote an honest comparison of the ways people journal, including where Day One is genuinely the better choice. It has end-to-end encryption on every tier, which Ember does not, and for some people that settles the question on its own.

One last thing

Export your journal even if you are not going anywhere.

Having a plain text copy of your own writing, sitting in a folder you control, is just good practice. Apps change their pricing, get acquired, or quietly stop being maintained. A text file outlasts all of that, and it costs you ten minutes once a year.

A journal that reads itself back

Ember reads across everything you write and surfaces what keeps returning. Bring an old archive with you, or start tonight.

Keep reading

  • Past journalers

    What to do with 10 years of journal entries

    A long archive is either an asset or a folder you never open, and the difference is what you do next. Four honest options for a decade of writing.

    5 min read
  • Past journalers

    The best way to read back your old journals

    Rereading your own writing is harder than it sounds, and mostly for reasons nobody warns you about. A practical method, and what to do about the cringe.

    5 min read