How does jrnl store journal entries, and are they future-proof?

jrnl stores your journal entries as plain-text files, which is the main reason it can credibly claim to be future-proof. Because the format is plain text rather than a proprietary database, the files remain readable without jrnl itself and can be opened, searched, backed up, or moved with ordinary tools. The one important exception is encryption: if you encrypt a journal, readability depends on having the password, and losing it means losing access to the contents.

What "plain-text files" means in practice

When you write an entry, jrnl saves it to a text file on your own machine. There is no hidden binary format and no vendor-controlled cloud store required to read it. That has a few practical consequences:

• You can open entries in any text editor. If jrnl ever stops being maintained or you move to another operating system, the content is still there.
• You can search and process entries with standard tools. Command-line utilities, scripts, or a text editor's search function all work on the files directly.
• You can back up or migrate by copying files. Moving your journal to another machine is a file copy, not an export/import procedure.

This is the sense in which the format is "future-proof": the data does not depend on a specific application continuing to exist. The site's own framing is that plain-text journals "will still be readable in 50 years," in contrast to proprietary apps that may disappear.

Multiple journals, still just files

jrnl supports keeping several journals for different parts of your life — for example, one for work and one for personal notes. Each of these is still stored as plain text, so having more journals does not change the underlying storage model. You get separation of content without giving up portability.

Encryption changes the picture

jrnl can encrypt journals using AES encryption. This is a deliberate trade-off:

The site is explicit that with encryption, "nobody will be able to read your dirty secrets—not even you, if you lose your password." So encryption strengthens privacy but weakens the pure future-proofing argument: the file survives, but its contents are inaccessible without the key. If long-term readability without any secret is your priority, keep the journal unencrypted; if confidentiality matters more, encrypt and treat the password as something you must not lose.

Syncing and accessing entries anywhere

Because entries are just files, you can sync them with other tools such as Dropbox to capture thoughts from different devices. This works precisely because jrnl is not locking your data into its own service — the sync layer is separate from the journal format. The same property that makes the files portable also makes them easy to sync and back up with whatever file-sync tool you already use.

What to check before relying on it

• Confirm where your journal file lives so you know what to back up or sync.
• Decide on encryption up front, since it determines whether you need a password to read the files later.
• Test readability yourself: open the journal file in a plain text editor to verify the content is stored as readable text.

jrnl is free and open source, so the storage behavior described here is not tied to a paid tier or a hosted account — the files are yours, in a format you can read without the app.