Task Format Converter

About this tool

The Task Format Converter turns one task list into another common task-list format: todo.txt, Markdown checklists, JSON, or CSV. It parses each task into a shared model before writing the target format, so completion state, priority, +projects, @contexts, creation dates, due dates, completion dates, and extra key:value metadata survive the conversion.

Use it when you are moving tasks between a plain-text todo.txt workflow, a README or issue checklist, a spreadsheet, and a scriptable JSON pipeline. Set the input format explicitly for strict conversions, or choose Auto-detect to sniff JSON arrays/objects, Markdown checklist items, CSV header rows, and otherwise fall back to todo.txt.

Worked example

Input todo.txt:

(A) 2026-08-01 Draft release notes +work @desk due:2026-08-05

Converted to Markdown checklist:

- [ ] (A) Draft release notes +work @desk due:2026-08-05 created:2026-08-01

The task text stays readable, and todo.txt's native creation date is preserved as a created: metadata tag because Markdown checklists do not have a built-in creation-date field.

Limits and edge cases

• Markdown output uses created: and completed: metadata tags for dates that Markdown checkboxes cannot represent natively.
• CSV uses a fixed header: text,done,priority,projects,contexts,created,due,completed,tags.
• todo.txt priorities are uppercase single letters such as (A).
• Auto-detect is intentionally simple; choose the source format explicitly if a list could be interpreted more than one way.

FAQ