Plain Text Task Management: Why It Outlives Every App

Plain text task management is the practice of keeping your todos as lines in ordinary text files instead of inside an app's database. The files open in any editor ever made, search in milliseconds, version cleanly in Git, and survive every app shutdown, acquisition, and pricing change. The tradeoffs are real, and this page covers them honestly: no reminders, no sync magic, no shared boards.

This is the explainer behind our markdown task management guide. That page is the workflow; this one is the argument for the format itself, why people keep returning to text files after every app cycle, and where the format genuinely loses.

Why does plain text outlast every task app?

Plain text outlasts every task app because the format has no vendor. A text file is not a product; it is the substrate products are built on. ASCII text predates the web, markdown has kept its core syntax stable since 2004, and GitHub Flavored Markdown checkboxes have not changed since 2014. Nothing you write as plain text today needs a migration, ever.

App longevity looks worse. Wunderlist, once the most beloved todo app, was acquired by Microsoft in 2015 and shut down in May 2020; users got an export window and a migration nudge, not their workflow back. That is not a scandal, it is the standard lifecycle: apps get acquired, sunset, repriced, or rewritten, and each event lands on your data. A text file todo from 2005 opens in every editor shipped in 2026. The inverse guarantee, that any current app will still run in 2046, cannot be made for a single one of them.

What can a text file todo do that an app cannot?

A text file todo can be searched, diffed, scripted, and versioned with tools that are older, faster, and more reliable than any app's built-in features. The practical set:

• Search at scale. rg "\- \[ \]" ~/tasks lists every open task across every file in milliseconds, at 10 tasks or 100,000. No app search is that fast or that composable.
• Version control. git log on a tasks file is a complete audit trail of what was added, finished, and deleted, with dates. git diff answers "what changed this week?" for free.
• Scripting. A text file todo is an API. Count open items, archive finished ones, or roll unfinished tasks into tomorrow's file with a five-line script.

rg --count-matches '\- \[ \]' ~/tasks   # open tasks, everywhere
git log --oneline -- tasks/work.md       # full history of one file

None of this requires a plugin, an account, or an internet connection. The checkbox syntax that makes the lines render as tasks is a two-character convention, covered in our markdown checkbox syntax reference.

Is plain text really zero lock-in?

Yes, and it is the only format that earns the phrase. Zero lock-in means leaving costs nothing because there is nothing to export: the files are the data, already in the most portable form that exists. You switch tools by opening the same folder in a different editor.

Compare the alternatives, as of 2026. A Todoist export is a CSV that loses comments, recurrence rules, and project nesting unless you reassemble them by hand. A Notion export is a zip of markdown or HTML files that flattens database structure into static pages. Both are better than nothing, and both are admission tickets: proof that the data was never really yours while it lived there. The quarterly test for any tool is simple, export everything and open the result in a plain editor. If what comes out is not useful on its own, you are renting.

What are the honest tradeoffs of plain text productivity?

Plain text productivity costs you four things, and pretending otherwise is how the format gets oversold. You give up reminders, automatic sync, collaboration, and enforced structure.

• No reminders. A text file never pings you. Time-based commitments belong in a calendar; the text file holds everything else and gets reviewed at fixed times, morning and shutdown.
• No sync magic. Sync is a folder decision you make once: Git, iCloud Drive, Dropbox, or Syncthing. It works well, but you chose it, and the rare conflict is yours to resolve.
• No collaboration. Assignments, mentions, and shared boards need a data model. Two people with Git habits can share a task file; a team that coordinates through notifications cannot.
• No enforced structure. A typo in a due date is just text. The format trusts you completely, which is a feature until the day it is not.

For coordination-heavy work the verdict flips, and a database-backed task manager is the right call. The full decision matrix lives in the markdown task management guide.

How do you start a plain text system in 15 minutes?

Start with one inbox file, one sync choice, and one syntax convention. The setup:

1. Create inbox.md. Every new task goes here first, one checkbox line per task. Processing it into topical files is a weekly job, not a per-task job.
2. Standardize on GFM checkboxes. - [ ] for open, - [x] for done, no creative variants. The convention is what makes the cross-file searches work.
3. Pick one sync. Git if you want history, a synced folder if you want zero thought. Do not run both on the same files.
4. Schedule the portability test. Once a quarter, copy the folder to a different editor and confirm everything still reads and searches. It will, and the habit proves it.

That is the entire system. Everything else, tags, due dates, project files, is an addition you earn by needing it.

Where does capture fit in a plain text setup?

Capture is where plain text systems actually fail, and it has nothing to do with the format. Opening the right file and typing - [ ] while a thought is still warm is friction, and friction at the capture step is what quietly kills systems that were otherwise working. Storage was never the problem.

The fix that keeps the format pure is capturing by voice and letting the filing happen automatically. quik.md transcribes a spoken task, the AI organize step routes it into the right project with a next step written, and everything exports as plain markdown, so your files remain the source of truth. The workflow is covered in voice to markdown. quik is a PWA, the free plan covers a daily AI-organize cap with browser speech recognition, and Pro is $14.99 monthly or $69.99 yearly with a 7-day trial, or $99.99 once for lifetime. For where a capture layer sits among task apps generally, the pillar on AI task managers maps the category.

Pricing shown reflects plans at the time of writing. Check quik.md/pricing for current rates.

FAQ

What is plain text task management?

Plain text task management is the practice of keeping your todos as lines in ordinary text files, usually with markdown checkbox syntax, instead of inside an app's proprietary database. Every task is a line you can read with any editor, search with grep, version with Git, and move between tools without exporting anything.

Is plain text better than a task manager app?

It depends on what you optimize for. Plain text wins on longevity, portability, and searchability: files from 2005 still open, and migration is copying a folder. Apps win on reminders, sync, collaboration, and visual boards. Solo knowledge workers who value ownership usually prefer plain text; teams that coordinate through notifications need a real app.

How do I sync plain text tasks across devices?

Three common options: Git gives you sync plus full history and conflict resolution; iCloud Drive, Dropbox, or Syncthing sync a folder with zero setup; and some editors like Obsidian offer their own sync layer on top of plain files. None of them change the file format, so switching sync tools never touches your data.

Can a plain text todo file send reminders?

Not by itself. A text file has no notification layer, which is the format's most honest weakness. The usual workaround is to keep time-based commitments in a calendar and use the text file for everything else, reviewing the file at fixed times each day so nothing time-sensitive depends on the file pinging you.

What is the fastest way to get tasks into a text file?

Typing into an always-open inbox file is the baseline. Faster options are editor quick-capture shortcuts and voice capture: tools like quik.md transcribe a spoken task, file it into the right project with AI, and export plain markdown, so the text file stays the source of truth without the typing friction.

What should you read next?

• Markdown task management, the workflow guide this explainer supports.
• Markdown checkbox syntax, the two-character convention behind every text file todo.
• Voice to markdown, fixing the capture step without leaving plain text.
• AI task manager, where AI capture and routing fit next to files you own.

References

• todo.txt, Gina Trapani's plain-text task convention.
• GitHub Flavored Markdown spec, GitHub.
• Git documentation, the version control layer for text files.
• TaskPaper, Hog Bay Software.