August 6, 2026
A Dynalist alternative for people who still want an outliner
Dynalist still has a lot going for it. It is quick, it respects a keyboard, and it gives you a proper nested outline instead of turning every thought into a document. If that is the whole job, there is no emergency. Your outline can stay where it is.
The reason to look around is its future. Dynalist’s own major-feature changelog ends in June 2020. The app still works, and its help center and community are still online, but the product is now a settled tool rather than one that is adding new ideas. That can feel reassuring. It can also make a long-term home feel small.
For most people leaving Dynalist, the best replacement keeps the part of Dynalist they used every day: a fast tree they can shape while they think. listlis is the fit when that is what you want. Obsidian is the better choice when local Markdown files and a plugin ecosystem are the point. Workflowy remains a fair choice when its exact bullet-first model is the thing you miss.
Dynalist still fits a specific workflow
Dynalist has aged better than a lot of productivity software because the central idea was already simple. Open a document, make a line, nest it, zoom in, and keep going. It supports dates, search, sharing, notes, and export without asking you to learn a database or build a system around the outline.
That is enough for many people. If your lists are stable, the app is reliable for you, and you do not miss anything, staying put is sensible. A migration creates work. It should buy something real.
The case for moving starts when the outline has become a place where your work keeps growing, but the app around it has stopped growing with you. Maybe you want tasks and notes to live in the same visible structure. Maybe you want a current keyboard-first app with active development. Maybe you want to connect your outline to the assistant you already use. Those are reasons to evaluate a new home. Mere restlessness is not.
The useful alternatives to Dynalist
There are four common directions, and each has a clear trade.
| If you need | Best fit | The trade |
|---|---|---|
| A simple, actively built outliner for notes and tasks | listlis | It is younger than Dynalist and has a smaller ecosystem |
| Local Markdown files, plugins, and linked notes | Obsidian | It is a knowledge base first, not a pure outliner |
| The closest cloud-based bullet-list feel | Workflowy | Its free plan caps new bullets each month |
| Fields, queries, and structured records | Tana | You pay in setup time and complexity |
Obsidian is the right move if you are really leaving for local files. Its folder-and-plugin model gives you ownership and room to customize, but outlining is one tool among many. The app can become a whole workshop. That is great for people who want a workshop. It is extra surface area if all you wanted was a cleaner list.
Workflowy is the natural home for someone who wants the familiar interface and little else. It remains very good at the thing Dynalist does. The question is whether that is enough of a change to justify moving, especially if the monthly free-plan limit was part of what made you look for an alternative in the first place. The Workflowy alternatives guide gets into that choice in more detail, and the Workflowy vs Logseq comparison covers the more involved PKM direction.
Tana earns its place for people who want an outline to become a structured database. Supertags, fields, and queries can model a great deal. They also make every new idea ask for more decisions. If your outlines are mostly projects, notes, tasks, and half-formed thoughts, a field schema can turn a fast capture tool into paperwork.
listlis keeps the tree at the center
listlis starts from the same instinct that made Dynalist stick: the outline is the interface. There is one tree. A node has a title and, when it needs more room, an optional Markdown body. Tasks, notes, and ideas do not have to go into separate products just because they have different names.
The working rhythm stays close to an outliner. From a focused row, o adds a sibling below it. Tab nests the row under the line above; Shift-Tab brings it back out. ! turns a line into a todo, and c completes it. Completion carries through the subtree, so finishing the last child closes the parent too. Moving a branch stays a structural action, not a drag-and-drop exercise.
That makes a weekly plan feel straightforward. A root called “This week” can hold a project, its next action, the meeting notes underneath it, and the small tasks that emerged from the meeting. Press Shift-Enter when one line needs a Markdown body. Press / when you need to find something later. The outline remains legible because the title stays the surface and the detail stays behind it.
listlis also gives the tree a few places to go without turning it into an all-purpose workspace. A node can become a read-only shared link. A subtree can be co-edited. A connected assistant can read and write the outline through MCP, so the structure is available to the tools you already use instead of trapped behind a separate chat panel. Those additions matter when you need them. The main screen is still an outline.
Moving can stay low-risk
A careful move begins with an export instead of a dramatic cutover. Dynalist can export outlines as OPML, HTML, or plain text. listlis accepts OPML and Markdown outlines, so a small branch is enough for a real trial. A current project can live in the new tree for a week while the older archive remains untouched.
That trial answers more than a feature checklist. You will find out whether your work wants a graph, a database, a stack of documents, or a tree. For a Dynalist user, the trial makes the preference felt quickly. The tree may be enough. It may simply need a product that still has somewhere to go.
If that sounds familiar, listlis is ready for one live project. The first few lines will tell you more than a migration plan. For the wider field, the outliner comparison hub keeps the honest cases for Dynalist, Workflowy, Logseq, Tana, and Roam in one place.