The question sounds more dramatic than it needs to. Most people who keep a digital journal are not thinking about 20-year horizons — they are thinking about what to write today.
But consider the evidence. The journaling apps that were dominant five years ago are not all still operating in the same form. Evernote went through an acquisition and significant product changes. Day One changed hands. Google Inbox — not a journal, but a personal communication archive that many people relied on — was killed entirely. Services that once felt permanent turned out to be products with business models that stopped working.
For anyone who keeps a digital journal with the intention of being able to read it in 10 or 20 years — or to leave it for someone else — the format and storage decisions made today determine whether that intention succeeds.
The Three Failure Modes
Digital personal writing can become inaccessible in three distinct ways, and all three are more common than people expect.
Format Failure
Digital files are not inherently readable. A file in a proprietary format requires software that understands that format to open it. If the software that created the file stops being maintained — or if the company behind it shuts down, pivots, or changes file formats in a major update — older files may become unreadable.
This is not hypothetical. Microsoft Word files from the early 1990s, in the original .doc format, require either the original software or a compatible converter to open correctly in modern versions of Word. Files created in early versions of iWork are no longer supported by current versions of Pages. The landscape of “files we can no longer reliably open” grows constantly.
Journaling apps are not immune. Day One’s file format is proprietary. The app can export to JSON, which is technically readable, but not in a form a person would want to sit down and read in 15 years. Specialized journaling apps create files that are essentially useless without the original app or a dedicated export tool.
Service Failure
Many digital journals are not stored as files on a user’s device at all. They exist as data in a cloud service, accessible through an app but not directly accessible by the user. When that service changes, the journal changes with it.
Service failure takes several forms. The service shuts down entirely. The service is acquired by a company with different data practices. The service changes its business model and eliminates the feature set the journal depended on. The service decides to sunset the platform you use — the mobile app, the web interface, the API — while nominally keeping the service alive.
In each case, the journal entries that existed in the service are in a different position than files stored on a drive you own. You cannot take them with you until the service offers an export, and the export may not preserve everything.
Media Failure
Files stored on physical media — hard drives, USB drives, optical discs — can fail. Hard drives have a mean time between failures measured in years, not decades. Flash storage (USB drives, SSDs) is vulnerable to charge decay over long periods without power. Optical media (CDs, DVDs) can degrade. The drives that worked when a file was created may not be available or functional when you try to read it.
This is the oldest problem in digital archiving, and it is the easiest to address: multiple copies, stored on different media, in different locations.
The Format Decision
The most important decision for long-term journal preservation is what file format to use.
The general principle from digital preservation research is: the simpler the format, the more durable it is. Formats that require proprietary software, complex rendering, or external dependencies are formats that will eventually become inaccessible.
Plain Text (.txt)
Plain text is the most durable digital format available. A plain text file created in 1980 can be opened today by any text editor on any operating system. It has no dependencies — no software, no fonts, no rendering engines, no external assets. If the character encoding is UTF-8 (which handles text in any language, including Hindi and Mandarin), a plain text file is as close to permanently readable as any digital format gets.
The Library of Congress recommends UTF-8 plain text as a preservation format for textual records. Academic archives use it. The MIT Libraries digital preservation guide cites plain text as the format “far more likely to remain usable over the long term even if the software that created them is not available.”
The tradeoff is simplicity. Plain text has no formatting — no bold, no headings, no embedded images, no tables. For a journal, that is usually acceptable. Dates can be part of the file name or a structured header within the file. Images can be stored separately and referenced by filename.
Markdown (.md)
Markdown is plain text with lightweight formatting conventions: asterisks for bold, hashes for headings, dashes for lists. Markdown files are readable as plain text even without rendering, but render as formatted documents in a growing number of applications and editors. Many journaling apps support Markdown; many knowledge management tools (Obsidian, Logseq) use it as their native format.
Markdown is not as universally standard as plain text — there are several Markdown dialects — but the core syntax is stable, widely understood, and highly likely to remain readable indefinitely. It is a reasonable default for a digital journal that wants some formatting without proprietary dependencies.
PDF and PDF/A
PDF is a reliable format for documents you want to preserve in a specific visual form — the way a page looks, with fonts and layout intact. PDF/A is a variant of PDF designed specifically for archival purposes: it embeds fonts, prohibits external dependencies, and does not rely on features that might not be available in future software.
PDF and PDF/A are good formats for finalised journal entries that you do not expect to edit further. They preserve visual appearance across software changes. They are not ideal for ongoing journaling, because editing a PDF is awkward. A practical approach is to write in plain text or Markdown and export to PDF/A periodically for archival copies.
What to Avoid
Proprietary app formats: Day One’s native format, Notion’s internal structure, Evernote’s .enex files — these are all formats that depend on specific software to read properly. Use the app’s export function to convert to a more durable format.
Rich text and word processor formats: .doc, .docx, and .pages files are widely readable now but depend on specific software and have changed format significantly over the years. They are better than proprietary app formats but less durable than plain text.
Formats with external dependencies: HTML files that reference external stylesheets or scripts become broken when those dependencies disappear. A simple HTML file with all styling inline is more durable than one with complex external references.
The Vendor Lock-in Problem
Dedicated journaling apps create vendor lock-in by design. When you write in Day One, your journal lives in Day One. When you write in Notion, your notes live in Notion. Moving to a different app or service requires an export, and exports are never perfect.
The export problem is real and underappreciated:
- Incomplete exports: Many apps do not export everything. Metadata, tags, formatting, linked content, or embedded media may not survive the export process intact.
- One-time exports vs. ongoing archives: An export done now captures what exists now. Future entries are still in the app’s ecosystem. Staying on top of exports requires ongoing effort.
- Format degradation: Even when an export is complete, the output format may not preserve the structure and context that made the original entries useful.
The cleanest solution to vendor lock-in is to write in a format you own from the start — plain text or Markdown files in a folder structure you control. Then you can use any app to write (a plain text editor, Obsidian, iA Writer, Typora) and your journal is not dependent on any of them. The files exist regardless of the app.
The Storage Decision
Where you store journal files determines how they survive over time.
Local Plus Off-Site
The most resilient approach is local copies plus off-site copies. Journal files stored only on one device are lost if that device fails or is stolen. Files stored only in one cloud service are at risk if that service changes or is unavailable.
A simple setup:
- Journal files in a local folder on your computer
- Synced to a private cloud storage service
- Backed up to an external drive periodically
This gives you three copies: local, cloud, and physical backup. Losing any one of them does not mean losing your journal.
Private Cloud Storage vs. Journaling App Servers
The key distinction between storing journal files in private cloud storage versus keeping them in a journaling app’s servers is control.
Private cloud storage — storing files in a general-purpose file vault you control — means your journal files are yours. You can download them at any time. You can move them to a different service. You can view them with any text editor. You do not need the original app.
Journaling app servers hold your entries as data in their system. You can access that data through the app, and most apps offer export features, but the entries are not files you own in the same straightforward sense. They exist as records in a database the app company controls.
For long-term preservation and privacy, files you control are preferable to records in someone else’s system.
Encryption and Longevity
Encrypted files add a layer of complexity to long-term access. If you use file-level encryption and lose the key, the files are unrecoverable. This is an argument for using storage services with managed encryption (where the service handles encryption and decryption) rather than file-level encryption that you manage yourself, unless you have a reliable key management system.
Services that apply server-side encryption — like daftei’s AES-256 encryption at rest — protect your files from unauthorised access without requiring you to manage encryption keys yourself. Your files are encrypted on the server, but you access them normally through the app or web interface.
A Practical Migration Plan
If your journal currently lives in a dedicated app, the steps to a more durable setup are:
Step 1: Export Everything Now
Export your entire journal from the current app in the best format available. If the app offers plain text or Markdown export, choose that. If it only offers JSON, find a tool that converts the JSON to readable files. If the only export is PDF, accept it — it is better than nothing.
Do this now, not when the app starts to decline. The time to export is while the service is still fully operational and the export tools are working correctly.
Step 2: Convert to a Durable Format
If the export produced files in a format that requires specific software to read — JSON, ENEX, HTML with external dependencies — convert them to plain text or Markdown. A folder of dated text files is a journal. It is durable, portable, and requires no special software to read.
Step 3: Store in a Place You Control
Put the exported and converted files in a folder on your computer. Sync that folder to a private cloud storage service. Back up the folder to an external drive.
Going forward, write in a plain text or Markdown file in that folder, or use an app that writes to files in a folder you own rather than to a proprietary database.
Step 4: Repeat Annually
Set a reminder to repeat the export and conversion process once a year. This captures any entries from the past year in a durable format and keeps the archival copy up to date.
The Privacy Dimension
The practical overlap between long-term preservation and privacy is significant.
A journal stored as plain text files in a private storage vault that you control is both more durable and more private than a journal stored in a cloud journaling app. You do not need the app to read it. You do not need the company to still exist. You do not need to agree to updated terms of service to access your own writing.
Daftei stores files of any type — including plain text journal files, Markdown notes, exported PDF archives, and audio memos — with TLS 1.3 encryption in transit and AES-256 encryption at rest. The service does not sell data, does not run ads, and does not use stored content to train third-party AI. Free storage starts at 5 GB; Pro is unlimited at $5.99 per month, $44.99 per year, or $89.99 as a lifetime purchase. For users in India, Pro is available at ₹249 per month or ₹1,799 per year.
The journal you are writing today deserves to be readable by the person you become in 20 years. Format and storage decisions made now are the difference between a record that survives and one that does not.