Comparison

Ember vs Journey

Journey has been around a long time and runs almost everywhere, with unusually good export options for an app in this category. It is a solid, conventional journal. Ember is narrower and is built around one thing Journey does not attempt.

Journey's pricing and features checked in October 2026. These move — if you are reading this much later, verify before relying on it.

Side by side

Where each one lands

 EmberJourney
Core ideaReads across your entries and surfaces what recursStores, syncs and presents entries across many platforms
PlatformsWeb and iOSiOS, Android, web, desktop, Chrome OS
Export formatsFull export any timePDF, DOCX, ePub, plain text and ZIP
EncryptionEncrypted at rest, server-side. Not end-to-end.Encryption available; not end-to-end by default
MediaText-firstPhotos, video and audio supported
Be honest

Who should not switch

Real reasons to stay with Journey. If one of these is you, the rest of this page does not matter.

  • You want the same journal on Android, Windows and Chrome OS as well as Apple devices.
  • You want to turn a journal into an ebook or a Word document — the ePub and DOCX exports are genuinely useful and Ember has no equivalent.
  • Your entries lean heavily on media.

And who Ember suits

  • You already have a long Journey archive you have never read back.
  • You want recurring themes found for you rather than maintained by hand.
Moving

Switching from Journey

What to export, and what Ember does with it.

  1. 1In Journey, export as PDF or plain text. Ember does not read the DOCX or ePub exports.
  2. 2Unzip if you exported an archive.
  3. 3Import into Ember. Dates in the text are detected and each one starts a new entry.
  4. 4Review the staged entries, fix any dates that were inferred wrongly, then commit.

More on importing an existing archive

Questions

Before you move anything

Does Ember read Journey's DOCX or ePub export?
No. Use PDF or plain text, both of which import cleanly. DOCX and ePub are presentation formats and Ember does not parse them.
Can I keep using both?
Yes, and some people do for a while — writing in one and importing periodically into the other. It is more friction than it sounds, but nothing stops you.

Try it against your own archive

The only useful test is what Ember says about your writing rather than someone else's. Import what you have and see whether the themes it finds are ones you recognise.

Free to start.